fix(billing): deep-audit P0/P1 fixes for the pinned Stripe API (2026-04-22.dahlia)

Independent audit (verified vs Stripe Basil 2025-03-31 changelog):
- P0: period end moved off the top-level Subscription -> read
  sub.items.data[0].current_period_end (grace/lapse now actually fires;
  was always null -> past_due members never went 'late').
- P0: invoice subscription metadata moved under invoice.parent.
  subscription_details -> read parent (metadata member-resolution was
  always failing, mislinking dues payments).
- P1: handle only invoice.paid (not also invoice.payment_succeeded) +
  pre-insert dedupe on (space_id,platform,external_id) -> no double
  payment-ledger rows.
- P2: idempotencyKey on customers.create -> no duplicate Stripe
  customers under concurrent checkout.
- 040: documented the 'do not wrap in manual BEGIN/COMMIT' caveat.
(P0 webhook-reprocess-on-failure was fixed in ca34e53.) Audit verdict:
isolation/secrets/RLS/status-bounds were already sound.
This commit is contained in:
Moheeb Zara
2026-05-17 03:46:08 -07:00
parent ca34e5393a
commit b477c38425
3 changed files with 58 additions and 24 deletions
+27 -4
View File
@@ -95,7 +95,13 @@ export async function POST(
customerId,
)
if (!memberId) return
const periodEnd = isoFromUnix((sub as unknown as { current_period_end?: number }).current_period_end)
// API 2026-04-22.dahlia (Basil 2025-03-31): the billing period moved off
// the top-level Subscription onto each subscription item. Dues are a
// single-price subscription, so item 0 carries the period end.
const periodEnd = isoFromUnix(
(sub.items?.data?.[0] as unknown as { current_period_end?: number } | undefined)
?.current_period_end,
)
await admin.from('member_billing').upsert(
{
@@ -142,14 +148,30 @@ export async function POST(
await applySubscription(event.data.object as Stripe.Subscription)
break
}
case 'invoice.paid':
case 'invoice.payment_succeeded': {
// Handle ONLY invoice.paid (Stripe also fires invoice.payment_succeeded
// for the same invoice — handling both would double the ledger).
case 'invoice.paid': {
const inv = event.data.object as Stripe.Invoice
const customerId = typeof inv.customer === 'string' ? inv.customer : inv.customer?.id ?? null
// API 2026-04-22.dahlia (Basil): invoice subscription + its metadata
// moved under invoice.parent.subscription_details.
const invParent = (inv as unknown as {
parent?: { subscription_details?: { metadata?: Record<string, string> } }
}).parent
const memberId = await resolveMemberId(
(inv.subscription_details?.metadata?.member_id as string | undefined) || undefined,
invParent?.subscription_details?.metadata?.member_id || undefined,
customerId,
)
// Ledger idempotency: invoice.paid + a retry are distinct event ids
// but the same invoice; never double-record one charge.
const { data: dupe } = await admin
.from('payments')
.select('id')
.eq('space_id', spaceId)
.eq('platform', 'stripe')
.eq('external_id', inv.id)
.maybeSingle()
if (!dupe) {
await admin.from('payments').insert({
space_id: spaceId,
member_id: memberId,
@@ -165,6 +187,7 @@ export async function POST(
transaction_date: new Date().toISOString(),
raw_data: { event_id: event.id, invoice: inv.id },
})
}
if (memberId) {
await admin
.from('space_members')
+7 -2
View File
@@ -141,11 +141,16 @@ export async function startDuesCheckout() {
let customerId = billing?.stripe_customer_id as string | undefined
if (!customerId) {
const customer = await stripe.customers.create({
// Idempotency key keyed by member: concurrent checkouts won't create
// duplicate Stripe customers (Stripe returns the same customer).
const customer = await stripe.customers.create(
{
email: (m.email as string | null) ?? undefined,
name: (m.display_name as string | null) ?? undefined,
metadata: { space_id: member.space_id, member_id: member.id },
})
},
{ idempotencyKey: `cust:${member.space_id}:${member.id}` },
)
customerId = customer.id
await admin
.from('member_billing')
+6
View File
@@ -18,6 +18,12 @@
--
-- Idempotent: ADD VALUE IF NOT EXISTS, CREATE TABLE/INDEX IF NOT EXISTS,
-- DROP POLICY IF EXISTS then CREATE.
--
-- Apply this file as-is (Supabase SQL editor / psql). Do NOT wrap it in a
-- manual BEGIN/COMMIT: `ALTER TYPE ... ADD VALUE` historically could not run
-- inside a transaction block (fine on Supabase PG15 unwrapped). The new
-- value is not used by any statement here, so a single implicit transaction
-- is safe and re-runs are no-ops.
-- =============================================================================
ALTER TYPE public.payment_platform ADD VALUE IF NOT EXISTS 'stripe';