Commtrac Software
Product 02 of 04
Real time clearing and ledger infrastructure
Commtrac Clearing
A clearing node deployed on your own infrastructure. It credits customers the moment a qualifying payment is initiated, confirms finality on the corporate account, and keeps every connected system current.
Credited
0.00
Final
0.00
Open
0.00
Reference
At a glance
Pricing
Two rates. No deployment fee, no monthly license.
0.25%
of each cleared payment
40%
of instant deposit fees marked up to customers
Estimate
Work out a monthly bill
Set a monthly cleared volume and, if you bill customers for instant deposits, the fees you collect for it. Those fees are your revenue and your price to set; the share applies only when you charge one. The figures below are arithmetic on the published rates, not a quote.
The problem
A payment initiated is not a payment settled.
Every rail leaves a gap between the moment a customer pays and the moment funds are final. Institutions that wait out the gap make every customer wait with them. Institutions that credit early without a framework are extending credit on instinct, at scale, with no record of why.
Settlement itself arrives as a line on a corporate bank statement that says almost nothing about what it was for. The tools that promise to automate reconciliation stand outside the payment: they did not initiate it, cannot know the moment it left, and have no say in the memo it carries. The best they can produce is a probable match, and a probable match is not finality.
Corporate accountinbound credits
Internal ledgerawaiting settlement
The same three payments, recorded twice. Nothing on the statement identifies the order, the client or the ledger a credit belongs to, and nobody learns of finality until someone goes looking for it.
The solution
Cleared at initiation. Settled with proof.
Commtrac Clearing is a clearing node an institution deploys on its own infrastructure. It credits customers the moment a qualifying payment is initiated, confirms finality by matching each inbound credit on the corporate account, and writes the result into the systems the institution already runs.
The clearing register
One record from initiation to finality
Every payment the node touches becomes a single entry carrying its order reference, its rail, the moment it was credited and the moment finality was confirmed. The back office, the risk team and the auditor read from the same line.
| Reference | Order | Rail | Amount | Credited (UTC) | Finality (UTC) |
|---|---|---|---|---|---|
| CLR-70211 | ORDER-9912 | RTP | 2,000.25 CAD | Credited at initiation, inside policy14:02:11 | 14:02:36 |
| CLR-70212 | INV-2041 | EFT | 18,500.00 CAD | Credited at confirmed finality15:41:19 | 15:41:19 |
| CLR-70213 | MT5-70441 | SWIFT | 68,400.00 CAD | Credited at confirmed finality16:12:03 | 16:12:03 |
| CLR-70214 | ORDER-9954 | RTP | 350.00 CAD | Credited at initiation, inside policy14:06:15 | 14:06:40 |
The risk engine
Instant clearing is a policy decision
Each institution defines exactly which payments qualify for instant credit. The node enforces that policy on every event, and everything outside it simply clears when finality is confirmed.
Thresholds the institution sets
Settlement value, customer risk tier, account age and payment history are all inputs. The figures shown are a specimen. The policy is whatever the risk team writes.
Internal logic has a vote
Through the Commtrac SDK, internal fraud systems and business rules participate in every clearing decision before a single unit of value is credited.
Outside policy is not a failure
A payment that does not qualify is not declined. It credits automatically at confirmed finality, with the same record and the same reconciliation, and no operator queue in between.
Real time clearing events
The node is notified the instant the Commtrac API successfully initiates a customer payment. Wallets, accounts and virtual ledgers can be credited seconds after checkout, ahead of settlement on the underlying rail.
Finality confirmed by match
The node watches the corporate account and matches each inbound credit against the memo the Commtrac API wrote and locked at initiation. The reference arrives bank to bank exactly as the merchant set it, so finality is a recorded fact rather than an operator judgement.
Deployed inside the perimeter
Commtrac Clearing runs on the institution’s own infrastructure. Corporate account access is configured locally, and credentials never reach Commtrac’s cloud or anyone else’s.
A risk engine the institution writes
Transaction value, customer risk profile, historical payment behaviour, account age and internal fraud rules decide which payments clear instantly. Custom business logic joins the decision through the SDK.
A back office that stays current
Once finality is confirmed, connected CRM, ERP, accounting and internal ledger systems are updated automatically through the cross platform SDK. Reconciliation stops being a queue.
A compliance archive, when required
An optional module collects customer payment confirmations and official bank receipts as they occur, and archives them for audits, dispute resolution and regulatory review.
Deployment
Your infrastructure. Your credentials never leave it.
The node holds exactly three connections. One receives initiation events from the Commtrac API. One reads the corporate account to confirm finality. One writes into the back office over the SDK. Pick a connection and read what crosses the boundary, and what never does.
Integration
What adoption looks like
Deploy the node
Commtrac Clearing installs on infrastructure the institution controls. From the first event it processes, everything it decides and records happens inside your perimeter.
Connect the corporate account
Account access is configured locally on the node. Credentials never reach Commtrac or anyone else, and finality matching runs against statements only the institution can see.
Write the clearing policy
Transaction value, customer risk tiers, account age, payment history and internal fraud rules define what clears instantly. Custom business logic joins the decision through the SDK.
Wire in the back office
The cross platform SDK connects CRM, ERP, accounting and internal ledger systems, so confirmed finality posts to every one of them without an operator in between.
Switch on the archive, if required
The optional compliance module collects customer payment confirmations and official bank receipts as they occur, filed for audits, dispute resolution and regulatory review.
The network
Where Clearing sits
The Commtrac API
Opens the sessions and initiates the payments this node clears. The reference it writes and locks at initiation is the same reference the node matches on to confirm finality.
Commtrac POS
Palm authenticated checkout settling account to account in person. Every terminal ships with Commtrac Clearing installed, at no charge for the clearing software.
Commtrac Messaging
The outbound counterpart. Where Clearing confirms value arriving, Messaging instructs settlement leaving, carrying instructions between institutions in Comtell.
Next step
Put Commtrac to work against your own volumes.
Tell us the rails you run and the institutions your customers bank with. We will walk through what it looks like on your existing stack, and what it costs at your volumes.
Contact sales
Global settlement infrastructure