Verified BursaPay workflow: Use webhook delivery logs to identify failed deliveries, response codes and retry state.
1. Overview & Purpose
BursaPay stores webhook delivery history including event type, status, response code, duration and retry metadata.
2. Requirements & Setup
The developer must have webhook management access to inspect delivery history.
3. Step-by-Step Workflow
- Open a webhook's delivery logs.
- Find the failed event and inspect its response code.
- Compare retry_count and next_retry_at with your receiver logs.
- Inspect full payload/response details when deeper debugging is required.
4. Rules & Troubleshooting
A delivery failure is distinct from an application-level payment failure; first determine whether BursaPay delivered the event and what your endpoint returned.
5. Verification & Next Steps
Fix the receiver and retry only after the underlying issue is understood.