Skip to main content
Ideal for: Returning money to a customer after a payment has already succeeded — a cancelled order, a returned item, a billing mistake.

​
Dashboard or API?

There are two ways to issue a refund. The API is not enabled by default.

The Refunds API requires approval

SeerBit enables the refund endpoint per merchant. Until your account is approved for it, calls to the endpoint will not succeed and refunds must be issued from the dashboard.To request access, contact your SeerBit account team or SeerBit Support.

​
Before you can refund

A refund requires a dispute on the transaction. You cannot refund a payment that has no dispute raised against it — adding the dispute is the first step, not an optional one. Funds always return to the card that was originally charged. You cannot redirect a refund to a different card or account.

​
Full or partial refund?

You can issue several partial refunds against one payment, as long as the running total never exceeds the amount charged. Once the full amount has been returned, the payment is closed and cannot be refunded again — a further attempt, or an attempt for more than remains, is rejected.

​
Refunds API

POST

​
Authentication

Refund 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.

​
Request Sample

cURL

​
Parameter description

​
Response

A refund against a reference SeerBit cannot find returns:
Note: status: "SUCCESS" describes the API call, not the refund. Read data.code — a refund only succeeded when it reads 00.

​
Refunding from the dashboard

1

Find the transaction

Locate the payment that needs refunding in your transaction list.
2

Open it

Click the transaction to see its full detail.
3

Issue the refund

Click Issue refund.
4

Choose full or partial

Select a full or partial refund, and enter the amount if partial.
5

Give a reason

Select a reason for the refund. This is carried on the refund record.
6

Confirm

Click Refund.

​
Getting notified

SeerBit sends a refund webhook event when a refund is processed — whether it came from the dashboard or the API — so your system can update the order either way. The payload carries the original transactionRef, the amount returned, the refund type, and the reason as description. A separate dispute event fires when a dispute is raised — see dispute event.

​
Notes

  • Send the original payment’s paymentReference. A refund is not a new transaction with its own reference — it acts on the payment being reversed.
  • status: "SUCCESS" is not confirmation of a refund. Always read data.code.
  • Refunds fire webhooks in test mode too, so you can exercise your handler before going live. See test and live modes.
  • A refund is not a reversal of your settlement. Refunded amounts are recovered from your SeerBit balance — see receiving settlements.
  • The transaction fee on the original payment is a separate matter from the refunded amount. Confirm how your account treats fees on refunds with your SeerBit account team.