Implementation examples Node.js
Use our APIs to accept cards with 3D Secure authentication through a redirect page. When adding card payments with redirect 3D Secure authentication to your integration, you additionally need to:
- Collect the additional parameters in your payment form.
- Provide the required 3D Secure parameters when making a payment request.
- Handle the redirect.
Requirements
Before starting your integration:
- If building a mobile integration, contact our Support Team to make sure that 3D Secure is triggered in your app.
- Make sure that you have integrated our Card Component for Web, iOS, or Android or built your own UI for collecting shopper's card details.
- If you are using 3D Secure for PSD2 compliance, read our comprehensive PSD2 SCA guide.
Collect additional parameters in your payment form
For higher authentication rates, we strongly recommend that you collect the card holder name, the shopper billing address and email address in advance in your payment form. Deliver these parameters to your backend when making a payment as they are required by the card schemes.
Collect card holder name in your payment form
You can use our Card Component to build your payment form for 3D Secure 2 authentication. Select the channel that you are using below:
Make a payment
Select the channel that you are using below:
Present the payment result
Use theĀ resultCode from the /payments or /payments/details response to present the payment result to your shopper. You will also receive the outcome of the payment asynchronously in a webhook.
For card payments, you can receive the following resultCode
values:
resultCode | Description | Action to take |
---|---|---|
Authorised | The payment was successful. | Inform the shopper that the payment has been successful. If you are using manual capture, you also need to capture the payment. |
Cancelled | The shopper cancelled the payment. | Ask the shopper if they want to continue with the order, or ask them to select a different payment method. |
Error | There was an error when the payment was being processed. For more information, check the
refusalReason
field. |
Inform the shopper that there was an error processing their payment. |
Refused | The payment was refused. For more information, check the
refusalReason
field. |
Ask the shopper to try the payment again using a different payment method. |
Test and go live
Use our test card numbers to test how your integration handles different 3D Secure authentication scenarios.