motovaultpro/backend/src/features/subscriptions/domain/subscriptions.service.ts at 3b5b84729fbfc159b36a545f8e79eae03f1aa032

egullickson/motovaultpro

Fork 0

Files

Eric Gullickson 8a73352ddc

Deploy to Staging / Build Images (push) Successful in 3m39s

Details

Deploy to Staging / Deploy to Staging (push) Successful in 53s

Details

Deploy to Staging / Verify Staging (push) Successful in 9s

Details

Deploy to Staging / Notify Staging Ready (push) Successful in 8s

Details

Deploy to Staging / Notify Staging Failure (push) Has been skipped

Details

fix: charge immediately on subscription and read item-level period dates

Three fixes to the Stripe subscription flow:

1. Change payment_behavior from 'default_incomplete' to
   'error_if_incomplete' so Stripe charges the card immediately instead
   of leaving the subscription in incomplete status waiting for frontend
   payment confirmation that never happens.

2. Read currentPeriodStart/End from subscription items instead of the
   top-level subscription object. Stripe moved these fields to
   items.data[0] in API version 2025-03-31.basil, causing epoch-zero
   dates (Dec 31, 1969).

3. Map Stripe 'incomplete' status to 'active' in mapStripeStatus() so
   it doesn't fall through to the default 'canceled' mapping.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

2026-02-16 20:40:58 -06:00

31 KiB

Raw Blame History

View Raw

31 KiB Raw Blame History

31 KiB

Raw Blame History