Verified BursaPay finance workflow: Explains the operational signals surfaced on financial profiles, including withdrawals, wallet state, bank lock and recent webhook errors.
1. Overview & Purpose
Role-specific financial profiles surface recent withdrawals and selected operational signals such as bank-lock state and webhook errors in the last 30 days where implemented.
2. Requirements & Setup
The target role-specific financial profile must exist.
3. Step-by-Step Workflow
- Open the relevant Finance workflow.
- Select the user, payment, fee, top-up or account context.
- Review the available financial records and filters.
- Verify the displayed result and related audit trail before acting on it.
4. Rules & Troubleshooting
Profile-level webhook error counts are not user-specific because WebhookLog has no per-user foreign key in the implementation.
5. Verification & Next Steps
Treat these signals as investigation prompts and follow them to the underlying records before taking action.