Payment / Consent
Collect payment proof before the next step
Use a temporary QR payment flow, then record PDPA and policy acceptance before manual review and release.
Open PaymentMobile H5 • Future LIFF-ready • Operator-friendly
A lighter, cleaner entry hub for registration, repair, and future user-facing service flows.
Built for operator delivery, QR entry, and LINE-ready mobile experience. Keep entry pages professional, keep service warm, and keep reports in the separate result domain.
Entry
Domain only
Clear
No report pages here
Light
Mobile-first UI
Operator overview
What this entry layer should feel like
V2 Tailwind UI
Modern but restrained
Use gradient, glass, and motion, but keep business pages efficient and mobile-safe.
Tech skeleton + service warmth
Borrow structure from your AI site, but borrow emotional tone from the sample service store.
Domain boundary first
Keep line for collection and entry only. Let the separate ulike result domain handle report rendering and history.
Four service entries
A cleaner entry layer with no report or history pages mixed in.
The homepage should guide users and operators clearly: register first, repair when needed, and keep future bank or verification capability visible but controlled. Report rendering stays on the separate result domain.
Register
Start check and collect user details
Parse QR parameters, validate required data, and submit registration through a clean mobile form.
Open Register
Repair / Training
Submit repair and spectrum training data
Use a dedicated page for the future strict schema and avoid burying repair in legacy extra fields forever.
Open Repair
Future entry
Bank, verification, or service activation
Reserve the surface now so operators can see the roadmap, but keep real integration behind a future configuration switch.
Flow design
Keep the operator flow short, clear, and ready for future LINE embedding.
Step 1
Scan
Enter through QR or direct mobile link.
Step 2
Fill
Provide registration or repair details in a lightweight form.
Step 3
Submit
Send validated data to your FastAPI endpoints.
Step 4
Continue
Proceed to later result or verification flows through the proper domain and backend sequence.