Skip to main content
Ideal for: Debiting a customer’s bank account directly, with their authorisation — useful for larger amounts where card fees bite, and for customers without a card. This payment method allows your customers to make payments through their internet banking portal or by providing their bank account number and authenticating using an OTP sent to their mobile phone number or email registered to that account

How it works

  1. To initiate a direct bank debit payment, make a request to the account payments service with the payments/initiates endpoint.
  2. When the request is made you are expected to get a pending response.
  3. The response from banks differ, some banks will return with a redirect url while others will not.
  4. When a redirect url is returned, you are expected to redirect to the link supplied which will take the customer to the bank page. On this page, customer is expected to enter the OTP sent to their registered phone number or email with the bank. After the OTP is submitted, SeerBit redirects back to the redirect url supplied by the merchant.
  5. When the redirect url is not returned, the transaction would be awaiting validation.
  6. To validate the transaction the customer gets an OTP( one time password) via the registered number with the bank or via email.
  7. Use the OTP entered by the customer and reference to call the payments/validate endpoint to complete the transaction.​
  8. Verify the payment​

Before you use these endpoints

These endpoints are for merchants who want to build their own checkout. You collect the payment details in your own interface and send them to SeerBit, deciding for yourself how the payment experience looks. If you would rather not build and maintain that, use Simple Checkout or Standard Checkout instead — SeerBit renders the payment interface, supports every method, and takes on the compliance burden.

You calculate the fee, not SeerBit

The hosted checkout works out the transaction fee and shows it to the customer. These endpoints do not. SeerBit charges exactly the amount you send. So if your dashboard is set so the customer bears the fee, you must calculate that fee and include it yourself. If you don’t, the fee comes out of your settlement instead — you will receive less than you charged. Set the fee bearer in your dashboard settings, and see transaction fees for how the two models differ.

How methods are selected

Every payment method uses the same endpoint — what changes is the paymentType you send and the extra fields that method needs.

Authentication

All payment method calls are authenticated with a bearer token, generated from your public and secret keys.

Authentication

How to generate the token, and which credential every other SeerBit API expects.

Initialising a Bank Account Payment

For the full specification, see our API Reference POST

Request Sample

The code snippet below shows an example request for initialising this payment

Response Sample

The code snippet below shows an example request for initialising this payment