Forward card data
This endpoint allows to securely forward cardholder data to a certified third-party provider. It will inject sensitive cardholder data from the PCI token into the request before forwarding it.
Authorizations
Headers
Name of a header to set on the forwarded request. Guardian strips the credential your call authenticates with (for example x-api-key) before forwarding; use this pair to send the destination's own credential instead. Only takes effect together with x-own-header-value.
"x-api-key"
The destination's own idempotency key, relayed to the destination unchanged. A key of visible ASCII characters (! to ~) arrives as sent, whether or not idempotency is switched on for your instance. Guardian doesn't check the key and doesn't deduplicate forwards: whether a repeat is safe is up to the destination, and any idempotency header in the response comes from the destination. Must not contain card data. See Idempotency.
"payment-7f3c2a9e-0001"
Body
The payload the caller wants to forward to the third party provider.
To securely handle and inject sensitive cardholder data, predefined templates can be used. These templates help structure and standardize the data injection process while ensuring compliance with security and regulatory requirements.
Response
Success response
The response from the third party provider.