Simulate a card authorization

Authorization involves verifying a card's validity,
ensuring business criteria are fulfilled, and checking fund availability before temporarily reserving said funds.
Use this endpoint to emulate an authorization transaction by providing the cardId and other pertinent authorization information in your query.

Body Params
string
required

The UUID of the card used for this authorization

string
required

The authorization amount in USD

Responses

400

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).

401

Although the HTTP standard specifies "unauthorized", semantically this response means "unauthenticated". That is, the client must authenticate itself to get the requested response.

403

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.

429

The user has sent too many requests in a given amount of time ("rate limiting").

500

The server has encountered a situation it does not know how to handle.

Language
Credentials
Choose an example:
application/json