Forward cryptogram
Forward a request to a certified third-party provider with cryptogram data injected server-side, so it never touches your systems. This lets SAQ-A merchants use network tokens without ever handling a raw cryptogram, and mirrors Forward card data.
- Resolves the single-use
x-cryptogram-referencereturned by Request cryptogram inreferencemode. - Injects the cryptogram and other PCI-scoped fields (token PAN, expiry, ECI, and more) into your request body via placeholders.
- Forwards the result to the
x-destination-url.
See Network Tokens for the full placeholder list.
Authorizations
Headers
The cryptogram_reference UUID returned by Request cryptogram in reference mode. Single-use and short-lived.
The target URL to which the request shall be forwarded. Guardian forwards calls only to whitelisted destination URLs (major payment providers are included by default). Contact support to whitelist a custom URL.
Path Parameters
The ID of the network token.
Body
The payload to forward to the third-party provider.
Use placeholders to inject sensitive, cryptogram-derived data on the fly. Available placeholders include
{{ cryptogram }}, {{ dynamic_cvv }}, {{ eci }}, {{ expiry_month }}, {{ expiry_year }}, {{ number }}
(the network token number / TPAN), {{ type }}, {{ scheme_reference }}, {{ network_token_id }}, and {{ network_token_type }}.
Append | unwrap to emit a value as its native type instead of a string, e.g. {{ expiry_month | unwrap }}.
See Network Tokens for the full placeholder list.
Response
Success response
The response from the third-party provider.