BobPlus Africa sends a webhook callback to your system after every successful or failed deposit or payout transaction. This callback contains all relevant details about the transaction status, allowing your system to process the outcome automatically and securely.
Purpose: Notify your system of transaction results in real time.
Target Audience: All developers and businesses integrating with BobPlus Africa APIs.
Quickstart: Handling Callbacks
Set up an endpoint on your server to receive POST requests from BobPlus Africa.
Parse the JSON payload and extract the transaction details.
Verify the hash parameter to ensure authenticity (see below).
Process the transaction result in your system.
Respond with HTTP 200 OK to acknowledge receipt.
Sample Success Callback Response
{
"channel": "100001",
"reference": "3883328",
"transaction_id": "CP7S36ULT8P",
"third_party_id": "SP7S36U3T8",
"currency": "KES",
"amount": "10",
"fees": "0.2",
"acc_name": "John Doe",
"result_code": 0,
"result_description": "The service request is processed successfully.",
"hash": "c920aaebae731f9e16d9a8f1fc1e349b99313cf230f18126a0bbd07d64aac2e0"
}
Sample Failed Callback Response
{
"channel": "100001",
"reference": "3883328",
"result_code": 1032,
"transaction_id": "2345432345",
"result_description": "DS timeout user cannot be reached",
"hash": "e07f51540e120030f5beb594ba34f335f16f2f78c4a7a7b0d53647ac44590ff9"
}
How to Verify the Hash Parameter
The hash parameter is a SHA-256 HMAC that proves the callback is from BobPlus Africa. You should verify it by generating your own hash and comparing it to the one provided.
Concatenate all response fields in the order sent, except the hash parameter.
Hash the resulting string using your consumer key (provided during registration).