To benefit from a streamlined integration process, we recommend using Checkout.com to authenticate 3D Secure payments. If you wish you to use a third-party provider, you will need to include additional fields in your request.
Use the details below to set up your request.
For the full specification, as well as complete request and response examples, see our API reference.
Use the valid secret key of your Checkout.com account. You can find this in the Hub.
Information required for 3D Secure payments.
Indicates your preference for whether or not a 3DS challenge should be performed. The customer’s bank has the final say on whether the customer is challenged. If 3ds.exemption and 3ds.challenge_indicator are provided, then 3ds.exemption overrides 3ds.challenge_indicator.
The Electronic Commerce Indicator security level associated with the token. Required unless the previous_payment_id is specified. For 3D Secure payments the ECI must be provided in the 3ds payment field.
Whether to process this payment as a 3D Secure. Set this to true.
Requests an SCA exemption for the transaction. The customer’s bank has the final say on whether or not it applies. If the requested 3ds.exemption is not supported or enabled, 3ds.challenge_indicator is used as a fallback.