Payments
Payment flow
In a nutshell
Understand the full lifecycle of a Paystack transaction from initialization to settlement.
Every Paystack transaction follows the same pattern, no matter which payment channel the customer eventually uses. A card payment, bank transfer, mobile money payment, or USSD payment may look different to the customer, but the integration model is the same: your server starts the transaction, the customer authorizes it, and your server confirms the outcome before you deliver value. Thinking about payments in these three stages makes it easier to build a reliable flow that works across channels.
The flow starts with initialization. Your server creates a transaction and receives identifiers such as an access_code or an authorization_url. At this stage, Paystack has not collected money yet; it has only created a payment session with the amount, customer details, reference, and any routing details your integration needs. Initialization should always happen on your server so your secret key stays protected and your system remains the source of truth for the transaction details.
The next stage is authorization. This is when the customer actually tries to pay, whether through Popup, a redirect checkout page, or a direct API flow for channels like bank transfer or USSD. During this period, the transaction can move from an initialized state into an active one while the customer enters card details, approves a debit, makes a transfer, or completes a bank or network prompt. Different channels may take different amounts of time, but they are all part of the same authorization stage.
The final stage is verification or confirmation. Your server should confirm the outcome through a webhook, the verify endpoint, or both before treating the payment as complete. This is the moment where your business decides whether to deliver a product, mark an invoice as paid, or update an internal ledger. A callback or redirect alone is not proof of payment; only a confirmed transaction status is. Once verified, the transaction settles according to Paystack's normal settlement timelines.
For what each transaction status means and how to handle it, see Transaction statuses.
Info
The payment channel changes how the customer authorizes the payment, not the underlying lifecycle. Your integration should always model payments as initialize, authorize, then verify.