3-D Secure

Prevent Fraud. Ensure Compliance.


Icon-Dark-Network Tokens

Flexible compliance and fraud prevention from TokenEx.

  • Comply with the SCA requirements of PSD2

  • Seamlessly integrate multifactor authentication into your checkout process

  • Reduce false declines and chargebacks, potentially shifting liability to issuers

For organizations subject to Payment Services Directive 2--or those looking for a more secure checkout experience--3-D Secure can be a valuable solution for strong customer authentication. As a result, organizations can reduce false declines and increase approvals while minimizing their PCI scope and preserving their ability to work with any payment service provider.

Connect with us to learn how 3DS can help you.

How it Works


Data flow - 3ds v4



  1. TokenEx client sends authentication request to TokenEx.
  2. TokenEx forwards the request to the 3DS server.
  3. If a challenge is necessary, TokenEx receives it and routes it to the end user via the client.
  4. If the challenge is successfully completed, the transaction is approved for processing.



Why work with TokenEx instead of another 3DS provider?

TokenEx is an open API platform, so you have the freedom to use our tokens and services with any third party you want. That means you're not limited to using our 3DS service with a single processor or provider. We also offer unmatched PCI scope reduction, so you never have to handle raw cardholder data.

How is 3DS different from other fraud prevention tools?

3-D Secure is a three-step process for authentication that verifies an individual's identity before authorizing an online credit or debit card transaction. It also shifts the liability for a fraudulent transaction to the issuing bank, so you can avoid paying for chargebacks if fraud occurs.

If I use 3DS, will all of my transactions be subject to authentication checks or challenges?

No. There are certain exemptions for low-risk transactions, so if a transaction is below a certain threshold, it will not require a 3DS challenge. To pass a Transaction Risk Analysis (TRA), none of the following checks should apply to a transaction: 


  • Unusual device information or payer/payee locations
  • Unusual behavior or patterns in spending
  • The detection of nefarious software
  • The presence of common fraud scenarios