When you tell Base44 "add payments," it installs Stripe or Base44 Payments (powered by Wix). Both are solid — until you read the fine print: a registered business and a bank account in a supported country before you can take a single real payment. paas.build removes that wall. A live merchant account the same day, no company, 3.9% flat — wired into Base44 through surfaces it already supports.
Three things Base44's built-in payments can't do — straight from Base44's own docs and feedback board:
paas.build fixes all three: progressive KYB means live the same day with no company; FCA rails cover merchants Stripe/Wix lock out; and because you're the merchant on our 24/7 rails, recurring billing runs server-side.
Pick one. You don't need Base44's permission or a partnership — these are documented Base44 surfaces.
In Base44: Settings → Account → MCP connections → Add custom MCP. Base44's AI then "treats MCP connections as tools it can call when your request requires external data or actions." Base44 docs
Now say to the Base44 chat: "use paas.build to create a live merchant account and a checkout." Note Base44's limit — MCP runs in the editor chat while you build, not at app runtime; use it to provision + scaffold, then one of the runtime paths below to charge.
A workspace admin adds our OpenAPI spec once; your app then calls it at runtime via base44.integrations.custom.call(), with your key stored as an encrypted workspace secret. Base44 docs
Backend functions "run on the server, so you can safely store API keys and secrets as environment variables" and fetch any external API. Base44 docs
| On a $9 subscription | Fee | Effective |
|---|---|---|
| Stripe / Wix Payments pattern (5% + $0.50) | $0.95 | 10.6% |
| paas.build (3.9% flat) | $0.35 | 3.9% |
Base44's built-in options are Stripe and Base44 Payments (powered by Wix), plus Tranzila/Max for Israel. But Base44 lets you wire ANY external service three ways: a custom MCP connection, a custom OpenAPI integration, or a backend function. paas.build plugs in through all three, so a Base44 app can take payments even where Stripe and Wix Payments aren't available.
Yes - that's the gap paas.build fills. Stripe live mode and Wix Payments both require a registered business and bank account first. paas.build uses progressive KYB: your Base44 app goes live with a real capped merchant account the same session, and verification completes in the background. No company needed to start.
Base44's own users have asked for this repeatedly (the top payments request on their feedback board). paas.build runs on FCA-authorised UniPaaS rails and onboards builders in the UK, EU and US, with your customers able to pay from anywhere - covering merchants Stripe and Wix Payments lock out.
Base44's webhooks only fire while someone is actively using your app, which breaks 3am renewals, retries and dunning. Because paas.build is the merchant/PayFac running its own 24/7 rails, recurring billing, failed-payment retries and dunning run server-side, independent of app sessions.
3.9% flat per transaction. No monthly fee, no setup fee, no fixed per-transaction fee - so a $9 subscription costs $0.35, versus roughly $0.95 at a typical Merchant of Record.