When 3D Secure runs as part of Secure Fields or the mobile SDKs, the resulting authentication data is available as payload placeholders in a Vault Forward request. This lets you pass 3DS data alongside card details to downstream endpoints that require it. 3DS forwarding requires a checkout session — useDocumentation Index
Fetch the complete documentation index at: https://docs.gr4vy.com/llms.txt
Use this file to discover all available pages before exploring further.
x-vault-forward-checkout-session instead of x-vault-forward-payment-methods. See CVV & Secure Fields for how to set up the checkout session.
Placeholders
The following 3DS placeholders are available when 3DS authentication has run via a checkout session:| Placeholder | Description |
|---|---|
CARD_3DS_CAVV_1 | Cardholder Authentication Verification Value (CAVV) generated by the issuer. |
CARD_3DS_ECI_1 | Electronic Commerce Indicator (ECI) — the security level of the transaction. |
CARD_3DS_VERSION_1 | 3D Secure protocol version used (for example 2.1.0). |
CARD_3DS_DIRECTORY_RESPONSE_1 | Status returned by the directory server (for example C for Challenge Required). |
CARD_3DS_AUTHENTICATION_RESPONSE_1 | Final result of the authentication challenge (for example Y for Successful). |
CARD_3DS_SERVER_TRANSACTION_ID_1 | UUID assigned to this transaction by the 3DS server. |
CARD_3DS_DS_TRANSACTION_ID_1 | UUID assigned by the Directory Server (dsTransID). |
CARD_3DS_SCHEME_1 | Card scheme used during 3DS (for example visa, mastercard). |
All 3DS placeholders use
_1 because you can only provide one checkout session per Vault Forward request.Example
Conditional logic
3DS values may not always be present — for example, when authentication was not required or the transaction was frictionless. Use template logic to handle missing values gracefully.If/else
Or
Theor operator outputs the first non-empty value: