> ## Documentation Index
> Fetch the complete documentation index at: https://doc.seerbit.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Overview

> Compare the ways your customers can pay and choose the right ones.

SeerBit supports several ways for your customers to pay. Every method is available through both [Simple Checkout](/online-payments/integrations/simple-checkout) and [Standard Checkout](/online-payments/integrations/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

<CardGroup cols={2}>
  <Card title="Card payments" icon="credit-card" href="/payment-methods/card-payment" className="seerbit-nav-card">Mastercard, Visa and Verve, with PIN, OTP and 3-D Secure flows.</Card>
  <Card title="Bank account" icon="landmark" href="/payment-methods/bank-account" className="seerbit-nav-card">Debit a customer's bank account directly with their authorisation.</Card>
  <Card title="Transfer" icon="arrow-left-right" href="/payment-methods/transfer" className="seerbit-nav-card">Give the customer account details to transfer into, and confirm on receipt.</Card>
  <Card title="USSD" icon="hash" href="/payment-methods/ussd-payment" className="seerbit-nav-card">Let customers pay from a feature phone with a short dial code.</Card>
  <Card title="Mobile money" icon="smartphone" href="/payment-methods/mobile-money" className="seerbit-nav-card">Collect through MOMO operators across supported markets.</Card>
  <Card title="In-store POS" icon="square-terminal" href="/in-store/overview" className="seerbit-nav-card">Take card-present payments on a SeerBit terminal.</Card>
</CardGroup>

## Choosing a method

| If you want to | Use |
| - | - |
| Accept the widest range of customers online | [Card payments](/payment-methods/card-payment) |
| Avoid card scheme fees on larger amounts | [Transfer](/payment-methods/transfer) or [bank account](/payment-methods/bank-account) |
| Reach customers without smartphones or cards | [USSD](/payment-methods/ussd-payment) |
| Collect in markets where wallets dominate | [Mobile money](/payment-methods/mobile-money) |
| Charge a customer standing in front of you | [In-store POS](/in-store/overview) |

## 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](/payment-methods/card-payment) 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](/online-payments/integrations/standard-checkout#transaction-fees).

Neither applies if you use [Simple Checkout](/online-payments/integrations/simple-checkout), [Standard Checkout](/online-payments/integrations/standard-checkout) or a [plugin](/online-payments/integrations/e-commerce-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](/online-payments/after-payments/verify-payment) or [webhooks](/online-payments/after-payments/webhook-events) rather than the browser redirect, and handle the `PENDING` state described in the [status codes](/development-resources/responses/seerbit-status-code) reference.

Test credentials for every method are on the [testing page](/test-and-live).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.