Futurista Soft Book a call (opens in a new tab)
Founder guide

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.

Short answer

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 says a project can’t use both at once.

What the symptom usually means

What you seeUsuallyTry first
Checkout button does nothingA popup blocker stopping checkout opening in a new tabAllow popups for your app’s address and try again
Checkout opens but payment failsA test card used with a live key, or a real card with a test keyUse Stripe’s test cards with a test key, and real cards only with a live key
Stripe rejects the keyA publishable key (pk_), or a restricted key without enough permissionsUse 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 StripeThe workspace’s Stripe connector is switched offAsk a workspace admin or owner to switch it on under Connectors in the admin settings
Checkout fails with an errorThe backend function hit a problemRead the checkout function’s logs, and Stripe’s Developers → Logs
Customer portal won’t openThe portal isn’t switched on in Stripe, or you’re in the preview panelActivate the customer portal in Stripe, test on the published app
“No signatures found matching…”The webhook is checked against the wrong signing secretSee the webhook section below
Webhook gets 401 (your own Supabase)The function still requires a signed-in user, and Stripe never sends oneTurn JWT verification off for that function, and check Stripe’s signature instead
Customer paid, nothing unlockedAccess is granted on the success page only, or the webhook endpoint was deletedGrant access from the webhook, and check the endpoint still exists
Test payments work, live ones don’tTest and live are separate, with different keys, prices and webhook secretsCheck 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.

Before you go live

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.

Read next