paas.build Open my account
paas.build ×Lovable logo Lovable

Add payments to your Lovable app.
Live today.

Lovable builds your app from a conversation — payments should work the same way. Paste one message, and your app has a real merchant account behind it.

3.9% flat · no company required · UK, EU & US businesses · buyers pay from anywhere
Get your keys by email
Go live when you're ready - no company needed, 3.9% flat.
Using Lovable Payments? Know what you're choosing.

Lovable's built-in payments runs on Paddle as Merchant of Record - convenient, but Paddle becomes the legal seller: their name on your buyer's invoice, their review queue before you sell, and typically 5% + $0.50 (an effective 10.6% on a $9 subscription). With paas.build you stay the merchant: your brand on the checkout, live the same session via progressive KYB, 3.9% flat - and if your app's users need to get paid too, splits and payouts are native. If you want tax handled for you globally, Paddle is the honest pick - here's the full trade-off.

The chat prompt
lovable — prompt
Add payments to my app with paas.build — create my account and mount checkout.
Connect the MCP server

For any MCP-capable agent

In Lovable's chat, the agent reads paas.build/agents and calls our API directly — no setup. When you continue in an MCP client (Cursor, Windsurf, Claude Code, Cline, VS Code), point it at our server to get identify_business, go_live and create_checkout.

# Hosted remote MCP server (streamable HTTP) — no install https://paas.build/mcp
# or the npm package (stdio) npx -y @paasbuild/mcp

Registry name: io.github.UNIPaaS/paas-build-mcp. Full per-client configs are on the docs page.

The problems Lovable builders actually hit

You’ve seen these. So have we.

✗ Stripe doesn’t run in preview

The official flow only works after you deploy — so every payment tweak means another deploy just to test.

source: Lovable docs →

with paas.build: Our sandbox works anywhere: real test account, test cards, no deploy needed.

✗ The webhook-secret maze

Payment succeeds but your app never updates — STRIPE_WEBHOOK_SECRET mismatches and edge-function ordering are the #1 support topic.

source: Lovable FAQ →

with paas.build: First sale with zero webhook plumbing — drop-in checkout or a hosted link.

✗ Setup spread across three tools

Keys in chat, Supabase edge functions, success URLs configured in two places — lots of moving parts before £1 moves.

source: Lovable docs →

with paas.build: Two env vars from your welcome email. That’s the whole setup.

Three steps

From prompt to first payment

1. Tell Lovable what you sell

In the chat, describe your product and paste the prompt below. Lovable's agent reads our docs and wires the checkout component.

2. Open your account at paas.build

Click Open my account here (or let the agent call our API). You get a real account — sandbox + production — the same day, capped until verification completes in the background.

3. Take your first payment

Drop your keys into Lovable's env settings. Your buyers pay inside your app — your name on the receipt.

FAQ

Do I need a company to accept payments in my Lovable app?

No. Individuals and sole traders go live the same day with a capped account; verification completes in the background. Companies finish a short identity step.

How much does it cost?

One flat rate: 3.9% per transaction. No monthly fee, no per-transaction fixed fee, no "contact sales".

Can my Lovable app pay my own users too?

Yes — paas.build is a payment facilitator, so marketplaces and communities can split payments and pay their users out. A merchant-of-record (like Paddle) structurally cannot.

Your payments, live today. Not in a week.

One prompt. A real account. 3.9% flat.