Lovable payment gateway production errors
Checkout works in test, but fails on your published Lovable app. First identify how payments were connected. Built-in payments use separate test and live environments and require completed go-live checks. Connecting your own Stripe account uses one key at a time, including in preview. Those setups need different checks. Lovable built-in payments · Self-managed Stripe. Both read October 31, 2026.
This guide covers a published app whose checkout fails after a successful test. If publishing itself fails, use the Lovable deployment guide. For other app failures, see Lovable app troubleshooting.
Identify your payment setup before changing anything
Open More → Payments. A Self-managed Stripe badge identifies the integration that connects a Stripe account you control directly. Built-in payments instead provide a test/live data toggle and a go-live checklist. The Stripe connector setting alone does not identify your setup: the same workspace setting controls both Stripe integrations. Self-managed Stripe, “Manage the integration” and FAQ; built-in payments, “The payments tab.” Read October 31, 2026.
Using an existing Stripe account does not, by itself, mean you have the self-managed integration. Built-in Stripe lets you link its sandbox to an existing account during the claim step. Confirm the integration in Lovable before following either branch. Built-in Stripe go-live, read October 31, 2026.
Do not disconnect payments to diagnose this failure. Keep keys out of messages and screenshots. For self-managed Stripe, do not assume preview is a test environment: with a live key, preview payments are real. This walkthrough uses status checks and existing logs, with no live purchase. Built-in disconnection behavior · Self-managed Stripe test and live behavior, read October 31, 2026.
Match the observation to the next check
Follow the rows in order within your integration. The expected observation is a checkpoint, not proof that live payment processing has passed.
| Observed status | Applies to | Documented check | Expected observation and next step |
|---|---|---|---|
| Checkout opens, but the attempted card type does not match the payment mode | Both integrations | Compare the already-attempted card type with the established mode. Built-in preview accepts test cards; the published app uses live mode. Self-managed Stripe follows its configured key, even in preview. | Test cards belong only in test mode; real cards belong only in live mode. Rejection of a mismatched card is expected and is not, by itself, evidence of a code fault. Do not try a real card to diagnose this. If the self-managed mode is unknown, stop payment attempts and use the unknown-mode path below. [1][2] |
| Preview checkout succeeds; published checkout does not; go-live steps remain incomplete | Built-in payments | Inspect the Payments go-live checklist, including the provider-specific steps below. | An incomplete verification, readiness or onboarding step explains why test success has not enabled live payments. Resolve the named step before investigating checkout code. [1] |
| Payments shows The live API key is invalid | Built-in payments | Check the displayed environment and exact error. Lovable directs this case to support. | The message identifies a provider authentication problem. Contact Lovable support to restore the connection; do not treat it as an instruction to disconnect. [1] |
| Go-live steps are complete, but the live catalog differs from the tested catalog | Built-in payments | Compare products and prices in the test/live views and check whether the catalog changes were published. | Products and prices created through Lovable sync on publish. Manage corrections through Lovable, then publish the intended changes. Discounts are excluded from that sync. [1] |
| Payments shows Self-managed Stripe, and the app still uses test configuration | Self-managed Stripe | Use the mode check below: the account owner's existing record of the most recent key submission can establish test mode; Lovable does not display the stored value. If mode cannot be established, mark it unknown and stop payment attempts. Compare product/price references only against the established mode. | This integration has one key at a time. Live operation needs live products and live price IDs as well as live credentials. Test and live price IDs differ; built-in catalog sync is not the procedure here. [2] |
| Clicking checkout opens no new tab | Self-managed Stripe | Check whether the browser blocked a popup for your app. Allow it for that address and open checkout, stopping before payment. | Checkout should open in a new tab. If it opens but payment fails, check the card/mode row first, then inspect the existing error logs. [2] |
| Checkout returns an error | Self-managed Stripe | Read the checkout function logs and the matching failed request in Stripe's Developers → Logs. | Record Stripe's actual error before choosing a fix. Use More → Settings → Logs for the built-in backend, or Edge Functions logs in your own Supabase dashboard. [2] |
Table sources, read October 31, 2026: [1] Lovable built-in payments, “Test and live environments,” “Go-live,” “Publishing and product sync,” and invalid-key FAQ. [2] Connect your own Stripe account, “Test and go live” and “Troubleshooting.” The row order is our diagnosis recommendation.
Built-in payments: finish the provider's go-live path
First compare the card type from the failed attempt with the environment: preview accepts only test cards, while published checkout uses live mode and processes real cards. A card/mode mismatch is not a reason to rewrite checkout. Do not retry with a real card as a diagnostic step. Test and live environments · Stripe card/mode troubleshooting, read October 31, 2026.
For Paddle, inspect readiness, project setup, seller verification and domain review. The project setup check requires a product with a price and published changes. Readiness checks look for the required policy pages and substantive site content. A domain review marked Action required needs the issue in Paddle's email resolved before resubmission; a fully rejected domain needs Paddle support. These are provider checks, not an instruction to replace your checkout code. Paddle go-live, read October 31, 2026.
For built-in Stripe, check that you have claimed the account and completed Stripe's onboarding steps. During onboarding, Stripe prompts you to copy products, prices and the Lovable app into the live account. Installing that app connects live keys and webhooks. Lovable also checks your site's privacy policy, terms, refund policy and substantive content. Follow this built-in flow rather than the self-managed key setup. Stripe go-live, read October 31, 2026.
After initial setup, products and prices managed through Lovable sync when you publish. Compare the live catalog with the intended offer after the publish. Avoid editing built-in products directly in the provider dashboard: Lovable warns that this can create ID mismatches between environments. If only a discount fails, check that discount in the live environment separately; publish sync does not include discounts. Publishing and product sync, read October 31, 2026.
Self-managed Stripe: inspect the failed request
For the self-managed integration, a successful test does not establish that the app is configured for live mode. Lovable stores STRIPE_SECRET_KEY but never shows its value again, so opening the Secrets view cannot reveal its mode. Where your key is stored, read October 31, 2026.
If the account owner has an existing record of the most recent key submitted through Connect Stripe or Update Stripe secret key, check that record privately. Lovable documents rk_test_ and sk_test_ as test-key prefixes. Use that record only if it identifies the current submission; an older test record does not establish the current mode. If the record is missing or uncertain, write mode unknown and stop payment attempts, including in preview. Continue with existing-log inspection only. The record check is our diagnosis recommendation based on Lovable's key and mode documentation, read October 31, 2026. Do not retrieve, copy or share a secret for this check, or replace production credentials just to find out the mode.
Once mode is established, compare the app's product and price references with that environment. Live operation needs live products and live price IDs. Self-managed go-live instructions, read October 31, 2026.
If checkout produces an error, use the function log and Stripe request log to identify it. Keep a private diagnostic note containing the integration type, test or live mode, affected app URL and the error text. Redact credentials and customer details before sharing an excerpt. Ask for a fix tied to that error, rather than a replacement of the entire payment integration. The log locations are documented in Lovable's Stripe troubleshooting, read October 31, 2026; the note format is our recommendation.
Do not add a webhook merely because production checkout fails. Self-managed Stripe checks payment and subscription status directly by default; webhooks are an optional addition. Built-in payments manage their own webhooks. Instructions to create an endpoint for one setup do not apply to the other. Self-managed webhooks · Built-in webhook endpoints, read October 31, 2026.
If an existing payment succeeded but access never appeared, record that as a different observation. For built-in payments, a missing app webhook endpoint can stop subscription activation even though purchases succeed. For self-managed subscriptions, Lovable documents matching the signed-in user's email to the Stripe customer's email. Inspect the relevant setup before treating this as a failed charge. Built-in webhook endpoints · Self-managed subscriptions, read October 31, 2026.
Validate without making a live charge
For built-in payments, use the preview's test mode for a test purchase. Check the resulting test transaction, the return flow and whether the intended features become available. Lovable documents these as test checks. Recheck the live go-live checklist and catalog separately. Built-in testing, read October 31, 2026.
For self-managed Stripe, only run a simulated purchase when the account owner has confirmed that the project uses test credentials. If it uses live credentials or its mode is unknown, stop at configuration and existing-log inspection. Preview does not provide a separate test environment for this integration. Self-managed test and live behavior, read October 31, 2026.
Record what passed and what remains unknown. These checks do not verify a live charge, settlement or the complete production purchase flow. Lovable's self-managed guide includes a real purchase in its go-live procedure; that step is outside this walkthrough.
If your own domain fails to load or shows a certificate warning before you reach checkout, the custom-domain SSL checker checks DNS and certificates for the domain and its www counterpart. It does not verify payments, account approval or checkout. Checker scope, read October 31, 2026.
Check the rest of your launch
Request a free launch-safety check.
Sources
- Built-in payments, test and live modes, and go-live: Lovable, “Add payments to your app”
- Connecting your own Stripe account and going live: Lovable, “Connect your own Stripe account”
Updated October 31, 2026