fix(cloud): persist Stripe Connect capability booleans so fiat payouts aren't permanently rejected (#11172)

[NubsCarson]

Closes #11172.

Problem (HIGH — launch-blocking for the fiat payout rail)

The Connect account.updated webhook derived status from the capability booleans but dropped the booleans. payouts_enabled defaults false (migration 0150) and the payout transfer gate reads it directly:

// transfer/route.ts
if (account.status !== "active" || !account.payouts_enabled) → reject

So a creator fully onboards → Stripe fires account.updated (charges_enabled=true, payouts_enabled=true) → we stored status='active' but left payouts_enabled=false forever → every Stripe Connect fiat payout permanently rejected, with no recovery path. (On-chain hot-wallet payouts are unaffected — this is the Stripe fiat rail specifically.)

Fix (option a — keep the column truthful)

mapConnectWebhookEvent now returns the raw chargesEnabled/payoutsEnabled from account.updated, and the webhook route persists them alongside status via updateByAccountId (which already accepts charges_enabled?/payouts_enabled?). The column reflects reality: true when Stripe reports the caps, false when it doesn't.

await stripeConnectAccountsRepository.updateByAccountId(outcome.accountId, {
  ...(outcome.status ? { status: outcome.status } : {}),
  ...(outcome.chargesEnabled !== undefined ? { charges_enabled: outcome.chargesEnabled } : {}),
  ...(outcome.payoutsEnabled !== undefined ? { payouts_enabled: outcome.payoutsEnabled } : {}),
});

Chose (a) over (b) (dropping the redundant gate check) so the persisted column stays accurate for any other reader, not just the transfer gate.

Tests

• stripe-connect-payout.test.ts: mapper surfaces the booleans (both true → also active; charges-true/payouts-false → surfaced truthfully).
• stripe-connect-webhook-route.test.ts: the account.updated persist now asserts { status: "active", charges_enabled: true, payouts_enabled: true } — the regression guard (previously { status: "active" } alone, which is exactly the bug).

bun test packages/cloud/shared/src/lib/services/stripe-connect-payout.test.ts            # 12 pass
bun test packages/cloud/api/__tests__/stripe-connect-webhook-route.test.ts               # 13 pass

packages/cloud/shared typecheck + packages/cloud/api build + biome all clean.

Evidence

• The write/read contract is proven by the route test asserting the exact persisted patch (the payout gate then reads a true column). No mock stands in for the persisted value.
• N/A (no UI / no new migration / no model): the column + repo method already exist; this wires the webhook to write them.

Money-path — flagging for maintainer review/merge rather than self-merge. [cloud-security]

[greptile-apps]

Your trial has ended. Reactivate Greptile to resume code reviews.

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 7d9e4835-d761-49f8-a232-b7c7d31cd561

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch nubs/stripe-connect-persist-payouts-enabled

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[claude]

Claude encountered an error —— View job

---

I'll analyze this and get back to you.