3D Secure
One authentication flow on every processor.
Customers approve the payment with their bank in a window over your checkout, whichever processor takes it. You decide when to ask.
Why run 3D Secure through Orchestrapay
Every processor does 3D Secure differently. Your checkout should not have to.
Challenges inside your checkout
The bank's approval screen opens in a window over your payment form and closes itself when the customer is done. Nobody leaves your page.
Same flow on every processor
Stripe, the Mastercard Gateway, PayPal and Authorize.net each return challenges their own way. Your checkout sees one.
Fraud liability moves to the bank
When a payment is authenticated with 3D Secure, the card issuer, not you, generally carries the cost of a fraud chargeback.
Built for strong customer authentication
In Europe, PSD2 asks you to authenticate most online card payments. 3D Secure is how you do it.
Off-session payments handled
If a bank challenges a renewal or a saved-card charge made without the customer present, the challenge comes back to you to send them.
Nothing extra to build
3D Secure ships with the Orchestrapay payment form and React SDK. There is no separate authentication integration per processor.
Decide when to authenticate
Ask for 3D Secure where it protects you, skip it where it costs you.
Each processor in your routing graph can force 3D Secure or leave the decision to the processor. Set it by country, card number range, amount or customer history.
- 01Force 3D SecureIfCountry is in the EEARoute to Stripe
- 02Force 3D SecureIfAmount over €500Route to Mastercard Gateway
- 03Processor decidesIfCard succeeded before for this customerRoute to Stripe
- 04Processor decidesIfEverything elseRoute to Authorize.net
Per processor
| Processor | Challenge | Force |
|---|---|---|
| Stripe | ||
| Mastercard Gateway | ||
| PayPal | ||
| Authorize.net |
Challenge: the processor can return a 3D Secure challenge, shown in your checkout. Force: you can require 3D Secure on every payment sent to it.
How it works
From pay button to approved, without leaving the page.
Route
Your routing graph picks the processor and whether this payment must be authenticated.
Challenge
If the bank asks for it, the approval screen opens over your checkout. The customer approves in their banking app or with a code.
Complete
The window closes, the payment finishes on the same processor, and your page gets the result.
Questions teams ask before they switch.
3D Secure is the card schemes' way for a bank to confirm that the person paying is the cardholder, usually with an approval in a banking app or a one-time code. Visa calls it Visa Secure and Mastercard calls it Identity Check.
Authenticate where it pays off.
Tell us which processors you use and where you sell. We will show you how 3D Secure fits your routing and what it costs.
- One 3D Secure flow on every processor
- Customers never leave your checkout
- A transparent number before you sign anything