How to take payments in a Base44 app: Stripe or Base44 Payments

Base44 gives you two ways to take payments, both on the Builder plan or higher: Stripe, installed from the AI chat into a test sandbox you later connect to your own Stripe account, and Base44 Payments powered by Wix, a built-in provider run by Wix Payments. Stripe is the usual choice for subscriptions and anything developer-facing. Base44 Payments is quicker to switch on and adds buy-now-pay-later options, in the countries it supports.

Payments are part of the Base44 integrations guide.

Stripe on Base44, step by step#

Base44 released a new Stripe flow in January 2026. From the Stripe setup docs:

1. Install Stripe. Ask the chat, for example Install Stripe and add a checkout for my Pro plan at $19 a month. Review the reply and click Install Stripe. Base44 creates a test environment.
2. Create products and prices. They’re created in Stripe itself, and you manage them from your Stripe dashboard or by asking the chat. Base44 doesn’t keep a separate product database for them.
3. Test the checkout with Stripe’s test card.
4. Claim your sandbox. Go to Dashboard → Integrations → Stripe → Claim your Stripe sandbox and sign in to your Stripe account or create one. You have 60 days to claim it, and the account you connect receives your payouts.
5. Go live. Once your Stripe account finishes activating, Base44 creates your live API keys automatically. If Stripe needs more information, Resume setup in Stripe takes you back to its onboarding.

The Integrations → Stripe page keeps a setup guide showing which steps are done.

Webhooks and “paid” status#

A checkout that redirects to a success page doesn’t prove the payment went through. Stripe tells your app with webhooks, which on Base44 arrive at a backend function’s HTTP endpoint. Ask the chat to handle the events your app depends on, such as checkout.session.completed, invoice.paid and customer.subscription.deleted, and to verify Stripe’s signature. Base44’s own prompt examples include verifying payments before adding credits and making sure credits are only added once even if the page is refreshed.

Common Stripe problems on Base44#

• Blank page or redirect loop after payment. Base44’s docs point to the app environment or redirect settings. Make sure success and cancel URLs use your published domain, and don’t mix preview URLs with live callbacks.
• Test mode still on. If live payments don’t appear, check that the sandbox has been claimed and live keys exist.
• Subscription access not updating. Usually a missing webhook handler. Check your app logs.

Base44 Payments powered by Wix#

Base44 Payments is Base44’s built-in provider, processed by Wix Payments. From the Base44 Payments docs:

• Builder plan or higher, and available to eligible customers in listed countries and currencies.
• Methods: major cards, digital wallets, buy now pay later (Affirm, Klarna, Afterpay/Clearpay, each with its own qualification rules) and local payment methods depending on your country.
• Fees: Wix Payments service fees apply per transaction and appear in settlement reports.
• Restrictions: some products and services can’t be sold, per Wix’s prohibited products policy.
• Verification: your app needs clear business information, pricing, currency and policies before payouts flow. Until verification completes, payouts may be delayed.

You connect it from the dashboard and accept Wix’s payment terms. The currency in your Wix account must match your Base44 Payments account.

Stripe or Base44 Payments?#

That last row matters if you might ever migrate. A Stripe account, its customers and its subscriptions stay with you if the app moves elsewhere.

Selling in a mobile app#

If you publish your Base44 app to the App Store or Google Play, Base44’s docs are clear: “Do not use Stripe for payments inside your mobile app” for digital goods such as subscriptions or in-app features. Apple and Google require their own billing systems for digital content. See Base44 mobile apps.

What to do next#

1. Decide between Stripe and Base44 Payments using the table.
2. Build and test the checkout in the sandbox.
3. Add webhook handling before you claim the sandbox and go live.