# StandaloneTokenCreateIdempotencyStatus

A model the API reference uses in a request or a response. The operation pages link every field typed as this model here.

What create idempotency actually did to a standalone token-create request, reported on the create
response so a caller can tell from the response alone whether the key it sent protected the mint.

## Values

| Value | Description |
| --- | --- |
| `NotRequested` | The request carried no idempotencyKey, so there was nothing to deduplicate. A repeat send mints a second token for the same card. |
| `KeyAccepted` | The request carried an idempotencyKey and this request claimed it. This is the original create; a repeat send of the same request inside the deduplication window returns this token instead of minting another. |
| `Replayed` | The idempotencyKey matched a create that had already produced a token for this merchant and credential, so nothing was minted. The response body is that original token exactly as it stands, with its original identifiers and public reference. |

## See also

- [All documentation](https://devportal.demo.winkpg.io/llms.txt): the machine-readable index of every public page on this site.