Biloh handles money through two separate Stripe accounts — think of them as two tills that never share a drawer.
- Till 1 — platform billing. Biloh's own Stripe account bills each business for its Biloh subscription (the monthly or annual plan). Money flows from the business to Biloh.
- Till 2 — your payments. Each business connects its own Stripe account to charge its own customers. Money flows from the customer to the business. Biloh never sits in the middle of that drawer.
Keeping the two tills separate is what lets Biloh bill you for the software while you, independently, get paid by the people you serve.
Which till pays for what?
Till 1 is the subscription you pay Biloh: a plan with a fixed monthly or annual price, charged on Biloh's platform account. Till 2 is everything you invoice your own clients for — a cleaning program, a quoted job, a deposit — charged on the Stripe account that belongs to you.
How do I charge my own customers — do I hand Biloh my keys?
No. You connect your existing Stripe account through Stripe's hosted authorisation flow ("Connect with Stripe"). You log into Stripe, approve the connection, and Stripe hands Biloh a connected-account id (acct_…) — never your secret keys. Because it is your own account:
- Card payments settle directly to you.
- You own your payouts, refunds, disputes, and Stripe fees.
- Disconnecting later revokes Biloh's access on Stripe's side, not just locally.
This is Stripe Connect Standard — connecting an account you already own and have already passed identity checks on — rather than a managed account Biloh creates for you. The trade-off is deliberate: you keep full ownership, and Biloh never holds your banking details or your keys.
Why two tills instead of one?
A single shared account would entangle the platform's revenue with each business's revenue — a reconciliation and compliance mess, and a real risk that one business's charge could be misattributed to another. Two tills keep the books, the bank accounts, and the liability cleanly separated. That same insistence on a forgery-proof boundary shows up in how payment webhooks decide who a charge belongs to: see trusting the signed account over webhook metadata.