I have just tested this once again with my friends account while he was here. Did everything from scratch.. I invited him to a sub account of mine and tried to make a purchase online with a card of his that was attached to the shard sub account. The 3ds event was sent to me, the owner of the sub account, with no way to confirm it (Error, only the cardholder can authorize this transaction.). While on his phone no event came up. So we were unable to complete the transaction.

@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.

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.

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

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

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?