3-D Secure and SCA
When Ginger authenticates a card payment with 3-D Secure, which exemptions apply, and how you change it per project.
3-D Secure (3DS) authenticates the cardholder with their issuer. In the European Economic Area, Strong Customer Authentication (SCA) under PSD2 requires it for most customer-initiated card payments. An authenticated payment usually shifts the fraud liability to the issuer.
When Ginger runs 3-D Secure
By default, Ginger authenticates every customer-initiated card payment with 3DS 2. It skips 3DS when:
- The payment is merchant-initiated (MIT), such as a subsequent recurring payment. The first payment of a recurring series is authenticated.
- The payment is an Apple Pay or Google Pay payment with a cryptogram: the device has authenticated the customer.
- A low value exemption applies: the amount is under the threshold you set on the contract. The issuer can still ask for authentication.
- A dynamic 3DS rule of the project prefers not to request it, for example for cards issued outside the EEA.
With Elavon and IPG, when the issuer declines a payment without 3DS with a soft decline, the customer authenticates with 3DS and Ginger retries the payment. For the other processors, ask your Ginger contact how a soft decline is handled.
3-D Secure per processor
| Processor | 3DS server | Dynamic 3DS rules | Your own 3DS |
|---|---|---|---|
| Silverflow | Ginger, through Silverflow | Yes | Yes |
| Elavon | Endeavour | No | No |
| Rapyd | Rapyd | Yes | No |
| Shift4 | Shift4 | No | No |
| IPG | IPG | No | No |
Change when 3DS runs
| You want to | Use |
|---|---|
| Skip 3DS for small amounts | A low value exemption on the project's card contract |
| Skip or force 3DS by card country | Dynamic 3DS rules on the Silverflow or Rapyd contract |
| Run 3DS in your own payment page | Your own 3-D Secure, for acquirers on Silverflow |
The data the schemes require
The 3DS request carries customer data from the order. Mastercard requires an identifier, an address and the IP address in every authentication request: see Mastercard 3DS AReq data.
For your merchants
How merchants handle 3DS in their checkout is in 3-D Secure in the payment acceptance docs.