Commtrac

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.

Deployable. Available to licensed institutions now.

A Commtrac POS terminal wired to a Commtrac API unit through a checkout session
Commtrac Clearingdeployed on your infrastructure

Reference

At a glance

ReleaseDeployable
DeploymentLocal node, your infrastructure
InterfaceCross platform SDK
EventsCommtrac API initiation feed
CreditWallets · Accounts · Virtual ledgers
FinalityCorporate account memo match
Risk engineInstitution defined policy
Back officeCRM · ERP · Accounting · Ledger
ComplianceOptional receipt archive
PerimeterCredentials stay on site
Commercial termsFraction of cleared value · No license

Commercial terms

Priced on cleared value. Nothing to deploy for, nothing to license.

A fraction of a percent of cleared value

Commtrac Clearing is metered as a small fraction of each payment it clears. Nothing is charged for a payment that never reaches the node.

No deployment fee, no monthly license

The node installs on the institution’s own infrastructure with no set up charge and no recurring license.

Instant deposit fees stay your product

Where an institution bills its own customers for instant deposits, the price and the decision to charge it belong to the institution. A share applies only when such a fee is billed.

Two bankers reviewing clearing terms together at a meeting table

How terms are set

Terms are set with the Commtrac team against an institution’s volumes, rails, and deployment.

Speak with the Commtrac team

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

14:02TRANSFER IN 000132998+2,000.25
15:41EFT CREDIT MISC+18,500.00
16:12INCOMING WIRE 8841002+68,400.00

Internal ledgerawaiting settlement

ORDER-9912Client 882132,000.25 CAD
INV-2041Client 5510218,500.00 CAD
MT5-70441Client 7193368,400.00 CAD

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.

Customer paymentCommtrac API event
Clearing nodeYour infrastructure
Corporate accountFinality match
Back officeCRM · ERP · Ledger

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.

ReferenceOrderRailAmountCredited (UTC)Finality (UTC)
CLR-70211ORDER-9912RTP2,000.25 CADCredited at initiation, inside policy14:02:1114:02:36
CLR-70212INV-2041EFT18,500.00 CADCredited at confirmed finality15:41:1915:41:19
CLR-70213MT5-70441SWIFT68,400.00 CADCredited at confirmed finality16:12:0316:12:03
CLR-70214ORDER-9954RTP350.00 CADCredited at initiation, inside policy14:06:1514:06:40
credited at initiation, inside policycredited at confirmed finality
A clearing terminal printing a continuous settlement record while a second unit reads it
The clearing recordone line from initiation to finality

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.

2.1

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.

2.2

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.

2.3

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.

2.4

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.

2.5

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.

2.6

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.

Connection the node holds
DisclosureLocal node
ConnectionCommtrac API event feed
DirectionInbound only
Crosses the perimeterPayment metadata for each initiation
Stays insideEvery decision the policy makes

Integration

What adoption looks like

01

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.

02

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.

03

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.

04

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.

05

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

01

The Commtrac API

Deployable

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.

03

Commtrac POS

Scheduled release · Q1 2028

Biometrically authenticated checkout settling account to account in person. Every terminal ships with Commtrac Clearing installed, at no charge for the clearing software.

04

Commtrac Messaging

Scheduled release · Q2 2027

The outbound counterpart. Where Clearing confirms value arriving, Messaging instructs settlement leaving, carrying instructions between institutions in Comtell.

Featured paper

From Commtrac Foundations

A clearing robot filing settlement records at a deskfinancial clearingPaper 02

Paper 02 · Published August 2026

The Certainty Gap

Why financial clearing is still guesswork, and how Commtrac ends it

Every institution that accepts bank payments runs a clearing function today, and almost none of them designed it. This paper names the improvised layer between a payment arriving and funds being usable, prices what it costs, and sets out a clearing node governed by policy the institution writes.

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
Commtrac

Global settlement infrastructure