Payments - Introduction / Learning brief
Canada's Lynx RTGS
Your notes
In simple terms / 01
What this means in plain language
Lynx is Canada's high-value real-time gross settlement system, operated by Payments Canada and settling in Bank of Canada money, with mechanisms that balance immediate finality against efficient use of liquidity.
Lynx is the system that moves large, time-critical payments between Canadian banks. It is a real-time gross settlement (RTGS) system, which means each payment is settled on its own, in full, the instant it is processed, rather than being bundled and netted later. It is operated by Payments Canada, and settlement happens in Bank of Canada money, the safest form of settlement asset in the country. Lynx replaced the earlier Large Value Transfer System (LVTS) and uses the ISO 20022 messaging standard. To keep this immediacy affordable, Lynx offers two ways to settle so that banks do not have to hold more cash than necessary.
Complete lesson / 02
Understand the full idea, step by step
Some payments are simply too large to wait in a pile. A company completing an acquisition, a bank squaring its position with another bank — for these, "settled by tonight" is not good enough. Canada's answer is Lynx, and it shows a tension every high-value system must resolve: the receiver wants finality now, but paying everything instantly ties up a great deal of cash.
Lynx at a glance
- What it is
- Canada's high-value real-time gross settlement (RTGS) system
- Operator
- Payments Canada
- Settlement asset
- Bank of Canada money — balances at the central bank
- Messaging
- ISO 20022
- Predecessor
- The Large Value Transfer System (LVTS)
- Distinctive feature
- An urgent gross mode beside a liquidity-saving mechanism
Real-time gross settlement (RTGS) — each accepted payment settles individually, in full, as it is processed
In an RTGS system there is no waiting for an end-of-day cycle and no netting before settlement: every accepted payment moves the full amount across accounts at the settlement institution the moment it settles. The receiver gets per-payment finality — once settled, the money is theirs and the payment cannot be unwound. Note what RTGS does *not* mean: the system still validates, sequences, and may queue instructions. RTGS describes how settlement happens, not an absence of processing.
If settling instantly is so good, why not settle every payment that way?
Because gross settlement is hungry for cash. If Bank Alfa must pay out CAD 2,450,000.00 in full before any incoming payments arrive, it needs that much sitting ready at the central bank. Multiply that across every payment of the day and banks would have to park enormous balances doing nothing. The cost of that idle liquidity is real — so modern RTGS systems look for safe ways to reduce it.
Two doors into settlement
Lynx resolves the tension by offering two settlement mechanisms. The urgent mechanism settles a payment gross and immediately, provided the sending participant has the funds — built for deadlines like Asha Traders' 11:00 release. The Liquidity Savings Mechanism (LSM) takes ordinary payments into a central queue and continuously searches for offsetting flows: if Bank Alfa owes Nordbank and Nordbank owes Bank Alfa, the mechanism settles the group together so that only the difference draws on balances. Each settled payment is still final and individual — the saving is in *when* payments are released against each other, not in weakening finality.
| Urgent (gross now) | LSM (queue and offset) | |
|---|---|---|
| Best for | Time-critical, deadline-bound payments | The everyday bulk of high-value traffic |
| Path to settlement | Settles at once if funds are available | Waits briefly in a queue for offsetting flows |
| Liquidity used | Full amount from the sender's balance | Roughly the net of offsetting payments |
| Finality once settled | Immediate and irrevocable | Immediate and irrevocable — identical |
The equipment payment, step by step
- CUSTOMER
Asha Traders instructs Bank Alfa: pay CAD 2,450,000.00 to the manufacturer's account at Nordbank, today, before 11:00.
- VALIDATION
Bank Alfa validates and screens the instruction, then debits Asha Traders' account on its own books. The interbank leg still lies ahead.
- MESSAGE
Bank Alfa submits an ISO 20022 payment message to Lynx, flagged for the urgent mechanism because of the deadline.
- VALIDATION
Lynx checks that Bank Alfa's settlement funds cover the full amount. A payment that is not covered does not settle — it waits or is returned, but it never settles short.
- SETTLEMENT
Lynx settles the payment gross: Bank Alfa's balance in Bank of Canada money falls by CAD 2,450,000.00 and Nordbank's rises by the same amount. This moment is final.
- NOTIFICATION
Nordbank receives the settled payment's details and credits the manufacturer's account.
- NOTIFICATION
The manufacturer sees final funds and releases the equipment. No later event can claw the payment back.
WHAT IF — Bank Alfa's available balance does not cover an urgent payment
What happens: The payment does not settle. It waits until funds arrive — from incoming payments or a top-up — or is dealt with under the system's rules if it cannot be funded in time.
How it is handled: This is the risk-control design working, not a malfunction: because settlement is final and irrevocable, Lynx must never let a participant settle money it does not have. Bank Alfa's treasury monitors its position through the day and moves liquidity in before large outflows; Maya's operations team watches for payments sitting unsettled longer than expected.
STRICTLY SPEAKING
Strictly speaking, the names, parameters, and internal rules of Lynx's mechanisms — how the queue searches for offsets, what limits and controls apply, and the system's operating schedule — are set by Payments Canada's rules and have evolved since Lynx replaced the LVTS. Treat this lesson as the stable shape of the system: gross urgent settlement beside a liquidity-saving queue, with settlement in central-bank money. For operational specifics, consult the operator's current documentation.
FOR NOW, REMEMBER
- Lynx is Canada's high-value RTGS: each settled payment is individual, full-value, and final, in Bank of Canada money.
- Pure gross settlement is safe but cash-hungry — that is the core trade-off of every RTGS design.
- Lynx offers an urgent gross mechanism for deadlines and a Liquidity Savings Mechanism that queues and offsets ordinary payments.
- A payment that is not fully funded never settles — finality this strong demands funds up front.
TRY IT YOURSELF
Bank Alfa has two Lynx payments to send this morning: a CAD 8,000,000.00 interbank obligation due at a contractual deadline in twenty minutes, and a CAD 3,000,000.00 supplier payment that must simply settle sometime today. Liquidity is tight. What is the sensible routing?
Lynx settles one currency for one country. Hong Kong runs the same RTGS idea four times over — in four currencies, side by side — and uses an Asian time zone to settle dollars and euros while New York and Frankfurt are still asleep.
KEEP GOINGKey takeaways / 03
Three things to remember
- 01
Lynx is Canada's high-value RTGS, operated by Payments Canada and settling in Bank of Canada money with per-payment finality.
- 02
It replaced the Large Value Transfer System (LVTS) and carries payments in the ISO 20022 message standard.
- 03
It offers two settlement mechanisms, an Urgent Payment Mechanism (UPM) and a Liquidity Savings Mechanism (LSM), supported by a Risk Control Mechanism (RCM).
Practical use cases / 04
Where you would use this
A bank settling the cash leg of a large securities trade where finality must be certain and immediate.
A time-critical corporate payment, such as a property completion, that must reach the beneficiary bank the same day.
A bank grouping several queued payments so the Liquidity Savings Mechanism can offset them and save cash.
Worked example / 05
Put the idea into a real situation
Illustrative example: Bank Maple must send 50,000,000 Canadian dollars to Bank Cedar and marks it urgent. Under the Urgent Payment Mechanism the payment settles gross and immediately because Bank Maple has the funds, giving Bank Cedar final money at once. Later, Bank Maple has three ordinary payments queued that partly cancel against incoming payments from Bank Cedar; the Liquidity Savings Mechanism offsets them together so only the small net difference draws on Bank Maple's balance, all within the Risk Control Mechanism's limits.
Operational sequence / 06
Follow the message and decision path
This compact sequence is a learning model. Exact routing and rulebook behavior can vary by scheme, participant, and implementation.
Read the steps as text
- 01MessageBank Alfa submits the Lynx wire paymentBank Alfa (sending bank) → Lynx (Payments Canada) · FI to FI customer credit transfer (pacs.008)
The sending bank submits a high-value wire to Lynx as an ISO 20022 message, so rich remittance data travels with the payment. Nothing has settled yet — this is the instruction.
- 02Clearing obligationLynx checks the settlement balanceLynx (Payments Canada) → Bank of Canada (settlement)
Lynx clears the individual payment by checking that Bank Alfa holds enough settlement balance at the Bank of Canada to cover it. An RTGS system will not create money it does not have.
In an RTGS, each payment clears on its own — there is no netting cycle to wait for before settlement.
- 03SettlementThe Bank of Canada settles the paymentBank of Canada (settlement) → Nordbank (receiving bank)
Immediately after the payment clears, the Bank of Canada moves central-bank money from Bank Alfa to Nordbank, one payment at a time. Settlement is real-time and final — the wire is irrevocable.
- DR Bank Alfa's settlement account at the Bank of Canada — CAD 900,000.00
- CR Nordbank's settlement account at the Bank of Canada — CAD 900,000.00
- 04MessageNordbank is told the payment is finalLynx (Payments Canada) → Nordbank (receiving bank)
Lynx confirms to the receiving bank that the payment has settled with finality in central-bank money, with the ISO 20022 details of the payment it now holds.
- 05PostingNordbank books the fundsNordbank (receiving bank)
Because the interbank leg already settled with finality, Nordbank can credit its customer's account without waiting for anything else to clear.
- CR Beneficiary's account at Nordbank — CAD 900,000.00
Read the steps as text
- 01MessageRiya sends an e-Transfer to Arjun's email aliasRiya (sender) → Bank Alfa (sender bank)
Riya types Arjun's email address in Bank Alfa's online banking and enters CAD 200.00. She never asks for his account number — the alias is enough to address the payment.
- 02MessageInterac tells Arjun money is waitingInterac e-Transfer (network) → Arjun (recipient)
Interac e-Transfer sends a notification to Arjun at the alias Riya used. This message announces the payment and points to it; it does not itself carry any funds.
- 03PostingArjun's account is credited near-instantlyNordbank (recipient bank)
Arjun accepts (or auto-deposit applies) and Nordbank books the credit, making CAD 200.00 available to him within moments — this is the fast experience the customer feels.
- CR Arjun's account at Nordbank — CAD 200.00
- 04PostingBank Alfa debits Riya and holds the amountBank Alfa (sender bank)
Bank Alfa debits Riya's account (or holds the amount it earmarked at send) so that the CAD 200.00 is committed on its own books, pending settlement with Nordbank.
- DR Riya's account at Bank Alfa — CAD 200.00
- 05SettlementThe two banks settle between themselves — separately and laterBank Alfa (sender bank) → Interbank settlement (Payments Canada)
Separately from the near-instant availability Arjun saw, Bank Alfa and Nordbank settle their interbank position through Payments Canada. This deferred settlement leg is distinct from — and later than — the customer's instant experience, and it is not the real-time gross settlement used by Lynx.
Interac e-Transfer is a separate system from Lynx, Canada's high-value RTGS. The alias messaging and instant availability sit apart from this deferred interbank settlement.
- DR Bank Alfa settlement position — CAD 200.00
- CR Nordbank settlement position — CAD 200.00
Evidence & review / 07
Evidence & review
Lynx (Payments Canada), Canadian-dollar high-value payments; general RTGS/LSM concepts apply to other jurisdictions
What this brief simplifies: The urgent/LSM contrast is taught as two clean doors; the operator's actual mechanism names, queue algorithms, risk-control parameters, and schedule are not quoted and change over time. The fictional scenario uses cast banks as Lynx participants.
Sources for this brief3
- Market practiceMarch 2003 edition
A glossary of terms used in payments and settlement systems ↗ — CPSS (now CPMI), Bank for International Settlements · RTGS, liquidity saving mechanism, finality
Terminology has evolved since this edition; newer CPMI publications refine some definitions.
- Official requirement
Principles for financial market infrastructures ↗ — CPMI and IOSCO (Bank for International Settlements) · Settlement finality and liquidity risk principles for FMIs
Published by the CPSS (now CPMI) and IOSCO; contains 24 principles plus responsibilities for authorities. This site uses it only for high-level concepts such as settlement finality.
- Simplified educational illustration
Payments Signal editorial teaching models — Payments Signal
Used wherever diagrams, scenarios, figures, or example values are didactic constructions rather than sourced facts; every such use carries a simplifications disclosure. All people, companies, banks, and list entries in examples are fictional.