What Is an MT202 SWIFT Message? MT202 vs MT103 and MT202 COV Explained
What Is an MT202 SWIFT Message? MT202 vs MT103 and MT202 COV Explained
Global Payments

Published on 20/11/2026

What Is an MT202 SWIFT Message? MT202 vs MT103 and MT202 COV Explained

Get paid by clients abroad with fewer SWIFT hops

Share local USD, EUR, GBP or CAD details so clients pay by a normal bank transfer.

MT202 is a SWIFT message that one bank sends another to move the bank's own funds, which is why its formal name is the general financial institution transfer. It names banks only, never a customer. The customer side of a payment travels in a different message, the MT103, which carries the payer, the payee and the amount.


A cover version, the MT202 COV, adds the payer and payee details so that every bank in the chain can run its anti-money laundering and sanctions checks. Because banks can send the customer instruction and the funds by separate routes, your client's MT103 may reach your bank before the money itself does.


As an exporter or freelancer, you will usually never see this bank-to-bank message, since it moves between banks rather than to you. Knowing what it is helps when a client shares a payment record, because you can tell which documents show the payment was sent and which one shows it reached your account.


MT202 vs MT103 key differences for exporters receiving payments

The MT103 carries your client's instruction, while the bank-to-bank message moves money between banks. For the field-by-field detail of the customer message, see our guide to the SWIFT MT103. The points that matter when a client pays you from abroad line up like this.

PointMT103MT202
Formal nameSingle customer credit transferGeneral financial institution transfer
What it doesCarries one customer's payment instructionMoves funds between banks for settlement or liquidity
Who it is sent betweenPayer's bank to payee's bank, sometimes through correspondentsBank to bank only; every party is a financial institution
Names the payer and payee?Yes, in field 50a and field 59aNo; it names banks only
Main beneficiary fieldField 59a, the beneficiary customerField 58a, the beneficiary bank
ISO 20022 versionpacs.008pacs.009 (pacs.009 COV for the cover version)
Valid proof of payment for you?No; it shows the instruction was sent, not that you were creditedNo; it carries no customer details and cannot name you
Who usually sees itYour bank, and you if the client shares a copyBanks in the chain only

Read as a pair, the split is simple: one message talks about customers, the other settles between banks. Neither replaces the other, and in a cover payment banks send both together.


What the COV version adds and why correspondent banks need it

The cover version was introduced on 21 November 2009 to make payments more transparent. The plain version had no space for the original payer or payee, so banks passing the funds along could not screen who was really paying whom. The COV version fixed that by carrying the customer details alongside the bank details.


It does this with a second block of fields. Sequence A holds the bank information found in the plain version, while sequence B repeats the underlying customer transfer: the ordering customer in field 50a, the beneficiary customer in field 59a and optional remittance details in field 70. Those customer fields must match the MT103 that the cover payment supports.

FeaturePlain MT202MT202 COV
Used forBank-to-bank transfers on the bank's own accountCovering a customer payment sent by the cover method
Customer detailsNonePayer and payee in sequence B
Linked MT103NoneSame UETR as the MT103, copied unchanged
Screening by banks in the chainBanks onlyBanks can check the payer and payee

The plain version must not be used to fund a customer transfer sent by cover; that job belongs to the cover version. The COV never replaces your client's MT103, because it cannot carry the customer instruction on its own.


What an exporter sees, from the MT103 to the credit advice

When your client's bank pays by the cover method, two messages leave it at once and take different paths. You see only the parts that touch your bank, which is why a payment can look sent on the client's side while your account has not moved yet.


This matters most when you invoice clients abroad every month and track each receipt against an invoice. Knowing which message reached your bank, and which one stayed between the correspondents, tells you whether to wait, ask your client for the reference, or ask your bank to trace the payment.


An example of the MT103 and the funds travelling separately


The names and numbers here are dummy values for illustration only. Northwind Analytics Ltd in London pays Asha Tech Services Pvt Ltd in Pune USD 4,250 against invoice INV-2026-118.


  1. The instruction - Northwind's bank sends an MT103 straight to Asha's bank, carrying the payer, the payee and a UETR, the unique reference that follows the payment end to end.
  2. The funding message - Northwind's bank sends an MT202 COV with the same UETR to its correspondent bank, which holds the accounts the money actually moves through.
  3. The handover - The correspondent, and any intermediary bank after it, passes the funds on bank to bank, and each can screen the payer and payee in sequence B.
  4. The credit - Asha's bank receives the funds, credits Asha and usually gets only a credit advice, the MT910, rather than the cover message itself.


Because the MT103 travels directly, it can arrive before the funds that the cover message is moving. That gap is normal in the cover method. In the serial method, a single MT103 passes through each bank together with the money instead.


Why an MT202 alone does not show you were paid


A shared copy of either bank message can look reassuring, yet neither one confirms that the money reached you. Here is what each message can and cannot tell you about your invoice:


  • The bank-to-bank message - It has no field 50a or field 59a, so it cannot name you as the payee, and field 21 holds only a related reference.
  • An MT103 - It shows what the payer's bank instructed, which helps with tracing, but only your own bank can confirm that the money was credited to your account.
  • Their ISO 20022 versions - A pacs.008 or pacs.009 copy works the same way, so the newer format still shows what was sent between banks rather than what reached your account.


Treat both messages as evidence that something was sent, and look to your bank for evidence that something arrived.


What to ask your client and your bank for instead


Ask for the documents that each side can genuinely produce:


  • From your client - A copy of the MT103 or pacs.008 payment advice together with the UETR, because your bank can use that 36-character reference to trace the payment along its route.
  • From your bank - The credit advice or statement entry for the incoming payment, since that is the only record that confirms the money was actually credited to your account.
  • For your export records - Your FIRA and e-BRC, which come from your bank's reporting of the inward remittance and not from any SWIFT message, so ask your bank rather than your client.


If incoming payments from abroad are a regular part of your business, foreign currency receiving accounts let your clients pay you locally in their own currency.


Key fields such as 32A and 58A, with an example message

The MT202 format has four mandatory fields, 20, 21, 32A and 58a, and a set of optional ones that describe the route. You do not need to read every tag, but a few lines help you check that a message matches your invoice. Here are the fields and the one thing each tells you.

FieldNameWhat you can check
20Transaction reference numberThe sending bank's own reference to quote if you query it
21Related referenceWhether it points to the MT103 your client sent
32AValue date, currency and amountDate, currency and amount against your invoice, before charges
52AOrdering institutionWhether it is your client's bank
53A and 56ASender's correspondent and intermediaryThe route the funds took, not you
57AAccount with institutionUsed when funds go through another bank first
58ABeneficiary institutionWhether it is your bank
72Sender to receiver informationFree-text notes between the banks

Fields 52A and 58A hold bank identifier codes, the same format explained in our guide to the SWIFT code. Here is a short dummy message; every bank code, reference and amount in it is invented for illustration.


```


{1:F01BANKGB2LAXXX0000000000}{2:I202BANKUS33XXXXN}{3:{121:3f8a1c2e-5b7d-4e19-9c40-7a2d6e8b1f35}}{4:


:20:DUMMYREF202611A


:21:INV2026118COVER


:32A:261117USD4250,00


:52A:BANKGB2LXXX


:58A:BANKINBBXXX


:72:/INS/DUMMY EXAMPLE ONLY


-} ``` In a message like this, field 121 in block 3 holds the UETR and block 4 holds the fields above. A COV version would add sequence B after field 58A, with the payer in field 50K, the payee in field 59 and the invoice reference in field 70.


Is the message still used now that banks use ISO 20022

Since 22 November 2025, banks exchange cross-border payment instructions in the ISO 20022 format rather than the old MT format, and Swift can convert MT messages that still arrive. Banks, portals and clients still use the familiar names, so you will keep hearing the old MT names for some time.

Older SWIFT messageISO 20022 message
MT103pacs.008
MT202pacs.009
MT202 COVpacs.009 COV
MT910camt.054

If a bank still sends an old-format message, Swift's contingency service translates the common types, including the plain and cover versions, into the matching ISO 20022 message, and it has charged for that service since 1 January 2026. For you, the practical effect is small, because your bank still credits you and still issues the same records.


The idea is unchanged: pacs.009 moves funds between banks, and its cover version carries the underlying customer details just as the COV did. For background on the new standard, read our explainer on ISO 20022, and for the wider catalogue of message types, see our list of SWIFT message types.


How Xflow handles incoming SWIFT payments and FIRA for exporters

At Xflow, we run a cross-border payments platform that helps Indian ITES businesses and freelancers get paid by clients abroad. We hold the final Payment Aggregator - Cross Border (PA-CB) authorisation from the Reserve Bank of India (RBI) as of February 2026.


  • Local receiving accounts - Your clients pay into our receiving accounts in 25+ currencies, so ITES businesses and freelancers alike are not tied to one currency or one route.
  • Settlement and records - Funds reach your Indian bank account on the same business day, and each withdrawal comes with a free FIRA issued by an RBI-authorised bank.


Because your client pays into a local account, there is usually less need to chase an MT103 copy or trace a correspondent. Each withdrawal comes with the FIRA you need for your export records.


Conclusion for exporters on bank-to-bank transfer messages

The bank-to-bank message moves money between banks, the MT103 carries your client's instruction, and the cover version covers a customer payment while sharing the MT103's UETR. You usually see only the MT103 or pacs.008 copy and your bank's credit advice. For proof that you were paid, rely on your bank's credit record, FIRA and e-BRC.


When a payment looks sent but has not arrived, ask your client for the UETR and share it with your bank so it can trace the funds. Whether you run an ITES business or work as a freelancer, the same checks apply to every currency you are paid in.


Frequently asked questions

MT202 is a SWIFT message that moves funds between banks for the sending bank's own purposes, such as settlement or funding a correspondent account.


It names banks only, with no payer or payee, so it never carries a customer's payment instruction.

No. It contains no customer details, so it cannot show you were the intended payee. Proof comes from your bank's credit advice or statement entry, not from any SWIFT message. Your bank issues your FIRA after the money is credited.

The plain message moves bank funds and names banks only.


The COV version covers a customer payment sent with an MT103, adds a second block naming the payer and payee, and carries the same UETR as that MT103, so every bank in the chain can screen it.

No. SWIFT carries the messages that tell banks what to do, while the money moves through accounts that banks hold with each other.


In a cover payment, the instruction and the funds can even travel separately, which is why a payment can appear sent before your account is credited.

The name is still in daily use, but since 22 November 2025 banks exchange cross-border payment instructions as pacs.008 under ISO 20022. Swift can convert MT103 messages that still arrive, so banks and clients keep referring to an MT103 when they mean the payment advice.

A cover payment splits one payment into two messages. The payer's bank sends the MT103 straight to the payee's bank and sends the COV message through correspondent banks to move the funds.


The payee's bank then credits the payee and usually receives only a credit advice.

Yes.


A short bank-to-bank transfer message holds a reference in field 20, a related reference in field 21, the date, currency and amount in field 32A, and the paying and receiving banks in fields 52A and 58A. The format section above shows a dummy example with invented values.

Related Posts