PAYMENTS
Lovable Stripe Integration and Test Checkout
Choose built-in payments or your own Stripe account before configuring checkout. With your own account, the key determines the mode: a live key can produce real charges even in preview.
On this page
Lovable
StripePayment route → mode → access updates
01Built-in payments and owned Stripe are separate routes.
02Test and live products use different price IDs.
03Disconnecting does not cancel existing customer subscriptions.
Start with one practical task
Use a test product and walk through checkout to the resulting account state. Record which side owns the price, which event confirms payment and how a repeated event is handled.
Choose built-in or owned Stripe
Built-in payments provisions a Stripe or Paddle account and manages keys, webhooks and environments. The owned-Stripe route uses your account and key. Requirements vary by plan, app and backend; confirm the current requirements before choosing.
Keep mode and identifiers aligned
For owned Stripe, the supplied key determines test or live mode; preview has no separate test environment. Test and live price IDs differ. A live key can cause real charges even from preview.
Verify the complete payment outcome
A complete checkout flow includes successful and failed payments, webhook delivery, subscription changes and application entitlement updates. Confirm those outcomes in the chosen environment, and keep the payment route and identifiers consistent across the app.
A few more details
Does disconnecting Stripe cancel active subscriptions?
No. Lovable’s documentation says existing subscriptions and refunds must be managed separately in Stripe.
Can I use built-in and owned Stripe simultaneously?
The current guide says a project cannot use both payment routes at the same time.
Sources & maker notes
This guide is based on the cited documentation and maker sources. vibeforthat has not run an independent installation or end-to-end product test for this article.