[sgjohnson]

> > A Frenchman using Wero will be able to transfer money to a Spanish friend on Bizum, with the same simplicity as a domestic payment.

SEPA Instant Payments also solves that.

[culhatsker]

Yes, the only difference is that you need to communicate your bank account number and likely your legal name.

[sc11]

Wero doesn't change that as it's just another interface for SEPA instant payments. In its current version, it just adds phone numbers as an alias. Via the phone number you can also find out their full name and, after a transaction, their account number, as long as they've enabled Wero for their account.

[sgjohnson]

> you need to communicate your bank account number

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.

[Aachen]

They made it mandatory in NL not long ago iirc, or at least the validation now is and the bank doesn't let me leave the field blank. It does seem to be okay with variants of the name

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)?

[kakacik]

which... isn't really a problem for legal transfers, is it

[Markoff]

not the case in Czechia, only thing you need is bank account number and bank code, nothing else

[drstewart]

Wero and Bizum are built on top of SEPA anyway

[hommelix]

> SEPA Instant Payments also solves that.

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.

[omnimus]

In countries where instant SEPA through QR codes are popular that "app to generate this QR code" is your bank app. All of them can do it.

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.

[dgan]

I doubt so, because i need to type god-knows-how-many characters by hand, while visually separating them into chunks by 4, then explicitly authorize the receiver. Oh, and explicitly authorise the country

[sgjohnson]

> then explicitly authorize the receiver. Oh, and explicitly authorise the country

I've never had to do any of this, and I quire frequently send SEPA payments from Latvia.

[dgan]

Well i am in France, and what I said is factually true for some banks; at least mine (LCL)

[cybrox]

While your complaint is valid, no need to separate in chunks, there's a checksum.