This page is part of the REST API Guides. For 3D Secure at capture time, handled automatically, see Payments Library 3D Secure.
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 thethreeDSAuthentication 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 thecardNumber field with an @ prefix; cvv is optional and can be left out for a tokenized card.
Sending Raw Card Details (Non-Standard)
What’s Next
Charge Payments
Basic charge operations
Authorize & Capture
Hold funds and capture later