Can I vibe code Recurly?

Build a full-stack Node.js/TypeScript subscription management core service using PostgreSQL and Prisma ORM.

The service must implement the following entity schema and business logic:

1. DATA MODELS & SCHEMA:
- Customer (id, email, default_payment_method_token, currency, gateway_customer_ids JSON)
- Subscription (id, customer_id, plan_id, status: active|past_due|canceled|paused, current_period_start, current_period_end, trial_end, cancel_at_period_end)
- Plan (id, code, name, price_cents, interval: month|year, trial_days)
- Invoice (id, customer_id, subscription_id, state: draft|open|paid|uncollectible|void, total_cents, subtotal_cents, tax_cents, line_items JSON, payment_attempts_count, next_retry_at)
- PaymentTransaction (id, invoice_id, gateway_name, transaction_reference, status: success|failed, error_code, amount_cents)

2. CORE BILLING ENGINE LOGIC:
- Cron/Worker engine that scans active subscriptions due for renewal (current_period_end <= NOW()).
- Proration engine: Calculate exact mid-cycle upgrade/downgrade charges using line-item adjustments (unused time credit on old plan vs prorated charge on new plan).
- Payment Gateway Abstraction Layer: Implement an interface `PaymentGateway` with mock integrations for Stripe and Braintree. Route transactions dynamically based on configuration.
- Dunning State Machine: When an invoice payment fails, transition status to `past_due`. Implement a retry schedule (Day 1, Day 3, Day 7, Day 14). Trigger customizable webhook notifications on each failure. Mark invoice `uncollectible` and update subscription status to `canceled` after 4 failed attempts.

3. REVENUE RECOGNITION (ASC 606 LIGHT):
- Generate monthly ledger schedules upon invoice payment. Split linear daily revenue recognition records across the subscription service period (e.g., $120 annual subscription creates 12 monthly $10 revenue recognition line items).

4. API & ADMIN PANEL:
- REST APIs for customer self-serve portal: swap plan, update payment token, cancel at period end, pause subscription.
- Admin dashboard endpoints: retry failed invoices manually, trigger mid-cycle plan changes, inspect audit logs.

OUT OF SCOPE:
Do not build native UI components. Do not implement direct PCI card field rendering (use mock payment tokens). Do not implement physical tax calculation software; mock tax as flat 10% rate.

FAILURE MODES TO HANDLE:
Concurrency locks on subscription billing workers to prevent double-charging during scale-out. Double-entry validation on all invoice line-item calculations. Transaction rollback on gateway timeouts.

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