Card payments on your own Stripe account

What it is

A secret key and optional webhook signing secret stored encrypted on the account row, resolved per account with a short cache, plus a per-account settlement currency. Deliberately not Stripe Connect. The key is only ever returned masked to the UI — unlike the CRM token, the full value never round-trips.

Also called: connect Stripe · take card payments · merchant of record · who holds my money

See it

Card payments on your own Stripe account

Day rate

$400

Days figured

6

Crew size

5

Fuel & equipment

$300

Finished 2 days early — $1,400 back to the crew

The Stripe card in Settings → Integrations: masked key, currency selector, and a green 'Webhook configured automatically' line. Sample data — no customer information appears here.

How it works

1Admin pastes a Stripe secret key in Settings → Integrations.
2The key is encrypted and stored; a masked label and connected timestamp are recorded.
3Currency defaults from environment but can be overridden per account.
4getStripeClient resolves and caches the client per account for outbound calls.
5Only the masked preview and a hasWebhookSecret boolean are returned to the UI.

Why we built it

The module records the architectural choice and its reasoning: 'Single-account model: each org charges on ITS OWN Stripe account (the org is merchant of record — funds, fees, refunds, payouts are theirs)... NOT Stripe Connect — there's one merchant, so Connect's onboarding/account-header machinery buys nothing here; if a second tenant onboards, it just stores its own key.' The masking rule is stated in the route: 'masked-only (secret keys grant payment access; never round-trip the full value).' There is also a currency note flagged for a real client: 'Client is in BC — cad.'

The problem

Routing funds through the platform would make it merchant of record.
A single-currency assumption broke for Canadian builders.
Returning a live payment key to the browser would be a payment-access leak.

Sound familiar?

“does the software company hold my customers' money”“how do refunds work”“I want payments in Canadian dollars”

What you get

Money goes straight to the builder's own account.

Refunds, disputes and payouts stay in their own dashboard.

The payment key is never exposed in full after being saved.

What's inside

The payment webhook sets itself up

Saving a Stripe key creates the webhook endpoint inside the builder's own Stripe account and stores the signing secret, so nobody has to visit the Stripe dashboard.

Invoices mark themselves paid

A verified payment event records the payment against the right invoice, once, with the money only counted when funds have actually cleared.

Safety net for a lost payment webhook

A scheduled sweep re-reads recent settled payments across every payment provider and account, and replays anything not already recorded.

Payments behind a swappable boundary

Card payments run through a provider-neutral contract — checkout, settled-payment listing, single-payment lookup and webhook verification — so a second processor is a registry row, not a rewrite.

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 →