Build guide, sources linked

How to add payments to a Bubble.io app, no company needed

Bubble is one of the most capable no-code builders, and its native path to money is Stripe. If you already have an activated Stripe account, use the plugin, it is smooth. The wall builders hit is at go-live: taking a real payment needs a Stripe account Stripe will actually approve, which usually means a registered company. Here is what that wall is, and how to charge customers the same day without it.

The wall

Bubble has an official Stripe plugin that handles one-time payments, subscriptions and even Connect for marketplaces. To go live with it you need to register a Stripe account and activate it, which means giving Stripe business or personal details and banking information it accepts, before you can switch from test keys to live keys. If you are pre-company, or in a situation Stripe declines or later freezes, your app is finished but it cannot get paid. That is not a Bubble limitation, it is a merchant-onboarding one, and it is the same on every no-code builder. Source: Bubble docs - ecommerce and payments

The path around it: the API Connector

Bubble's API Connector plugin can call any REST API, which is all you need. paas.build gives you a real merchant account with no company via progressive KYB, plus a checkout endpoint. Wire it in three steps:

1. Open the account. Get your sandbox and production keys the same session at paas.build, individuals and sole traders included. No company, no review queue.

2. Add the API in Bubble. Install the API Connector plugin, add "paas.build" as an API, store your key as a private shared header, and create a call to the checkout endpoint that returns a payable link or session.

3. Trigger it from a workflow. On the buy or subscribe button, run the API call and send the user to the returned link. Add a backend workflow to receive the webhook so renewals, retries and dunning run server-side, even when nobody has the app open.

The full endpoints and an agent-native setup live in the docs, and an AI builder can wire the whole thing by reading llms.txt or calling the MCP server.

The cost, and who stays the merchant

A flat 3.9%, no fixed fee, no monthly fee. You stay the merchant of record, so your name is on the checkout, the customer is yours, and the money settles to you on FCA-authorised safeguarded rails. You keep your own sales tax, which is the honest trade against a Merchant of Record.

On a $9 sale	Typical MoR (5% + $0.50)	paas.build
Fee	$0.95 = 10.6%	$0.35 = 3.9%
Who is the merchant	The provider	You
Company needed	Usually	No

When the Stripe plugin is the right call

Use Bubble's Stripe plugin if you already have an activated Stripe account in good standing and you are in a supported country. It is native, well documented, and there is no reason to reach past it.

Use paas.build if you have no company yet, Stripe declined or froze you, or you just want to be live and charging today. Real merchant account the same session, flat 3.9%, you stay the merchant, UK, EU and US. Not sure where your app stands? Run the free payment-readiness check.

FAQ

Can you take payments in Bubble without Stripe?

Yes. Bubble's native plugin is built around Stripe, but Bubble's API Connector can call any REST payment API. paas.build gives you a real merchant account and a checkout endpoint you call from a Bubble workflow, so you can charge customers without a Stripe account, and without a registered company, in the UK, EU or US.

Does Bubble's Stripe plugin need a company?

To take live payments, Bubble's Stripe plugin needs an activated Stripe account, which means verified details and banking information Stripe accepts. Builders without a registered company, or whose account Stripe declines, hit a wall at go-live. paas.build uses progressive KYB to open a live capped account the same session, individuals included.

How do I connect paas.build to Bubble?

Use Bubble's API Connector plugin. Add paas.build as an API, store your key as a private header, and create a call to the checkout endpoint that returns a payable link or session. Trigger it from a workflow when a user clicks buy or subscribe. A backend workflow can also verify the webhook so subscriptions and renewals run server-side.

What does paas.build cost for a Bubble app?

A flat 3.9% per transaction, no fixed fee, no monthly fee, no company required. You stay the merchant, so your name is on the checkout and the funds settle to you on FCA-authorised safeguarded rails. Available to builders in the UK, EU and US.

Open my account - no company needed Check my app →