Paystack

Accept and reconcile payments across Africa with Paystack. Agents initialize and verify hosted checkout transactions, manage customers and subscription plans, and pay out to bank accounts and mobile-money wallets via transfers.

11 actions API key available

Paystack website ↗ Platform Documentation ↗ Capability data verified 2026-07-28

A new wholesale order arrives with the buyer's email and total

Create Customer registers the buyer and returns the customer_code for everything that follows

Initialize Transaction creates the hosted checkout with the amount in the currency subunit and a saved reference

The authorization_url goes to the buyer by email as their payment link

Verify Transaction confirms data.status is success after the redirect, before fulfillment releases anything

The weekly settlement pass reconciles List Transactions against the supplier balances owed

The finance lead approves the payout batch with recipients and amounts side by side

Initiate Transfer pays each approved supplier from the Paystack balance

What This Integration Enables

Paystack is payment infrastructure for markets where money moves on many rails at once: cards, bank transfers, mobile-money wallets, across NGN, GHS, ZAR, KES, and more, with every amount expressed in the currency subunit. FlowRunner agents run the full loop, collection and disbursement. On the way in, they create customers, initialize hosted checkouts, and enforce the discipline Paystack's own documentation insists on: verify server-side before delivering value. On the way out, they register transfer recipients and initiate payouts from the balance. - Collection: hosted checkout links generated on demand, references saved, status verified before anything ships - Reconciliation: transactions listed by date, status, and customer, matched to the ledger nightly instead of monthly - Recurring revenue: plans created with plan codes ready to bill customers on a schedule - Disbursement: recipient codes for bank accounts and mobile-money wallets, payouts initiated in reviewed batches Money out is the sharp edge. Initiate Transfer moves real funds to real accounts, so it runs behind a [human-in-the-loop](/concepts/human-in-the-loop) gate, while the verification and reconciliation that surround it run unattended.

Without FlowRunner

Payment status by inbox Whether a customer actually paid gets answered by searching email threads and dashboard tabs

Value shipped on redirect The customer lands on the thank-you page and the goods go out, whether or not the charge settled

Payouts as a spreadsheet ritual Supplier and partner payments mean an afternoon of dashboard entry, twice reviewed, still nervous

With FlowRunner

Every charge has a verified answer Verify Transaction runs before fulfillment, every time, and pending is treated as not paid

Reconciliation is a nightly pass Transactions flow to the ledger with references intact, matched while the day is still fresh

Payouts are batched, reviewed, sent Agents assemble transfers with recipient codes and evidence; one approval moves the batch

Use Case Scenarios

Verify before value, without a developer on call

Orders from the storefront generate payment links: Create Customer, then Initialize Transaction with the amount converted to subunits, kobo for a Lagos customer, cents for a Cape Town one, and the authorization_url goes out through [Gmail](/integrations/gmail-service). When the buyer completes checkout, the agent runs Verify Transaction on the saved reference and releases fulfillment only on data.status success. A pending or failed status routes to a retry sequence instead of a shipped box. The rule every payments team knows but enforces inconsistently becomes a workflow that cannot skip the step.

The daily revenue picture across every rail

Each morning the agent runs List Transactions for the previous day and writes the results to [Google Sheets](/integrations/google-sheets): amount, currency, channel, customer, status, reference. Successful charges mirror into [QuickBooks](/integrations/quickbooks-online) as payments for reconciliation, and the day's total posts to [Slack](/integrations/slack) by currency. Disputed or reversed charges get flagged with their full detail from Get Transaction. Finance opens the morning with yesterday already reconciled, which changes month-end from an investigation into a review.

Supplier payouts with one approval and a full trail

A marketplace owes its suppliers weekly. The agent computes balances from the week's verified transactions, registers any new supplier's account with Create Transfer Recipient, nuban bank accounts for Nigerian suppliers, mobile-money wallets where that is how the supplier gets paid, and assembles the batch: recipient, amount in subunits, and the sales evidence behind each number. The finance lead reviews the batch as one decision. On approval, Initiate Transfer moves each payout, and the settlement summary with references and statuses posts to the finance channel. Suppliers get paid on the same day each week, and the trail from sale to payout is complete without anyone building it.

Human-in-Loop Highlight

Initiate Transfer moves money out of the Paystack balance to a recipient_code, and a transfer sent to the wrong recipient does not come back with an apology. A mistyped account resolution, a stale recipient list, or a balance computed from unverified transactions turns into real funds in someone else's account, recoverable only by asking nicely. Paystack itself treats this operation with suspicion, requiring the send-money permission and sometimes OTP finalization. FlowRunner adds the layer above: agents assemble the batch, verify every underlying transaction, and present recipients, amounts, and evidence for a single human approval before any transfer initiates. Create Transfer Recipient rides the same review, because the recipient registered today is the destination money flows to for months. The agent does the arithmetic; a person releases the funds.

Agent processes routinely

Detects exception requiring judgment

Clear match Continues automatically

Ambiguous Routes to human via preferred channel

Human decides

Agent resumes with decision

Agent Capabilities

11 actions

Transactions

Initialize Transaction Creates a transaction and returns the hosted checkout authorization_url plus a reference to verify later. Amounts are in the currency subunit: kobo for NGN, pesewas for GHS, cents for USD and ZAR.
Verify Transaction Confirms a transaction's status by reference. The server-side check that gates fulfillment: data.status success means paid, everything else means not yet.
List Transactions Lists transactions newest first, filterable by status, customer, amount, and date range. The reconciliation feed.
Get Transaction Retrieves one transaction's full detail by its numeric ID, for dispute work and deep reconciliation.

Customers

List Customers Lists customers newest first with email, customer code, and identification status.
Create Customer Creates a customer keyed on a unique email, returning the customer_code used across transactions, subscriptions, and transfers.
Get Customer Retrieves a customer by email or code with their transactions, subscriptions, and authorizations attached, the one-call account picture.

Plans

List Plans Lists subscription plans with billing interval, amount, and the plan_code that subscribes customers.
Create Plan Creates a recurring billing plan with amount in the currency subunit, returning its plan_code.

Transfers

Create Transfer Recipient Registers a bank account or mobile-money wallet as a payout destination, returning the recipient_code transfers are sent to. Reviewed on creation, because it defines where money goes.
Initiate Transfer Sends funds from the Paystack balance to a registered recipient. Real money, gone on send: the action this page's human gate exists for. Requires the Transfers feature and send-money permission, and may require OTP finalization.

Frequently Asked Questions

What can FlowRunner do with Paystack?

FlowRunner agents can run Initialize Transaction, Verify Transaction, and List Transactions in Paystack, plus 8 more actions.

Does connecting Paystack to FlowRunner require OAuth?

No. Paystack connects to FlowRunner with an API key, no OAuth flow required.

Can Paystack trigger a FlowRunner workflow automatically?

Paystack doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.

Start building with Paystack

$100 in credits. No card required. Connect in minutes.

Start Building Free Talk to us