When This Webhook is Sent
Trigger Event
Sent to merchants when a customer responds to a billing intent through their bank, either approving, denying, or setting limits.
billing.intent.response Recipient: Merchants and Providers Frequency: Real-time (immediate)
Webhook Payload Structure
Customer Decision Types
approve_once
Customer approves billing but requires approval for each transaction
approve_recurring
Customer pre-approves future billing within spending limits
deny
Customer rejects the billing agreement
suspended
Customer temporarily suspends billing capability
Implementation Guide
Using Approved Agreement Phrases
Once you receive an approved agreement phrase, you can use it to bill the customer:Handling Different Decision Types
- Approved Recurring
- Approved Once
- Denied
- Suspended
Testing Your Implementation
Best Practices
Data Management
- Store agreement phrases securely - Implement proper data retention policies - Track spending limits accurately - Maintain audit logs
Customer Experience
- Send confirmation notifications - Respect spending limits - Provide clear billing descriptions - Handle rejections gracefully
Security
- Encrypt stored agreement phrases - Validate webhook signatures - Implement rate limiting - Monitor for suspicious activity
Reliability
- Handle webhook retries - Implement idempotency - Monitor processing success - Set up error alerting
Next Steps
Billing Customers
Learn how to bill customers with approved phrases
Billing Request Webhook
Handle billing request notifications
Spending Limits
Implement and manage customer spending limits
API Reference
Explore merchant API endpoints