Articles / Learning brief
High-value payments and HVPS+
Your notes
In simple terms / 01
What this means in plain language
High-value payment systems are usually central-bank real-time gross settlement systems that settle large payments individually and with finality. The HVPS+ (High Value Payments Plus) guidelines align how ISO 20022 messages are used across them, so a payment reads the same across borders.
A high-value payment system moves large, time-critical payments between banks, and most are run by a central bank as an RTGS (real-time gross settlement) system. Real-time gross settlement means each payment is settled on its own, one by one, the moment it is processed, and once settled it is final and cannot be reversed. Because these systems sit at the centre of a currency, they handle the largest and most urgent transfers. As they adopt ISO 20022 (International Organization for Standardization standard 20022), a risk appears: each system could fill in the new messages slightly differently. HVPS+ (High Value Payments Plus) is a set of market-practice guidelines that answers this by describing exactly how ISO 20022 messages should be populated in high-value systems. When every real-time gross settlement system follows the same guidelines, a payment carries the same fields in the same places whichever system it passes through, which keeps data intact and processing automatic as a payment crosses borders.
Complete lesson / 02
Understand the full idea, step by step
Most of the payments in this course are small enough to wait a beat — a batch tonight, a credit in the morning. But some are not. When a bank settles a market trade or moves a very large sum, waiting is the risk. For those, an economy runs a different kind of system, built for certainty rather than cost.
RTGS — real-time gross settlement
A high-value payment system is usually a central bank's RTGS system. Gross means each payment settles on its own, in full, rather than being bundled and offset against others. Real-time means settlement happens as the payment is processed, not at day's end. Funds move in central-bank money, and once settled the transfer is final and irrevocable — which is the whole reason these systems exist.
| Account | Dr | Cr |
|---|---|---|
| Bank Alfa's settlement account | USD 2,500,000.00 | |
| Nordbank's settlement account | USD 2,500,000.00 |
Illustrative two-entry view of one gross settlement. A real system also manages each bank's intraday liquidity, queues, and reservations; the account structure is simplified here.
If each payment settles on its own in full, where does the money come from at the exact moment it settles?
That is the trade-off of gross settlement. Because payments are not netted, each one needs enough funds available in the paying bank's settlement account the moment it settles. So banks manage their liquidity through the day — watching what is coming in against what must go out, and sometimes queuing a payment until cover arrives. Netting many payments and settling only the balance uses less liquidity, which is why it suits lower-value traffic; but for large, urgent value, gross settlement with finality is worth the liquidity it demands.
One standard, many systems, the same divergence risk
As high-value systems replace older message formats with ISO 20022, each faces the same choice about how to fill in the new messages — and left alone, each could choose differently. That is the same divergence problem CBPR+ solves for cross-border payments, now appearing inside each domestic system. The answer is the same kind of tool: a shared market practice that narrows the base standard to one agreed way of populating each message.
HVPS+ — High Value Payments Plus
HVPS+ is a set of market-practice guidelines — developed by central banks, market infrastructures, and commercial banks through the industry's Payments Market Practice Group alongside SWIFT — for how ISO 20022 messages should be used in high-value systems. It states which elements are used and mandatory, how parties and amounts are structured, and which code lists apply. HVPS+ runs no payment system itself; it is a shared reference each operator adopts.
| CBPR+ | HVPS+ | |
|---|---|---|
| Which leg | Cross-border interbank, over SWIFT | Domestic high-value systems (RTGS) |
| Who agrees it | Correspondent-banking community via PMPG/SWIFT | Central banks and market infrastructures via PMPG/SWIFT |
| What it narrows | ISO 20022 for cross-border payments and reporting | ISO 20022 for high-value settlement messages |
| Relationship | Deliberately aligned so data carries at the boundary | Deliberately aligned so data carries at the boundary |
Alignment across borders
The payoff shows most clearly where a payment crosses between systems. A cross-border payment often travels over a correspondent relationship formatted to CBPR+, then lands in a domestic RTGS system to reach the final bank. If the two practices described their messages differently, data would have to be reshaped at the boundary — and reshaping is where structured detail is lost and manual repair begins. HVPS+ is deliberately aligned with CBPR+ so a structured address, a purpose code, or a party identifier populated for the cross-border leg carries into the domestic leg without being rebuilt.
STRICTLY SPEAKING
Strictly speaking, this harmonisation is never quite total. Each high-value system keeps some local rules, and every operator publishes its own specific usage guidelines that a participant must still follow. The direction is steady convergence on one shared way of expressing a high-value payment — not a single identical message everywhere.
FOR NOW, REMEMBER
- A high-value system carries the largest, most time-sensitive payments — usually a central bank's RTGS, settling each payment on its own, in full, and with finality.
- Gross settlement gives certainty but demands intraday liquidity, because each payment needs cover at the moment it settles.
- HVPS+ is the market practice that narrows ISO 20022 for high-value systems, the same kind of tool CBPR+ is for cross-border.
- HVPS+ is deliberately aligned with CBPR+ so data survives the boundary between a cross-border leg and a domestic RTGS leg.
TRY IT YOURSELF
Bank Alfa's USD 2,500,000.00 payment to Nordbank has settled in Central Bank Omega's RTGS system this morning. An hour later Bank Alfa realises it sent to the wrong counterparty. What is true about that settled payment?
SWIFT MT and ISO 20022 are the standards this course lives in — but they are not the only ones. Next, a short map of the other message families worth recognising, from card messaging to national file formats.
KEEP GOINGKey takeaways / 03
Three things to remember
- 01
A high-value payment system is usually a central-bank RTGS (real-time gross settlement) system that settles large payments individually and with finality.
- 02
HVPS+ (High Value Payments Plus) is a market-practice guideline for how ISO 20022 messages are populated in high-value systems.
- 03
Shared guidelines make a payment carry the same fields in the same places across different systems, protecting data and automation.
Practical use cases / 04
Where you would use this
A central bank operating an RTGS system adopts HVPS+ so its ISO 20022 messages match the market practice used by other high-value systems.
A bank's payments team builds one ISO 20022 implementation that works across several HVPS+-aligned systems rather than a different one for each.
A correspondent bank relies on consistent HVPS+ fields so a cross-border payment entering a domestic system needs no manual repair.
Worked example / 05
Put the idea into a real situation
Illustrative example: a fictional bank, Meridian Trust, must settle a EUR 4,750,000.00 interbank payment to a fictional counterparty, Kestrel Union Bank, on the same day. It sends the payment into a central-bank RTGS (real-time gross settlement) system as an ISO 20022 pacs.009 message formatted to HVPS+ (High Value Payments Plus) guidelines. The system settles the full EUR 4,750,000.00 individually and finally in central-bank money within 30 seconds, with no netting against other payments. Because the same HVPS+ field usage matches the CBPR+ cross-border guidelines the payment followed on its earlier leg, the structured parties and amounts carry across the boundary unchanged, and Kestrel Union Bank books the funds without a repair step.
Evidence & review / 07
Evidence & review
Domestic high-value payment systems (usually central-bank RTGS) adopting ISO 20022 under HVPS+ market practice, and their alignment with CBPR+ for cross-border.
What this brief simplifies: RTGS settlement and liquidity are shown in a two-entry teaching ledger; queues, reservations, and intraday liquidity mechanics are named but not modelled. No volumes or thresholds are quoted. Named parties are fictional teaching cast.
Sources for this brief4
- Market practice
High Value Payments Systems Plus (HVPS+) usage guidelines ↗ — HVPS+ task force (published by Swift) · ISO 20022 usage in high-value systems
Full guidelines are published on MyStandards; content here relies on public summaries.
- Market practice
Cross-Border Payments and Reporting Plus (CBPR+) usage guidelines ↗ — Swift (CBPR+ working group) · Cross-border alignment with HVPS+
Full guidelines require MyStandards access; content here relies on public summaries. MT-to-CBPR+ translation rules are published on Swift's translation portal.
- Official requirementMarch 2003 edition
A glossary of terms used in payments and settlement systems ↗ — CPSS (now CPMI), Bank for International Settlements · RTGS, gross settlement, settlement finality
Terminology has evolved since this edition; newer CPMI publications refine some definitions.
- Scheme-specific rule
CHAPS ↗ — Bank of England · Operator-specific high-value usage guidelines
The Bank of England has operated CHAPS directly since November 2017; participant-facing reference documents are published separately.