Detailed breakdown of amount components. These amounts are denominated in currency and in the smallest currency unit.
Whether this request was approved.
A code created by Stripe which is shared with the merchant to validate the authorization. This field will be populated if the authorization message was approved. The code typically starts with the letter "S", followed by a six-digit number. For example, "S498162". Please note that the code is not guaranteed to be unique across authorizations.
Time at which the object was created. Measured in seconds since the Unix epoch.
Three-letter ISO currency code, in lowercase. Must be a supported currency.
The pending_request.merchant_amount at the time of the request, presented in the merchant_currency and in the smallest currency unit.
The currency that was collected by the merchant and presented to the cardholder for the authorization. Three-letter ISO currency code, in lowercase. Must be a supported currency.
The card network's estimate of the likelihood that an authorization is fraudulent. Takes on values between 1 and 99.
When an authorization is approved or declined by you or by Stripe, this field provides additional detail on the reason for the outcome.
If the request_history.reason is webhook_error because the direct webhook response is invalid (for example, parsing errors or missing parameters), we surface a more detailed error message via this field.
Time when the card network received an authorization request from the acquirer in UTC. Referred to by networks as transmission time.
The
pending_request.amountat the time of the request, presented in your card's currency and in the smallest currency unit. Stripe held this amount from your account to fund the authorization if the request was approved.