One engine. Three products.
Per-transaction cost, per-merchant economics and reconciliation all run on the same priced transactions: each card transaction calculated at its true IC++ cost, in real time. That is why the three never disagree with each other.
txn_103838897746976156_6003583
Interchange
IRD EW · 1.150000%
Scheme fees
2 applied
- PreAuth HN2EA1126€0.000200
- Acquirer authorization2EA1166Q€0.009300
True cost
at authorization
Where it starts
The engine that prices the transaction
Real-time cost engine
Interchange and every scheme fee calculated in under 50 ms, at authorization, capture, refund and chargeback.
What you do with it
Merchant economics, reconciliation and monitoring.
Each one runs off the same cost number rather than three approximations of it.
Pricing management
Per-merchant pricing rules on top of true IC++ cost
Set how each merchant is priced by region, card type, amount and currency, and see the margin on every transaction.
Explore pricing managementMerchant analytics
See which merchants actually make you money
Scheme cost in basis points by merchant, MCC, card product and region, so under-priced merchants stand out.
Explore merchant analyticsInvoice reconciliation
Every Visa and Mastercard billing line, matched and explained
Visa and Mastercard invoices matched line by line against calculated fees, with every difference traced to its rule.
Explore invoice reconciliationInterchange reconciliation
IP755120 and Visa clearing reports, matched to the transaction
The schemes' own clearing reports reconciled against your transactions, with a daily deviation in basis points.
Explore interchange reconciliationRule change monitoring
Scheme fee changes, priced against your book in advance
Visa and Mastercard releases and bulletins mapped in with effective dates, so you see what each change costs before it is billed.
Explore rule change monitoringThe same engine works from the issuing side. Interchange revenue assurance for issuers
Integration
However you want to plug it in.
Embedded once in a gateway so every acquirer on it inherits real-time IC++ costing, or called directly as API-as-a-service with the payload you already have.
Card transaction
An authorization, capture, refund or chargeback arrives.
Gateway or switch
Sends the payload it already has. The transaction path is unchanged.
Recivr fee engine
Resolves interchange and every applicable scheme fee, and responds in under 50 ms.
Analytics, reconciliation, monitoring
The same priced events feed the surfaces you review later.
A gateway or processor integrates Recivr once. Every acquirer on that platform inherits real-time IC++ costing without writing a line of code.
Either way, Recivr never needs a PAN — it prices from the transaction attributes that determine cost.
Find the margin in your own book
Send us a day of traffic and a clearing file. We'll return the true IC++ cost of every transaction in it, and show you where the margin is being lost.