get in touch
4 Reasons Smart PSPs and Orchestrators Are Moving 3DS Server In-House

4 Reasons Smart PSPs and Orchestrators Are Moving 3DS Server In-House

For a payment service provider, a 3DS Server can be more than a mandatory interface to EMV 3-D Secure. Its integration, availability, logging and deployment model influence how the PSP runs authentication across merchants, gateways and acquiring connections. Bringing the Server into your own environment may improve operational control, but it does not transfer issuer authentication decisions to the PSP or guarantee lower costs.

This guide helps PSPs, acquirers and payment orchestrators decide whether to license a 3DS Server, use a transaction-based managed service or keep their current arrangement.

What the 3DS Server actually controls

The 3DS Server is the EMV 3-D Secure component on the 3DS Requestor and acquiring side. It initiates an authentication request and exchanges the required protocol messages through the card-scheme Directory Server (DS). The issuer's Access Control Server (ACS) evaluates the authentication request and determines the relevant cardholder authentication outcome, including whether a challenge is requested.

ComponentPrimary responsibilityWhat it does not do
Merchant / PSPInitiates payment and supplies the necessary authentication context.Does not determine the issuer's final authentication outcome.
3DS ServerBuilds and exchanges protocol messages, handles relevant responses and integrates authentication into the merchant-side payment stack.Does not own the issuer ACS risk policy or independently approve card payments.
Directory ServerRoutes relevant protocol messages to the participating ACS and supports card-range and version-related information exchange.Is not the PSP's in-house authentication risk engine.
Issuer ACSEvaluates the authentication request and conducts or requests cardholder verification as appropriate.Does not replace the merchant-side 3DS Server.

In the protocol, AReq/ARes messages handle authentication request and response; PReq/PRes support preparation and Directory Server information exchange; and following an applicable challenge, RReq/RRes communicate and acknowledge the result via the DS. Browser or SDK challenge communications use the relevant client-to-ACS path; CReq/CRes should not be presented as general 3DS Server-to-ACS requests.

This distinction matters when evaluating a 3DS Server vendor. A supplier may provide merchant-side reporting, APIs and message handling without offering control over issuer risk rules. See EMVCo's challenge-flow technical overview for the relevant protocol roles.

Four reasons PSPs consider bringing 3DS Server in-house

1. Greater integration control

A PSP with several acquiring partners may need a consistent authentication integration layer and visibility into how requests move through the checkout process. An internally operated 3DS Server can be integrated more closely with the gateway, merchant configuration, monitoring and troubleshooting tools.

However, replacing an acquirer or retrying a failed authorisation is not a guarantee that a previous 3DS authentication can be reused. Whether a subsequent transaction requires a fresh authentication depends on its circumstances, scheme rules, credential context and the parties involved. Payment routing and 3DS authentication must be designed and tested together.

2. Operational visibility into authentication failures

When authentication fails, the operations team needs to determine whether the issue sits in merchant data, integration, message validation, scheme connectivity, an issuer response or the challenge experience. A technical evaluation should show which log fields, transaction identifiers and error categories are available, rather than relying on a generic “analytics” claim.

3. Choice of software and operating model

Some PSPs need to host authentication infrastructure in a specific environment; others prefer a managed service. Control over infrastructure can be useful for data residency and architecture requirements, but it also creates responsibilities for patching, high availability, security operations and incident response.

4. Cost predictability at the right scale

A licensed 3DS Server may be commercially appropriate for predictable volumes or specific infrastructure requirements. A transaction-based SaaS model may be more suitable when the business prefers an operating expense and does not want to manage the full environment. Neither option is inherently cheaper. Compare the same projected volume, schemes, support scope and period before deciding.

Licensed 3DS Server vs transaction-based SaaS

FinOn offers a one-time software licence model and a transaction-based SaaS model for its 3DS Server. Commercial details are agreed individually; the price of a licence should not be mistaken for total lifetime operating cost.

Decision factorSoftware licenceTransaction-based SaaS
Commercial starting pointOne-time software licence feePay-as-you-go, per-transaction service model
Hosting / operationsDetermined by the proposed deployment and responsibility matrixDetermined by the managed service agreement
Cost drivers to reviewImplementation, infrastructure, maintenance, monitoring, support and applicable scheme workUsage assumptions, integration, included services, support and exceptions
Procurement documentsProduct approval, system requirements, licence and support termsProduct approval, service/security scope, SLA and service terms
Best evaluated throughThree-year total cost of ownership and operational capacityThree-year volume forecast, service scope and exit considerations

Ask the provider to define exactly what counts as a billable transaction and which deployment services are included. Do not infer setup fees, recurring minimums or a universal support charge without a quotation.

What to verify before purchasing a 3DS Server

The technical proof of concept should reflect the PSP's intended processing environment, not just a single successful frictionless transaction.

Demo / proof-of-concept checkExpected evidence
Supported protocol versionsLOA for the exact product version and confirmation of relevant schemes and deployments.
Authentication flowRepresentative AReq/ARes scenarios and supported follow-up messages.
Directory Server integrationApplicable DS connections, card-range exchange and onboarding responsibilities.
Browser and application journeysHow the 3DS Server interacts with browser/merchant SDK flows and the relevant issuer challenge process.
Error handlingRejected or timed-out messages, diagnostics, transaction correlation and controlled recovery.
OperationsLogs, available monitoring fields, incident process and applicable service levels.
Availability and scalingEvidence relevant to forecast volume and agreed infrastructure or service architecture.
Commercial and exit scopeItemised proposal, support responsibilities, updates and handover terms.

FinOn 3DS Server: published EMVCo approval

3DSS FINON, version 2.3.1, has a published EMVCo Letter of Approval covering EMV 3DS specification versions 2.2.0 and 2.3.1.1. Approval reference: 3DS_LOA_SER_FITC_020301_01050, dated 10 July 2025, with an expiration date stated as 28 May 2027.

View the official 3DS Server Letter of Approval. Confirm its current status and any scheme-specific requirements before contracting. EMVCo approval does not itself certify every production environment or connection.

When an in-house 3DS Server is not the best choice

Consider keeping a managed service if your PSP has limited 3DS transaction volume, no dedicated infrastructure operations team, few integration dependencies, or a service arrangement that already meets technical and commercial requirements. A licensed deployment may add operating complexity without delivering enough incremental control to justify it.

Conversely, self-operation becomes more interesting when the PSP has clear requirements for hosting, integration autonomy, reporting, configuration access or consistent management across acquiring relationships. There is no universal volume threshold at which self-hosting becomes preferable.

Evaluating an in-house 3DS Server?

Bring your scheme requirements, expected monthly authentication volume, PSP/gateway architecture and deployment preferences. Request a FinOn technical demonstration and a proposal for licence or SaaS delivery.

How FinOn fits into a PSP's authentication stack

FinOn describes an API-based 3DS Server with licensed and service delivery options, integration into payment and merchant-side systems, administration and logging capabilities, and an associated merchant-side 3DS SDK for mobile applications. Request the current integration specifications and product version rather than assuming every feature is included in the selected package.

In a wider acceptance stack, the 3DS Server should be evaluated alongside the payment gateway and relevant payment orchestration layer. They have related but distinct responsibilities.

Frequently asked questions

Can a PSP operate its own 3DS Server?

Yes, provided the product, scheme integration, deployment and operational responsibilities fit the intended use. An in-house 3DS Server does not replace the issuer ACS or transfer issuer authentication decisions to the PSP.

Does an in-house 3DS Server eliminate per-transaction costs?

Not necessarily. A software licence has a different commercial model from transaction-based SaaS, but infrastructure, support, testing, scheme and other costs can still arise. Compare complete proposals.

Can a PSP reuse 3DS authentication when switching acquirers?

Do not assume so. The applicability of an earlier authentication to a subsequent payment or routing attempt depends on scheme rules, transaction context and technical implementation. Validate the exact scenario with the relevant partners.

Is the FinOn 3DS Server EMVCo-approved?

FinOn 3DSS FINON version 2.3.1 has a published EMVCo Letter of Approval for EMV 3DS 2.2.0 and 2.3.1.1. Check the cited approval for the exact version and its current status.

Can we test the integration before purchasing?

Request a technical walkthrough or agreed proof-of-concept scope from FinOn. Access to a sandbox and the specific scenarios available for testing should be confirmed directly with the team.

What is needed for a quotation?

Specify target schemes and markets, monthly authentication volume, merchant and acquiring architecture, required protocol versions, deployment model, integrations and launch window. Request separate scope and responsibility details for licence and SaaS options.

Compare the operational requirements, not just vendor prices

FinOn can discuss the 3DS Server model that fits your PSP and demonstrate the relevant authentication integration and monitoring requirements.

Ready to see the Full Picture?

Let’s connect - and walk you through a personalized demo.

Your message has been sent.
We will contact you shortly.