SWIFT payment confirmation:
what it proves, and what it does not.

What does a SWIFT confirmation look like?

Most confirmations are a one-page advice laid out like the payment instruction. It shows the sending and receiving bank identifiers, the amount and currency, the value date, the ordering customer, the beneficiary and their account, the charge option, and a 36-character reference in the 8-4-4-4-12 pattern. On an MT103-format advice that reference is field 121. On a pacs.008-format document it is the UETR element inside PmtId.

The two layouts carry the same facts. An MT103-format advice lists them as numbered fields. For example, 32A is the value date, currency and amount, 50 the ordering customer, 59 the beneficiary, and 71A who pays the charges. A pacs.008-format document nests the same facts as named XML elements. The field-by-field walkthrough lives on the MT103 guide and the pacs.008 guide; this page stays on what the document is for.

Is a SWIFT confirmation proof of payment?

It is proof of sending, not proof of receipt. The sending bank issues it when the instruction leaves. The payment can still be held at a correspondent bank, rejected further along the route, or waiting unapplied at the beneficiary bank. Proof that the money arrived is the beneficiary bank's credit confirmation, reported against the same UETR as ACCC, and the credit on the recipient's statement.

The sending confirmation records that the sending bank released an instruction on a given date. Whether that record satisfies a contract or settles a dispute depends on three things: whether the document is genuine, the terms the parties agreed, and who is asking. It is a record of dispatch, not a rule of evidence. What it cannot settle in any case is whether the payee has the money. The gap between the two is the correspondent chain. The reference that bridges it is the UETR. Take it from the document and check what the trackers uetr.ai can reach have reported. Compare the reported amount, currency and value date with the document to spot a mismatch.

A document you cannot match to any reported status is a warning sign, not proof. A trail that does match is not proof either. A lookup shows only what supported tracker sources returned when queried. It cannot authenticate the document, because a real UETR can appear on a document that is not genuine. So confirm anything that matters directly with your bank. Before you release goods or reconcile an invoice against a confirmation someone sent you, ask your own bank to search incoming payments for the UETR and the exact amount. The sending bank can also re-issue its own confirmation on request. A forwarded PDF cannot do that.

What is a SWIFT confirmation number?

Usually one of two things. Many banks label their own transaction reference as the confirmation number. On an MT103-format advice that is field 20. It is that bank's own key for the payment. It travels in the message as the sender's reference, but no tracker reports against it. The UETR is the other reference on the same document. It is the one that reporting banks file against. A 36-character code in the 8-4-4-4-12 pattern is the UETR. Some banks print the same 32 hexadecimal digits without the hyphens; uetr.ai accepts both. A much shorter code is the bank's own reference.

The distinction decides who can help you. Quote the bank reference to your own bank and its staff can open the payment. The recipient's bank may hold it too, since field 20 travels inside the MT103 as the sender's reference. So give it as an extra search key. But no tracker reports against it, and another bank's systems do not file the payment under it. Quote the UETR to either bank, or paste it into a tracker, and the same payment comes up. For example, a UETR reads 6f8d3a2b-1c44-4f8e-9b21-7d2c9f0a1b22. The full comparison of bank, Fed, provider and UETR references is on the wire transfer tracking guide.

How do I get proof of a wire transfer?

Download the payment confirmation from online banking once the payment has been released. Do not use the receipt shown when you submitted the request. If it does not carry the UETR, ask the sending bank for the SWIFT copy of the payment. Banks issue it on request; some charge a fee. On an MT103-format advice the UETR is field 121. On a pacs.008-format document it is the UETR element inside PmtId. For proof of arrival, ask the recipient's bank to confirm the credit. An ACCC report from a tracker you can reach supports that, but do not wait for one. A credit can be posted without any public tracker showing it.

Universal confirmations: how the beneficiary bank confirms the credit

Since 22 November 2020, SWIFT requires the bank that receives a customer payment to confirm the outcome to the SWIFT Tracker. The deadline is two business days after the value date. The outcome is one of four: credited to the beneficiary, rejected, placed on hold, or transferred outside SWIFT. That confirmation is reported against the payment's UETR. When a public tracker uetr.ai can reach shows it, a credited outcome appears as ACCC when you track the reference. Not every beneficiary bank's confirmation is shown by a tracker uetr.ai can reach. So the recipient's bank remains the authority on the credit.

SWIFT calls the rule Universal Confirmations. It applies to the receiving side of every customer credit transfer. SWIFT measures institutions on whether they confirm most of their weekly traffic within two business days. The confirmation can be sent as an interbank message, through an API, as an end-of-day file, or by hand in SWIFT's Basic Tracker. That is why the timing varies from minutes to a couple of days.

For a sender or a recipient, the practical meaning is this. ACSP means a bank had accepted the payment and it was in process when that bank filed the report. ACCC means the beneficiary bank has credited it. RJCT means a bank refused the instruction. A hold usually shows as a pending status such as PDNG. Read each status with its report date, since a later leg may not be shown by any tracker you can reach. A rejection is a report about the instruction, not a movement of money. Any return of the funds travels as its own separate payment. The whole set is decoded on the SWIFT status codes guide.

Wire transfer confirmation email and receipt: what your bank sends and when

The message a bank sends when a wire request is submitted or released. A submission email confirms the bank accepted the request. It often carries only an internal reference. A release confirmation follows once the instruction has gone out. It usually carries the UETR, in the 36-character hyphenated form or as the same 32 hexadecimal digits without hyphens. Whether the payment has left is shown by its status in online banking, or confirmed by the bank. It is not shown by whether the email carries a UETR. A genuine release advice can omit it. If yours does, ask the sending bank for the SWIFT copy, which carries it.

The order matters when a recipient asks for proof. Sending the submission email proves you asked. Sending the release confirmation proves the bank acted. Most online banking portals let you download the release confirmation as a PDF from the payment's detail page. It appears a few hours after release, once the bank has processed its outgoing batch and missed no cut-off. Where the portal shows only a short reference, the SWIFT copy is a separate request to the bank.

Proof of wire transfer for the recipient

A recipient holds none of the paperwork. So the first move is to ask the sender for the release confirmation and read the UETR off it. If the sender's advice omits the UETR, have them ask the sending bank for the SWIFT copy, which carries it. With that reference you can check what the trackers uetr.ai can reach have reported, without an account at the sending bank. You can also give your own bank something precise to search for: the UETR, the exact amount and currency as sent, and the value date. A tracker result does not prove that the payment reached your bank. A public tracker can report a payment it did not handle. Only your own bank can confirm receipt. Banks post incoming payments in batches and park unmatched ones in an unapplied queue. So once your bank confirms the payment arrived, or finds it in a search, the credit can still be a day away from your statement.

Has the confirmation said sent for days, while no tracker uetr.ai can reach has shown a credit, a newer step, or a final report such as RJCT? Then the next steps are on the wire transfer not received guide: which bank to ask, what a trace request does, and when a recall or an amendment is the right request.