Generate Network Token Cryptogram
Generates a fresh, single-use network token cryptogram for a vaulted card so it can be authorized on an external PSP.
vaulted_token, the same identifier you use in Create Payment. Yuno resolves the card’s current network token internally and absorbs token rotation, so you always receive a consistent, current (DPAN, cryptogram, ECI) set.
How it works
- Request a cryptogram right before you authorize. Every call generates a fresh, single-use cryptogram from the scheme: there is no idempotency, and duplicate calls return new cryptograms (no money moves).
- Submit
network_token.number(DPAN),cryptogram, andecito your PSP as a network-token transaction. - If the authorization is declined and you retry, request a new cryptogram first. A used or stale cryptogram cannot be replayed.
Cryptogram-only mode
Sendinclude_network_token: false and the response omits network_token.number (the DPAN) and network_token.token_data entirely. The network_token object keeps its non-PAN-equivalent metadata (network, status, par, network_token_id), and the response carries cryptogram and eci as usual. Because no PAN-equivalent data is returned, this mode does not require PCI certification.
Pair it with the Forward Proxy to run a network-token transaction end-to-end without PAN-equivalent data ever entering your systems:
- Request the cryptogram with
include_network_token: false. - Build the forward request with the
{{vaulted_token.<TOKEN>.network_token_number}}expression (and thenetwork_token_expiration_*expressions) where the destination expects the DPAN. Include thecryptogramvalue directly in the body, since cryptograms are generated per transaction and the proxy does not resolve them as expressions. - Send it through the proxy immediately: the proxy resolves the card’s current DPAN at forward time, and the cryptogram is bound to a specific DPAN. Requesting the cryptogram right before the forward keeps the pair consistent. A delay spanning a token rotation would make them mismatch.
network_token in the response gets a clear rejection, never a silently degraded response shape.
Requirements
To use this endpoint your organization must:- Have the product enabled for your organization.
- Be onboarded for network tokens for the card’s brand and the requested
country. - Be a PCI-certified merchant to receive the network token (DPAN) in the response. Cryptogram-only mode (
include_network_token: false) does not require PCI certification.
vaulted_token must be an enrolled card of your organization that already has an active network token.
Supported networks: Visa and Mastercard.
network_transaction_id and do not require a cryptogram. This endpoint is for customer-initiated transactions that need a fresh cryptogram.Cryptogram lifetime
The cryptogram is single-use. Request it immediately before you authorize, and do not cache it.expires_at is the latest time at which the scheme accepts the cryptogram. It is the validity of the cryptogram, not of the network token or the card.
- A timestamp (today, Mastercard): treat it as a hard limit. A cryptogram submitted after
expires_atis declined. null(today, Visa): the network publishes no validity for this cryptogram. This does not mean it never expires. Use it right away.
Errors
Errors return acode and a messages array. The exact messages value per code:
vaulted_token that doesn’t exist and one that belongs to another organization both return the same PAYMENT_METHOD_NOT_FOUND, so there is no existence leak.Authorizations
Body
The vaulted token of the card, the same identifier used as payment_method.vaulted_token in Create Payment. The card must be an enrolled card of your organization with an active network token.
"9b2f4b1c-7f3a-4c2e-9b1a-2b3c4d5e6f70"
Optional. Whether the response includes the PAN-equivalent parts of the network token: network_token.number (the DPAN) and network_token.token_data. Defaults to true, which requires your organization to be a PCI-certified merchant. Send false for a cryptogram-only response with no PAN-equivalent data (the network_token object keeps network, status, par and network_token_id) — available without PCI certification, designed to pair with the Forward Proxy, which resolves the DPAN at forward time via the network_token_number expression. A non-PCI organization that sends true or omits the field receives 403 NETWORK_TOKEN_RETURN_NOT_ALLOWED.
false
Response
Cryptogram generated.
Latest time (UTC) at which the scheme accepts this cryptogram. It is the validity of the cryptogram, not of the network token or the card. null when the network publishes no validity for the cryptogram (today, Visa). Either way, request a new cryptogram for every authorization attempt and do not cache it.
"2026-07-21T14:32:10Z"