CreateIdempotencyStatus
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 transaction create request, reported on the create response so a caller can tell from the response alone whether the key it sent protects the charge.
Values
Values:
Values combine: send one or more member names separated by a comma and a space, or the integer sum of their values. Responses carry the names.
NotRequested |
The request carried no idempotencyKey, so there was nothing to deduplicate. A repeat send will charge again. |
KeyIgnored |
The request carried an idempotencyKey, but deduplication is not enabled for this merchant, so the key had no deduplication effect. It is stored with the transaction and remains available through the lookup-by-idempotency-key operation, but a repeat send with the same key will charge again. Ask your provider to enable deduplication for the merchant. |
KeyAccepted |
The request carried an idempotencyKey, deduplication is enabled, and this request claimed the key. This is the original create; a repeat send with the same key inside the deduplication window replays this transaction instead of charging again. |
Replayed |
The idempotencyKey matched a create that had already completed for this merchant, so nothing was charged. The response body is that original transaction exactly as it stands, original identifiers and timestamps included. |
Fields
| Field | Type | Description |
|---|
This model has no documented fields.