Overview
Webhooks provide real-time notifications when payment and request events occur, enabling immediate response to status changes without polling.Supported Events
Payment Events
Payment detected, confirmed, failed
Request Events
Request created, updated, cancelled
How It Works
Flow:- Event: Payment or request status changes
- Trigger: Automatic webhook activation
- Delivery: HTTP POST to your endpoint
- Process: Handle event in your application
Event Types
Payment Events
payment.detected
- Payment transaction foundpayment.confirmed
- Payment confirmed on blockchainpayment.failed
- Payment transaction failed
Request Events
request.created
- New request createdrequest.updated
- Request information changedrequest.cancelled
- Request cancelled by creator
Webhook Configuration
Endpoint Requirements
- HTTPS Only: Secure webhook endpoints required
- Response Codes: Return 200-299 for successful processing
- Timeout: Respond within 30 seconds
Retry Logic
- Automatic Retries: Failed deliveries retried with backoff
- Maximum Attempts: Up to 5 retry attempts
- Retry Schedule: 1min, 5min, 25min, 2hr, 12hr
Security Features
Signature Verification
HMAC signatures for authenticity
IP Allowlisting
Restrict webhook sources