Taking payments
Connect your own Stripe account so the things you build can charge for something.
You keep your own Stripe account
We never hold your money. You connect your own Stripe account, payouts go straight to you, and you can disconnect at any time.
Connecting
- In Stripe, open Developers → API keys and copy the publishable key and the secret key.
- In BuildMidas, open Settings → Payments — or the + menu inside a build chat. Both open the same dialog.
- Paste both keys and save. The webhook signing secret is optional; add it once you have created a webhook endpoint in Stripe.
Start with Stripe's test keys. Whether you are in test or live mode is decided by the keys themselves rather than a switch here, and both keys must come from the same mode or the save is refused.
What gets built
Once connected, ask for payments in plain words — "sell a $9 plan", "add a checkout". What gets built depends on what kind of product it is:
- Classic website — Stripe Payment Links, because a static site has no server that could hold a secret key safely.
- Dynamic app — a real checkout endpoint and a signature-verified webhook, with success and cancel pages.
- Web game — the checkout flow when it has a backend, otherwise Payment Links.
- Store apps — store billing, not Stripe. That is store policy for digital goods.
- WeChat and Douyin mini-games — those channels use their own payment rails under your local business entity.
Where your secret key goes
It is encrypted where it is stored and never sent back to your browser — the screen only ever shows a mask. It reaches exactly one place: the backend of your own deployed app, handed to it as an environment variable when that app starts. It is never written into build files and never shared with another account.