LovableLovable 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.
The official flow only works after you deploy — so every payment tweak means another deploy just to test.
with paas.build: Our sandbox works anywhere: real test account, test cards, no deploy needed.
Payment succeeds but your app never updates — STRIPE_WEBHOOK_SECRET mismatches and edge-function ordering are the #1 support topic.
with paas.build: First sale with zero webhook plumbing — drop-in checkout or a hosted link.
Keys in chat, Supabase edge functions, success URLs configured in two places — lots of moving parts before £1 moves.
with paas.build: Two env vars from your welcome email. That’s the whole setup.
In the chat, describe your product and paste the prompt below. Lovable's agent reads our docs and wires the checkout component.
Click Go live 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.
Drop your keys into Lovable's env settings. Your buyers pay inside your app — your name on the receipt.
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.
One flat rate: 3.9% per transaction. No monthly fee, no per-transaction fixed fee, no "contact sales".
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.