Netcetera

Service Overview

Start with the chain. A merchant or acquirer submits a transaction to a 3DS Server, the 3DS Server passes the request to the card scheme Directory Server, the Directory locates the issuer ACS, the ACS runs the challenge, and the result travels back the same way. Every link is a different vendor's product. A merchant only touches the 3DS Server directly, and often only indirectly inside the acquirer or gateway it already uses, while the Directory is operated by the scheme and the ACS is built or bought by the issuer. So the quality of 3DS is not decided by one supplier: frictionless pass rates, challenge page behaviour and failure semantics are spread across several parties.

Netcetera sits at the centre of that chain. It is a software vendor for financial services, branded G+D Netcetera on its site, with Netcetera AG based in Zurich. EMV 3-D Secure is a core product line spanning 5 components: 3-D Secure Directory Server, 3-D Secure Issuer Service, 3-D Secure Quality Assurance Platform, 3DS SDK and 3DS Server. Beyond that it runs 4 further lines: digital banking with Account Information Service, a Digital Euro integration platform, Mobile Wallet and Online Banking; retail banking; AI solutions; digital identity with BrIDge, Customer Identity and Access Management, EUDI Wallet and Self-Sovereign Identity mySSI; and digital wealth with Omnium.

The key question is who it serves. Its Directory Server and Issuer Service are the central pieces of the 3DS chain, but the customers are issuers, acquirers and scheme members. A normal merchant never signs with it and does not need to. That does not make it irrelevant: a meaningful share of your 3DS experience depends on whose ACS your issuer runs and whose Directory the scheme uses, and frictionless pass rates, challenge UX and error semantics come from exactly those two points. The merchant cannot buy it, but the merchant's conversion rate is shaped by it.

Procurement therefore depends on who you are. Ordinary merchants should not buy; acquirers, issuers, scheme members and institutions building their own ACS or Directory should evaluate it. The fact that it also ships Click to Pay, Passkeys and eCOM Tokenizer network tokenization, the authentication forms that come after 3DS, confirms the positioning as scheme-grade authentication infrastructure rather than a point tool.

Key Strengths

• Both central roles in one vendor: Directory and Issuer are the 2 hubs of 3DS and most vendors cover only one. One supplier for routing and issuing reduces cross-vendor integration and clarifies responsibility for institutions building a full stack.
• 5 components can land in stages: Directory Server, Issuer Service, Server, SDK and the quality assurance platform are separable, so an institution can start from the missing link instead of replacing the whole chain at once and absorbing all the risk in one release.
• Quality assurance as its own product: what slows a 3DS programme is rarely business logic but scheme certification and cross-browser, cross-device compatibility testing. A dedicated platform moves that testing earlier instead of discovering behaviour differences after launch.
• 3 post-3DS authentication forms: Click to Pay through Secure Remote Commerce and SRCI, Passkeys and eCOM Tokenizer tokenization. When schemes push tokenization and card-not-present checkout without card entry, this portfolio avoids a scramble for a second vendor.
• Digital identity connects to the authentication stack: BrIDge, CIAM, EUDI Wallet and mySSI cover enterprise identity management through self-sovereign identity, giving banks strong customer authentication options inside the same framework.
• Payments and fraud capability sit together: Payment Fraud Prevention, Verification of Payee and CloudPay can share data with 3DS decisions, which narrows the gap where authentication succeeds but collection still loses money.

Product Ecosystem

3-D Secure Directory Server

The central component for schemes and clearing institutions, routing transaction requests to the correct issuer ACS and returning authentication results. For regional schemes and institutions that need their own directory, this is the hardest part of the chain to source externally.

3-D Secure Issuer Service

The issuer-side authentication service that renders the challenge, performs verification and signs the result. An issuer's frictionless pass rate, challenge experience and failure messaging are effectively set by the policy and implementation in this layer.

3-D Secure Server

Built for merchants and acquirers, submitting transactions into the directory and processing the returned authentication result. Acquirers and payment service providers are the usual buyers here; merchants only reach it through their acquirer.

3DS SDK

The component integrated into mobile and web clients to run challenge flows. SDK quality drives behavioural consistency across devices and browsers, and is the most common source of integration delays.

3-D Secure Quality Assurance Platform

A platform for testing and assessing a 3DS implementation before formal certification and launch. Its value is turning scheme certification from a pre-launch black box into a reproducible checklist.

Payment Enabling and Post-3DS Authentication

The payment enabling line includes Debit Issuing Processing, Payment Solutions, Payment Fraud Prevention, Data Sharing Platform, Verification of Payee, the P40 and P3a/FZ3 pension systems, Secure Remote Commerce with Click to Pay and SRCI, Passkeys, Trusted Payments, CloudPay, eCOM Tokenizer and the Fusion Platform. Among these, Click to Pay, Passkeys and eCOM Tokenizer directly address how to challenge less and expose fewer card numbers after 3DS.

Digital Banking, Identity and Wealth

Digital banking covers Account Information Service, a Digital Euro integration platform, Mobile Wallet and Online Banking; identity covers BrIDge, CIAM, EUDI Wallet and mySSI; wealth is Omnium. These lines explain why the vendor can deliver end to end instead of one point tool.

Limitations

• Merchants usually cannot buy directly: Directory Server and Issuer Service customers are issuers, acquirers and scheme members, and normal e-commerce businesses neither reach nor need them. Putting Netcetera on a merchant 3DS shortlist targets the wrong link.
• You have no say over its deployment: whichever 3DS Server you pick, the issuer decides whose ACS handles the challenge. Your only lever when failure rates look wrong is escalation through the acquirer, not swapping a supplier.
• Part of the 3DS experience is outside your control: challenge UI, frictionless pass rates and failure semantics belong to the issuer ACS and the scheme directory. Merchant-side improvement is limited to the quality of the transaction data you submit.
• Frictionless ratios follow risk models and exemptions: low-value exemptions, trusted beneficiaries and SCA interpretation are not purchasable, and a vendor can only refine signals inside those rules.
• 3DS does not cover every fraud type: post-authorisation fraud, friendly fraud, first-time card binding after takeover and parts of APP scams fall outside 3DS, so an issuer still needs a broader fraud programme.
• Compliance responsibility does not transfer: whoever supplies ACS and Directory, PCI DSS scope and SCA accountability remain with the merchant and acquirer, and certification does not create an audit conclusion for you.
• Integration and scheme certification take months: 5 components in stages means multiple integration rounds, and Directory or ACS certification schedules run on timelines the buyer does not control.
• Cost scales with institution size: component selection, card portfolio, transaction volume and deployment model all move the quote, and the hidden cost of running your own stack, including operations, on-call and compliance evidence, often exceeds the licence fee.

Use Cases

• Issuers building or replacing an ACS (★★★★★): Issuer Service is the core, with the quality assurance platform and SDK covering the path from development to scheme certification.
• Acquirers and PSPs building their own 3DS Server (★★★★☆): when 3DS capability must be owned rather than resold, the Server and SDK components are the relevant options.
• Schemes, clearing houses and regional networks (★★★★★): the Directory Server is the most critical infrastructure at that layer, and very few vendors can supply it.
• Institutions launching Click to Pay, Passkeys or tokenization (★★★★☆): post-3DS forms come from the same vendor as the 3DS stack, which reduces policy conflicts between two frameworks.
• Cross-border acquirers serving issuers in several markets (★★★☆☆): rule configuration for Directory and ACS matters under differing market rules, though the actual coverage must be confirmed market by market.
• Mainland China operations (☆☆☆☆☆): domestic card 3DS runs through domestic acquirers and the domestic scheme and overseas vendors are not part of it. Cross-border sellers using overseas acquiring can use that path, after confirming acquirer and scheme admission requirements for the 3DS Server.
• Worst fit: ordinary standalone stores and small merchants (★☆☆☆☆): they cannot buy the central components and cannot change issuer or scheme behaviour, so the investment does not match the return.

Pricing

Cost drivers include the component mix across Directory, Issuer, Server, SDK and the quality platform, card portfolio and annual transaction count, frictionless policy complexity, whether post-3DS forms launch at the same time, SaaS versus on-premise deployment, and the certification and operations scope of project delivery. No price list is published, so any precise figure belongs in a contract.

The table reflects the currently published product structure on the Netcetera website. No standard rate card is published; actual quotes, delivery scope and supported countries are governed by your contract.

FAQ

• I run an online store. Can I buy Netcetera 3DS directly?
  Your scenario normally does not need it. The core components serve issuers, acquirers and scheme members, and merchant 3DS capability usually arrives through the acquirer or gateway. Approaching Netcetera targets the wrong link.

• Does it affect my conversion rate at all?
  Yes, but you are a passive party. The issuer's ACS decides challenge experience and frictionless judgement, and the scheme Directory decides routing and rules. If one card type or issuer shows abnormal failures, the route is escalation through your acquirer, not changing your own vendor.

• How is it structurally different from other 3DS providers?
  Most 3DS providers cover only the Server link, while this vendor also holds the 2 central roles of Directory Server and Issuer Service, plus a standalone quality assurance platform and SDK. The difference is coverage, not the strength of any single feature.

• How do Click to Pay and Passkeys relate to 3DS?
  They are authentication forms that come after 3DS. 3DS verifies the cardholder at the transaction moment; Click to Pay removes card entry, Passkeys remove passwords and OTPs, and tokenization reduces card number exposure. They complement 3DS rather than replace it.

• Is it suitable for mainland China institutions?
  Domestic card 3DS runs through domestic acquirers and the domestic scheme, and overseas vendors are not part of that path. For cross-border business on overseas acquiring, the Server or SDK can be evaluated, but admission and certification follow acquirer and scheme rules.

Source: original 16IDC content. Product capabilities, supported countries and fee definitions follow the official documentation on netcetera.com and your contract.