Every time an online shopper confirms a card payment in their banking app, a 3DS Server started that conversation. It's the merchant-side component of EMV 3-D Secure: it collects data about the payment and the device, sends it toward the card issuer and handles the result, whether the issuer approves without friction or asks the shopper to confirm.
A PSP needs 3-D Secure for card-not-present payments in many markets, but it doesn't have to build the server itself. This page explains how a 3DS Server fits into the protocol, what building one involves, and how licensing or outsourcing compare.
Where the 3DS Server sits in EMV 3-D Secure
EMV 3DS involves three domains: the merchant and acquirer side, the card scheme in the middle and the issuer on the other end. Each runs its own component.
| Component | Run by | What it does |
|---|---|---|
| 3DS Server | Merchant, PSP or acquirer, or a provider for them | Collects payment and device data, starts authentication, receives the result |
| 3DS SDK | Inside the merchant's mobile app | Gathers device data and shows challenges in the app |
| Directory Server | The card scheme | Routes messages between the 3DS Server and the right issuer |
| Access Control Server | The issuer or its provider | Decides whether to approve frictionlessly or to challenge the shopper |
An EMV 3DS Server is the only one of these a PSP runs, or rents. The other three belong to app developers, schemes and issuers.
How a 3-D Secure check runs
The sequence is quick when it works, and most of it is invisible to the shopper. In outline:
- The shopper submits card details on the checkout.
- The 3DS Server sends an authentication request with payment and device data to the scheme's Directory Server.
- The Directory Server passes it to the issuer's Access Control Server.
- The issuer either approves frictionlessly or asks for a challenge, such as a confirmation in the banking app.
- The result returns to the 3DS Server, which passes the authentication data to the authorization request.
The richer the data in step 2, the more often issuers approve without a challenge. That's why the quality of a 3DS Server's data collection matters for conversion, not just for compliance.
Who sets the rules
EMVCo maintains the EMV 3DS specifications and the approval processes that go with them, including approval of 3DS product vendors, service providers and test tools. The specifications keep moving: EMVCo's 3-D Secure page lists drafts of the protocol and SDK specifications open for comment until January 8, 2027.
Card schemes add their own programs on top, and in the European Economic Area, strong customer authentication rules under PSD2 make 3-D Secure the usual way to authenticate online card payments, with the PSD2 rules also setting when a payment may skip the challenge.
Building your own 3DS Server
A 3-D Secure server is a well-specified product, which makes building one possible and keeping it current hard. You'd implement the protocol messages, device data collection, browser and app flows, and connections to each scheme's Directory Server.
Then comes approval. The product has to pass EMVCo's testing for the protocol version you support, and schemes have their own onboarding before your server can talk to their directories. Each new protocol version restarts part of that work. For a typical PSP, the effort only pays off if 3-D Secure itself is a product it plans to sell.
Licensing or outsourcing instead
PSPs usually take one of three shortcuts instead, and each removes the approval work from their own team.
| Route | How it works | Suits |
|---|---|---|
| License 3DS Server software | You run an approved product in your own environment | PSPs that self-host and want control |
| Use a 3DS service provider | A provider runs the 3DS Server and you call it through an API | PSPs that want the least operational work |
| Use your gateway's 3-D Secure | The gateway runs authentication as part of the payment flow | PSPs that want it built in |
The third row is the simplest for a new PSP. Authentication results then flow straight into routing and authorization without a separate integration.
3DS Server for PSPs on our gateway
Our gateway runs 3-D Secure as part of every card payment flow and supports an external MPI, so a PSP that already uses its own 3DS provider can keep it. Authentication sits next to 150 built-in configurable fraud filters, so rules can decide which payments go to authentication and which stop earlier.
Merchants get it through the hosted payment page, the JS SDK and the iOS and Android SDKs, with the challenge screen coming from the issuer as the protocol requires. On SaaS, it runs inside our PCI DSS v4.0.1 Level 1 certified platform.
Questions
What is a 3DS Server?
The merchant-side component of EMV 3-D Secure. It collects payment and device data, sends authentication requests through the card scheme's Directory Server to the issuer and receives the result.
What's the difference between a 3DS Server and an MPI?
MPI, or merchant plug-in, is the older name from 3-D Secure 1. In EMV 3DS the equivalent component is the 3DS Server, though many providers still use the MPI name.
Should a PSP build its own 3DS Server?
Usually not. Building means implementing the protocol, passing EMVCo approval and scheme onboarding, and repeating parts of that for every new protocol version.
Does 3-D Secure reduce chargebacks?
Authenticated payments typically shift fraud liability toward the issuer under card scheme rules, which is one reason merchants and PSPs use it. Check the current rules of each scheme for your markets.