Can I vibe code Sezzle?

1. DATA MODEL & SCHEMA:
Create a Postgres schema for a merchant-funded installment schedule engine. Tables: `installment_plans` (id, order_id, customer_id, total_amount, fee_amount, status, created_at), `installments` (id, plan_id, sequence_number, due_date, amount_due, amount_paid, status, stripe_payment_intent_id), and `payment_methods` (id, customer_id, stripe_customer_id, payment_method_id, is_default).

2. CORE FUNCTIONALITY:
- Frontend Widget: Embeddable JS widget that calculates a Pay-in-4 schedule (25% today, 25% every 2 weeks) and renders it on product pages and checkout.
- Order Orchestration: Upon checkout submit, authorize and capture the first 25% via Stripe API while saving the vaultable payment method token.
- Scheduled Job Engine: A daily Cron worker that queries due installments for the current date, attempts automated off-session Stripe charges, updates installment status, and emits webhooks on success or failure.
- Merchant Dashboard: Minimal React UI showing overall active plans, upcoming collections, overdue installments, and manual charge retry options.

3. FAILURE MODES & EDGE CASES TO HANDLE:
- Failed Card Charge: Implement exponential backoff dunning logic (retry at day +1, day +3, day +7) and trigger email notification triggers.
- Partial Refunds: If merchant refunds an order, calculate proportional adjustments to remaining unpaid installments before processing card refunds.
- Card Expiration: Alert customer 7 days before an upcoming installment if vault card expires prior to due date.

4. OUT OF SCOPE:
Do not implement credit bureau soft pulls, underwriting algorithms, regulatory compliance disclosures (Truth in Lending Act), external debt collections, or merchant balance sheet financing. This system assumes merchant absorbs all credit risk.

$ each button prefixes agent-specific run instructions · build your own product, never copy proprietary code, trademarks or designs