Lovable·FixpaymentsStripeintermediate

A Stripe Customer Is Linked to the Wrong User

Quick Answer

The customer-to-user mapping is being created in the wrong place or with unreliable identity assumptions. This usually happens when billing state is attached from the browser, from email matching alone, or from a race condition during signup and checkout. Start with "Audit where the Stripe customer ID first gets attached" before making broader code changes.

Quick Fix Summary

Most likely cause	The customer-to-user mapping is being created in the wrong place or with unreliable identity assumptions. This usually happens when billing state is attached from the browser, from email matching alone, or from a race condition during signup and checkout.
Fastest fix	Audit where the Stripe customer ID first gets attached
Use this page if	One user gets another user's access

You're in the right place if...

!One user gets another user's access
!Stripe customer IDs look correct in Stripe but wrong in Supabase
!Returning customers create new subscriptions that attach to the wrong account

Why this happens

Fix

Audit where the Stripe customer ID first gets attached

Find the exact point where your app maps a Stripe customer to an internal user. If that happens from loose client state, email guesses, or unaudited metadata, it is the likely bug.

Use one deterministic mapping rule

Create or reuse the Stripe customer only from a signed-in server context and store that customer ID against the current authenticated user immediately.

Check for duplicate customer records

Users can accidentally end up with multiple customer IDs if the app recreates customers instead of reusing them.

select user_id, stripe_customer_id
from subscriptions
where stripe_customer_id is not null
order by user_id;

Patch the generated checkout flow

Tell Lovable to stop guessing identity during billing.

Copy this prompt

Audit the Stripe customer mapping in this app. Create or reuse Stripe customers only from a signed-in server-side context, store the mapping against the correct authenticated user, and remove any browser-side or email-only logic that can attach billing state to the wrong user.

Prevent this next time

Customer mapping should be deterministic, server-side, and tied to authenticated identity. Email matching alone is not a safe billing identity system.