Glossary
Payment status
A payment status is the state of a payment in its life: created, pending the payer's action, authorised, paid, declined, expired, cancelled, refunded in part or in full, charged back. Final statuses do not change on their own; pending ones change when the provider answers or the payer acts. Merchants read the status through webhooks and the API rather than the redirect, because the redirect may never arrive while the money still does.
Pending is a state, not an error
Bank transfers, vouchers, QR codes and many wallets are paid outside the session: the payment stays pending with an expiry while the payer acts, then becomes paid, expired or, rarely, paid late after expiry, which the platform must handle rather than drop. Cards may be pending during 3-D Secure or a provider timeout, with the final answer arriving by callback.
Reading statuses correctly
A redirect to the success page is not proof of payment; the webhook or a status call is. Refunds and chargebacks are their own records linked to the payment, so a paid payment can carry a partial refund and still be paid. Statuses from different providers are mapped to one platform set, with the provider’s raw status kept for support.
On the platform
Tranzify keeps one status model for all methods, records every status change with its source and time in the journal, pushes changes by webhook with retries, lets the back office correct a status manually with the change logged, and shows the whole history in the trace.
Updated: 2026-11-08