Back to home
INTEGRATION
PAYMENT FEATURES
AFTER PAYMENT
Receiving Settlements
Anytime an event happens on your account, your application can be notified by SeerBit. This is where webhooks come in. This is useful for events that are not triggered by direct API request, but when the response from that request needs to be known (for instance, in cases when there is an update to a transaction status). It is necessary only for behind-the-scenes transactions. SeerBit webhooks are HTTP calls that are triggered by specific events. SeerBit webhooks replace regular API calls with instant, real-time notifications. It can be set up on your dashboard by specifying a URL we would send POST requests to you whenever an event that might be of interest happens. Each webhook notification contains an eventType that specifies which type of event triggered the webhook notification.
Failed Transactions
Expose an endpoint on an open server
We can send notifications as HTTP callbacks (webhooks) to an endpoint on a server that must be open. To receive webhooks, you must have a server that:
- Has an endpoint that can receive JSON requests
- Depending on your network and security requirements, you might also need to add our IP address to your firewall’s whitelist
Subscribe to webhook notifications
To configure webhooks notifications:
- Login to your dashboard
- Navigate to Account Settings > Webhook
- Enter your notification URL
- Click on Subscribe
Accept Nofications
To ensure that your server is properly accepting notifications, we require you to acknowledge every notification with an HTTP 200 response code. If we don't receive this response within 10 seconds, for example because your server is down, all notifications to your endpoint will be queued and retried. For more information, refer to Queued notifications. When your server receives notification:
- Save the notification in your database
- Acknowledge the notification with the following HTTP response status code 200
- Apply your business logic
Make sure that you acknowledge the notification before applying any business logic, because a breakage in your business logic could otherwise prevent important updates from reaching your system.
Webhook Integration
A seerbit integration includes the following :
- Events: This is an action that triggers notifications. Webhooks can be used to create alerts that trigger for these events.
- Subscriptions: This is set-up in the portal to subscribe to notifications associated with a specific event. There is a configurable service in the application to which alerts are sent.
- Notification Body: Details about the event that generated the alert, such as the time it happened.
Webhook Event Types
refund
dispute
transaction
transaction.recurrent
transaction.wallet
transaction.recurring.debit
dispute
transaction
transaction.recurrent
transaction.wallet
transaction.recurring.debit
Queued Notifications
It is expected that you respond to an event notification with a status response code of 200 (OK). This code will be used by us to acknowledge that you received the notification. Any status response code outside of the 2xx series will be considered a failed response and we will continue to retry regularly for up to 7 days, at increasing time intervals as follows:
2 Minutes
5 Minutes
10 Minutes
15 Minutes
30 Minutes
1 hour
2 hours
4 hours
5 Minutes
10 Minutes
15 Minutes
30 Minutes
1 hour
2 hours
4 hours
After that, retries happen every 8 hours for the following 7 days. If we do not receive a response within the 2XX series, all notifications to this endpoint will be queued. Subsequently, we will attempt to retry sending the notification to your endpoint until it is accepted. Once accepted, you will receive all queued notifications as well.
Refund Event Sample
The refund event notification body is structured thus:
Dispute Event Sample
The dispute event notification body is structured thus:
Transaction Event
The transaction event notification body is structured thus
Wallet Transaction Event
The wallet transaction event notification body is structured thus
Recurrent Transaction Event
The recurrent transaction event notification body is structured thus
Recurring Debit Transaction
The code snippet below shows an example response for verifying a subscription
Virtual Account Transaction
The virtual account transaction event notification body is structured thus
Need something else?
If you have any questions or need general help, visit our support page
Signup for developer update
You can unsubscribe at any time. Read our privacy policy.