Can I vibe code Chargebee?

Build a production-grade subscription billing and usage metering engine in Node.js/TypeScript using PostgreSQL and Redis.

CORE DOMAIN MODELS:
- Customers: ID, external_id, email, tax_id, payment_method_token, currency, gateway_id.
- Plans: ID, code, name, billing_interval (month/year), base_price, currency, trial_days.
- Metered_Features: ID, code, aggregation_type (sum, max, count, last_value).
- Usage_Events: ID, customer_id, feature_code, timestamp, value, idempotency_key.
- Subscriptions: ID, customer_id, plan_id, status (trialing, active, past_due, canceled), current_term_start, current_term_end, cancel_at_period_end.
- Invoices: ID, subscription_id, customer_id, total, tax, currency, status (draft, paid, void, payment_failed), due_date.
- Invoice_Items: ID, invoice_id, description, amount, quantity, unit_price, type (base, usage, prorated_adjustment).
- Revenue_Schedules: ID, invoice_item_id, total_amount, recognized_amount, deferred_amount, start_date, end_date, ASC606_status.

CORE APIS & FUNCTIONALITY:
1. Usage Event Ingestion: Implement POST /v1/events with Redis-backed deduplication (using idempotency_key). Flush aggregated event metrics to PostgreSQL using batching for meter calculations.
2. Subscription Lifecycle Engine:
   - Create/Upgrade/Downgrade subscriptions. Calculate proration down to the second when switching mid-cycle.
   - Implement advance invoice generation 3 days prior to term_end.
3. Invoicing & Billing Cycle Execution:
   - Scheduled job running every hour to detect subscriptions reaching `current_term_end`.
   - Calculate usage-based charges from aggregated events for the billing window.
   - Calculate line-item prorations, apply coupons/discounts, and build final `Invoices`.
4. Payment Gateway Orchestration:
   - Integrate Stripe API for tokenized payment execution on draft invoices.
   - Dunning Logic: On payment failure, transition subscription to `past_due`. Implement smart retry schedule (Retry at Day 1, Day 3, Day 7, Day 14). Trigger customizable webhooks on final failure before setting to `canceled`.
5. ASC-606 Revenue Recognition Ledger:
   - For every paid invoice item, generate daily ratable revenue recognition schedules across the service period.
   - Expose GET /v1/reports/revenue-recognition returning Monthly Recognized Revenue vs. Deferred Revenue liability.

OUT OF SCOPE:
- Native tax filing API integration (stub out local tax rate lookup).
- Frontend UI components (provide pure JSON REST APIs).
- Multi-entity legal consolidations.

TECHNICAL CONSTRAINTS & FAILURE MODES:
- All database billing operations must run inside strict ACID SQL transactions to prevent double-billing.
- Usage event processing must guarantee zero event loss and strict idempotent idempotency handling.
- Dunning process must prevent concurrent billing attempts using Redis distributed locks (Redlock).

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