Loading article…
Loading article…
Last updated on Aug 24, 2026
Test the 3D Secure (3DS) experience before rolling it out on your live Advanced Billing site. See Understand PSD2, SCA, and 3DS for more on the underlying PSD2 and SCA requirements.
Advanced Billing currently supports 3DS on the following gateways: Stripe, Braintree, CyberSource, Windcave (formerly Payment Express), Adyen, and BlueSnap.
Complete each step below, in order, to test and implement 3D Secure. Select each link for more information:
Advanced Billing offers two ways to authenticate your customers' PSD2 transactions: a pre-authentication or post-authentication flow. There are several differences in how each of these authentications handles transactions that are flagged for SCA.
The authentication path controls when the customer is authenticated through 3D Secure.
Pre-authentication occurs at the same time the user enters their card details. This makes it easy for you, the merchant, since no further action is required on your end. This method surfaces a pop-up that authenticates the customer for $0, which does not necessarily match the final purchase price of the product.
Pre-authentication is applicable for:
To enable pre-authentication for supported gateways on Maxio.js, add the flag threeDSecure: true to your load.js form.
With post-authentication, Advanced Billing waits until the token is used to check the need for SCA. In other words, a Maxio.js token is not authenticated until it is used. For API Subscription creation requests that fail due to SCA, Advanced Billing returns an action_link URL that you can share with the user. This URL leads to a page where authentication can be completed. See 3D Secure Post-Authentication Flow for details on implementing this workflow.
Post-authentication is applicable for:
Still need help?
Reach out and our support team will take it from here.