Coinepay | MT103 Payment Confirmation: What It Is and How to Use It

If someone asks you for an “MT103 payment confirmation,” they usually want information that helps locate an international bank transfer. An MT103 can show that a payment instruction was sent, but it does not, by itself, prove that the recipient’s account was credited. The distinction matters when a sender says a transfer is complete and the recipient cannot yet find it.

What is an MT103?

MT103 is the name of a legacy Swift Single Customer Credit Transfer message. Financial institutions used it to communicate instructions for a customer payment. Swift carries the message; the institutions involved process the funds. A copy of an instruction is therefore different from confirmation that the recipient has received spendable money.

Since the November 2025 migration to ISO 20022 for cross-border interbank payments, the corresponding pacs.008 message is the normal format exchanged under Swift’s CBPR+ rules. MT103 has not disappeared entirely, but a bank or provider may now supply a pacs.008 record, a transfer receipt or tracking details instead of a document headed “MT103.” If someone asks specifically for an MT103, clarify whether they need the payment instruction, a reference for tracing, or confirmation of the final outcome.

What does an MT103 look like?

A legacy MT103 is a structured message with numbered fields, not a standard certificate with one universal visual layout. What you receive may be a message copy, a formatted PDF or a provider’s own confirmation. Fields commonly used to identify a transfer include:

:20: the sending institution’s transaction reference.
:32A: the value date, currency and interbank settlement amount. The value date is not proof of the date the recipient could use the funds.
:50a: the ordering customer, usually the sender.
:59a: the beneficiary, usually the intended recipient.
:71A: the charge arrangement, where shown.

An MT103 can also carry a UETR—a 36-character Unique End-to-end Transaction Reference—in header field 121. The UETR helps participating institutions track the same payment across its route. Not every customer-facing receipt reproduces every message field, so ask the sending institution which reference it can provide.

An obviously fictional example

The following is an invented, incomplete illustration of selected legacy fields. “EXAMPLE ONLY” is not an account identifier, and this text cannot be used to make or verify a payment:

:20: FICTIONAL-REFERENCE
:32A: 261016USD1234,56
:50K: EXAMPLE SENDER
:59: EXAMPLE ONLY RECIPIENT
:71A: SHA

In this illustration, SHA identifies a charge-sharing arrangement; it does not state a fee. A real document may contain additional headers, institution identifiers, account details and fields relevant to that payment. Do not rely on an image or edited text supplied by an unknown person as independent proof that funds were sent.

How does it differ from related codes and confirmations?

Term	What it identifies or reports	What it does not prove alone
MT103	A legacy customer-payment instruction between institutions.	That the beneficiary’s account was credited.
pacs.008	The ISO 20022 customer-credit-transfer instruction now normally exchanged for these Swift payments.	That processing at the receiving institution is complete.
UETR	A 36-character reference used to track a payment across institutions.	The payment’s outcome without a status check.
Tracker outcome	A reported status, such as credited, rejected, held or transferred outside Swift.	That a separate PDF instruction is itself proof of credit.

Swift’s Universal Confirmations concern institutions reporting outcomes to its payment Tracker. That reporting is not the same thing as producing an MT103 PDF. Ask the institution handling your transfer for the current status if you need to know what happened after the instruction was sent.

Where can you find an MT103 or equivalent confirmation?

Start with the sending bank or transfer provider. Check its transfer details, receipt or downloadable documents for a Swift confirmation, pacs.008 or MT103 copy, UETR, and transaction reference. The label and available document depend on the provider and the route used. A provider’s “complete” status may mean it has sent money onward rather than that the receiving bank has finished processing it.

If you are the recipient, ask the sender to request the confirmation and current tracking status from the sending institution. Then give the receiving bank the UETR or available reference, along with the sender’s name, expected currency and other details the bank requests. Institution-provided tracking is more useful than treating a screenshot as proof of final credit. Share documents containing personal or account information only through channels you trust.

When do you need one—and when do you not?

A payment instruction or tracking reference is useful when a bank transfer appears missing, the beneficiary bank asks for trace details, or the sender and recipient need to reconcile a specific payment. It can help identify which transfer to investigate. If you need evidence that money was received, ask for the latest outcome from the relevant institution or check the recipient’s account records; an MT103 alone does not establish receipt.

You do not need an MT103 for every international payment. A transfer using a local bank payout, mobile wallet or cash pickup may not produce a customer-facing MT103 at all. Even for a Swift-routed payment, an institution may provide a pacs.008 record or another confirmation instead. If the recipient can already identify the credit and no one requires additional documentation, requesting a legacy message copy may add little.

Common mistakes and what happens if details are wrong

Calling the instruction proof of arrival: a message copy shows payment information, not necessarily final beneficiary credit. Request the current outcome if receipt is disputed.
Confusing references: the field :20: sender reference and the UETR serve different purposes. Give the bank both if available, and copy each exactly.
Searching only for the expected description: a recipient may see a different sender name, reference, currency or amount in their account records. Ask the receiving institution to check using the available trace details.
Entering incorrect recipient details: an incorrect account or payout detail can lead to rejection or return. Contact the sending provider promptly; do not assume that changing a PDF or sending a corrected screenshot changes an instruction already in process.
Assuming every held payment needs a new MT103: a payment can require further review, be rejected or be blocked under applicable sanctions rules. A document cannot override those checks. Ask the provider what action, if any, is required.

Check names and account or payout details against the recipient’s real information before confirming a transfer. If something is wrong after submission, tell the provider exactly what needs correction and follow its instructions rather than submitting an unrelated replacement payment without understanding the first payment’s status.

How to use confirmation details with Coinepay Global Remittance

Set up your account. Register with Coinepay and complete any required identity verification. Transfers are subject to sanctions screening and local regulations; Coinepay may ask for documents explaining the purpose or source of funds.
Enter the real recipient and payout details. Coinepay supports bank account deposits, mobile wallets and cash pickup. Choose the available method for the destination and review the details carefully. The exchange rate and fees are shown in the app before you confirm the transfer.
Follow the transfer status. Use the Coinepay self-service dashboard or mobile app to check its tracking information. If the recipient cannot locate the money, collect the Coinepay transfer reference and the status shown.
Ask for the right tracing information. Contact Coinepay support with the transfer reference and explain what the receiving institution needs. Ask whether that particular transfer has a Swift instruction copy, UETR or another confirmation available. Do not assume a bank deposit, wallet payout or cash pickup will have an MT103.

Coinepay can send transfers to countries and regions except those under comprehensive sanctions, and it does not serve sanctioned persons. If a transfer is under review, provide requested information through Coinepay’s official channels. A confirmation document is a tool for identifying and tracing a payment—not a way to bypass payment checks or guarantee its final outcome.

Get your Coinepay virtual card: Sign up · App Store · Google Play · Customer support

FAQ

Does an MT103 prove the recipient was paid?

No. It is a payment instruction, not proof that the beneficiary’s account was credited. Ask the relevant institution for the current payment outcome.

What should I ask for if a bank requests an MT103 today?

Ask the sending institution for its available Swift instruction or transfer confirmation, the UETR if available, and the current tracking status. It may provide a pacs.008 record instead.

Where is the UETR on an MT103?

It appears in header field 121 of an MT103. A customer-facing confirmation may show it elsewhere or omit it, so ask the sending institution.

Will my Coinepay transfer have an MT103?

Not necessarily. The available confirmation depends on the transfer route and payout method. Check your transfer status and ask Coinepay support what tracing details are available.

MT103 Payment Confirmation: What It Is and How to Use It