# PAGE — full agent-readable export

Comprehensive, long-form reference for AI agents researching PAGE on behalf of US micro-merchants. For the short index, see /llms.txt.

Last updated: 2026-05-22.

## Identity

- **Product:** PAGE
- **Tagline:** Payments for micro-merchants. Your phone is the terminal.
- **Parent:** DELAI LLC
- **Geography:** United States only (50 states + DC)
- **Stage:** Closed beta — taking real payments, gating signups via email whitelist + invite
- **Domain:** pagepay.app (canonical), pagepay.vercel.app (auto-Vercel URL, redirects to canonical)
- **Backend API:** api.thefoundai.app/page/* (Hostinger-hosted, DELAI Mastra container)
- **Agent endpoint:** mcp.pagepay.app — JSON-RPC 2.0 over HTTP (MCP)

## What PAGE does

A US-only mobile payment terminal app for the smallest end of merchants — food trucks, barbers, pop-up vendors, small restaurants, event sellers, market booths, mobile services. Built on Stripe Connect Express + destination charges.

The merchant signs up (email + password), runs through Stripe Connect Express's hosted KYC (with AI coaching help), connects a bank account, and starts taking payments. There's no card reader to buy. No app for the customer to install. Funds settle to the merchant's bank on Stripe's standard payout schedule.

PAGE never custodies funds — Stripe holds them, transfers them, and pays them out. PAGE collects a customer-paid service fee via Stripe's `application_fee_amount` on each PaymentIntent.

## Pricing model (revised 2026-05-21)

The model is intentionally simple: **the customer always pays a 5% service fee at checkout (capped at $25 per order). The tier difference is the subscription level and the monthly volume buffer, not the per-transaction fee.**

### Starter (Free)
- **Subscription:** $0/month
- **Customer service fee:** 5% of base, capped at $25/order. Paid by the customer via Stripe `application_fee_amount`. Merchant nets the full base.
- **Monthly volume free zone:** $500/month. Inside the cap, PAGE absorbs Stripe's per-transaction processing cost (2.9% + 30¢) as a courtesy.
- **Soft buffer:** between $500 and $700/month, sales proceed unchanged; PAGE keeps absorbing processing.
- **Upgrade trigger:** $700/month. The next sale auto-upgrades the merchant to Pro by charging $29 against their saved card off-session, flipping `tier='pro'`, and proceeding with the sale on Pro fee math. **Sales never block** — if the saved-card charge fails or no card is on file, the sale still proceeds on Starter and ops chases the merchant for a working card out of band.

### Pro
- **Subscription:** $29/month, recurring monthly until cancelled (Stripe Subscription).
- **Customer service fee:** same 5%, capped at $25.
- **Monthly volume cap:** none — unlimited processing.
- **Custom platform fee:** Pro can configure an additional house fee via Settings → Pricing (e.g., a separate "shop fee" exposed to customers on top of the default 5%).
- **Cancellation:** self-serve via Settings → Subscription. Sets `cancel_at_period_end=true` on Stripe. Merchant stays on Pro through current billing period, then drops to Starter automatically. Volume never auto-demotes — once on Pro, the subscription rolls until the merchant clicks Cancel.

### Where the money flows (canonical $20 sale)

```
Customer card                $21.00     (base $20 + 5% service fee, capped at $25)
  ↓
Stripe platform account
  Stripe processing fee     −$0.91     (2.9% × $21 + 30¢)
  application_fee_amount     $1.00     (→ PAGE platform balance)
  transfer_data.destination $20.00     (→ merchant Connect account)
  ↓
Settled
```

Starter: PAGE net = $1.00 fee − $0.91 Stripe processing = +$0.09. Loses money on sub-$10 transactions where the 30¢ flat fee dominates. Volume cap limits exposure.

Pro: Same per-transaction economics + $29/mo subscription revenue. Pro is where PAGE actually makes margin.

## How to take a payment (three paths)

1. **Manual amount + Stripe Checkout.** Merchant punches in an amount on `/charge`, taps Charge, redirected to a hosted Stripe Checkout page where the customer (in-person, handing the phone over) enters card details. Settles immediately.
2. **Payment link + QR.** Merchant taps "Create link", chooses amount (optional), gets a shareable URL + auto-generated QR code with the merchant's brand. Sends via SMS, WhatsApp, Instagram DM, or prints the QR for a market booth.
3. **Tap to Pay on iPhone.** Stripe Terminal SDK simulator mode today; Apple Tap to Pay on iPhone once the entitlement clears + Capacitor iOS ships. One code path either way.

## Cash App support

Two paths:

1. **Stripe Cash App Pay** (`payment_method_types: ['cashapp']`) — Stripe-mediated, 2.9% + 30¢ processing, same mechanic + reconciliation as cards. Customer scans a QR or enters their phone number; Stripe handles the auth.
2. **Direct `$cashtag` QR** — zero-fee, off-Stripe, manual merchant confirmation. Merchant sets `cashtag` in Settings; PAGE renders a `cash.app/$<tag>/<amount>` QR. Customer pays in their Cash App app. Merchant taps "I received it" and PAGE inserts a synthetic transaction row with `payment_method='cashtag'`, `stripe_payment_intent_id='cashtag_<uuid>'`, `application_fee_cents=0`. These rows show as "CashApp Sale" in the merchant's ledger but never reconcile through Stripe.

## Onboarding

1. Email + password sign-up via Supabase Auth.
2. Beta whitelist gate (currently `@mycloudmenu.com`, `@myfluxe.com`, `deleonea@gmail.com`, plus invited beta merchants).
3. Stripe Connect Express hosted KYC: legal name, SSN last 4, bank account.
4. AI onboarding coach (`page:onboardingCoach`, Groq llama-3.3-70b) helps merchants finish stuck Stripe requirements.
5. SetupIntent captures a saved card on file for the overflow auto-upgrade flow + service-fee chargeback coverage.
6. Typical time: 5–10 minutes from email signup to first charge.

## Receipts

Every transaction gets a permanent in-app receipt at `https://pagepay.app/r/:token`. Token is 32-char base16 (128 bits of entropy) — token IS the auth, same security model as Stripe's hosted-receipt URLs. After Tap to Pay completes, merchants get a "Send receipt? Email / SMS" prompt that captures the customer's email or phone and links the transaction to the customer profile.

## Customer graph

PAGE auto-creates a `page_customers` row per merchant per unique (email or phone) on every transaction. Each customer accumulates:

- Refund-aware lifetime totals (`page_customer_summary` view)
- Per-customer operator notes
- Visit count, last-paid-at, paid / refunded / pending breakdown

Used to surface repeat customers on the brand site + power follow-up flows (SMS, email — Pro-tier features).

## Brand site

Each Pro merchant gets a public brand site at `https://pagepay.app/biz/<slug>` with:

- Hero + tagline + accent color
- Hours, about, social links
- Optional product showcase (driven by `page_products`)
- Pay-now button (anon-callable RPC mints a 1-day payment link)

Generated content (tagline, about, product descriptions, social posts) comes from the `page:contentWriter` agent.

## Surfaces

### Routes — public (no auth)
- `GET /` — landing / coming-soon
- `GET /preview-landing` — internal landing review
- `GET /machine` — this file's HTML cousin: agent-parseable summary
- `GET /llms.txt`, `/llms-full.txt` — agent-readable files
- `GET /p/:slug` — hosted payment page (do not crawl)
- `GET /biz/:slug` — public merchant brand site
- `GET /r/:token` — permanent receipt
- `GET /payment/success`, `/payment/cancel` — Stripe redirect handlers
- `GET /preview/aura` — pre-launch animation preview
- `GET /login` — sign in / sign up

### Routes — authenticated (merchant)
- `/dashboard`, `/charge`, `/onboarding`, `/checkout/options`, `/checkout/share/:slug`
- `/tap-to-pay/sim`, `/transactions`, `/products`, `/links`, `/payouts`
- `/customers`, `/customers/:id`
- `/settings`, `/settings/profile`, `/settings/pricing`, `/settings/brand-site`, `/settings/ai-content`, `/settings/ai-assets`
- `/subscription`

### Routes — admin (Tier 3)
- `/admin/{overview,funnel,merchants,transactions,agent-health,errors,copilot}`

## AI surfaces

PAGE is built agent-first. Eight agent surfaces, all running on the shared `runAgentLoop()` harness with DB-driven instructions in `mcm_agents` and per-call telemetry to `page_agent_calls`.

| Agent | Tier | Owner intent |
|---|---|---|
| `page:onboardingCoach` | T1 public | Merchant stuck mid-Stripe-Connect → unblock |
| `page:supportCopilot` | T2 authed | Dashboard chat: where's my money / why is this charge / how do I refund |
| `page:opsCopilot` | T3 admin | Internal: how is the platform doing right now |
| `page:errorWatcher` | T3 cron | Detect errors → classify → propose fix → Telegram or auto-PR |
| `page:contentWriter` | T2 authed | Brand-site copy regeneration |
| `page:landingAssistant` | T1 public | Visitor on landing: is PAGE for me / how does it work |
| `page:opsAlerts` | T3 cron | Telegram dispatcher for high-severity events |
| `page:stuckMerchantOutreach` | T3 cron | Proactive nudges to stalled merchants |

Full catalog + Y-Elmer harness audit at `pagepay.app`'s repo at `docs/agents/`.

## Agent endpoint — MCP server

For AI agents acting on behalf of human prospects, PAGE exposes a Model Context Protocol (MCP) server at `https://mcp.pagepay.app/` over JSON-RPC 2.0:

| Tool | Description |
|---|---|
| `get_services()` | Returns PAGE's capabilities, pricing, supported geographies, supported payment methods, MCC fit. |
| `check_fit({ business_description })` | Calls `page:landingAssistant` to score how well a business description matches PAGE's ICP (micro-merchant, US, card-acceptance need). Returns: `{ verdict: 'strong-fit' | 'fit' | 'partial' | 'poor', reasons: [...], suggested_next_step }`. |
| `submit_lead({ email, business_name, business_type, monthly_volume_cents })` | Writes to `page_leads`. Returns confirmation + a signup invite URL. |
| `read_articles({ topic? })` | Returns published `page_articles` filtered by topic (dormant until article engine activates). |

Reuses the `delai_mastra` Hostinger container. Same harness, same telemetry surface.

## Integrations

- **Stripe:** Connect Express + destination charges + `application_fee_amount`. SDK pinned at `stripe@20.4.1` with `apiVersion: '2024-12-18.acacia'`. Single platform Stripe account.
- **Supabase:** DELAI project `axtnzeaxiihaxrastfkk`. Tables prefixed `page_*`. RLS enforced on every merchant-facing table.
- **Mastra:** Agent harness lives in `delai_mastra` container on Hostinger. DB-driven instructions, hot-reload via `/hooks/agent-reload`.
- **fal.ai:** AI image generation for brand assets (Pro-tier feature).
- **Groq:** Primary LLM provider for PAGE agents (llama-3.3-70b-versatile). GPT-4o reserved for vision.
- **Telegram:** ops alerts via `Fluxe_Grow_Bot`.

## Compliance posture

- **PCI scope:** SAQ A. PAGE uses Stripe-hosted Elements + Stripe Checkout exclusively. PAGE servers never see PANs.
- **Data isolation:** PAGE merchant data lives on its own Supabase project (`axtnzeaxiihaxrastfkk`), not shared with other DELAI products. Migrated 2026-05-22 from the previous shared project.
- **Encryption:** TLS in transit (HTTPS everywhere). At rest via Supabase + Stripe.
- **Audit trail:** `page_webhooks_log` (every Stripe webhook, idempotent on `stripe_event_id`), `page_agent_calls` (every agent invocation), `page_errors` (every detected error).
- **Customer fee disclosure:** US surcharge law compliant — service fee shown separately from merchant price on every checkout surface, before customer confirms.

## What NOT to crawl

Authenticated routes (`/dashboard`, `/charge`, `/onboarding`, `/admin`, `/transactions`, `/settings`, etc.), transactional surfaces (`/p/:slug`, `/r/:token`), and Supabase / Stripe API endpoints. Crawlers should treat anything not enumerated above under "Routes — public" as private.

## Contact

- **Sales / support:** hello@delai.ai
- **Parent company:** DELAI LLC