Skip to main content
SeerBit supports several ways for your customers to pay. Every method is available through both Simple Checkout and Standard Checkout, and all of them initialise through the same endpoint — POST /api/v2/payments/initiates — with a different paymentType. Offering more than one method generally raises conversion, because customers differ in what they have available.

​
Available methods

Card payments

Mastercard, Visa and Verve, with PIN, OTP and 3-D Secure flows.

Bank account

Debit a customer’s bank account directly with their authorisation.

Transfer

Give the customer account details to transfer into, and confirm on receipt.

USSD

Let customers pay from a feature phone with a short dial code.

Mobile money

Collect through MOMO operators across supported markets.

In-store POS

Take card-present payments on a SeerBit terminal.

​
Choosing a method

​
Building your own checkout

The pages above document the direct API — POST /api/v2/payments/initiates — for merchants who want to control how the payment interface looks. Two things follow from that:
  • Card payments require PCI DSS certification. Your server would be receiving raw card details, so SeerBit will not enable card payments on your account without a valid certificate. Every other method is unaffected.
  • You calculate the transaction fee. Unlike the hosted checkout, these endpoints charge exactly the amount you send — so if the customer bears the fee, you must add it. See transaction fees.
Neither applies if you use Simple Checkout, Standard Checkout or a plugin.

​
Before you go live

Some methods settle asynchronously — a customer can leave the page before the payment resolves. Always confirm the outcome with payment verification or webhooks rather than the browser redirect, and handle the PENDING state described in the status codes reference. Test credentials for every method are on the testing page.