Skip to main content
SeerBit is a payment platform for African markets. These docs cover four things you can build:

Collect payments online

Take card, bank, transfer, USSD and mobile money payments on your website or app.

Take payments in store

Push a payment to a SeerBit POS terminal from your ERP or till software.

Pay people out

Send funds from your SeerBit Pocket to bank accounts, singly or in bulk.

Build a marketplace

Split one payment across several accounts and settle each party automatically.

Choosing an integration

Most people start by collecting payments online. There are three ways to do it, and the right one depends on how much control you need over the payment experience. All three are PCI compliant and support every payment method on your account. You can change your mind later; they use the same keys and the same transaction records.

How an integration fits together

Whichever path you pick, a payment follows the same shape:
1

Authenticate

Exchange your keys for a token, or sign the request — see Authentication.
2

Create the transaction

Tell SeerBit the amount, the currency and who is paying.
3

Let the customer pay

They complete the payment on a SeerBit page, an inline form, or a terminal.
4

Confirm the result

Read the outcome from a webhook or by verifying the payment — never from the browser redirect alone.
That last step is the one people skip, and it is the one that causes unfulfilled orders and double shipments. Build it in from the start.

Start here

Quickstart

Take a test payment end to end in about ten minutes.

Authentication

Keys, tokens and request signing — and which applies to what.

Test and live modes

Test cards, how the two modes differ, and how to tell them apart.

Go live

KYC, swapping keys, and the final production check.
Questions? Reach the team at SeerBit Support.