Payment and delivery readiness
The platform has the routes, product data, delivery model, and provider boundaries. The next phase is connecting real Stripe first, then PayPal after the Stripe path is stable.
Hosted Stripe Checkout Session creation and verified webhook processing are implemented. Production still needs test/live Stripe keys, price ID, and webhook secret in the deployment environment.
STRIPE_SECRET_KEYSTRIPE_WEBHOOK_SECRETSTRIPE_CONFIDENT_PROMPT_VAULT_PRICE_IDRun Stripe test-mode checkout and webhook QA before accepting live payments.
PayPal is intentionally second. The app has a provider slot and env placeholders, but Stripe should be stabilized first.
PAYPAL_CLIENT_IDPAYPAL_CLIENT_SECRETPAYPAL_WEBHOOK_IDAdd PayPal provider after Stripe purchase and delivery flow is stable.
Prisma models exist for products, funnels, customers, purchases, entitlements, payment events, and delivery events. Runtime needs DATABASE_URL in each environment.
DATABASE_URLConfirm Supabase pooled runtime URL in Vercel before preview/live deployment.
Resend delivery email payloads, access-link generation, webhook-triggered delivery attempts, and manual library access requests are implemented.
RESEND_API_KEYDELIVERY_FROM_EMAILACCESS_TOKEN_SECRETAdd a verified sender/domain in Resend, then run a test-mode purchase email delivery QA pass.
The library, thank-you page, and download route require verified webhook entitlements before exposing short-lived Supabase private storage signed URLs.
ACCESS_TOKEN_SECRETSUPABASE_URLSUPABASE_SERVICE_ROLE_KEYSUPABASE_STORAGE_BUCKETCreate a private Supabase Storage bucket, upload paid PDFs under product slug folders, then run entitlement-gated download QA.