409 Conflict
The change cannot go to the wallet
- Code
change_to_wallet_unavailable- Status
409Conflict- Type
https://errors.clavian.io/change-to-wallet-unavailable
What it means
A cash overpayment’s change cannot be credited to the player’s wallet on this payment: the tender is not cash, the sale names no player, nothing was overpaid, or the venue’s wallet is off or taxes top-ups at sale rather than redemption.
What to do
Hand the change back in cash instead, or attach a player and take the payment again where the wallet is on and taxes top-ups at redemption. The same payment is refused the same way.
Example
The API answers with status 409 and this body, as application/problem+json. A detail may be added, saying what went wrong this time; it is for people, and changes.
{
"type": "https://errors.clavian.io/change-to-wallet-unavailable",
"title": "The change cannot go to the wallet",
"status": 409,
"code": "change_to_wallet_unavailable",
"requestId": "req_01k5znw4hmfay8vvr14d2pf2db"
}
Endpoints that return it
From the OpenAPI document, every endpoint that names it among its answers:
POST /v1/organizations/{organizationId}/venues/{venueId}/sales/{saleId}/paymentsTake a tender against a sale