Lovable Stripe not working? Fixing checkout, keys and webhooks
Last reviewed 21 November 2026
Payments are where a broken app costs real money: customers who pay and get nothing, or checkout that silently fails. Lovable has two different ways of taking payments, and the fixes depend on which one you have, so start there.
First check whether your app uses Lovable’s built-in payments or your own Stripe account, since a project can’t use both. Then match the symptom: checkout that does nothing is often a popup blocker, a payment that fails at checkout often means a test card used with a live key (or the reverse), a rejected key usually means the wrong key type, and payments that don’t unlock usually mean a missing or failing webhook. Read the function logs and Stripe’s own logs before changing code.
Which payment setup do you have?
- Lovable’s built-in payments (“Lovable payments”, powered by Paddle or Stripe) need a paid Lovable plan. Lovable creates the account and handles the webhooks, and keeps separate test and live environments. See Lovable’s payments guide.
- Your own Stripe account, connected with your API key. Lovable writes backend functions that call Stripe, and stores the key as a secret named
STRIPE_SECRET_KEY. See Lovable’s Stripe guide.
Lovable says a project can’t use both at once.
What the symptom usually means
| What you see | Usually | Try first |
|---|---|---|
| Checkout button does nothing | A popup blocker stopping checkout opening in a new tab | Allow popups for your app’s address and try again |
| Checkout opens but payment fails | A test card used with a live key, or a real card with a test key | Use Stripe’s test cards with a test key, and real cards only with a live key |
| Stripe rejects the key | A publishable key (pk_), or a restricted key without enough permissions | Use a restricted (rk_) or secret (sk_) key, and check the restricted key’s permissions in Stripe. Never paste keys into chat |
| No option to connect Stripe | The workspace’s Stripe connector is switched off | Ask a workspace admin or owner to switch it on under Connectors in the admin settings |
| Checkout fails with an error | The backend function hit a problem | Read the checkout function’s logs, and Stripe’s Developers → Logs |
| Customer portal won’t open | The portal isn’t switched on in Stripe, or you’re in the preview panel | Activate the customer portal in Stripe, test on the published app |
| “No signatures found matching…” | The webhook is checked against the wrong signing secret | See the webhook section below |
| Webhook gets 401 (your own Supabase) | The function still requires a signed-in user, and Stripe never sends one | Turn JWT verification off for that function, and check Stripe’s signature instead |
| Customer paid, nothing unlocked | Access is granted on the success page only, or the webhook endpoint was deleted | Grant access from the webhook, and check the endpoint still exists |
| Test payments work, live ones don’t | Test and live are separate, with different keys, prices and webhook secrets | Check each one is the live version |
Webhooks: the usual cause of “paid but nothing happened”
Stripe’s fulfilment guide is clear that you can’t rely on the success page alone: people close the tab, and the redirect never runs. A webhook tells your backend the payment really happened.
- By default, Lovable’s own-Stripe setup doesn’t use webhooks. It checks with Stripe directly and matches subscriptions to users by email. If you ask for webhooks, you create the endpoint in Stripe and give Lovable the signing secret.
- The signing secret starts with
whsec_. It isn’t your API key. Each endpoint has its own, and the test and live versions differ, as does the one the Stripe CLI prints for local testing. Stripe says the wrong secret is the most common signature error. - The check needs the raw request, exactly as Stripe sent it. Code that reads it as JSON first will fail the signature check.
- Answer quickly and expect repeats. Stripe wants a fast success response, retries failures, and can send the same event more than once, so record which events you’ve handled.
- On built-in payments, deleting the app’s webhook endpoint means purchases succeed but features never unlock. For “invalid webhook signature”, Lovable suggests first checking that the webhook handler still exists and that no duplicate endpoint uses the same address. If deliveries still fail, ask it to rotate the secret, republish straight away, then check your payment dashboard for purchases made in between, because missed events aren’t sent again.
Before you go live
- Know which mode you’re in. With a live key, payments made in the preview are real.
- Use a restricted key with only the permissions the app needs. Stripe recommends it.
- Unlock features on the server, from the webhook, never because the browser says payment worked.
- Disconnecting isn’t switching off. On your own Supabase, the key stays in Supabase and deployed functions keep charging until you delete it.
When to get help
If customers have paid and not received what they bought, fix that first and contact them. Payment logic is worth having a developer read, because the bugs are quiet and expensive. See hiring a Lovable developer.
Questions founders ask
Does Lovable have a Stripe integration?
Yes, two kinds: built-in payments, which Lovable sets up and runs for you on paid plans, and a connection to your own Stripe account using your API key.
Which Stripe key do I give Lovable?
A restricted key (starting rk_) or a secret key (sk_) in the Connect Stripe form, never a publishable key, and never pasted into the chat. Stripe recommends restricted keys.
Why do test payments work but live ones fail?
Stripe keeps test and live completely separate: different keys, product and price IDs, and webhook signing secrets. Each needs its live version.