Which is irrelevant for my point, what’s relevant for the comment chain is that a person can quickly make a direct transfer and the second person receives it instantly most of the time. The inner workings of the functionality are not relevant when talking about the use case.
You make it seem like I need to send a request email to the target bank, then wait until their certified postal mail reaches my bank, then my bank sends them money. This is a hyperbole, what I mean is that you make it seem way more cumbersome than it is for the end user.
I agree that it’s important from a security standpoint, but it’s not relevant from a usability standpoint.
They originally said:
In the US you really could not send money from one Person to another?
And you answered:
It’s actually the same in Europe. You can only authorize someone else to take money out of your account.
You are describing how the process works internally to someone in a chain that describes usability from the end user. In Europe we can send money, we tell the bank which amount and where, and then they use their incredibly shitty security methods to perform the transaction. That’s agnostic to me from an usability standpoint. That’s why I said that you were not saying relevant information.
I go to my phone app, make a transfer, put the IBAN of the one I want to send money, put amount, bank tells me if it takes a day or is immediate, go.
The other person recieves money, lately most banks have it instantly, so they get it instantly.
Is it really that important what the banks are doing internally if I’m the one initiating the action and they get the money?
I even have my usual contacts in the bank’s app, so most of the time sending the money is super simple.
I’m familiar with the UI. Its pull-based in the back end. Source: I worked for a bank
Which is irrelevant for my point, what’s relevant for the comment chain is that a person can quickly make a direct transfer and the second person receives it instantly most of the time. The inner workings of the functionality are not relevant when talking about the use case.
You make it seem like I need to send a request email to the target bank, then wait until their certified postal mail reaches my bank, then my bank sends them money. This is a hyperbole, what I mean is that you make it seem way more cumbersome than it is for the end user.
It’s absolutely important. Because pull based transactions are less secure.
I agree that it’s important from a security standpoint, but it’s not relevant from a usability standpoint.
They originally said:
And you answered:
You are describing how the process works internally to someone in a chain that describes usability from the end user. In Europe we can send money, we tell the bank which amount and where, and then they use their incredibly shitty security methods to perform the transaction. That’s agnostic to me from an usability standpoint. That’s why I said that you were not saying relevant information.