Plan payer authentication with 3DS
Handle issuer authentication before submitting a payment.
Separate authentication from payment
3DS exchanges information with the issuer to authenticate the cardholder. Authentication may finish without interaction or require a challenge. Neither outcome is itself a captured payment.
Preserve the interaction
The documented Gateway.js flow initializes the 3DS service, creates its interface, mounts it and listens for challenge, completion and failure events. Keep the mount point stable during framework rendering.
Connect the backend
On completion, send the authentication results to your backend for the matching payment. Preserve the required result fields and bind them to the same amount and order. Keep payment credentials server-side.
Test the failure paths
Review frictionless completion, challenge success, cancellation, timeout and failure. Decide which results permit a payment attempt; do not treat every callback as approval. Integration planning overview. Exact component configuration, account enablement and issuer challenge behavior require separate verification.