# Client web views — opened from WhatsApp

The three "linked from WhatsApp" web views. Each is a single-purpose page: e-sign, invoice payment, status summary. The client arrives via a magic link in WhatsApp; auth is by phone number; there is no nav, no footer, no portal.

## What's in the prototype

`index.html` shows three phone-sized views side by side at 380px each.

Design principles applied:
- **One job per page.** Title, supporting object, primary action — nothing else.
- **Large touch targets.** Primary CTA is 56px tall with 17px label — comfortable for a 65-year-old on a 4-year-old Android.
- **Generous type.** Body is 14px; headings 24px; amounts 44px (the invoice amount is the largest object on the page).
- **No nav, no footer.** The user came from a single WhatsApp link to do a single thing and return to WhatsApp.
- **Tabular numerals everywhere.** Dollar amounts, dates, file numbers, invoice numbers all align.
- **Inline language switcher** (e-sign view) — EN / ਪੰਜਾਬੀ / हिन्दी / ગુજરાતી, set in their proper scripts.
- **WhatsApp return** — the status view ends with the literal WhatsApp green CTA, "Reply on WhatsApp" — the most likely next action.

## Out of scope here

- Live signature pad interaction (we show the zone; the implementation lives in the engineering brief)
- Interac/Stripe payment flow (we show the price + CTA; not the redirect)
- Localized copy for the three Indic scripts (we show the script chip; the full localized page is a future deliverable that needs native-speaker review)