# 3D Secure: one authentication flow on every processor

Orchestrapay runs 3D Secure the same way on every card processor you connect.
Customers approve the payment with their bank in a window over your checkout,
and your routing rules decide when 3D Secure is required.

Page: https://www.orchestrapay.com/products/3d-secure

## What it does

- **Challenges inside your checkout.** The bank's approval screen opens in a
  window over the payment form and a dedicated return page closes it. Customers
  never leave your site.
- **Same flow on every processor.** Challenges from Stripe, the Mastercard
  Gateway, PayPal and Authorize.net reach your checkout in one shape.
- **Fraud liability moves to the bank.** Authenticated payments generally shift
  fraud chargeback liability to the card issuer.
- **Built for strong customer authentication.** 3D Secure is how card payments
  meet PSD2 authentication rules in the European Economic Area.
- **Off-session payments handled.** If a bank challenges a renewal or saved-card
  charge, the challenge is returned to you to send to the customer.
- **Nothing extra to build.** Included in the Orchestrapay payment form and the
  `@orchestrapay/react` SDK.

## Decide when to authenticate

Each processor node in your routing graph can force 3D Secure or leave the
decision to the processor. The graph can branch by country, card number range
(BIN), amount, or whether the card has succeeded before.

| Processor | Returns challenges | Can force 3D Secure |
| --- | --- | --- |
| Stripe | Yes | Yes |
| Mastercard Gateway | Yes | Yes |
| PayPal | Yes | Yes |
| Authorize.net | Yes | No |

## How it works

1. **Route.** The routing graph picks the processor and whether to authenticate.
2. **Challenge.** If the bank asks, the approval screen opens over your checkout.
3. **Complete.** The window closes and the payment finishes on the same
   processor.

## FAQ

**Do customers get redirected to their bank?** No. The bank's screen opens over
your checkout and closes itself when done.

**Does 3D Secure protect me from chargebacks?** From fraud chargebacks, yes:
liability generally shifts to the issuer. Not from disputes about the goods or
service.

## Related

- [Smart Routing](https://www.orchestrapay.com/products/smart-routing.md)
- [Apple Pay & Google Pay](https://www.orchestrapay.com/products/apple-pay-google-pay.md)
- [PCI DSS Compliance](https://www.orchestrapay.com/solutions/pci-dss-compliance.md)
- [Talk to sales](https://www.orchestrapay.com/contact)