Buy Now, Pay Later for SaaS and Online Courses

AI Prompts to Build This

Copy these build prompts into Claude, Cursor, or your AI coding tool. Create a free account to unlock the full research behind them.

1. 1. Project Setup

   Build the weekend MVP of "Split-Pay for Digital Products": a checkout widget that lets a buyer split a course or SaaS price into monthly installments, with access that follows payment status. Sandbox only: no real money moves.
   
   Stack: Next.js (App Router), TypeScript, Tailwind, Supabase (Postgres, Row Level Security, Auth with email magic link for merchants). A Vercel cron route runs the daily installment job. Deploy on Vercel.
   
   Tables (Row Level Security on: a merchant reads only its own rows):
   - merchants(id, user_id, name, engagement_data_enabled)
   - buyers(id, email, phone)
   - plans(id, merchant_id, buyer_id, total_cents, installment_count, installment_cents, status, product_type) where product_type is one of course, saas, membership
   - installments(id, plan_id, due_at, paid_at, status, amount_cents)
   - engagement_events(id, buyer_id, product_id, event_type, occurred_at)
   
   Screens: /login, /dashboard (merchant), /widget-demo (a fake course page with the widget).
   Env vars (names only): NEXT_PUBLIC_SUPABASE_URL, NEXT_PUBLIC_SUPABASE_ANON_KEY, SUPABASE_SERVICE_ROLE_KEY (server only), CRON_SECRET.
   
   Do not build: live-mode payments, advancing real money to sellers (record what would be advanced on the plan), KYC, merchant payouts, billing for the platform itself, real underwriting data.
   Done when: npm run dev starts, you can sign in as a merchant, and the five tables exist with Row Level Security on.

2. 2. Core Feature

   Build the one feature that proves the idea: split the price, tie access to payments, and handle a missed one gently.
   1. Add the payment keys to the env vars: STRIPE_SECRET_KEY and STRIPE_WEBHOOK_SECRET, in test mode only. The checkout widget is a script tag or component. On load it calls POST /api/plans/eligibility with the buyer's email and the cart total.
   2. Eligibility runs a lightweight score from card signals and any engagement_events for that buyer, and returns the approved options (3, 6 or 12 months) or a decline with a reason.
   3. On plan creation, save the plan and its installments, charge the first installment, and save the payment method for off-session charges. Record on the plan what would be advanced to the seller. Move no money to the seller.
   4. A daily cron route (protected by CRON_SECRET) charges due installments, updates their status, and on a missed payment starts a grace-period countdown and calls a webhook the merchant can use to pause access. Do not revoke access at once.
   5. Log every state change with a timestamp and a reason.
   6. /dashboard shows financed volume this month, active plans with on-track, grace-period and defaulted statuses, and the default-rate trend.
   Rules: test mode only, and say so in the UI. Lending is regulated, so take legal advice before moving real money. Never show a decline reason that exposes another buyer's data.
   Empty state: with no plans, show the widget demo link and the webhook URL.
   Done when: a test buyer can split a price into 3, the first installment charges in test mode, a failed second charge starts the grace period and calls the merchant webhook, and access stays on until the grace period ends.

3. 3. Landing Page

   Build a one-page landing site for Split-Pay for Digital Products, installments for SaaS and online courses.
   Hero: "Let buyers split the price. Keep your sales." Sub: "Installments built for products that unlock access, not ones that ship a box." One button: Join the waitlist.
   Sections: the problem (high-ticket courses and annual plans lose buyers at checkout), how it works in four steps (connect checkout, the buyer splits the price, the seller is paid up front, access follows payment), and an FAQ that says plainly this is a product in development, how missed payments are handled, and that lending rules apply.
   Waitlist: store the email in a waitlist table in Supabase. No other service.
   Voice: sober and clear. Make no promise of approvals.
   Done when: the page renders on a phone and a submitted email appears in the waitlist table.

4. 4. Branding Package

   Use a design or image tool for this one. A coding agent cannot draw a logo.
   Brand for Split-Pay for Digital Products: a wordmark and an icon that suggest a price split into equal steps.
   Colors: off-white, deep navy and one calm green. Type: one sober sans for the interface and tabular numbers for amounts.
   Deliverables: wordmark, icon, an installment-schedule component style, and one launch graphic.
   Done when: each deliverable is saved in one folder and the amounts line up in a column.