Payment Flow
How a payment travels from your app to settlement, and where your integration participates.
End-to-end lifecycle
Your server calls Initiate Payment with a signed request and gets a payment_link + transaction_id.
GrowthBnk selects a gateway server-side using your routing rules.
The chosen gateway hosts the checkout for the customer.
The customer completes payment on the hosted page.
The gateway returns the customer to your surl/furl. Treat this as a hint, not proof.
GrowthBnk POSTs a signed event to your webhook URL — verify it and act on it.
Your system records the terminal status (SUCCESS/FAILURE/DROP/CANCELLED). Reconcile with Transaction Status if needed.
Funds are settled to your connected bank account and available for reconciliation.
The customer redirect (callback) can be interrupted or spoofed. Only mark an order paid after a verified webhook or a Transaction Status check returns SUCCESS.
Who does what
| Step | Owner | Your action |
|---|---|---|
| Initiate | You → GrowthBnk | Sign & POST Initiate Payment; store transaction_id. |
| Route & process | GrowthBnk → Gateway | Nothing — server-side. |
| Pay | Customer | Redirect to payment_link. |
| Notify | GrowthBnk → You | Verify webhook signature; update order. |
| Reconcile | You | Poll status as a backstop; reconcile settlement. |
Related
Webhooks · Transaction Status · Refunds · Integration Checklist