SEPA Instant Payments also solves that.
SEPA Instant Payments also solves that.
in Latvia we need to do this for domestic payments anyway. We use IBAN even for domestic payments..
> and likely your legal name.
not mandatory. If provided, the bank tells you whether the recipient name matches the account, but if not, you can proceed with the payment anyway.
I, too, would prefer to just be able to give people a random number to send money to. Isn't that a GDPR requirement anyway: data minimisation? Can they legally require this beyond their 90% of the law (that is, custody of the thing I'm trying to move)?
Even more than now there is a QR code format for SEPA Instant Payments. Some invoice have a QR code and when it is scanned with a bank app, the fields for a bank transfer are prefilled. IBAN, amount, etc...
We just need an app to generate this QR code for the amount one wants to request.
The stupid problem here is that as EU was pushing SEPA countries themselves came up with the QR payload formats. And since it was first introduced and popular in more eastern europe countries... the western countries can't just follow the already popular codes but have to change the payload format for pointless reason (human readability). There is huge NIH syndrome with German/French/Netherlands tech.
So now you have one format that uses new lines as deliminator, other format uses : as deliminator and another that's not human readable at all and it's binary.
Of course all of them are using same SEPA and essentially just prefill the information into the bank app. I wouldn't be surprised if banks just gave up and parsed the data in all the formats, picking the most reasonable automatically.
I've never had to do any of this, and I quire frequently send SEPA payments from Latvia.