Strong authentication, two-factor and checking identity in support
Two-factor is the everyday name for asking for two proofs to log in.
Strong customer authentication is the legal definition, with independent categories and, for remote payments, a link to the amount and the payee. And it is not what support does when checking who is writing. The customer does it in the app.
Why it matters
In a fintech, strong customer authentication decides who bears a fraud.
If the provider does not require it, the customer is only liable for an unauthorised transaction if they acted fraudulently. For support it draws a line. What needs it is not settled in the chat.
When it is required
Article 68 of Royal Decree-law 19/2018 requires it, with the exemptions in the European technical standard, when the customer does one of these three things.
- Accesses their payment account online.
- Initiates an electronic payment. For a remote payment, the authentication is linked to an amount and a payee.
- Carries out any action through a remote channel that may imply a risk of payment fraud or other abuse.
What it changes for support
The customer completes strong authentication in the app, and support points them there.
| Situation | What support does |
|---|---|
| Wants to change the phone number or email | Shows where to do it in the app |
| Offers the code they received | Does not accept it and tells them not to share it |
| Does not recognise a charge | Logs it. If strong authentication was not required, the customer is only liable for fraud (Article 46.2) |