Built for merchant-services ISOs
Your residuals, reconciled and closed — without the spreadsheet.
Upload the residual files your processors already send. Get back a clean book, partner commissions you can defend line by line, and a month that closes in an afternoon.
Most ISOs run their entire book out of one workbook that one person understands, rebuilt by hand every month, and reconciled by eye.
It works right up until a MID moves, a file arrives late, or that person is on vacation when a partner asks why their check is short.
Six states, and the month is closed.
Not a workflow you configure — the sequence the product runs on. At any moment you can say exactly which one a period is in, and who it is waiting on.
- 1
Upload
Files in, any shape — checked against the source, exceptions cleared by a human
- 2
Calculate
Every partner's payout, line by line
- 3
Statements
Spreadsheet and PDF, with the working
- 4
Publish
Partners see their figures when you say so
- 5
Pay
Recorded against the run
- 6
Lock
The period stops moving
Drop in the files you already get
Residual files land as they come — messy headers, several tabs, MIDs stored as text. They are parsed, normalized, and loaded without anyone touching a spreadsheet.
Reconciled against the bank file
Computed totals are checked against the processor's own summary rows, and differences are graded until a human accepts or explains them. Most tools ask you to trust the number. This one proves it.
Splits that match how you actually pay
Per-account or whole-book, step-downs, revenue share, dual-partner MIDs, house accounts. Every payout traces back to the rule and the source row that produced it.
Close the month, then send it
Lock a period and the numbers freeze. Statements go out, payments get recorded against what was computed, and the gap between the two is impossible to lose track of.
Tenancy
Your book never shares a database with another ISO's.
Every customer gets their own physically separate database. Not a tenant column, not a row-level policy — a different database. There is no query that could return another firm's merchants, because their data is not in there.
Your merchants, partners, statements and files.
Not a row your session could reach.
Not a row your session could reach.
- Your book lives in its own database
- Not a tenant column in a shared table. Isolation holds even if a query forgets to filter, because there is nothing else in there to leak.
- An agent sees their own accounts, and nothing else
- Scoped on the server on every request, never by hiding buttons. We test it adversarially — by asking for another agent's numbers and checking we get refused.
- Multi-factor is required, not encouraged
- Owners cannot use the product without it, and neither can anyone recording a payment. Twelve-character minimum, sessions rotated daily.
- Every action leaves a record
- Uploads, exports, permission changes, statement downloads. Readable by you in the app, not something you have to request from us.
- We can't look at your data quietly
- Support access is read-only, expires on its own, and appears in your activity log the moment it starts.
Pricing
Priced by the size of your book, not the size of your team.
One flat monthly fee per organization. Unlimited staff, unlimited partners — your agents log in free. Every plan includes everything; the tiers only differ in how many active merchant accounts they cover, counted across all of your entities.
Every workspace starts with a 14-day trial of the full product, free. Outgrow a tier and nothing stops — we'll talk about moving you up. A merged group of MIDs counts as one account; dormant accounts don't count at all.