Collect in the driveway.
Card, Tap to Pay, check, cash, bank: collected on the job and landed on the invoice. Stripe processes, you stay merchant of record, and Thorbis adds no platform fee.
Thorbis ↔ Stripe
- Card on the job2.9% + $0.30
- ACH direct debit0.8%
- Thorbis platform fee$0
- Cash and checksfree to record
The data contract
What moves, and which way.
Payments, into the record
Card, Tap to Pay, and bank payments collected on the job land on the invoice that earned them, not in a processor dashboard someone reconciles later.
Deposits, visible
Payouts show up as deposits you can see against the jobs inside them. The deposit is real money, not a screenshot of a balance.
Cards, never held here
Card data lives with the processor, not on Thorbis servers. That boundary is documented on the security page, in writing, before rollout.
The rate card
The rates are printed.
Domestic card 2.9% + $0.30, ACH 0.8%, disputes $15. The full processor table is on the pricing page beside every other number, because a payment rate you have to ask for is a payment rate that moves. See the whole rate card →
Wired, not welded
A connection you can unplug.
Every integration is a stated contract: what flows, which way, and what happens when you turn it off. No integration holds your data hostage.
The connection model
Connect. Normalize. Then automate.
Connect
Authorize the account and choose what moves. Admin access in both systems, granted once, visible always.
Normalize
External records land in their Thorbis homes: a customer is a customer, an invoice is an invoice, no bespoke shapes.
Automate
Only after the first records are verified by a person. The connection has an owner before it has automation.
A system of record
Every field has one home that wins. The books stay QuickBooks's; the jobs stay Thorbis's. Nothing is mastered in two places.
A sync owner
One named person reads the sync health and the exception queue. A connection nobody owns is an outage nobody notices.
An exception path
Records that do not match cleanly go to human review, never silently overwritten, never silently dropped.
Go-live
Staged, so the books stay clean.
01
Connect a test slice
A test account or a limited data set, never the whole company on day one.
02
Verify the mapping
Fields, permissions, and record categories checked against what you expect.
03
Run one real workflow
A single invoice, a single payment, followed to its destination and read.
04
Watch, then widen
Sync health reviewed after launch, the exception owner named, then the volume.
Asked before connecting
Straight answers.
Does Thorbis add fees on top of Stripe's?
No. You pay the processor's posted rates (the same table printed on our pricing page) and Thorbis takes nothing on the payment. Recording cash, checks, and external payments is free.
Who is the merchant of record?
You are. The money is between your company and your customer; Thorbis connects the collection to the job record and stays out of the flow of funds.
Can a $40,000 job go through this?
It should not have to. A $10 card charge stays easy, and a big progress bill can be collected by check or bank without being forced through card rates that would eat the margin.
Other integrations
Start
Money in before the truck leaves.
The invoice is the job's last step, and the payment is the invoice's: collected on site, landed on the record, deposited where you can see it.
Waitlist open. One email when your invite is ready, nothing else.
Coming from a suite? We’ll extract your records.
Rather talk first? Email the team.