• Refunding unknown card transaction blocks card aswell | Workaround: Freeze card

Trying to get a refund on an unknown card transaction, the wizard always lead me to a screen with only one option: To block the card entirely and irreversibly.
That is not what I wanted. Yes, I was considering that option, but first and foremost I wanted to initiate the refund.
Currently, it is enough to change the CVC and I wanted to have control over which actions I take.

Luckily, I found a workaround. If I freeze the card and initiate the refund then, it doesn't ask me to block the card and lets me proceed with the refund request.

Even though I get a strong suggestion to block the card, it should not be the only option, especially if the refund request hasn't even been created yet. And other options like temporarily freezing the card, changing the CVC, etc. should be made available.
Blocking the refund request entirely, until you block the card first, is really annoying and hinders the process. It can even be confusing.

    @SimJoSt#257628 Hi Joda! Thank you for all your bug reports today! It shows you like to improve things, and I can only encourage that 🙌

    However, as I've commented on your posts earlier today, Together isn't the place to report bugs. You can share suggestions and ideas here and ask questions to the community, but you'll mainly find other users here. Since bugs can't be solved by other bunq users but need to be fixed by bunq developers, I would again kindly request you to report those to bunq support. They are the ones who can properly assign the bugs to the right developers. And please don't post any new bug reports here on Together to keep things clean and organized. Thanks for understanding, and again thank you for your contributions!

      @thijsoost#257636 hey Thijs, thanks for your reply.
      Generally, I understand what you mean. But why is there a bug section, that the users can post to, if it is not being used and read by the developers.
      Like you said, I would like to improve things and had a lot of issues to share today. If I would do that through the support, it would take a long time, since I cannot create multiple support conversation, they get closed very fast, and I never receive any update on them when they are closed. That's why I decided to use the community, so more people know about them and they can get some traction. It's also great, so bugs don't get reported multiple times :)

      I work in the tech space as a very technical project manager and are writing a lot of bug reports internally, processing them from clients as well as providing a lot of them to software we are using in our business. A good flow for that is important. With bunq, it has always been a hassle to do it properly, in the right place and understandable by other people and further along the line.
      I even considered applying for a position at bunq, to change that and improve the process :)

      Just a little write-up to let you know where I am coming from.
      If you show me a better way, I will adhere to it.

        @SimJoSt#257673 I see what you mean! The "bug" tag is actually something from the past, I believe. Users used to be able to post their bugs in the community, but as far as I know it became difficult to keep an overview. Therefore, the advice now is to send bugs directly to bunq support, to make sure it is taken care of by the right person(s). Perhaps this is not very clear and this tag should disappear as an option.

        As for reporting multiple bugs at once: the support function is not prepared for that. What I could think of is making one Word/PDF file in which you describe all the bugs, and then send it to bunq. Or sharing a cloud folder in which you put several documents containing the bugs. Something like that, maybe? As much as I appreciate your efforts - I recognise many of the bugs you report! - sending it in the community is probably a waste of effort because the chances of it being addressed are very small.

        In short: there is currently no perfect solution for submitting multiple bugs all at once. But that does not mean that with some creativity, other ways can be found! Again: your efforts are greatly appreciated! But I'm afraid it won't work out this way, so we have to think of something else...

        (And if one of the bunq employees or my fellow moderators have other suggestions, please let us know!)

          a year later

          Thank you, @thijsoost, for the reply. I'll keep that in mind and will use the support more for bug reports. In my experience, when I notified them of bugs, they didn't really get resolved, and I was asked to post on here.
          As it's not possible to have multiple open support ticket, maybe this makes it a bit easier to structure them.

            Write a Reply...