Verified BursaPay workflow: Provides a troubleshooting workflow for tickets that appear to have been scanned already.
1. Overview & Purpose
The ticket model separates scanned from payment and approval state and records who scanned it and when.
2. Requirements & Setup
The ticket reference and event context should be captured before investigation.
3. Step-by-Step Workflow
- Read the ticket's scanned state.
- Inspect scanned_at and scanned_by when available.
- Confirm the ticket belongs to the correct event and holder.
- Escalate ambiguous cases instead of clearing scan state without authorization.
4. Rules & Troubleshooting
Never treat a second scan attempt as proof that the first scan was fraudulent; first verify the ticket and scan metadata.
5. Verification & Next Steps
Use the recorded scan details for audit and dispute resolution.