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.
RTP · SWIFT · EFTCommtrac 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.
Local node · SDKCommtrac POS
Account-to-account checkout authenticated by palm. Funds settle over local rails directly to the merchant account with zero interchange.
A2A · Palm authCommtrac Messaging
Institutional settlement messaging built on Comtell, the language of the Commtrac Network. Real-time finality across borders, backed by the Dru liquidity network.
Comtell · Dru network01The Commtrac API
RTP · SWIFT · EFTThe problem
Connectivity ends where payment begins.
Reading a customer bank account is close to solved. Moving money out of one is not. A customer paying at checkout is sent away to copy account numbers into their banking app, and the merchant waits to find out whether the transfer was ever made. Coverage stops at read access, and every institution is its own integration.
The cost lands as abandoned checkouts, mistyped details, and payments that carry no reference the merchant controls, so the money and the order it belongs to arrive as two unrelated events waiting to be matched by hand.
| Capability | Bank by bank integration | Read only aggregation | Details collected by hand | The Commtrac API |
|---|---|---|---|---|
| Ownership verification | Limited or per institution | Available | Not available | Available |
| Multi account linking | Limited or per institution | Available | Not available | Available |
| Customer authorized payment | Limited or per institution | Not available | Limited or per institution | Available |
| Verified destination details | Limited or per institution | Limited or per institution | Not available | Available |
| Merchant controlled data | Limited or per institution | Not available | Not available | Available |
| Native conversion | Not available | Not available | Not available | Available |
The solution
One integration. Every institution your customers bank with.
The Commtrac API resolves ownership, links the accounts a customer approves, and initiates the payment from that account to the merchant on whichever rail the customer bank runs. Account numbers never reach the merchant, and the customer never types one.
Demo Markets
$94.99 CAD
Demo Merchant Product
Select your bank
Can't find your bank? Search for it here
Securely powered by Commtrac
The Commtrac Checkout Session
The Customer Experience
One call opens a hosted session. The customer selects the institution they bank with, approves the payment there, and returns. The merchant builds none of it and stores none of it.
Nothing for the customer to install
The checkout is a URL, generated fresh on every API call. The customer follows the link and pays in their own bank. No Commtrac product has an app.
Merchant and order carried through
The merchant name, the product and the exact amount travel with the session request, so the customer confirms the order they actually placed.
Institution chosen by the customer
Supported banks are listed and searchable. There is no per bank redirect for the merchant to build, and no coverage gap to explain at checkout.
Approved inside their own bank
Authentication happens in the customer banking session. Nothing sensitive is entered on the merchant site, and no account number is ever typed.
Ownership verification
Confirm the legal name and registered address behind an account before value moves, on the same call that opens the session. Built for KYC and AML review.
Account linking
A customer authenticates once. Every account they approve stays available to the merchant, so future payments are a single confirmation rather than a new form.
Customer authorized payment
The merchant requests the payment and the customer approves it inside their own banking session. Commtrac initiates it on whichever rail fits, whether that is a domestic RTP push, a wire across SWIFT, or an EFT pull.
Verified destination details
Where a merchant pays its own customers, the API returns the verified account behind that customer rather than moving the funds itself. The SDK ties those details into whatever payout logic the merchant already runs.
Rich data the customer cannot touch
The merchant injects its own structured data into the bank payment itself: invoice numbers, order references, ledger keys, anything the back office needs to match on. Commtrac writes it and locks it, so the customer cannot edit, clear or overwrite what was set. The reference travels bank to bank inside the payment, and what arrives at the receiving account is exactly what the merchant wrote.
Native conversion
Cross currency payments convert against live interbank pricing at the trading rates of tier one liquidity providers, inside the same session.
02Commtrac Clearing
Local node · SDKThe 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.
03Commtrac POS
A2A · Palm authThe problem
Every sale pays the middlemen first.
A card sale pays a queue of intermediaries before it pays the merchant. Interchange, network assessments and processor margin are taken as a percentage of every ticket, and for a business running single digit margins those points are not a cost line. They are a silent partner.
Then the merchant waits for its own money. Card settlement batches on the processor's schedule, lands days later, and sits in an account the processor controls, exposed to holds, rolling reserves and disputes long after the customer went home happy.
Card railsettlement of a 100.00 bill
Commtrac POSthe same bill
The same bill, settled twice. For a merchant running three points of margin, the 2.80 the middlemen no longer take is not a discount on costs. Applied to every ticket, it is close to double the annual profit.
The solution
Account to account. Nothing in between.
Commtrac POS is a palm authenticated terminal that moves a sale from the customer's bank account to the merchant's over the domestic real time rail. No card network, no acquirer, no processor custody. The customer scans, the payment initiates, and because the rail is irreversible the merchant can treat the sale as cleared the moment it moves.
Awaiting palm. No card. No device.
The terminal
A payment in the time it takes to wave
The customer rests a palm over the terminal. Commtrac resolves who they are and which account they approved, initiates the transfer on the local rail, and clears it into the merchant account.
Enrolled once, recognized everywhere
A customer who links their palm at any Commtrac POS can pay at every Commtrac POS, with every bank account they choose to connect. There is nothing to carry and nothing to re enroll.
Presence is the credential
The payment is authorized by the customer standing at the terminal. There is no card number to skim, store, or test online, and no card network in the transaction at all.
The back office already knows
Every terminal ships with Commtrac Clearing at no charge, so the sale reaches order management, CRM and accounting systems the moment it initiates.
Worked example
Dinner in Toronto, 43.20 CAD
A customer finishes dinner and owes 43.20. They rest a palm on the terminal. An Interac e-Transfer leaves the account they linked and arrives in the restaurant’s own bank account in under ten seconds. No card is presented, no processor sits in the middle, and the restaurant keeps 43.10 of the 43.20.
What happens
The customer rests a palm on the terminal at the table.
Commtrac recognizes them and the bank account they already approved.
An Interac e-Transfer leaves that account for the restaurant.
The restaurant’s own bank account is credited.
What never happens
No card is presented, tapped, or kept on file.
No card network, acquirer or processor takes a share of the bill.
The customer never types an email address, an account number or a memo.
Nothing is installed. There is no app on either side of the counter.
Deviceless, cardless checkout
The customer presents a palm, approves, and leaves. No card, no phone, no wallet, and nothing between their bank account and the merchant account except the domestic rail.
Link once, pay anywhere
A palm enrolled at one terminal works at every merchant running Commtrac POS, and a customer can hold multiple linked bank accounts behind the same signature.
Local rails, straight to the account
Sales settle over the domestic real time rail directly into the account the merchant already banks with. There is no processor balance, no batch schedule, and no one holding the funds in between.
A fixed fee, not a percentage
Settlement costs a flat dime whatever the ticket. A dime on a 40.00 lunch and a dime on a 4,000.00 banquet, with no interchange and no volume tier negotiated over the merchant.
No chargeback surface
Real time rail payments are final when they move. With no card network in the transaction there is no chargeback mechanism to abuse, and with no card number there is nothing to steal.
Commtrac Clearing included
Each terminal comes with a Commtrac Clearing deployment free of charge, so instant confirmation, reconciliation and back office sync arrive with the hardware.
04Commtrac Messaging
Comtell · Dru networkThe problem
The message moves in seconds. The money takes days.
The message has never been the slow part. A cross border payout clears the treasury in seconds and then goes dark, crawling through correspondents that each add a day and lift a fee, while the institution that sent it can only raise inquiries about its own money.
What speed exists is bought with trapped capital. Institutions pre fund accounts across every corridor to imitate immediacy, the FX rate is discovered when the payment lands rather than when it leaves, and one mistyped routing detail is enough to strand the transfer entirely.
Corporate payout · Toronto to Tokyoas it runs today
The message arrived in seconds. The value arrived on day three, lighter than it left, at a rate nobody chose.
The solution
Value at message speed. Funded by Dru. Settled on proof.
Commtrac Messaging is a locally deployed node speaking Comtell, the settlement language of the Commtrac Network. Instead of pushing value through a chain of correspondents, the node messages Dru, the Digital Reserve Unit, a Commtrac affiliated network of pre funded liquidity pools. A pool on the beneficiary side pays out in real time, Dru purchases the confirmed receivable, and the institutions settle behind it on cryptographic proof rather than trust.
Your institution
comtell node
Dru pool
JP-TOK-02
Beneficiary bank
local rail
The message sequence
A settlement in three messages
One message releases the payout, one advances it from the local pool, and one settles it on proof. The corridor, the locked rate and the funding pool travel inside them, so nothing about the payment is left to be discovered later.
The rate travels with the message
Cross currency payouts convert at live interbank pricing the moment the message is released. What the beneficiary receives is a term of the payout, known before it leaves.
Proof instead of trust
Commtrac built ZKP circuits and a tokenless DLT let multiple institutions and Dru settle with each other in no trust environments, with no token to adopt and no rulebook to rewrite.
The risk belongs to Dru
Dru purchases the confirmed receivable and carries the settlement risk while it completes. Institutions stop pre funding corridors and free the capital parked in them.
Person to person
A cross border wire, addressed to an email
The same network carries person to person transfers over SWIFT with nothing required from the sender but the recipient's email address.
01
Addressed, not routed
The sender enters an email address and an amount. There is no SWIFT code to look up, no branch address, and no detail to mistype.
02
The recipient chooses
An incoming deposit notice lands in their inbox carrying their unique Commtrac Checkout link. They open it and select the bank the wire should land in. Nothing to type, nothing to know.
03
Deposited in real time
The moment they sign in and select the account, a Dru pool local to them disburses the deposit, while the wire settles behind it across the network.
True real time payouts
A payout instruction becomes money in the beneficiary account in seconds, whatever the corridor. The node notifies Dru, a local pool advances the funds, and the underlying settlement follows behind.
The Dru liquidity network
Dru, the Digital Reserve Unit, is a Commtrac affiliated factoring entity operating pre funded pools across the network. It purchases confirmed receivables before they settle and holds the risk while they do.
Conversion at initiation
Cross currency payouts convert against live interbank pricing when the message is released. The rate is part of the payout, not a discovery made days later at settlement.
Settlement on proof
Comtell carries Commtrac built ZKP circuits and a tokenless DLT, so institutions settle with each other and with Dru on cryptographic proof, in environments where nobody has to be trusted.
Wired into your ledgers
The SDK ties the node into internal business logic and risk parameters, from virtual trading ledgers to client wallets, with configurable settlement risk. It also bridges VISA, Mastercard and other card networks to those internal balances: a client spends a debit card straight from a trading account or wallet, and Dru settles the card leg in real time over the network.
Leaner correspondent banking
The same proof based settlement thins the capital banks keep parked in vostro and nostro relationships. Balances reconcile against verified messages instead of idle pre funding.