CROSS-BORDER SETTLEMENTS

MT103 and pacs.008: what to ask your bank for now

By Irina Russu, Head of Partnerships at ArtPay · Updated · 8 min read

Swift ended the coexistence period for cross-border payments on 22 November 2025, and the instruction that used to travel as an MT103 now travels as a pacs.008 message. Banks still issue a customer confirmation, and many still label it MT103. What to request is the payment confirmation plus the UETR, the end-to-end reference that lets a bank trace it.

What changed on 22 November 2025

For years a cross-border customer payment between banks could travel in one of two formats: the older Swift MT message, or ISO 20022. Swift's FAQ states that this coexistence period ended on 22 November 2025. Since then, according to Swift, MT payment instructions are no longer supported by the FIN service for bank-to-bank cross-border flows. The customer credit transfer that used to travel as an MT103 now travels as pacs.008, the ISO 20022 message that does the same job, and the bank-to-bank transfer that used to be an MT 202 now travels as pacs.009.

Swift built short-term contingency processing for MT messages still sent: an MT 103 that a bank still sends is checked against extra validation rules and converted into its ISO 20022 equivalent before delivery, so the receiving bank gets ISO 20022. A receiving bank that is not ready can ask for an MT representation of what arrives, through Swift's in-flow translation. Both services have been chargeable since 1 January 2026, and Swift describes them as temporary. Several older types were removed outright and are rejected by the network: MT 102, MT 102 STP, MT 103 REMIT, MT 201 and MT 203.

Tracking survived the change. Swift states that the MT 199 and MT 299 messages used for tracking through its gpi Tracker are still supported after November 2025, with no end date set, although they are deprecated and new tracking features arrive only in ISO 20022 and API formats. The next steps are on Swift's ISO 20022 page for financial institutions, which carries the CBPR+ roadmap.

For a company, little of this is visible. The bank still takes the order through online banking or a file upload, and still produces a confirmation afterwards. What changed is the message underneath, and with it the name of the document your finance team should ask for.

What to ask for now, in one sentence

Ask the sender: "Please send the customer payment confirmation for this transfer, plus the UETR." That line works whichever format the sending bank uses internally, and it gives the receiving side what it needs to look for the money.

A status in the payer's banking app is not enough. "Sent", "Completed" or "Processed" usually means the bank accepted the order or debited the account. It does not say which bank holds the payment now, and it carries no reference another bank can search for. A customer confirmation usually shows:

  • The date the payment was sent and the value date
  • The amount and currency
  • The ordering customer and their account
  • The beneficiary name, account number or IBAN, and the beneficiary bank's BIC
  • The charge code: OUR, SHA or BEN
  • The UETR, sometimes labelled "end-to-end reference" or "tracking reference"
  • The remittance information, which is the purpose line and invoice number

Compare the beneficiary details with your own, line by line. A wrong digit, a different name or the wrong bank code is a common reason a payment stalls or comes back. For EUR account details, the free IBAN checker confirms the IBAN and BIC format. For the next invoice, the payment details builder assembles the name, account details, reference, purpose line and charge code into one block the payer can copy.

What a UETR is and what it shows

UETR stands for Unique End-to-end Transaction Reference. It is a 36-character identifier created with the payment and meant to stay unchanged along the route. Swift uses it to link all the messages that belong to one transaction, which is why it is the most useful single reference for a trace.

With the UETR, a bank on the route that uses Swift tracking can usually see which bank holds the payment, whether it was credited, or whether it was rejected and is on its way back. It does not explain why a bank is holding a payment. That answer comes only from the bank itself.

The value date sets the timetable. It is the date the sending bank intended the funds to settle. Before it, a trace usually returns nothing useful. After it, the sending bank can be asked to open one. Bank holidays on either side move this, and the days US and European rails do not process are listed in the payment system holidays calendar for 2027.

Why your bank still says "MT103"

Many bank portals still label the downloadable confirmation "MT103", and many accounts teams still ask for one. The word lives on in contracts, invoice terms and help pages written years ago. A portal may keep the old name on a document that is now produced from a pacs.008, or from an MT that is converted on the way. Swift's conversion and translation services exist precisely so that banks can keep older systems running for a while.

So it is fine to ask for the document by the name the bank recognises. If the payer's bank calls it an MT103 copy, ask for the MT103 copy. If it calls it a payment advice or a Swift confirmation, ask for that. What matters is the content: the beneficiary details as sent, the value date and the UETR. If the document shows no UETR, ask the bank for it separately.

The reverse happens too. A supplier may insist on "an MT103" and turn down a confirmation with a different title. A short reply usually settles it: since November 2025 cross-border instructions between banks travel as ISO 20022 pacs.008 messages, and the attached confirmation shows the same fields, with the UETR for tracking.

What is not proof that the money reached you

None of the documents above confirms that the beneficiary was credited. A customer confirmation shows what the sending bank was instructed to send, and that it sent it. It says nothing about what happened at the next bank on the route.

A pacs.009, the ISO 20022 successor to the MT 202, is sometimes offered as further evidence. It confirms a transfer between banks, for example the cover payment that funds a correspondent bank. It does not confirm that the end customer was credited. A debit on the payer's statement is similar: it shows that the money left the payer's account.

What does show a credit is the beneficiary's own statement, or a tracking status saying the payment was credited to the beneficiary's account. Which document an auditor, a counterparty or a court accepts in a given case is a separate question, and it depends on the contract and the jurisdiction.

Who to ask, and in what order

A trace follows the payment, and the payment starts at the sender's bank. The beneficiary usually cannot open a trace at a bank where they hold no account, so the order of requests matters.

  1. The sender. Ask for the confirmation and the UETR. Ask them to check that the payment was released and is not waiting for a second approval in their own system.
  2. The sender's bank. If the confirmation is correct, the sender asks their bank to trace the payment by UETR. The sending bank can query the next bank in the chain and receive a status from it.
  3. Your own bank or provider. With the UETR, amount and value date, ask whether the funds have arrived and are held for a question, for example about the purpose of the payment or a name that does not match. Funds can sit at the receiving bank before they appear on the statement.
  4. The intermediary bank. A correspondent bank usually deals only with banks it has a relationship with, so questions to it go through the sending bank rather than from the beneficiary.

The beneficiary does not start the trace. Their part is to confirm their own details, ask their own bank about funds already received, and keep a record of who was asked, on which date, and what they said. If the payment is returned and has to be sent again, that record shortens the second attempt. How the payment moves on each rail, and why SWIFT involves more banks than a domestic transfer, is compared in ACH, Wire, SWIFT and SEPA.

When the money arrived but short

This guide is about where a payment is. If it arrived for less than the invoice, the question changes to which bank deducted what, and under which charge code. That case is covered in why an international wire arrives short, and the code that helps prevent it in OUR, SHA and BEN.

ArtPay provides a business account in USD and EUR: USD via ACH and Wire through SSB Bank, USD via SWIFT through Portage Bank, and EUR via SEPA through ClearBank. A client in the United States can pay USD as a domestic transfer and a client in the SEPA area can pay EUR by SEPA, which keeps SWIFT for the payers who need it. The transparent fixed fee for each route is set out in a written quote. Get the cost of your route in writing.

Sources: Swift — ISO 20022 FAQ: implementation, Swift — ISO 20022 FAQ: MT to ISO 20022 conversion, Swift — ISO 20022 for financial institutions and the CBPR+ roadmap.

Questions

Is the MT103 still used?

Not as the standard instruction between banks for cross-border payments. Swift ended the MT and ISO 20022 coexistence period on 22 November 2025. A bank that still sends an MT 103 has it converted by Swift into ISO 20022, a service charged since 1 January 2026. Many banks still use the name MT103 on the confirmation they give customers.

What replaced the MT103?

pacs.008, the ISO 20022 customer credit transfer sent from bank to bank. It carries the same core payment details as the MT103 in a richer, more structured format. The bank-to-bank transfer that used to be an MT 202 is now a pacs.009.

What is a UETR?

A UETR (Unique End-to-end Transaction Reference) is a 36-character identifier created with a payment and meant to stay unchanged along the route. With it, a bank that uses Swift tracking can usually see which bank holds the payment, whether it was credited, or whether it was returned.

Can the beneficiary trace an incoming payment?

Only in part. The beneficiary can ask their own bank whether funds have arrived or are held, quoting the UETR, amount and value date. A trace along the route is opened by the sending bank, so the request starts with the payer.

This guide is general information, not legal, tax or financial advice. Payment rules and timings vary by bank and country; confirm the details for your route with your provider.