Skip to content

SCA, strong customer authentication

Adrià Castany 2 min

What is strong customer authentication?

Strong customer authentication combines two or more independent elements from three categories, something only the user knows, something only the user has and something the user is, so that a breach of one does not compromise the others. In Spain, Royal Decree-law 19/2018 requires it of payment service providers.

Also called

autenticación reforzada de cliente, strong authentication

Stands for

Strong Customer Authentication

Topic
Support concepts
On this page
  1. Strong authentication, two-factor and checking identity in support
  2. Why it matters
  3. When it is required
  4. What it changes for support
  5. How Intake handles it
  6. Frequently asked questions

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.

SituationWhat support does
Wants to change the phone number or emailShows where to do it in the app
Offers the code they receivedDoes not accept it and tells them not to share it
Does not recognise a chargeLogs it. If strong authentication was not required, the customer is only liable for fraud (Article 46.2)

How Intake handles it

Frequently asked questions

What is strong customer authentication?

Authentication with at least two independent elements among something only the customer knows, something only they have and something they are. Article 3 of Spain’s Royal Decree-law 19/2018 defines it.

When is strong customer authentication required?

When accessing the payment account online, initiating an electronic payment and doing anything remotely that carries a fraud risk, subject to the exemptions in the European technical standard.

What if the provider did not require strong authentication?

For an unauthorised transaction, the customer only bears the consequences if they acted fraudulently, under Article 46.2 of Royal Decree-law 19/2018.

Glossary

Keep reading

Glossary

Related terms

See the full glossary

Add it without dropping what you use

15 minutes, no commitment