Skip to main content
Where the rest of these docs cover money coming in, this section covers money going out. Two products work together:

Pocket

The wallet your funds sit in. Create sub-pockets, check balances, move money between pockets, and look up transactions.

Payout

Send funds from a Pocket to a bank account — one transfer at a time, or many in a single batch.

​
How they relate

A Pocket is the balance. Every merchant approved for payouts gets a pocket ID, and settlements from your collections land there. You can subdivide a pocket into sub-pockets to keep funds separated — by branch, by department, by client. A Payout moves money out of a pocket to an external bank account. The pocket is the source; the payout is the instruction.
Note: Payouts require approval on your SeerBit merchant dashboard before they can be used via the API.
Live only: Pocket and Payout have no test mode — no test keys and no sandbox. Every operation in this section works on real balances and moves real funds.

​
Choosing an operation

​
The payout flow

Payouts are deliberately harder to trigger than collections, because they move money away from you. Every payout passes through four steps:
1

Authenticate

Exchange your pocket credentials for a bearer token.
2

Sign the request

Generate an X-Seerbit-Signature — an HMAC-SHA256 of the exact raw request body, signed with your secret key.
3

Initiate

Submit the transfer instruction. Single and bulk use the same endpoint; bulk adds a batchReference and a transfers array.
4

Confirm

Authorise the transfer with a second factor — an email OTP by default, or an authenticator code or transaction PIN if your pocket requires one. Nothing moves until this step completes. See Two-factor authentication.
Full request and response detail for each step is on the Payout page.

​
Before you integrate

  • Your secret key signs every payout request. Keep it server-side — a leaked payout key is materially worse than a leaked collection key, because it can move funds out.
  • batchReference on a bulk payout is your idempotency key. Reusing one is how you avoid paying a batch twice after a timeout.
  • Payouts are approval-gated. If the API rejects you before you reach the signature step, check your dashboard approval status first.
  • If your pocket requires an authenticator code or PIN, set it up before your first payout. On a strict channel, a payout cannot be confirmed without one.