A single-account model: the builder's own secret key is stored encrypted against their organisation and used for every charge on their invoices. Settlement currency is per-business. The platform's own billing runs on an entirely separate account and can never be used to charge a builder's customers.
Also called: connect stripe · my own stripe account · who holds the money · payment settings · cad or usd
- 1Keys are encrypted with AES-256-GCM and cached in memory for 60 seconds to avoid decrypting on every call.
- 2getOrgStripeClient returns null when a business has no key — online payment simply is not set up for them, and the Pay button does not render.
- 3The environment key only bootstraps the default org, so a second tenant without its own key can never accidentally charge on someone else's account.
- 4Currency resolves from the org's stored setting, then the environment default.
Builders take their customers' money into their own bank account, and a platform that sits in the middle of that owns their fees, refunds, chargebacks and payouts — not a position a customer's $40,000 draw should be routed through. Each business connects its own payment account and remains the merchant of record; the funds, the fees and the payouts are theirs. Charging cannot start until a business's own keys are in place, so one company's invoice can never be charged on another company's account.
- Platform-held funds and payout delays.
- A shared processor account risking cross-business charges.
- Wrong settlement currency for non-US builders.
See it on your own jobs
Twenty minutes, your numbers, no slide deck. We’ll build one of your real buildings in front of you and send you the estimate link at the end — yours to keep either way.
or keep browsing features →