Payments
Charge API
In a nutshell
Understand when to use the Charge API and how its multi-step payment flow works.
The Charge API is Paystack’s direct payment API for businesses that want to control how a payment is initiated and how each customer prompt is handled. Instead of sending customers to a hosted Checkout flow first, you submit a charge request to Paystack and respond to the result Paystack returns.
That makes the Charge API useful when you need a custom payment UI, tighter control over channel-specific behavior, or a server-orchestrated flow inside a mobile app, embedded product, or specialized checkout experience. It is also useful when the payment method itself determines the user experience, such as card prompts, temporary bank transfer accounts, USSD, or mobile money authorization on the customer’s phone.
The flow is usually multi-step.
First, you submit a charge request with the customer, amount, currency, and channel-specific fields. For cards, that includes the card object. For bank transfer, it includes bank_transfer. For mobile money, it includes mobile_money.
Next, Paystack returns a charge state that tells you what should happen next. A card charge may return send_pin, send_otp, send_phone, send_birthday, send_address, open_url, pending, success, or failed. Mobile money and some other channels can return pay_offline, which means the customer must finish authorization on another device or network surface. Bank transfer flows can remain pending while the customer completes the transfer.
Finally, your server confirms the result with a webhook or the verify endpoint, because the payment may complete after the initial API response. See Payment flow for the full lifecycle.
Compared with Checkout, the Charge API gives you more control but also more responsibility. Your application must decide how to display prompts, when to poll or verify, how to handle redirects, and how to manage failed or incomplete flows.
That extra control has compliance implications. If you collect raw card details in your own interface, your business must be PCI DSS compliant. Paystack explicitly recommends that only compliant businesses use the direct card charging flow. If you want Paystack to host the payment UI and reduce scope, Checkout is usually the better fit.
In practice, choose Checkout when you want speed and a hosted payment surface. Choose the Charge API when you want channel-level control and are prepared to own the operational and compliance complexity that comes with it.