JoeriAce
- Edited
I am asking for a solution so that I can still sent a payment request to my recipient’s email and phone number, even though the recipient might have been a bunq premium user once upon a time. Now, the request seems to disapear into the void.
When you create a payment request (or want to sent money to a contact), the app automatically recognises fellow bunq users and the request is received via the bunq app of the recipient. This saves time.
However, I encounter issues if the recipient is a former bunq user. Now his email and mobile phone number are still bound to his bunq account. Either an account-without-subscription or a downgraded-to Travel account; both cannot accept my payment request.
I am asking for a solution so that I can still sent a payment request to my recipient’s email and phone number, even though the recipient might have been a bunq premium user once upon a time.
I am not sure if this would be helped by removing IBAN’s aliassen, but regardless, asking them to remove their aliassen is not really an option because from their perspective it “is not their problem”; they closed their account and see no point in or are reluctant to logging in again.
In the case of a former-premium-now-downgraded-to-travel-card subscription, aliases and recognition by my (premium) bunq app no longer serve a purpose, right?
Because the receiving user cannot approve a payment request, why am I even able to sent a payment request to a travel card user? Wouldn’t it make more sense for that request to be sent to their e-mail or mobile number instead of the app, being a dead-end-street in-app in their situation?
I used the share link option within payment request to get around it for now, but that is more work and only works with request to 1 person, not to a whole table where normally you would just enter people’s names and bunq takes care of it. (Split-function.)