7ab5e12051
- Introduced ResidenceCardSubmission model to handle user submissions of residence cards, including status tracking and file management. - Updated User model to include a relation to ResidenceCardSubmission for better user data management. - Enhanced the checkout process to require residence card submission for SIM orders, improving compliance and verification. - Integrated VerificationModule into the application, updating relevant modules and routes to support new verification features. - Refactored various components and services to utilize the new residence card functionality, ensuring a seamless user experience. - Updated public-facing views to guide users through the residence card submission process, enhancing clarity and accessibility.
Portal Guides (How It Works)
These guides explain what the portal does, how data moves between WHMCS and Salesforce, and where caching affects what people see. They avoid deep implementation detail and focus on flows, data ownership, and error handling.
Start with system-overview.md, then jump into the feature you care about:
COMPLETE-GUIDE.md— single, end-to-end explanation of how the portal workssystem-overview.md— high-level architecture, data ownership, and caching quick reference.accounts-and-identity.md— how sign-up, WHMCS linking, and address/profile updates behave.catalog-and-checkout.md— where products/pricing come from and what we check before checkout.eligibility-and-verification.md— internet eligibility + SIM ID verification (Salesforce-driven).orders-and-provisioning.md— order lifecycle in Salesforce and how it is fulfilled into WHMCS.billing-and-payments.md— invoices, payment methods, and how billing links are handled.subscriptions.md— how active services are read and refreshed.support-cases.md— how cases are created/read in Salesforce from the portal.ui-design-system.md— UI tokens, page shells, and component patterns to keep pages consistent.