SWIFT Payment Tracker
Find the UETR of your international payment, read its gpi status, and ask your bank to trace it.
Live payment status is held by the banks, and this page cannot see it. It is not connected to the Swift network and it queries nothing. What it does is the work that comes before and after a trace: it finds and checks your UETR, the unique reference that follows a payment from bank to bank, explains the status and reason codes that banks report through the Swift gpi tracker, and writes the trace request that you send to your bank. It all runs in your browser.
1. Find and Check Your UETR
2. Read a Status
3. Write a Trace Request
Fill in what you know. The request is written in your browser, and you copy it into an e-mail or your bank's message service. Leave out what you do not know.
Your request
Swift gpi Statuses
The tracker reports one of three statuses for a payment.
| Status | Name | What it means | What to do |
|---|---|---|---|
| ACSP | Accepted, settlement in process | The payment passed the checks and is on its way. It has not been credited to the beneficiary yet. | Nothing is wrong yet. Look at the reason code, if there is one, to see where it is. |
| ACCC | Accepted, credit settlement completed | The money has been credited to the beneficiary's account. | The payment is complete. If the beneficiary cannot see it, ask their bank to check the account, using the UETR. |
| RJCT | Rejected | The payment or the transaction was rejected. | Ask your bank for the reason code, and what has happened to the money. Correct the cause before you send the payment again. |
Reason Codes for a Payment in Progress
With ACSP the tracker may add a code starting with G. It says where the payment is, and it is not a rejection.
| Code | What it means | What to do |
|---|---|---|
| G000PaymentTransferredAndSLAMaintained | The bank that reported passed the payment to the next bank, or to a market infrastructure, and the service obligations are being kept. | The payment is moving normally. No action is needed. |
| G001PaymentTransferredAndSLANoLongerMaintained | The payment was passed on to a bank that is not on gpi, or to an infrastructure where the service obligations may no longer be guaranteed. | Later updates may not appear. If the payment is late, ask your bank to trace it with the bank that has it. |
| G002CreditDebitNotConfirmed | The credit is pending and cannot be completed the same day. | This is not a rejection. If it stays like this for longer than you expected, ask your bank to trace the payment. |
| G003CreditPendingDocuments | The credit to the beneficiary is pending, because the bank has asked the beneficiary for documents. | Ask the beneficiary to contact their bank and give the documents that it asks for. |
| G004CreditPendingFunds | The credit is pending, because the bank is waiting for the funds, which come by a cover payment. | Ask your bank to confirm that the cover payment has been sent, and to trace it. |
Reason Codes for a Rejected Payment
With RJCT the tracker gives the reason for the rejection.
| Code | What it means | What to do |
|---|---|---|
| AC01IncorrectAccountNumber | The account number is invalid or missing. | Check the account number or IBAN with the beneficiary, and correct it before you resend. |
| AC04ClosedAccountNumber | The account has been closed at the beneficiary's bank. | Ask the beneficiary for the details of an account that is open. |
| AC06BlockedAccount | The account is blocked, so no transaction can be posted to it. | The beneficiary needs to ask their bank why the account is blocked. |
| BE01InconsistentWithEndCustomer | The identification of the end customer is not consistent with the account number. | Check that the beneficiary's name is exactly as it is on the account, and that the account number belongs to that person. |
| NOASNoAnswerFromCustomer | The bank failed to contact the beneficiary. | Ask the beneficiary to contact their bank, and give the bank a way to reach them. |
| RR03MissingCreditorNameOrAddress | The creditor's name or address, which is needed for regulatory requirements, is insufficient or missing. | Add the beneficiary's full name and address to the payment. |
| FF07InvalidPurpose | The purpose of the payment is missing or invalid. | Give the purpose of the payment, as your bank asks, and resend. |
| RC01BankIdentifierIncorrect | The bank identifier code in the message has an incorrect format. | Check the beneficiary bank's BIC, for example on our SWIFT code checker. |
| RC08InvalidClearingSystemMemberIdentifier | The routing code is not valid for the local clearing system. | Check the routing or bank code of the beneficiary bank. |
| FOCRFollowingCancellationRequest | The payment was returned following a cancellation request. | The payment was cancelled at a request. Ask your bank who made the request, and when the funds will be back. |
| DUPLDuplication | The payment is a duplicate of another payment. | Check whether the first payment went through before you send it again. |
| RR05RegulatoryInformationInvalid | Regulatory or central bank reporting information is missing, incomplete or invalid. | Ask your bank which information is needed, and add it. |
| AM06AmountTooLow | The amount is below the limit. | Ask your bank about the minimum amount, and send a larger payment if you can. |
| CUSTRequestedByCustomer | The payment was rejected at the request of the creditor. | Ask the beneficiary why they asked for the payment to be rejected. |
| MS03NotSpecifiedReasonAgentGenerated | A bank rejected the payment and gave no reason. | Ask your bank to ask the rejecting bank for the reason. |
Go Deeper
What a UETR Is
The UETR is the Unique End-to-End Transaction Reference of a payment. In the pacs.008 message it is a universally unique identifier that gives the payment an end-to-end reference, and its format is a version 4 UUID. It is made when the payment is created, and it is meant to stay the same as the payment passes from bank to bank, which is what lets each bank, and the tracker, recognise it.
The characters are the digits 0 to 9 and the letters a to f in lower case, in groups of 8, 4, 4, 4 and 12 with hyphens between them: 36 characters in all. The first character of the third group is always 4, and the first of the fourth group is always 8, 9, a or b. The example above is made up.
Where to Find It
In a Swift MT message the UETR is field 121 in block 3, the user header, for example {3:{111:001}{121:5f4dcc3b-5aa7-459f-8914-e776856789ef}}. In a pacs.008 message it is the element PmtId/UETR. Your bank's payment confirmation or your online banking may show it, and your bank can give it to you. The finder above reads it from a pasted MT message, a pacs.008 or any text.
How the Tracking Works
Each bank on a payment's route passes it on with the same UETR and reports its status against that UETR. Banks that use gpi send confirmations that carry the UETR back to the tracker, and match them to the original payment by it. What the tracker reports is one of the statuses in the first table above, with a reason code where there is one. Some payment providers return these statuses to their customers through their own systems, for example StoneX and Convera, which publish the tables that this page uses. This page has no lookup. To see the live status, ask your bank.
When a Payment Is Late
- Get the UETR from your bank, or from the confirmation of the payment, and check it in tool 1.
- Ask your bank for the current gpi status, the reason code and the date of the last update.
- Read the code in tool 2. A G002, G003 or G004 says why the credit is pending, and a rejection code says what to correct.
- If your bank has nothing more, send the trace request from tool 3.
- Check the details with the beneficiary: the IBAN on our IBAN validator, and the bank's BIC on our SWIFT code checker.
The page gives no time by which a payment should arrive. How long a payment takes depends on the banks, the currencies and the route, and your bank can tell you what to expect for yours.
What This Page Uses
The status and reason codes are those on which two published gpi status tables agree, from StoneX and Convera, and the codes G000 to G004 are also in Oracle's cross-border payments guide, which also shows the UETR in field 121 of block 3. The wording of what each code means and what to do is ours. The UETR format and its definition are from the Payments Canada pacs.008 usage guideline. Codes that the tables list and that are not here, for example the X codes for errors in status updates, are left out, because they matter to banks and not to a payer. We last checked on 20 September 2026.
Frequently Asked Questions
Can this page track my SWIFT payment?
No. It is not connected to the Swift network, and it queries nothing. The live status of a payment is held by the banks that handle it. The page helps you find and check the UETR, understand the status and reason codes your bank gives you, and write a trace request.
What is a UETR?
The Unique End-to-End Transaction Reference: a version 4 UUID that gives a payment an end-to-end reference. It looks like 5f4dcc3b-5aa7-459f-8914-e776856789ef, with 36 characters in groups of 8, 4, 4, 4 and 12. It is meant to stay the same as the payment passes from bank to bank.
Where do I find my UETR?
In a Swift MT message it is field 121 in block 3. In a pacs.008 message it is the element PmtId/UETR. Your bank's confirmation of the payment or your online banking may show it, and your bank can give it to you. Paste an MT103, a pacs.008 or any text into the finder, and the page picks it out.
What do ACSP, ACCC and RJCT mean?
ACSP is accepted, settlement in process: the payment is on its way and is not yet credited. ACCC is accepted, credit settlement completed: the money is credited to the beneficiary's account. RJCT is rejected.
What does G002 mean? Is my payment rejected?
No. G002 comes with ACSP, so the payment is still in progress. It means that the credit is pending and cannot be completed the same day. If it stays like this longer than you expected, ask your bank to trace the payment.
What do G000, G001, G003 and G004 mean?
All come with ACSP. G000: passed to the next bank and the service obligations are kept. G001: passed to a bank not on gpi, where they may no longer be guaranteed. G003: the credit is pending because the bank has asked the beneficiary for documents. G004: the credit is pending because the bank is waiting for the funds, which come by a cover payment.
Why does my payment stay at ACSP?
ACSP means the payment is not credited yet, and the reason code says why. G002, G003 and G004 each give a cause you can act on. This page gives no time by which a payment should arrive, because that depends on the banks, the currencies and the route. Ask your bank what to expect for yours.
What happens to my money if a payment is rejected?
The status tables do not say, and this page cannot tell you. Ask your bank for the reason code, and where the funds are. Correct the cause, for example a wrong account number (AC01) or a missing name and address (RR03), before you send the payment again.
Is the UETR the same as the end-to-end reference or the sender's reference?
No. A pacs.008 also has an end-to-end identification (EndToEndId), and an MT103 has the sender's reference in field 20. The UETR is a separate element, and it is the one the tracker uses.
Why does the page say my UETR is not valid?
A UETR must be a version 4 UUID: 32 hexadecimal characters in groups of 8, 4, 4, 4 and 12, with 4 as the first character of the third group and 8, 9, a or b as the first of the fourth. A UUID of another version, or with a mistyped character, fails. Ask your bank for the UETR again.
Do I need to send the trace request by e-mail?
That is up to your bank. The request is plain text, and you can copy it into an e-mail, your online banking's message service or a form. Nothing is sent from this page.
What does the ISO 20022 Message Decoder have to do with this?
A pacs.008 payment message contains the UETR, and a pacs.002 message carries the status. Our ISO 20022 Message Decoder reads those messages element by element.
How current are the codes?
They are the codes on which the StoneX and Convera gpi status tables agree, checked on 20 September 2026. The tables list more codes, such as the X codes for errors in status updates, and we left those out because they matter to banks and not to a payer.
Is anything I type stored or sent?
No. Everything runs in your browser. Nothing you paste or type is stored or sent.
