G+D Netcetera manages 1.4 billion tokens
Payment tokenization as prerequisite in e-commerce
Reduce risk for non-authenticated transactions, associated refunds, and lost revenue.
Establish frictionless flow and improve the cardholder experience during online shopping.
As digital payment systems become more interconnected, their vulnerability grows. The 3DS Server is built to evolve with that landscape.
Certified against PCI 3DS, PCI DSS and all major card schemes and many local schemes. Hosted on G+D Netcetera's Cloud Payment Platform, with regular updates and upgrades.
Admin UI for data configuration, transaction search, reports, and user access management. Test environment. Easy API integration. 24/7 online customer support.
Fast and easy integration via comprehensive technical documentation, guidance webinars, and professional G+D Netcetera support.
Compliant with Visa, Mastercard, American Express, JCB, Discover/Diners, Cartes Bancaires, UnionPay, Eftpos, Dankort, Jaywan, Elo.
G+D Netcetera’s PCI 3DS certification already covers the authentication components you depend on.
When card networks or regulators ask for proof of compliance, you point to G+D Netcetera's certification reports rather than running separate assessments.
G+D Netcetera is an official member of the AWS Partner Network.
The 3DS Server SaaS operates on AWS infrastructure, supporting high availability, elasticity, and operational resilience at any transaction volume, from individual merchants to large acquirer portfolios managing thousands of merchants.
The G+D Netcetera 3DS Server was the first product approved by EMVCo in Europe and the second in the world. Fully compliant with the EMV 3DS 2.x protocol and all major card scheme EMV 3DS 2.x programs. This is not a legacy product retrofitted for 3DS 2.x. It was purpose-built for the specification from the outset — and has been updated through every subsequent version since.
A single 3DS Server deployment supports configuration for multiple acquirers, merchants, and PSPs, within a single integration. Payment platforms managing large and diverse merchant portfolios can extend consistent, standards-based authentication across every client on a single infrastructure investment. Acquirers can cover smaller merchants with the same high-quality authentication as their largest clients.
A JavaScript Web SDK is included for invoking 3DS Method, Challenge and SPC request messages in browser-based transactions.
Merchants do not need to build their own browser-side authentication logic — the SDK handles it. Combined with the server-side 3DS Server, this is a complete client-server EMV 3DS implementation in a single integration project.
SaaS: Admin UI covering data configuration, transaction search and report creation, and user access management.
Full operational visibility built into the product across both deployment models.
SaaS: a simulated Directory Server and ACS for integration testing — no waiting for scheme test environment availability.
On-premise: the NDM Simulator provides a full test application with a demo web shop, Directory Server, and ACS. Both paths provide integration testing that mirrors production conditions.
EMV 3DS authentication happens entirely within the merchant environment. No disruptive redirects, nor handoffs to separate authentication pages. The cardholder stays in the checkout throughout.
The vast majority of genuine transactions complete without any step-up required. The cardholder taps pay, the authentication runs invisibly in the background, and the purchase completes. That is the right experience for customers who have done nothing wrong.
When a challenge is required, it is proportionate and fast — via biometrics, one-time password, or device recognition. Compliant with EMV 3DS programs and certified with: Visa, Mastercard, American Express, JCB, Discover/Diners, Cartes Bancaires, UnionPay, Eftpos, Dankort, Jaywan, Elo.
Security and user experience are not competing priorities but complementary elements of a successful digital strategy. As payment systems become more interconnected, their vulnerability to sophisticated cyberattacks grows. Companies cannot navigate this alone — and they should not have to."
A 3DS Server is the component on the acquirer or PSP side that initiates and manages the EMV 3DS authentication flow for card-not-present transactions. It communicates with the card scheme's Directory Server and the issuer's ACS to authenticate the cardholder before a payment is processed. PSPs and acquirers need a 3DS Server to meet Strong Customer Authentication requirements, reduce fraud risk for non-authenticated transactions, shift liability for fraudulent transactions to the issuer, and — critically — to do all of this without unnecessary friction on genuine transactions. How well the Server sends authentication data determines how many of your customers are challenged unnecessarily.
Three things that are hard to replicate: provenance (first EMVCo-approved product in Europe, second globally — built from the specification's foundation, not retrofitted for it), breadth (10+ scheme certifications with publicly available Letters of Attestation for each), and integration depth (G+D Netcetera also builds the ACS and Directory Server the 3DS Server communicates with, so testing is against real counterparts, not simulated proxies). The Juniper Research RegTech Gold award is external validation of that track record.
SaaS: API integration into your existing payment environment. A JavaScript Web SDK handles browser-side 3DS Method, Challenge and SPC Request messages. A simulated Directory Server and ACS are available for integration testing. Full technical documentation is available at 3dss.netcetera.com/3dsserver-saas/doc/current. Dedicated team to support the onboarding process. 24/7 customer support is included.
G+D Netcetera's PCI 3DS certification covers the operated authentication components. When card networks or regulators ask for proof of compliance, you point to G+D Netcetera's certification reports rather than running separate assessments. G+D Netcetera manages the certification process with the schemes — without requiring customer involvement for most of them.
Integration documentation for SaaS and on-premise deployments and API references. Both deployment paths, fully documented.