Verified BursaPay workflow: Map the major webhook event names to the business operations they represent.
1. Overview & Purpose
The webhook API supports payment, refund, withdrawal, customer, API-key, dispute, transfer, virtual-account, subscription and invoice event families.
2. Requirements & Setup
Choose only events that the receiving application actually needs.
3. Step-by-Step Workflow
- List the required business events.
- Subscribe the webhook endpoint to those events.
- Implement a handler for every subscribed event.
- Test unknown events as safely ignored.
4. Rules & Troubleshooting
Webhook consumers must not assume that every event is a payment success event; event_type determines the business contract.
5. Verification & Next Steps
Version the consumer logic and keep the event catalog close to the integration code.