Docs

3-D Secure

Many cards require 3-D Secure (3DS) authentication — the step where a customer confirms a payment with their bank, for example via a one-time code or their banking app. SecurePayAPI handles this for you.

What you need to do

Nothing extra. Both embedded checkout and hosted checkout run the full authentication flow automatically:

  • If the bank doesn't require a challenge, the payment completes seamlessly.
  • If a challenge is required, the customer is shown the bank's prompt right inside the checkout, then the payment completes.

You're notified of the final result the same way regardless of whether a challenge happened — a success message from the widget, or a completed status on the hosted page.

Note

Because authentication is built in, you don't handle card data or authentication redirects yourself. This also helps keep your integration's compliance scope small.

Testing the flow

See Testing for how to validate both the frictionless and the challenge paths before going live.

© SecurePayAPI · Built with Markdoc