Webhook setup
Elite Neo Bank Webhooks allow merchants to receive real-time payment and payout notifications directly on their server without continuously polling APIs. Webhooks are recommended for:- Payment status updates
- Payout status updates
- Settlement notifications
- Transaction reconciliation
- Automated workflow processing
What are Webhooks?
A webhook is an HTTP callback sent by Elite Neo Bank to your server whenever a transaction event occurs. Instead of repeatedly checking transaction status APIs, Elite Neo Bank automatically pushes updates to your configured webhook endpoint.Supported Webhook Events
- PG Orders Events
- PG Payments Events
- Payout Events
Webhook URL Requirements
Your webhook endpoint must:- Be publicly accessible
- Support HTTPS
- Accept
POSTrequests - Return HTTP
200 OKquickly - Handle JSON payloads properly
Example Webhook URL
Webhook Request Method
Webhook Headers UNDER DEVELOPMENT
Webhook Security UNDER DEVELOPMENT
Every webhook request is signed using HMAC SHA256 signature verification.
Webhook signatures should always be validated before processing webhook data.
The signature is generated using:
Example Payment Webhook Payload
Example Payout Webhook Payload
Webhook Verification Process
Recommended verification steps:- Read webhook payload
- Extract
X-SIGNATUREheader - Extract
X-TIMESTAMPheader - Generate local signature
- Compare generated signature with received signature
- Process webhook only if signatures match
Example Node.js Verification
Webhook Response Requirements
Your server should return:Retry Mechanism
If your server:- Times out
- Returns non-200 responses
- Fails to respond
Recommended Retry Handling
Your webhook system should:- Handle duplicate events safely
- Store webhook logs
- Use idempotent processing
- Verify transaction status using APIs when needed
Best Practices
- Always validate webhook signatures
- Use HTTPS endpoints only
- Respond quickly with HTTP 200
- Process webhook logic asynchronously
- Store webhook payloads for audit logs
- Verify final transaction status server-side
Important Notes
- Webhooks should not be trusted without verification
- Duplicate webhook events may occur
- Payment status should always be verified server-side
- Webhooks complement APIs and do not replace verification APIs
Common Errors
Invalid Signature
Possible reasons:- Incorrect secret key
- Payload modification
- Timestamp mismatch
Webhook Timeout
Possible reasons:- Slow webhook processing
- Server downtime
- Network failures
Recommended Production Workflow
- Receive webhook
- Verify signature
- Validate payload
- Store webhook event
- Verify transaction status using APIs
- Update merchant system
- Return HTTP 200 response
