Updated 2026-07-28
An AI app builder with Stripe payments
Describe a paid feature and Mortar builds it as real Django + Stripe — bring your own Stripe keys, or have Payments via Mortar create the account for you. Customers pay into your account, and you own the code.
How payments work
- ✓Two ways in: bring your own Stripe keys, or click "Payments via Mortar" and an account is set up FOR you — a short hosted verification (bank + ID) and your app takes card payments.
- ✓Your own keys: encrypted, injected only at runtime; the AI never sees them. No platform fee — you pay only Stripe's.
- ✓Payments via Mortar: no Stripe dashboard to learn, one account works across all your projects; Mortar's fee is 3% per successful payment.
- ✓Customers pay into YOUR Stripe account either way (you keep the code + the account).
- ✓Checkout wired with a tested primitive; verified webhooks.
- ✓Real Django (Python) — models, views, templates, migrations, tests.
Frequently asked
Whose Stripe account receives the money?
Yours. With your own keys, payments go straight to your account. With Payments via Mortar, the Stripe account created for you is also yours — it stays yours even if you disconnect, and Mortar only takes a 3% application fee per successful payment.
Do I need my own Stripe account?
No. Choose Payments via Mortar and the account is created for you — complete a short Stripe-hosted verification (bank details + ID) and your published app can take card payments. Power users can bring their own Stripe keys instead.
Does the AI see my Stripe secret key?
No. Keys are encrypted and injected only into your running app; the build agent references them by name and never sees the values.
Do I own the code Mortar generates?
Yes. Every project is a real Django repository you can export in full and run anywhere — there is no proprietary runtime and no vendor lock-in.
Build a real Django app you own
Describe it in plain English. Preview, edit, and export the full source — no lock-in.
Start building