3D Secure authentication for online card payments.
Run EMV 3-D Secure on the merchant side with a 3DS Server, or on the issuer side with an ACS. Strong authentication when it is needed, a smooth checkout when it is not.
Confirm this payment
Enter the 6-digit code we sent to your phone ending 21.
What you get
Authenticate the payments that need it. Let the rest flow.
Stronger fraud control
Send rich transaction and device data so the issuer can assess risk before it authorizes.
Smoother checkout
Low-risk payments can complete without a challenge. Challenges are designed for browser and in-app journeys.
Support for SCA
Use 3D Secure as part of your plan for Strong Customer Authentication and scheme requirements.
How it works
Five steps from checkout to result.
Collect
Checkout gathers card, device and transaction data.
Request
The 3DS Server sends it through the scheme's Directory Server.
Assess
The issuer's ACS evaluates the risk.
Authenticate
Frictionless approval, or a short cardholder challenge.
Return
The result and authentication value go back for authorization.
Capabilities
Everything both sides of 3D Secure need.
Requestor-side 3DS Server
Authentication requests and result handling for merchants, PSPs and acquirers.
Issuer-side ACS
Risk assessment and challenge handling for card issuers and programs.
Browser and app flows
Web redirects and native SDK journeys, with clear fallbacks.
Challenge experience
OTP, app and other supported challenge methods, with timeout and cancel paths.
Results and events
Protocol status, ECI and authentication values mapped for your payment flow.
Monitoring
Frictionless and challenge rates, errors and timeouts in one view.
Use cases
Where teams use it.
E-commerce
Online stores and marketplaces with card-not-present checkout.
Travel
Higher-value and cross-border bookings.
Subscriptions
Authenticate the first payment, then charge stored cards.
Card issuers
Run the ACS for your own card programs.
FAQ
Common questions.
Authentication is not approval. After 3D Secure, the issuer still decides whether to authorize the payment. Liability and SCA outcomes depend on scheme rules and your full setup.
What is EMV 3-D Secure?
A protocol that lets merchants and issuers exchange transaction data, so the issuer can assess risk and, when needed, ask the cardholder to confirm the payment.
What is an ACS?
The Access Control Server is the issuer-side component. It evaluates each request, chooses a frictionless or challenge path and returns the result.
Will every customer see a challenge?
No. The issuer's assessment decides. Many low-risk payments complete without one.
How are subscriptions handled?
The first, customer-initiated payment is authenticated. Later merchant-initiated charges can follow different rules.
Which versions and card schemes are supported?
Coverage depends on the deployment. We confirm protocol versions and schemes during technical scoping.
Related services
Works well with.
Review your 3D Secure flow.
Share your checkout channels and current setup. We will show where 3D Secure fits and what to change.