Room left
What a cardholder wants before they try, and what a support agent needs when they ask why not.
What a cardholder wants before they try, and what a support agent needs when they ask why not.
Authorization
OAuth2PasswordBearer In: header
Path Parameters
uuidCookie Parameters
Response Body
application/json
application/json
curl -X GET "https://example.com/api/b/v1/cards/497f6eca-6276-4993-bfeb-53cbbbba6f08/remaining"{}Change where the card may be used PUT
Category and country rules, separate from the amount ceilings. Takes effect on the next authorisation, like the limits, and for the same reason: a rule added now does not reverse a purchase already made. A refusal here is reported as its own decline reason — `category_not_allowed` or `country_not_allowed` — rather than as a limit breach, because the two lead to different actions. Somebody over a limit waits or asks for a raise; somebody blocked by category is holding the wrong card. **A missing value passes.** Not every network sends a category or a country on every authorisation, and refusing on absence would decline ordinary spend for a field the acquirer chose not to populate.
Stop it, for now POST
The reason is required: a frozen card is a person unable to buy something, and "it just stopped working" is the support call.