How to
Set up pilot payments & go-live env
Turn on Stripe payment links for the pricing page, plus the remaining go-live environment steps.
The pricing page's CTAs are wired to Stripe payment links through public environment variables. Until a link is set, each card falls back to the signup flow — so payments switch on from the Vercel dashboard with zero code changes.
1. Stripe payment links
- Create a Stripe account (stripe.com) and complete business verification.
- In Stripe: Payment links → New, one per plan:
- Readiness diagnostic — AED 499, one-time
- Bank application pack — AED 1,999, one-time
- Consultant workspace — AED 499, monthly recurring
- In Vercel (kredal-app project → Settings → Environment Variables), add:
NEXT_PUBLIC_STRIPE_LINK_DIAGNOSTIC=https://buy.stripe.com/...
NEXT_PUBLIC_STRIPE_LINK_PACK=https://buy.stripe.com/...
NEXT_PUBLIC_STRIPE_LINK_CONSULTANT=https://buy.stripe.com/...- Redeploy. The pricing CTAs flip from "Get started" to "Buy now"
automatically (
src/lib/payments.ts).
Manual invoicing remains fine for the first concierge pilots — links just remove friction.
2. Remaining go-live environment steps
| Step | Where | Why |
|---|---|---|
Working GEMINI_API_KEY | Vercel env | Current key returns 429 (quota) — extraction flags for review instead of parsing |
| Resend SMTP | Supabase → Auth → SMTP | Auth emails from your own domain; the default sender is rate-limited |
http://localhost:3000/** in redirect allowlist | Supabase → Auth → URL Configuration | Local-dev auth flows |
| Delete E2E fixtures when done | /admin → Workspaces | The two E2E workspaces are kept for demo reference |
Each step is dashboard-only; none require code changes.