I think I found a bug with the 3-D Secure approval of a transaction. My partner owns an account, he has given access to me. I have a card, which is linked to this account, which works fine.
However, yesterday I wanted to pay online with this card linked that account and therefore I had to approve the 3-D Secure authentication. The problem is, I received a push notification, but didn't see the awating event in the app. Maybe because it is not my account. My partner didn't get a push notification, but had the event in the app. However, he was not allowed to accept it, because this is only allowed for the card owner. Indeed he was also not allowed to cancel it.
So it was not possible for us to accept the 3-D Secure approval and hat do cancel the payment an make it againt with a card and an account, which both are owned by the same persond. This worked fine. However, this is not the way it was intended to work and my partner still has the awaiting event from the first payment in his app, he is not allowed to accept or cancel.

    I have the same issue. In the title it says it has been fixed. I just tested it, but the 3ds authentication request still gets send to the account owner instead of the card owner. Do we need to wait for an update of the app?

      Updated to Bunq 16 and the issue still persists for me. Please reply

        Hello bunqers 👋

        Thanks for reporting this bug to us! Please note we have escalated this to our developers team, and we will let you know once it's fixed 🙌

        For now I wish you a great weekend ahead 🌈

          A small side note: The awaiting event for the card payment, which cannot be approved or cancelled, is still present. Any tips, how to remove it?

            6 days later
            Dominik changed the title to [REPORTED] Android: Bug with 3-D Secure Approval.
              a month later

              Any update on this? I have reported this in app since 6 January and still waiting for a fix.

                @Erik-Pink-Jaguar#218188 Hi Erik 👋

                I see that we are still working towards solving this. To ensure that the fix for this bug works correctly, thus also to prevent that we create new bugs while fixing this one, our developers need to thoroughly test this scenario to ensure that everything works smoothly. This requires some time, but it's necessary to offer you the best bunq experience.

                We will make sure to send you a message as soon as we release a fix, and of course we'll do our best to fix this as soon as possible!

                Both your understanding and patience are much appreciated 🙏

                  a month later

                  Any update about this issue? It is taking too long. I am using and paying for BUNQ for this specific function and I have been waiting since January for a fix. Even worse is that customer support just sent this "update" (see attachment) to me. After more than 3 months you guys come up with this message? Outrageous. It is clearly a bug, since the request is not sent to the owner of the card, but only to the owner of the shared sub account. So how can the owner of the card accept the payment request?

                  Please confirm that you are still working on this issue and a have a deadline on when it should be fixed. Or I will be taking my business and personal accounts somewhere else.

                    @Erik-Pink-Jaguar#220346 Hello Erik 👋

                    I checked and can confirm that after extensive investigation we’ve noticed this is indeed not a bug but more of a fault in the app. I will make a suggestion that we change how this works, so you don't need to ask the card holder to take action for the payment instead of you. However, I cannot provide you with confirmation if and when this change will be implemented. I can keep you updated in this post and add the tag "Ideas".

                    Your understanding on the matter would be much appreciated 🙏

                      9 days later

                      @Nikoleta#220381 I do not understand how it isn't classified as a bug?

                      You say "I will make a suggestion that we change how this works, so you don't need to ask the card holder to take action for the payment instead of you."

                      If the card holder could confirm the transaction I would already be happy. The actual problem is that not even the card holder can confirm the payment.

                      When someone other than the owner of the shared sub account wants to make a payment with their own card that is linked to the shared sub account the transaction cannot be processed.

                      • The owner of the sub account gets the 3ds request, that he is not able to confirm because he is not the card owner.
                      • The card owner does not get a 3ds request at all.

                      In the end the transaction cannot be completed in any way.