Forward cryptogram
Securely forward a request to a certified third-party provider, resolving it against a cryptogram reference. Guardian retrieves the cryptogram stored against the reference and injects it, along with other PCI-scoped fields (token PAN, expiry, ECI, and more), into your request body before forwarding. This mirrors Forward card data and lets SAQ-A merchants use network tokens without ever handling the raw cryptogram. The reference is single-use and is invalidated after the first successful forward.
Documentation Index
Fetch the complete documentation index at: https://developer.hellgate.io/llms.txt
Use this file to discover all available pages before exploring further.
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 DPAN), {{ 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.