Lovable payments vs your own Stripe account

As of October 10, 2026, a Lovable app can take money in two ways, and a project uses one or the other. Built-in payments, introduced in Lovable's changelog entry of April 24, 2026, have Lovable create a Stripe or Paddle account for you, with webhooks, test and live environments and a dashboard set up. They need a Pro plan or higher. Your own Stripe account works on any plan, but by default it has no webhooks, matches subscribers by email, and leaves sales tax and disputes to you. Lovable recommends built-in payments for most projects; keep your own account if you already sell through Stripe or need custom billing. Switching later works, but subscriptions do not move on their own.

This guide is for US founders choosing how a Lovable app should charge customers, or whether to switch one that already has paying customers. Platform facts and fees come from Lovable's, Stripe's and Paddle's own documentation and pricing pages, listed under Sources. Setup steps are in our Lovable Stripe integration guide. This is general information, not tax or legal advice.

What are Lovable's built-in payments?

You ask for payments in the project chat and Lovable recommends Paddle or Stripe for what you sell. A short form with your email and name creates the provider account. Lovable then creates products and prices, builds the checkout, and adds a Payments tab under the More menu with revenue, transactions, refunds, chargebacks and a go-live checklist.

Three things happen behind the scenes:

• Two environments. The preview is test mode, where only test cards work; your published app is live. Each publish syncs products and prices from test to live.
• Webhooks are registered for you: two per environment, one feeding your app and one for Lovable's monitoring. Lovable warns that if your app's endpoint is deleted, purchases succeed but features never unlock.
• A go-live review. With Stripe, you claim the account Lovable created and finish Stripe's onboarding; with Paddle, you pass its business verification and domain review. Lovable also checks your live site for a privacy policy, terms, a refund policy and genuine content.

The limits, per Lovable's documentation:

• A Pro plan or higher, and no Lovable fee on top of the provider's own.
• Digital products first. Stripe can also take payments for physical goods, with inventory and shipping managed separately.
• Newer apps on Lovable's TanStack Start stack (created from May 13, 2026, or June 22 on Enterprise plans) work with Lovable Cloud or your own Supabase; older React and Vite apps need Lovable Cloud.
• Some countries are missing from a provider's list because of sanctions or regulation. If yours is, Lovable suggests the other provider.
• One provider per project, one active subscription per user by default, and no remixing a project with payments.
• Checkout styling and payment methods are set in the provider's dashboard, not through Lovable.

What does connecting your own Stripe account involve?

You create a restricted API key in Stripe and enter it in the Connect Stripe form in the Lovable chat, never as a chat message. Lovable stores it as a backend secret and builds checkout and subscriptions with server functions. It works on any plan, with Lovable Cloud or your own Supabase. Verification, payouts, taxes and disputes all happen in your Stripe account.

Four details catch founders out:

• Subscribers are matched by email: a subscription counts only when a user's sign-in email matches their Stripe customer email. Someone who pays with a work email and signs in with a personal one looks unpaid.
• No webhooks by default; the app asks Stripe directly. If you add a webhook, you create the endpoint and signing secret in Stripe yourself.
• One key at a time, with no separate test environment. With a live key in place, payments made from the preview are real.
• Lovable's Payments view is read-only here. Refunds and settings live in Stripe.

Disconnecting removes the key from Lovable and leaves your Stripe account and customers untouched. With your own Supabase, the key stays in Supabase, and the payment functions keep charging until you delete it there.

Paddle or Stripe: what is the difference for a US founder?

The real difference is who the seller is. A merchant of record is the business legally selling to your customer, responsible for collecting and paying sales tax.

Paddle is a merchant of record. It says it calculates, collects and remits sales tax for you, so you do not register for sales tax, and it fights chargebacks and handles buyer support. Your name appears on card statements alongside Paddle's. It pays out monthly: a balance above your threshold (at least $100) on the 1st is sent by the 15th.

With Stripe, your business is the merchant of record, and sales tax is your job. Stripe Tax, priced separately, can calculate tax, alert you near a state's threshold, register for you in supported US states and file US returns, but Stripe says you must file and remit the tax you collect. Disputes are yours too: when a customer's bank reverses a charge, Stripe takes the payment and a dispute fee from your balance, and you respond. Payouts run on a schedule you pick, daily to monthly; the first usually lands 7 to 14 days after your first live payment.

Stripe also offers a merchant of record service for digital products, Managed Payments, open to US-based businesses, which handles sales tax, fraud and disputes; customers see purchases as sold through Link, Stripe's checkout brand. Lovable lists it as an option for built-in Stripe but does not document how to turn it on, so confirm before counting on it. Whether you owe sales tax at all is covered in our launch checklist for US founders.

Fees, from each provider's pricing page on October 10, 2026:

Paddle costs more per sale and does the tax work; Stripe costs less and leaves tax to you. One conflict: Lovable's docs say Paddle charges a flat 10% on transactions under $10, while Paddle's pricing page offers bespoke pricing for products under $10. Confirm with Paddle if you sell cheap items.

How do built-in payments and your own Stripe account compare?

Can you take your account and customers with you later?

Mostly yes, but subscriptions need work. Built-in Stripe runs on an account you claim, and your Paddle seller account is yours too: disconnecting in Lovable does not close or change either. It is permanent, though: that account can never be reconnected to the same project.

Stripe says its users own the sensitive payment data they store with it. It will transfer saved cards to another PCI DSS Level 1 processor or copy them between Stripe accounts. It does not export payment history or subscriptions, which stay readable in your dashboard while the account stays open. Paddle says you can export subscriber data, and it moves card details to a new provider's PCI-compliant vault within two weeks of its security checks.

Between Lovable's options, nothing moves automatically. Moving from your own account to built-in payments creates a new provider account, and existing customers stay in your old one. Switching between Paddle and Stripe means recreating products and prices, and subscribers stay with the old provider until they resubscribe or you move them.

Which should you choose?

• Built-in with Paddle: you sell software or digital products and want someone else to be the seller for sales tax, at a higher fee per sale.
• Built-in with Stripe: you want the quickest setup, sell services or sell mostly in the US, and will handle sales tax with Stripe Tax or an accountant.
• Your own Stripe account: you already sell through Stripe, are on the Free plan, run an older app on your own Supabase, or need custom billing that engineers will take over.
• Stay put: if payments work and tax is handled, switching adds risk for little gain. Fix gaps, such as missing webhooks, in place.

If the app will also ship to phones, check Apple's rules for payments in store apps before you choose.

What should you check before switching an app with paying customers?

Work through these in order, and rehearse the switch in test mode first.

1. 01Confirm what you have nowIn Lovable, open More, then Payments. A Self-managed Stripe badge means your own account; a test and live toggle with a go-live checklist means built-in payments. In Stripe, Developers, then Webhooks shows built-in endpoints ending in ?env=sandbox or ?env=live.
2. 02List every live subscriptionExport active subscriptions, trials and renewal dates from Stripe or Paddle. Check against it afterwards.
3. 03Decide what happens to existing subscribersLovable does not move them. Leave them billing on the old account, or move them with the provider's tools, such as Stripe's Billing migration toolkit.
4. 04Never bill anyone twiceStripe's guide says to cancel old subscriptions before they charge, and when a renewal is close, start the new one after the last old charge. Stripe also has a setting that limits each customer to one subscription.
5. 05Map old IDs to new onesCustomer and subscription IDs change with the account. Link each user to the new IDs and keep the old ones for refunds. With your own Stripe, check each subscriber's Stripe email matches their sign-in email.
6. 06Remove the old code and keysLovable advises removing the old provider's code and webhook routes first. Leaving your own Stripe on your own Supabase? Delete STRIPE_SECRET_KEY there too, or the old functions keep charging.
7. 07Make the new webhooks safeEvents can arrive twice, so each must change your records once (idempotency). Test a purchase, renewal, cancellation, failed payment and refund.
8. 08Tell your customersDisconnecting notifies nobody. Tell subscribers what changes, including the name on their statement.

When should you stop prompting and get help?

Prompting can write a checkout or a webhook handler. It cannot move subscriptions between accounts or tell you where you owe tax. Get help when:

• Paying subscribers would need to move, and a mistake means double charges.
• Customers paid but were not upgraded; see paid but not upgraded.
• The same payment bug has come back after three rounds of prompting.
• You are unsure who owes the sales tax on your sales.

Our vibe-coding rescue service can plan the switch, rehearse it and check every subscriber afterwards. For a wider view first, the free production-readiness check scores your app and names its biggest risks.

Ongoing support plans are on our pricing page.

Sources

All checked on October 10, 2026.

• Lovable documentation: Add payments to your app, on built-in payments, eligibility, webhooks, go-live checks, limits, disconnecting and switching (docs.lovable.dev/features/payments).
• Lovable documentation: Connect your own Stripe account, on keys, email matching, webhooks, disconnecting and switching (docs.lovable.dev/integrations/stripe).
• Lovable changelog: Add payments to your app, in the entry dated April 24, 2026 (docs.lovable.dev/changelog).
• Stripe documentation: Managed Payments, How it works, and Eligibility, on Stripe as merchant of record (docs.stripe.com/payments/managed-payments).
• Stripe documentation: Stripe Tax, and File and remit, on tax calculation, threshold alerts, registration and filing (docs.stripe.com/tax; docs.stripe.com/tax/filing).
• Stripe documentation: Disputes, and Payouts, on chargebacks and payout schedules (docs.stripe.com/disputes; docs.stripe.com/payouts).
• Stripe documentation: Data migrations, Request a payment data export, and the Billing migration toolkit, on moving customers and avoiding double billing (docs.stripe.com/get-started/data-migrations; docs.stripe.com/billing/subscriptions/import-subscriptions-toolkit).
• Stripe: Pricing, on US card, Billing and dispute fees (stripe.com/pricing).
• Paddle documentation: What is Paddle?, on merchant of record, sales tax, chargebacks and card statements (developer.paddle.com/get-started/how-paddle-works).
• Paddle: Pricing, and When and how do I get paid?, on fees and payouts (paddle.com/pricing; paddle.com/help/manage/get-paid/when-and-how-do-i-get-paid).
• Paddle: Subscription migration, on moving payment details and subscriber data to another provider (paddle.com/seller-guides/subscription-migration).