3DSService

Add issuer-supported cardholder authentication to eligible ecommerce transactions with NMI 3-D Secure.

NMI Payer Authentication (3DS) exchanges transaction and customer data with participating card issuers before authorization. Most eligible transactions may follow a frictionless flow, while an issuer can request a step-up challenge such as a one-time passcode.

VCCP can help determine whether 3DS is available for your ecommerce setup and coordinate the compatible NMI gateway, integration, processor, acquiring bank and merchant enrollment.

How 3-D Secure Works

  1. The customer enters payment and checkout information through a supported ecommerce flow.
  2. The integration sends required information for issuer-supported payer authentication.
  3. The issuer may authenticate silently through a frictionless flow or request a customer challenge.
  4. The authentication result and supported 3DS values are returned to the integration.
  5. The transaction is submitted for authorization with the applicable authentication data.

Frictionless and Challenge Flows

Frictionless Flow

The issuer assesses the available data and authenticates or processes the attempt without an additional customer step. Supplying complete, accurate checkout data may improve the likelihood of a frictionless experience.

Challenge Flow

When the issuer requests more assurance, the customer completes an additional authentication step—often a one-time code or another issuer-selected method—before the payment proceeds.

Supported Integration Paths

  • NMI Payment API with a compatible NMI frontend component or Gateway.js workflow
  • Collect Checkout when configured for payer authentication
  • Compatible QuickClick and Three Step Redirect integrations
  • Eligible third-party authentication data passed through a supported processor and NMI API workflow

Enrollment and Compatibility

3DS is intended for eligible ecommerce transactions—not retail or mail/telephone-order payments. Activation may require a merchant website or supported hosted-payment link, an ecommerce-classified processing service, acquiring-bank information, card-brand enrollment details and a processor that supports NMI payer authentication.

Liability Shift Is Conditional

A successful or attempted 3DS authentication may provide chargeback-liability benefits for certain eligible fraud disputes. The outcome depends on the card brand, issuer, authentication result, processor, region, transaction type and applicable rules. 3DS does not prevent every fraud loss or protect against every chargeback reason.

Important Limitations

  • 3DS authentication is separate from payment authorization; authentication does not guarantee issuer approval.
  • Challenges can add customer friction or abandonment if the flow is not implemented clearly.
  • The merchant must correctly pass the returned authentication data with the authorization request.
  • Supported brands, regions, processors and integrations vary.
  • 3DS complements—but does not replace—gateway rules, bot protection, fraud monitoring and secure development.

Related NMI Tools

NMI 3DSService Frequently Asked Questions

What is NMI 3DSService?

NMI 3DSService provides payer authentication for eligible ecommerce transactions using the card networks’ 3-D Secure framework. It allows participating issuers to assess the shopper before payment authorization.

Will every customer have to enter a one-time code?

No. Many eligible transactions may follow a frictionless flow without an additional customer step. The issuer can request a challenge when it needs more assurance.

Does successful 3-D Secure authentication guarantee approval?

No. Authentication confirms an issuer-supported payer result, while authorization is a separate decision based on the card account, available funds and issuer rules.

Does 3-D Secure provide chargeback liability protection?

Some successful or attempted authentications may qualify for liability-shift benefits on eligible fraud disputes. The outcome depends on the card brand, issuer, result, transaction, processor, region and current rules.

Can 3DSService be used for phone orders or Virtual Terminal payments?

3DSService is intended for supported ecommerce customer checkouts, not ordinary mail-order, telephone-order, retail or merchant-entered Virtual Terminal transactions.

Can NMI Collect Checkout use 3-D Secure?

Collect Checkout may support payer authentication when the merchant, processor, acquiring bank and hosted checkout configuration are eligible and properly enrolled.

Does 3-D Secure replace fraud screening and CAPTCHA?

No. It adds issuer-supported authentication, but merchants should still use secure development, bot protection, gateway rules and appropriate risk monitoring.


Plan Authentication Around the Checkout

Tell VCCP how your ecommerce checkout is built, which processor and acquiring bank are involved, and where customers are located. We can help evaluate 3DS enrollment and the other fraud controls your payment flow may need.

Availability, enrollment, card-brand support, liability outcomes, pricing, processor compatibility and approval depend on the transaction, region, gateway configuration, acquiring bank, merchant account and underwriting. VCCP does not guarantee authentication, authorization or liability shift.