Retrieves a single authorization by its ID, including its current status, amount, and any associated onchain transactions.
A JWT signed using your CDP API Key Secret, encoded in base64. Refer to the Generate Bearer Token section of our Authentication docs for information on how to generate your Bearer Token.
The unique identifier of the payment session.
The ID of the payment session, a UUID prefixed by paymentSession_.
^paymentSession_[a-f0-9\-]{36}$"paymentSession_82c879c1-84e1-44ed-a8c2-1ac239cf09ad"
The unique identifier of the authorization.
The ID of the authorization, a UUID prefixed by authorization_.
^authorization_[a-f0-9\-]{36}$"authorization_82c879c1-84e1-44ed-a8c2-1ac239cf09ad"
Successfully retrieved authorization.
A hold placed on the payer's funds. Once authorized, the merchant can capture (collect) the funds. Only one authorization is allowed per session.
The unique identifier of the authorization.
^authorization_[a-f0-9\-]{36}$"authorization_82c879c1-84e1-44ed-a8c2-1ac239cf09ad"
The ID of the payment session this authorization belongs to.
^paymentSession_[a-f0-9\-]{36}$"paymentSession_82c879c1-84e1-44ed-a8c2-1ac239cf09ad"
The current status of the authorization.
pending, succeeded, failed "pending"
A decimal representation of the authorized amount, denominated in the session's asset.
"1.00"
An error that occurred during a payment operation.
{
"code": "insufficient_funds",
"message": "The payer does not have sufficient funds.",
"occurredAt": "2025-06-15T12:00:00.000Z"
}Optional metadata as key-value pairs. Use this to store additional structured information on a resource, such as customer IDs, order references, or any application-specific data. Up to 10 key/value pairs may be provided. Keys and values are both strings. Keys must be ≤ 40 characters; values must be ≤ 500 characters.
{
"customer_id": "cust_12345",
"order_reference": "order-67890"
}The payer for this authorization. For wallet authorizations, this is the blockchain address that signed the payloads. For Coinbase authorizations, this is the authenticated Coinbase account. This value is also reflected on the parent payment session's source field after a successful authorization.
{
"address": "0xAbC1234567890aBcDeF1234567890AbCdEf123456",
"network": "base",
"asset": "usdc"
}The onchain transactions associated with this authorization.
[
{
"transactionHash": "0xabc123def456789012345678901234567890abcdef1234567890abcdef123456",
"network": "base"
}
]The UTC ISO 8601 timestamp at which the authorization was created.
"2025-06-15T12:00:00.000Z"
The UTC ISO 8601 timestamp at which the authorization was last updated.
"2025-06-15T12:01:00.000Z"