HppSessionCreateIdempotencyStatus
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 session-create request, reported on the create response so a caller can tell from the response alone whether the key it sent protects the link.
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 opens a second session. |
KeyIgnored |
The request carried an idempotencyKey, but deduplication is not enabled for this merchant, so the key had no effect and a repeat send opens a second session. Ask your provider to enable create idempotency 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 of the same request inside the deduplication window replays this session instead of opening another. |
Replayed |
The idempotencyKey matched a create that had already completed for this merchant and credential, so no new session was opened. The response body is that original session exactly as it stands, with its original identifiers, short token, link and expiry. |
Fields
| Field | Type | Description |
|---|
This model has no documented fields.