Checkout authorizations
Get a checkout authorization
The authoritative state of one authorization, including the processor response once approved.
GET
string
required
The authorization id.
string
awaiting_approval, approved, submitted_on_device (hosted-form processors only; no processor evidence exists), declined, or expired.object
On
approved in token mode: the processor’s response to replay into the paused request.object
On
approved in cse mode: the encrypted card fields to write into the paused body, plus remove for sibling keys to drop.string
stripe_payment_intent, hosted_form_sum, or display_only.boolean | null
Whether what the processor charged matches the approved amount. Null when there was nothing to compare.
string | null
captured, authorized, none, or null.string
On
declined: user_declined, amount_mismatch, intent_not_confirmable, or processor_refused (with psp_error_code).object
Optional on a Razorpay
processor_refused result: bounded reason, source, step, payment_id, and order_id identifiers reported by the processor. Raw response bodies and descriptions are excluded. Older records may not contain these details.boolean
True when a device may already have sent the card. On
expired, treat the outcome as unknown and check the processor.processor_refused means the device reported a rejected processor request. A generic code such as Razorpay’s BAD_REQUEST_ERROR does not establish an issuer decline or prove that nothing was charged. Check the merchant payment status before starting another attempt.