Payments Academy
Two largest US dollar payment systems PAYMENT OPERATIONS STARTED LIVE 01 Two largest US dollar payment systems - have both completed their ISO ACTIVE 02 Fedwire processes around 800,000 payments - day with a value of around 4 QUEUED 03 Netted multilaterally - Payments are queued QUEUED 04 Upgrading payment engines - banks, the migration required upgrading QUEUED 05 Cutover - system, not a phased coexistence, which QUEUED 06 Exception handling - Your exception handling should use the ISO QUEUED The two largest US dollar payment systems have both completed their ISO 20022 migrations. Step 1 of 6 Two largest US dollar payment systems STARTED Two largest US dollar payment systems have both completed their ISO 20022 ACTIVE Fedwire processes around 800,000 day with a value of around 4 trillion dollars QUEUED Netted multilaterally Payments are queued QUEUED Upgrading payment engines banks, the migration required upgrading QUEUED Cutover system, not a phased coexistence, which QUEUED Exception handling Your exception handling should use the ISO QUEUED The two largest US dollar payment systems have both completed their ISO 20022 migrations.
Fedwire processes around 800,000 payments PAYMENT OPERATIONS IN PROGRESS LIVE 01 Two largest US dollar payment systems - have both completed their ISO DONE 02 Fedwire processes around 800,000 payments - day with a value of around 4 ACTIVE 03 Netted multilaterally - Payments are queued QUEUED 04 Upgrading payment engines - banks, the migration required upgrading QUEUED 05 Cutover - system, not a phased coexistence, which QUEUED 06 Exception handling - Your exception handling should use the ISO QUEUED Fedwire processes around 800,000 payments a day with a value of around 4 trillion dollars, and all of those payments now use ISO 20022 as well. Step 2 of 6 Fedwire processes around 800,000 payments IN PROGRESS Two largest US dollar payment systems have both completed their ISO 20022 DONE Fedwire processes around 800,000 day with a value of around 4 trillion dollars ACTIVE Netted multilaterally Payments are queued QUEUED Upgrading payment engines banks, the migration required upgrading QUEUED Cutover system, not a phased coexistence, which QUEUED Exception handling Your exception handling should use the ISO QUEUED Fedwire processes around 800,000 payments a day with a value of around 4 trillion dollars, and all of those payments now use ISO 20022 as well.
Netted multilaterally PAYMENT OPERATIONS IN PROGRESS LIVE 01 Two largest US dollar payment systems - have both completed their ISO DONE 02 Fedwire processes around 800,000 payments - day with a value of around 4 DONE 03 Netted multilaterally - Payments are queued ACTIVE 04 Upgrading payment engines - banks, the migration required upgrading QUEUED 05 Cutover - system, not a phased coexistence, which QUEUED 06 Exception handling - Your exception handling should use the ISO QUEUED Payments are queued, netted multilaterally, and settled at the end of the day. Step 3 of 6 Netted multilaterally IN PROGRESS Two largest US dollar payment systems have both completed their ISO 20022 DONE Fedwire processes around 800,000 day with a value of around 4 trillion dollars DONE Netted multilaterally Payments are queued ACTIVE Upgrading payment engines banks, the migration required upgrading QUEUED Cutover system, not a phased coexistence, which QUEUED Exception handling Your exception handling should use the ISO QUEUED Payments are queued, netted multilaterally, and settled at the end of the day.
Upgrading payment engines PAYMENT OPERATIONS IN PROGRESS LIVE 01 Two largest US dollar payment systems - have both completed their ISO DONE 02 Fedwire processes around 800,000 payments - day with a value of around 4 DONE 03 Netted multilaterally - Payments are queued DONE 04 Upgrading payment engines - banks, the migration required upgrading ACTIVE 05 Cutover - system, not a phased coexistence, which QUEUED 06 Exception handling - Your exception handling should use the ISO QUEUED For banks, the migration required upgrading payment engines to parse Step 4 of 6 Upgrading payment engines IN PROGRESS Two largest US dollar payment systems have both completed their ISO 20022 DONE Fedwire processes around 800,000 day with a value of around 4 trillion dollars DONE Netted multilaterally Payments are queued DONE Upgrading payment engines banks, the migration required upgrading ACTIVE Cutover system, not a phased coexistence, which QUEUED Exception handling Your exception handling should use the ISO QUEUED For banks, the migration required upgrading payment engines to parse
Cutover: single date for each PAYMENT OPERATIONS IN PROGRESS LIVE 01 Two largest US dollar payment systems - have both completed their ISO DONE 02 Fedwire processes around 800,000 payments - day with a value of around 4 DONE 03 Netted multilaterally - Payments are queued DONE 04 Upgrading payment engines - banks, the migration required upgrading DONE 05 Cutover - system, not a phased coexistence, which ACTIVE 06 Exception handling - Your exception handling should use the ISO QUEUED The cutover was a single date for each system, not a phased coexistence, which meant banks had to be ready on the day or stop sending payments. Step 5 of 6 Cutover: single date for each IN PROGRESS Two largest US dollar payment systems have both completed their ISO 20022 DONE Fedwire processes around 800,000 day with a value of around 4 trillion dollars DONE Netted multilaterally Payments are queued DONE Upgrading payment engines banks, the migration required upgrading DONE Cutover system, not a phased coexistence, which ACTIVE Exception handling Your exception handling should use the ISO QUEUED The cutover was a single date for each system, not a phased coexistence, which meant banks had to be ready on the day or stop sending payments.
Exception handling PAYMENT OPERATIONS COMPLETE LIVE 01 Two largest US dollar payment systems - have both completed their ISO DONE 02 Fedwire processes around 800,000 payments - day with a value of around 4 DONE 03 Netted multilaterally - Payments are queued DONE 04 Upgrading payment engines - banks, the migration required upgrading DONE 05 Cutover - system, not a phased coexistence, which DONE 06 Exception handling - Your exception handling should use the ISO ACTIVE Your exception handling should use the ISO 20022 status and return messages. Step 6 of 6 Exception handling COMPLETE Two largest US dollar payment systems have both completed their ISO 20022 DONE Fedwire processes around 800,000 day with a value of around 4 trillion dollars DONE Netted multilaterally Payments are queued DONE Upgrading payment engines banks, the migration required upgrading DONE Cutover system, not a phased coexistence, which DONE Exception handling Your exception handling should use the ISO ACTIVE Your exception handling should use the ISO 20022 status and return messages.

Key points of this lesson, in order.

0:00 / 2:34 Step 1 of 6

Fedwire and CHIPS ISO 20022 migrations: complete

US: Fedwire, FedNow, ACH, CHIPS, Lesson 8 of 8, Narration 2:34, D05 Domestic payment systems

ReconciliationSettlementISO 20022

What you will learn

Your objective. By the end of this lesson, you will be able to explain FEDWIRE and CHIPS ISO 20022 migrations: complete. The two largest US dollar payment systems have both completed their ISO 20022 migrations.

Why it matters. For a business analyst, the practical impact is that US payment projects now assume ISO 20022.

Chapter objective: Learner compares Fedwire, FedNow, ACH, and CHIPS in the United States, explaining settlement timing, finality, value limits, and the business cases each system serves. Learner applies this skill in realistic banking scenarios, with clear examples and correct terminology throughout.

Key learning points

  • Two largest US dollar payment systems
  • Fedwire processes around 800,000 payments
  • Netted multilaterally
  • Upgrading payment engines
  • Cutover: single date for each
  • Exception handling

Key terms

Reconciliation: The process of comparing records from two sources, such as a bank statement and an internal ledger, to confirm they agree.

Settlement: The final movement of funds between banks to discharge obligations created by cleared payments. Settlement is usually made in central bank money or through correspondent accounts.

ISO 20022: An international standard for financial messaging that defines XML message formats for payments, securities and trade.

Payment flow diagram showing Fedwire and CHIPS ISO 20022 migrations: complete.

Practise this lesson

Exercise

Read the ISO 20022 migrations message described in this lesson and identify its key parts.

Use the message structure, fields and example in this lesson.

  1. What to do. List the main blocks of the message, name the field that carries the amount, and name the field that identifies the payment.

Correct result. The message is made of blocks, each carrying a part of the payment instruction. The amount field and the identification field are the two a receiving bank checks first, because without them it cannot process or reconcile the payment.

Why. A message is only useful if you can read it. The blocks tell the receiving bank what to do, and the amount and identification fields are what it checks first.

Check your understanding

Practice question

Which of the following best describes FEDWIRE and CHIPS ISO 20022 migrations: complete?

Takeaway and next step

What to remember

For a business analyst, the practical impact is that US payment projects now assume ISO 20022.

Open the message type from this lesson and inspect its fields, then find the field that carries the amount.

Open the ISO 20022 Message Explorer →

Builds on "Choosing between Fedwire, FedNow, ACH and CHIPS".

Transcript and full text

Show transcript

The two largest US dollar payment systems have both completed their ISO 20022 migrations. CHIPS, the Clearing House Interbank Payments System, moved to ISO 20022 in April 2024. CHIPS processes around 500,000 payments a day with a value of around 1.8 trillion dollars, and all of those payments now use ISO 20022 messages. Fedwire, the Federal Reserve real-time gross settlement system, moved to ISO 20022 in July 2025. Fedwire processes around 800,000 payments a day with a value of around 4 trillion dollars, and all of those payments now use ISO 20022 as well. Together the two migrations moved the majority of US dollar wholesale value onto the same message standard as the rest of the world. The migration changed the message format but not the settlement model. Fedwire is still a real-time gross settlement system. Each payment settles individually in central bank money, in real time, with finality. CHIPS is still a netting system. Payments are queued, netted multilaterally, and settled at the end of the day. What changed is the data. Both systems now carry structured party information, structured remittance data, and the same field definitions as the cross-border pacs.008 and pacs.009 messages. A payment that travels from a US bank through Fedwire and then cross-border through SWIFT now carries consistent data throughout, which is the point of the migration: one data model from the domestic leg to the cross border leg. What exactly changed in the messages is worth listing, because it drives the requirements. The old proprietary formats carried party names as free text with limited structure. The new ISO 20022 messages carry structured addresses with separate fields for street, town, country and postcode, purpose codes that say why the payment is being made, legal entity identifiers where available, and remittance information that can be structured rather than a single free text line. The debtor and creditor agents are identified with BICs, the end to end reference is carried consistently, and the message version is explicit in the name, for example pacs.008.001.08. An analyst who writes a requirement that says the payment carries the beneficiary name must now say which structured field carries it, because there is more than one. For banks, the migration required upgrading payment engines to parse and generate ISO 20022 XML, updating screening systems to use structured data, and updating reconciliation to match on the new references. The Federal Reserve and The Clearing House published implementation guides, test environments, and cutover plans, and banks had to certify their readiness before the migration date. The cutover was a single date for each system, not a phased coexistence, which meant banks had to be ready on the day or stop sending payments. That is a hard cutover, and it is the riskiest kind: there is no fallback to the old format after the date, so the testing and the certification had to be complete before it. Screening is where the richer data pays off first. Under the old format, a sanctions screen had to match against a free text name and address, which produced false positives whenever a name was similar to a sanctioned name. Under ISO 20022, the screen can match on structured fields, on the country code, on the purpose code and on the legal entity identifier, which reduces false positives and lets genuine payments through faster. The analyst should confirm with the compliance team which structured fields the screening engine now uses, and should make sure the payment initiation screens capture those fields, because a structured field left blank is a screening gap. Reconciliation improves for the same reason. Under the old format, matching a payment to a trade or an invoice depended on a free text reference that could be truncated or mistyped. Under ISO 20022, the end to end reference, the instruction identification and the structured remittance data give reconciliation three separate keys to match on, and the pacs.002 status report carries the same references back, so the operations team can match a payment to its confirmation without manual work. The analyst should design the reconciliation around those three keys, and should specify what happens when one of them is missing: which key is the fallback, and who is told. The cross border consistency is the strategic gain. A US dollar payment that leaves a US bank through Fedwire or CHIPS and then travels through SWIFT to a bank in Europe or Asia now uses ISO 20022 messages, but Fedwire and CHIPS each use their own ISO 20022 usage guidelines and implementation guides, not the SWIFT CBPR+ usage guidelines. The message names overlap, but field rules, versions and market practice differ by system, so data may still need to be translated at the boundary. Source: Federal Reserve Fedwire ISO 20022 implementation guide; The Clearing House CHIPS ISO 20022 usage guidelines. That means the data does not have to be translated at the boundary, the screening does not have to be repeated on a different format, and the tracking reference survives the whole journey. An analyst working on a cross border payment that starts in the US should trace the message from the Fedwire or CHIPS leg through the SWIFT leg and confirm the same references appear at each step. For a business analyst, the practical impact is that US payment projects now assume ISO 20022. Your requirements should reference the Fedwire and CHIPS ISO 20022 usage guidelines, not the old proprietary formats. Your test cases should use ISO 20022 messages. Your exception handling should use the ISO 20022 status and return messages. And when a customer asks why a US payment carries more data than it used to, you can explain that the richer data improves screening, reduces false positives, and makes reconciliation faster. The migration is complete, the old formats are gone, and there is no reason to write a requirement against them.

The two largest US dollar payment systems have both completed their ISO 20022 migrations. CHIPS, the Clearing House Interbank Payments System, moved to ISO 20022 in April 2024. CHIPS processes around 500,000 payments a day with a value of around 1.8 trillion dollars, and all of those payments now use ISO 20022 messages. Fedwire, the Federal Reserve real-time gross settlement system, moved to ISO 20022 in July 2025. Fedwire processes around 800,000 payments a day with a value of around 4 trillion dollars, and all of those payments now use ISO 20022 as well. Together the two migrations moved the majority of US dollar wholesale value onto the same message standard as the rest of the world.

The migration changed the message format but not the settlement model. Fedwire is still a real-time gross settlement system. Each payment settles individually in central bank money, in real time, with finality. CHIPS is still a netting system. Payments are queued, netted multilaterally, and settled at the end of the day. What changed is the data. Both systems now carry structured party information, structured remittance data, and the same field definitions as the cross-border pacs.008 and pacs.009 messages. A payment that travels from a US bank through Fedwire and then cross-border through SWIFT now carries consistent data throughout, which is the point of the migration: one data model from the domestic leg to the cross border leg.

What exactly changed in the messages is worth listing, because it drives the requirements. The old proprietary formats carried party names as free text with limited structure. The new ISO 20022 messages carry structured addresses with separate fields for street, town, country and postcode, purpose codes that say why the payment is being made, legal entity identifiers where available, and remittance information that can be structured rather than a single free text line. The debtor and creditor agents are identified with BICs, the end to end reference is carried consistently, and the message version is explicit in the name, for example pacs.008.001.08. An analyst who writes a requirement that says the payment carries the beneficiary name must now say which structured field carries it, because there is more than one.

For banks, the migration required upgrading payment engines to parse and generate ISO 20022 XML, updating screening systems to use structured data, and updating reconciliation to match on the new references. The Federal Reserve and The Clearing House published implementation guides, test environments, and cutover plans, and banks had to certify their readiness before the migration date. The cutover was a single date for each system, not a phased coexistence, which meant banks had to be ready on the day or stop sending payments. That is a hard cutover, and it is the riskiest kind: there is no fallback to the old format after the date, so the testing and the certification had to be complete before it.

Screening is where the richer data pays off first. Under the old format, a sanctions screen had to match against a free text name and address, which produced false positives whenever a name was similar to a sanctioned name. Under ISO 20022, the screen can match on structured fields, on the country code, on the purpose code and on the legal entity identifier, which reduces false positives and lets genuine payments through faster. The analyst should confirm with the compliance team which structured fields the screening engine now uses, and should make sure the payment initiation screens capture those fields, because a structured field left blank is a screening gap.

Reconciliation improves for the same reason. Under the old format, matching a payment to a trade or an invoice depended on a free text reference that could be truncated or mistyped. Under ISO 20022, the end to end reference, the instruction identification and the structured remittance data give reconciliation three separate keys to match on, and the pacs.002 status report carries the same references back, so the operations team can match a payment to its confirmation without manual work. The analyst should design the reconciliation around those three keys, and should specify what happens when one of them is missing: which key is the fallback, and who is told.

The cross border consistency is the strategic gain. A US dollar payment that leaves a US bank through Fedwire or CHIPS and then travels through SWIFT to a bank in Europe or Asia now uses ISO 20022 messages, but Fedwire and CHIPS each use their own ISO 20022 usage guidelines and implementation guides, not the SWIFT CBPR+ usage guidelines. The message names overlap, but field rules, versions and market practice differ by system, so data may still need to be translated at the boundary. Source: Federal Reserve Fedwire ISO 20022 implementation guide; The Clearing House CHIPS ISO 20022 usage guidelines. That means the data does not have to be translated at the boundary, the screening does not have to be repeated on a different format, and the tracking reference survives the whole journey. An analyst working on a cross border payment that starts in the US should trace the message from the Fedwire or CHIPS leg through the SWIFT leg and confirm the same references appear at each step.

For a business analyst, the practical impact is that US payment projects now assume ISO 20022. Your requirements should reference the Fedwire and CHIPS ISO 20022 usage guidelines, not the old proprietary formats. Your test cases should use ISO 20022 messages. Your exception handling should use the ISO 20022 status and return messages. And when a customer asks why a US payment carries more data than it used to, you can explain that the richer data improves screening, reduces false positives, and makes reconciliation faster. The migration is complete, the old formats are gone, and there is no reason to write a requirement against them.

Full lesson text (all scenes)

Completing a lesson updates your progress dashboard on the homepage.

Scene timestamps are estimated by allocating the narration text proportionally across the real audio length. The audio playback position is the source of truth: pause freezes the visual, seeking restores the correct scene, replay restarts the scene animation.