Verified BursaPay workflow: Explain the developer-side handling of dispute-created, won and lost events.
1. Overview & Purpose
Gateway webhook contracts include dispute.created, dispute.won and dispute.lost events for developer integrations.
2. Requirements & Setup
The application needs a dispute state model that can map webhook outcomes safely.
3. Step-by-Step Workflow
- Receive the dispute event.
- Find the local payment/transaction by reference.
- Update the local dispute state idempotently.
- Notify the correct internal workflow when the dispute status changes.
4. Rules & Troubleshooting
A dispute webhook should not directly overwrite financial balances without going through the application's financial service layer.
5. Verification & Next Steps
Use the gateway reference and your local record ID together when reconciling dispute changes.