Pipeline
Two boards, not one
Signing merchants and recruiting agents are different jobs with different stages. They get separate pipelines instead of one board with a type field bolted on.
For payment processors, ISOs and agent offices
The CRM built for payments, not bent into it.
Work a merchant from first call to signed, then keep running the account — residuals, partner payouts, support tickets and 1099s — without exporting it into something else.
Why another CRM
General-purpose CRMs stop at the signature
They will track a deal. Then the merchant boards, and everything that actually pays your business — residual splits, agent overrides, payout runs, chargeback tickets, year-end 1099s — moves into spreadsheets and a portal nobody likes. That gap is the whole product.
Residuals
Residuals that reconcile
Splits, overrides and partner payouts computed in exact minor units. What is owed and what has been drawn are derived from the ledger, never from a stored balance that can drift.
Portfolio
Merchants after the sale
Approved merchants keep their history, custom fields, documents and health score in the same record the deal was worked in. No re-keying into a second system.
Contact
Every channel in the timeline
Email, SMS, live chat and calls land on the record they belong to, so the next person to pick it up can see what was already said.
Support
Tickets with routing
Merchant issues become tickets with queues, assignment and SLA timers, sitting beside the account they concern rather than in a separate helpdesk.
Compliance
1099 on a cash basis
Box 1 totals built from what was actually paid inside the calendar year, with the payees that are missing a TIN flagged before you file.
If you are already on something
Most people reading this are running IRIS
Which is now NMI Merchant Central — same software, new name. It is a serious product, and the honest comparison is row by row rather than a slogan. Ours is sourced to their own published pages, includes the rows we lose, and marks anything we could not confirm as unconfirmed rather than scoring it.
Where we win
Money arithmetic that reconciles, screening that cannot report a result it did not produce, and isolation enforced where code cannot forget it.
Where they win
Proven processor boarding, automated risk decisioning, and a mobile app. All three are in the table, in their column.
One product, not modules
Lead to quote to signature to boarding to payout to 1099 is one path on data the system already holds — not a set of tiers you assemble.
Multi-tenant
One deployment, many offices
Each organisation sees only its own records. Isolation is enforced in the data layer rather than remembered in each query, so a new feature is tenant-safe by default instead of by review.
Role-aware from the row up
An admin sees the office. A sales rep sees their own merchants and leads. The narrowing happens on the data, not by hiding buttons.
Two-factor built in
TOTP with backup codes, and an enforced-setup path for offices that require it across the board.
Yours to brand
Palette and identity are applied at runtime, so a reseller portal does not need a separate build or a separate deployment.
Money
Arithmetic that holds up under audit
Residuals decide what people are paid, so the maths is the product. Amounts are held as exact minor units — never floating point — with the currency's own exponent applied.
Nobody gets paid twice
What a partner can draw is computed as allocations less payouts still in flight. A failed or returned payout releases its hold; a pending one does not. There is no stored balance to fall out of step with the ledger.
Cross-currency, deliberately
Rates are directional and dated: no rate is quietly inverted to fill a gap, and a missing rate stops the run rather than defaulting to one-to-one. Conversions are computed exactly and rounded once.
See it against your own portfolio
The quickest way to judge it is with your merchants, your stages and your residual splits in front of you. Tell us roughly what you run and we will set up a walkthrough.