less than a minute read • Updated 20 hours ago
Transaction status reference
The status values a transaction can have, and what each one means when handling webhook payloads.
Status | Description |
|---|---|
| Transaction is complete |
| Transaction is complete |
| Transaction is complete, but payment is only authorized |
| (beta) The transaction payment is being captured; check again for final status |
| (beta) Transaction is complete, and the payment (previously authorized or verified) has been captured |
| The transaction has been declined by the gateway |
| The transaction has been completed by the customer, but a final status on the payment has not been received from the gateway. This status will be updated once a final response is received |
| The transaction has been rejected by the gateway |
| (beta) The transaction has been voided by the store |
| (beta) The transaction is being refunded; check again for final status |
| (beta) The transaction has been refunded |
| The transaction has been completed by the customer, and the payment information has been verified, but no payment has actually been taken |
| There was a problem with this transaction; check the transaction report in the administration for details |
Notes
Statuses marked “(beta)” are part of the beta advanced transaction editing functionality, and only apply if your store is enabled for that functionality.
The
verifiedstatus only applies to gateways that support verifying payment details (if configurable in your payment settings). This can happen if a gateway is set to only verify, or if it was a $0 transaction (like a future subscription) and the payment details were only verified as valid.Some gateways trigger multiple webhooks for a single transaction as the status changes from
pendingto a final status.