Verified BursaPay workflow: Explains the difference between ticket creation, payment, approval, and gate scanning.
1. Overview & Purpose
Ticket stores is_paid, is_approved, approved_at, scanned, scanned_by and scanned_at as separate operational states.
2. Requirements & Setup
Gate operators should authenticate as the appropriate event staff role and inspect the ticket state before scanning.
3. Step-by-Step Workflow
- Confirm the ticket exists for the correct event.
- Check is_paid before treating the purchase as paid.
- Check is_approved when the event requires approval.
- Use scanned and scanned_at to determine gate admission state.
4. Rules & Troubleshooting
Paid, approved and scanned are different states; one should not be assumed from another.
5. Verification & Next Steps
Use the event's ticket detail and scan records to investigate disputed admission.