A PUT request sent to freeze a card.
If you believe a cardholder's card may have been lost, stolen, or involved in potential fraudulent behavior,
you can freeze the card.
This freeze will prevent any new transactions but will still permit the following actions:
- ongoing payments
- authorization requests connected to a prior transaction, such as an additional authorization
- refunds
- chargebacks
- reversals
| Time | Status | User Agent | |
|---|---|---|---|
Retrieving recent requests… | |||
The server cannot or will not process the request due to something that is perceived to be a client error (e.g., malformed request syntax, invalid request message framing, or deceptive request routing).
Although the HTTP standard specifies "unauthorized", semantically this response means "unauthenticated". That is, the client must authenticate itself to get the requested response.
The client does not have access rights to the content; that is, it is unauthorized, so the server is refusing to give the requested resource. Unlike 401 Unauthorized, the client's identity is known to the server.
The request was well-formed but was unable to be followed due to semantic errors.
The user has sent too many requests in a given amount of time ("rate limiting").
The server has encountered a situation it does not know how to handle.