---
title: "Generate cryptogram for a Network Token"
method: POST
path: "/payment/instruments/{instrumentId}/generateCryptogram"
tags: ["Instruments"]
---

# Generate cryptogram for a Network Token

`POST /payment/instruments/{instrumentId}/generateCryptogram`

Generate cryptogram for a Network Token of a given instrument.

## Path parameters

- `instrumentId` string, uuid, required

## Headers

- `x-idempotency-key` string, uuid, required

## Request body

- object
  - `amount` object, required
    - `value` string, required — Decimal amount of the major currency unit. Can be any precision.
    - `currency` string, required — 3-letter ISO currency code.
  - `riskData` object
    - `ip4address` string — IPv4 address of the device.
  - `providerConfigId` string, uuid — Optional. The ID of the network token provider config to use for cryptogram generation. When provided, the request validates the config with the same rules as network token provision. When omitted, the workflow resolves the provider config from the instrument token path or, for legacy tokens without metadata, falls back to the active provider config only when it is unambiguous.

## Response `200`

Success.

- object
  - `success` boolean, required — Whether or not a cryptogram was successfully generated.

## Other responses

- `400` — Bad Request.
- `401` — Unauthorized.
- `403` — Forbidden.
- `404` — Not Found.
- `429` — Too Many Requests.

---

[API](https://skmtc.net/payrails/apis/payrails-api-reference.md) · [All operations](https://skmtc.net/payrails/apis/payrails-api-reference/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/payrails/payrails-api-reference/revisions/9dd2f0158582/schema)