Verified workflow guide: Explains the separate verification, approval and onboarding states used by BursaPay accounts.
1. Overview & Purpose
BursaPay separates identity/contact verification from broader approval and onboarding state. The CustomUser model carries email_verified, contact_verified, is_verified, is_approved and onboarding_complete independently.
2. What You Need
A user needs the normal account credentials plus whatever role-specific verification or approval the requested workflow requires.
3. Step-by-Step Workflow
- Open the relevant account or dashboard.
- Check email_verified and contact_verified status where exposed.
- For organizations and vendors, confirm approval/onboarding state before restricted actions.
- For registrars, confirm verification before performing restricted registrar work.
4. Rules, Boundaries & Troubleshooting
Do not assume email verification means organization/vendor approval. Support should identify the exact missing state instead of changing unrelated flags.
5. Verification & Next Steps
Complete the missing verification or approval step, then retry the blocked role-specific workflow.