Documentation
Callback Operations/manual Callback
Callback Operations - Manual Callback (Payment)
Manual callback is used to notify the merchant about the payment status and details manually
Overview
The manual callback endpoint allows you to trigger callback notifications manually for specific payments. This is useful when automatic callbacks fail or when you need to resend payment notifications to your system.
This endpoint requires Signature Authentication, IP Whitelisting, and is subject to Rate Limiting.
Request
Http Method & URL
POST /v1/callback/manual
Headers
| Header | Type | Required | Description |
|---|---|---|---|
|
Content-Type
|
string | Yes | application/json |
|
X-Signature
|
string | Yes | HMAC-SHA256 signature for request authentication |
Signature Generation: Refer to the Signature Generation section for detailed steps on generating the X-Signature header value.
Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
|
biller_code
|
string | Yes | Merchant identifier |
|
payref_id
|
string | Yes | Payment reference ID |
Request Body Example
{
"biller_code": "MERCHANT001",
"payref_id": "PAY123456"
}
Response
Success Response (200)
{
"success": true,
"message": "Manual callback triggered successfully",
"data": {
"status": "SUCCESS",
"message": "Callback sent successfully",
"payref_id": "PAY123456",
"merchant_response": {
"http_status": 200,
"body": "OK"
}
},
"timestamp": "2024-01-15T10:30:00Z"
}
Authentication Error Response (401)
{
"success": false,
"error": {
"code": "AUTHENTICATION_ERROR",
"message": "Invalid signature"
},
"timestamp": "2025-07-15T08:09:18Z"
}
Error Response (404)
{
"success": false,
"error": {
"code": "NOT_FOUND",
"message": "Payment not found"
},
"timestamp": "2025-07-15T08:09:18Z"
}
Was this helpful?