Skip to main content
This page is part of the REST API Guides. For 3D Secure at capture time, handled automatically, see Payments Library 3D Secure.
Prerequisites: API key, Payment Gateway Account with a 3DS-capable gateway, and a 3DS authentication provider. 3D Secure (3DS) is an authentication protocol that adds an extra layer of security for online card transactions. It helps reduce fraud and liability by verifying the cardholder’s identity before completing the payment.
On this path Orchestra does not perform the authentication. You authenticate the cardholder with your own 3DS provider and pass the results to Orchestra, which forwards them to the PSP. No 3DS configuration is required on your Orchestra account.If you want Orchestra to run the 3DS challenge for you, use the Payments Library or the eWallet operations endpoints instead. That path does require 3DS merchant details on the CardPay eWallet account.

Passing 3DS Authentication Data to PSPs

Many of Orchestra’s PSP integrations support receiving 3DS authentication data. If you have already performed 3DS authentication for a card (using your own 3DS provider or a third-party service), you can pass those authentication results to Orchestra when making a charge request.
For a complete list of PSP integrations that support 3DS data, see 3D Secure Integrations.

3DS Authentication Fields

When you have 3DS authentication results, include them in the threeDSAuthentication object within the card details:

Example: Charge with 3DS Data

The standard integration passes 3DS authentication data alongside a token captured by the Payments Library. Reference it in the cardNumber field with an @ prefix; cvv is optional and can be left out for a tokenized card.
If your backend already lawfully holds card data and needs to send it directly, see Sending Raw Card Details (Non-Standard) below.

Sending Raw Card Details (Non-Standard)

This example shows raw card details for completeness. Sending raw card data means it passes through your systems and puts you in PCI DSS scope. The standard integration captures the card with the Payments Library and references it here as a token (an @TOKEN value in the cardNumber field); see Example: Charge with 3DS Data above.

What’s Next

Charge Payments

Basic charge operations

Authorize & Capture

Hold funds and capture later