3D Secure asks the cardholder to authenticate. A successful authentication is not the same thing as an approved payment, and it is not a promise that a chargeback cannot happen.
Who can use this. An admin or super admin manages business configuration. If the business is forced, the banner says 3D Secure Enforced and 3D Secure verification is enforced for this business by the administrator. This setting cannot be changed. Otherwise use Enable 3D Secure on a payment link, payment page, invoice, recurring payment, or contract. The help text says it adds authentication for online transactions.
Before you start. The customer completes the step on the card issuer screen, which may be a challenge or may finish without a challenge. You do not type the customer's one-time code.
Steps
- Open Settings, Configurations, and confirm 3D Secure is available for the business.
- Edit the payment link, payment page, invoice, recurring payment, or contract.
- Check Enable 3D Secure, unless the enforced banner already locked it on.
- Send the link or page to the customer.
- If authentication does not finish, the customer can see 3D Secure not authorized, or 3D Secure is not supported for this card. Please try a different card.
- Afterward, open Transaction History. Only APPROVAL or Approved (AA) means the card payment went through. The transaction can also show 3D Secure Enabled.
| What you see | Meaning | What happens next |
|---|---|---|
| Enable 3D Secure | Requests authentication on that online payment. | The card sale still has to be approved afterward. |
| 3D Secure Enforced | You cannot turn the requirement off for this business. | Leave the control as it is. |
| Frictionless result | The issuer authenticated without a challenge step. | Still look for the payment status. |
| Challenge | The customer must complete the issuer prompt. | If they cancel or time out, do not treat the payment as approved. |
| Not supported | This card will not authenticate. | The customer needs a different card. No approval is created by that message. |
| DDD result stored with the payment | The gateway session is kept with the transaction when a charge is attempted. | It does not replace the response code. |
After you save or submit. Saving the checkbox changes later payments on that record. It does not authenticate a payment that already failed, and it does not move money.
Example. Example only: Example Cafe enables 3D Secure on a 15.00 payment link. The fictional customer completes the issuer prompt, and Transaction History shows APPROVAL. A second fictional try shows 3D Secure not authorized and no APPROVAL row. Only the first payment succeeded. Neither result is a guarantee about chargebacks.
Troubleshooting
- The customer closed the prompt. Check attempts and Transaction History. If there is no APPROVAL, you may send a new request.
- You expected 3D Secure on Virtual Terminal. The Enable 3D Secure checkbox documented here is on links, pages, invoices, recurring payments, and contracts. It is not a Virtual Terminal transaction-type button.
- You want 3D Secure to stop chargebacks. Do not rely on that. Chargebacks are a separate cardholder dispute. This dashboard's menus do not include a chargeback case file.
Related
Found this helpful?
( 0 out of 1 found helpful )
