Commtrac Software
UTC --:--:--
Global Settlement Infrastructure
Powering banking connectivity for commercial banks, fintechs, and merchants through next-generation financial technology.
Products
Four products. One settlement network.
The Commtrac API
Verify account ownership, link customer bank accounts, and initiate payments across RTP, SWIFT, and EFT rails through a single integration.
Deployable
Commtrac Clearing
A locally deployed clearing node that matches inbound settlement data, credits customer accounts in real time, and reconciles directly into existing back-office systems.
Deployable
Commtrac POS
Account-to-account checkout authenticated by biometrics. Funds settle over local rails directly to the merchant account with zero interchange.
Scheduled release · Q1 2028
Commtrac Messaging
Institutional settlement messaging built on Comtell, the language of the Commtrac Network. Real-time finality across borders, backed by the Dru liquidity network.
Scheduled release · Q2 2027
MyCommtrac
One portal for every Commtrac product. In the cloud, or installed.
MyCommtrac is the Commtrac cloud portal. A licensed institution reaches it in the browser, or through the Institution Terminal: a desktop application downloaded from the portal and installed on the workstation an operator administers Commtrac from. Both present the same workspace, and both reach Commtrac through the public edge and nothing else.
Every Commtrac product an institution licenses is managed from this one place: the API in Commtrac Cloud, and Clearing and Messaging nodes running on the institution’s own infrastructure.
Licensing
Access follows the licence. An institution becomes a licensed Commtrac member first; the portal then carries the products that licence includes, and the Comtell developer documentation issued to the organization.
Billing and metrics
Settled checkouts, the checkout and conversion ledgers, and the billing summary for every product the institution runs, read on demand.
Checkout sessions
Merchant API keys are generated, listed, and revoked here, beside the API reference and the catalog of banks the hosted checkout offers.
Settlement routing
Recipient details for every payment code and region, and the customer accounts linked to the institution.
Locally deployed servers
Institutions running Commtrac Clearing, Commtrac Messaging, or their own Commtrac API deployment orchestrate those servers from the same workspace: server management, linked corporate accounts, risk policy, account controls, and each product’s billing and metrics.
Operator authentication
Every operator signs in with a staff email and a two factor confirmation, under a session that expires on inactivity. Administration is an operator role, not a shared login.
The Institution Terminal
Built per industry, installed per operator
The Institution Terminal is built per industry code. An institution downloads the artifact matching the industry its licence records, and the workspace refuses to open against a licence for any other. It holds no address, path, or credential belonging to Commtrac’s core: it speaks to the public edge under the operator’s own session, and to nothing else. Institutions running their own deployment point the same application at their own servers.
One language. The whole network speaks it.
Comtell is the financial messaging language written by Commtrac and spoken by every part of the Commtrac Network. It is the language of Commtrac Messaging, and it is also what programs a checkout session, a clearing decision, and a settlement. Every Commtrac product is programmed directly by a set of Comtell message codes.
It is built for one thing: programmable banking. Any use case a bank, a fintech, or a merchant can name resolves to a Comtell instruction, from a hosted checkout to a clearing policy to an instant settlement funded from a pre funded pool.
What an instruction states
Who is moving value
An industry code and a product code classify the institution and the movement, so every downstream node knows the regulatory and audit context before it acts.
On which rail
A payment code names the rail: a domestic real time push, a wire across SWIFT, an EFT pull or push. Payments travel over those rails. The instruction travels in Comtell.
Which flow runs
A trac set states what a session is for: link every account a customer approves, send from a linked account with reconciliation, or send once and be done.
What became of it
Status codes and clearing codes record the outcome as a fact: initiated, refused, not completed, credited at initiation, confirmed at finality.
Against a message standard
ISO 20022 and the MT catalogue describe a payment. Comtell instructs one. A message standard is read after value has moved; a Comtell instruction is what moves it, and it carries the policy that decided to.
Against a general purpose language
A general purpose language executes whatever it is handed and leaves verification to whoever is watching. Comtell is deterministic: every instruction carries its own verifiable terms, so the receiving node acts on what the message states, with no third party to wait on and no hand in the loop.
Against a digital asset
Comtell requires no token, coin, or cryptocurrency of any kind, and never will. It settles fiat where it already sits, in the accounts institutions already hold, on proof, through Dru’s pre funded pools. There is no unreliable speculative digital asset to adopt, custody, or price.
About Commtrac
Banking software. Payment technology.
Commtrac Inc. · Alberta, Canada
Commtrac is a technology provider specializing in banking software and payment technology. It builds the settlement infrastructure that banks, fintechs, and merchants run: payment initiation, real time clearing, point of sale, and settlement messaging.
The money never runs through Commtrac. It moves bank to bank, on the rails the world already trusts. Commtrac is not a bank, a money services business, or a payment processor, and where liquidity is needed it belongs to Dru.