Interface Authorization

Unique identifier for the object.

String representing the object's type. Objects of the same type share the same value.

The total amount that was authorized or rejected. This amount is in currency and in the smallest currency unit. amount should be the same as merchant_amount, unless currency and merchant_currency are different.

Detailed breakdown of amount components. These amounts are denominated in currency and in the smallest currency unit.

Whether the authorization has been approved.

How the card details were provided.

List of balance transactions associated with this authorization.

You can create physical or virtual cards that are issued to cardholders.

The cardholder to whom this authorization belongs.

Time at which the object was created. Measured in seconds since the Unix epoch.

The currency of the cardholder. This currency can be different from the currency presented at authorization and the merchant_currency field on this authorization. Three-letter ISO currency code, in lowercase. Must be a supported currency.

Fleet-specific information for authorizations using Fleet cards.

Fraud challenges sent to the cardholder, if this authorization was declined for fraud risk reasons.

Information about fuel that was purchased with this transaction. Typically this information is received from the merchant after the authorization has been approved and the fuel dispensed.

Has the value true if the object exists in live mode or the value false if the object exists in test mode.

The total amount that was authorized or rejected. This amount is in the merchant_currency and in the smallest currency unit. merchant_amount should be the same as amount, unless merchant_currency and currency are different.

The local currency that was presented to the cardholder for the authorization. This currency can be different from the cardholder currency and the currency field on this authorization. Three-letter ISO currency code, in lowercase. Must be a supported currency.

Set of key-value pairs that you can attach to an object. This can be useful for storing additional information about the object in a structured format.

Details about the authorization, such as identifiers, set by the card network.

The pending authorization request. This field will only be non-null during an issuing_authorization.request webhook.

History of every time a pending_request authorization was approved/declined, either by you directly or by Stripe (e.g. based on your spending_controls). If the merchant changes the authorization by performing an incremental authorization, you can look at this field to see the previous requests for the authorization. This field can be helpful in determining why a given authorization was approved/declined.

The current status of the authorization in its lifecycle.

Token object used for this authorization. If a network token was not used for this authorization, this field will be null.

List of transactions associated with this authorization.

Treasury details related to this authorization if it was created on a FinancialAccount.

Whether the authorization bypassed fraud risk checks because the cardholder has previously completed a fraud challenge on a similar high-risk authorization from the same merchant.

The digital wallet used for this transaction. One of apple_pay, google_pay, or samsung_pay. Will populate as null when no digital wallet was utilized.