Skip to main content
On this page

3D Secure (3DS) authenticates a cardholder with the issuing bank before a card payment continues. DEUNA makes that authentication part of the same payment flow, whether DEUNA manages the 3DS experience or the selected payment provider supplies its supported 3DS flow.

How a 3DS payment works#

Sequence diagram
1Shopper2Checkout3DEUNA4Issuing bankSubmit card paymentSubmit payment onceRequest cardholderauthenticationPresent next_action only whenreturnedpending_3ds + next_actionwhen requiredOpen the returnedauthentication experienceBrowser checks run only whenrequiredCollect browser and device signalsFrictionless authenticationAuthentication resultChallenge requiredPresent challenge in the authenticationexperienceComplete authenticationAuthentication resultComplete or confirmpayment authorizationwhen eligibleRetrieve original order onthe backendCurrent payment status
Merchant or customerDEUNA

A returned 3DS action can start with automatic browser and device checks, sometimes called the 3DS Method. The customer may see a loading view before a challenge appears, or the flow may finish without asking them to act. Keep the returned experience open while DEUNA coordinates these steps.

The issuer determines whether the customer needs a challenge. The stages shown above are conditional; every payment does not pass through every screen.

Authentication success is not payment success. It allows authorization to continue. Always evaluate the final payment status after the 3DS step.

Depending on the connection, authentication can finish together with authorization or before it. DEUNA completes the remaining payment steps. Your checkout should not submit another purchase after the shopper finishes a challenge.

Supported 3DS models#

DEUNA-managed 3DS

DEUNA coordinates authentication and passes the result into the payment authorization. This gives merchants one integration and one shopper-action contract across compatible acquiring connections.

Use this model when you want DEUNA to manage the authentication journey and keep the checkout behavior consistent across providers.

Provider-managed 3DS

Some payment providers expose their own 3DS flow through their DEUNA connection. DEUNA normalizes the required customer action into the payment response and continues the payment when authentication finishes.

Support varies by provider, country, card network, and connection configuration. Use the live payment gateway catalog to verify advertised 3DS capabilities, then confirm enablement with your DEUNA Technical Account Manager (TAM).

Where it works#

IntegrationShopper experienceMerchant responsibility
Payment WidgetDEUNA presents the challenge inside the supported widget experience or redirect.Listen for the widget result and confirm the final payment status.
Payment LinkDEUNA presents and completes the supported authentication experience.Configure the return experience and retrieve the final DEUNA payment status.
Direct APIThe payment response can return pending_3ds and a next action for browser checks or a challenge.Present the returned action with a supported DEUNA SDK or the agreed browser integration, then verify the payment status.
Payment VaultA saved card payment can return the same 3DS next action.Use initNextAction in a supported SDK or implement the returned action safely.

Data that improves authentication#

Complete, truthful shopper and device data helps the issuer make a better risk decision and can increase the chance of a frictionless result.

Data groupRecommended fields
PaymentAmount, ISO 4217 currency, card or card token, and merchant reference
ShopperFirst name, last name, email, and phone number
Billing addressAddress line, city, postal code, ISO 3166-1 alpha-2 country, and ISO 3166-2 state code when applicable
OrderItem description, quantity, amount, and shipping context when available
DeviceDevice/session identifier, IP address, user agent, browser language, screen dimensions, color depth, and time zone

Do not send placeholders. For the United States, Canada, and China, send a valid ISO 3166-2 subdivision code when the address includes a state or province. Address enrichment may be available for selected account configurations, but the merchant remains responsible for collecting accurate checkout data.

Status and liability guidance#

  • pending_3ds means the 3DS payment flow remains unresolved. It does not guarantee that a visible challenge will appear.
  • processed confirms a completed purchase; authorized confirms reserved funds, with capture still required.
  • denied, cancelled, or expired means the payment did not complete.
  • A successful authentication can provide fraud-liability benefits, but eligibility depends on the card network, ECI, authentication value, transaction type, market rules, and dispute reason. Do not infer liability shift from the payment status alone.

See Payment Workflow & Statuses for the complete lifecycle and 3DS purchase flow for the API integration.

Next steps#

In this section