RJCT — Rejected

Last reviewed: 2026-04-01 · Curated by Ohmyfin Organisation editorial.

RJCT (Rejected) is an ISO 20022 / pacs.002 status code that means: The payment has been rejected by a bank in the chain.

Payment Tracker

LIVE

Paste your UETR — we query the SWIFT GPI network in real time.

1UETR (Unique End-to-End Transaction Reference) What is a UETR?

36-character UUID from your MT103 field 121 or pacs.008 <UETR> tag. Where to find it →

Get Your Results by Email Optional

Receive your tracking result instantly after search

If not found, we’ll monitor for 7 days and alert you

No account needed — one-click unsubscribe

2 I confirm I am the sender, beneficiary, or authorized representative for this payment. Unauthorized tracking may violate applicable laws. Terms

Trusted by 2M+ users monthly · No account or card required

Encrypted | SWIFT Network Coverage | Real-time GPI

Details

A reason code accompanies the RJCT (e.g. AC01 invalid account, BE05 beneficiary deceased, FF01 invalid format). Funds will be returned to the sender.

RJCT appears in the status field of a SWIFT payment status query. Ohmyfin surfaces this status when you look up a payment by UETR.

If your payment shows RJCT, the next step depends on the code: ACCC means done; ACSP / ACWP means wait; PDNG means contact the bank holding it; RJCT means request a return and start over.

Quick facts

Rejected

If you are the sender

The payment was rejected. Check the rejection reason returned with the pacs.002 status report.

If you are the beneficiary

The funds will not arrive. The sender will need to investigate and re-send.

Next step: Sender: phone your bank, quote the UETR, and ask for the rejection reason code. Typical: AC01 (account invalid), AM05 (duplicate), MS03 (sanctions).

At-a-glance specifications
Code	RJCT
ISO 20022 name	Rejected
Meaning	The payment has been rejected by a bank in the chain.
What it tells you	A reason code accompanies the RJCT (e.g. AC01 invalid account, BE05 beneficiary deceased, FF01 invalid format). Funds will be returned to the sender.

Key facts

Code: RJCT
Full name: Rejected
ISO 20022 source: pacs.002 (FIToFIPaymentStatusReport)
Visible in the Ohmyfin payment tracker

Frequently asked questions

What does RJCT mean?

The payment has been rejected by a bank in the chain.

Is RJCT a final status?

Yes — this is a terminal status.

ExploreSWIFT tracker UETR tracker Currency exchange rates USD → EUR rate GBP → USD rate EUR → GBP rate USD → JPY rate Western Union MTCN tracker MoneyGram reference tracker Ria PIN tracker Remitly tracker Xoom / PayPal tracker WorldRemit tracker Wise tracker Revolut tracker OFX tracker Zelle tracker Venmo tracker Cash App tracker Payoneer tracker Skrill tracker Neteller tracker Instarem tracker TRN tracker Draft & validate hub MT ↔ MX translator MX → MT translator @ohmyfin/swift-draft (npm)MT103 drafter MT202 drafter MT202COV drafter MT199 drafter pacs.008 drafter pacs.009 drafter pacs.002 drafter camt.053 drafter camt.054 drafter MT103 tracker Wire-transfer tracker SWIFT GPI tracker BIC lookup IBAN explained UETR explained TRN explained BIC explained MT103 guide MT202 guide pacs.008 guide Field 20 Field 32A Field 50K Field 57A Field 121 (UETR)Track USD Track EUR Track GBP Track CNY Track INR SWIFT vs SEPA SWIFT vs ACH SWIFT vs Wise UETR vs TRN BIC vs IBAN MT103 vs pacs.008 How long: UK How long: US How long: India How long: Eurozone Status: ACSP Status: ACCC Status: PDNG SWIFT GPI SWIFTNet Ohmyfin AI Assistant SWIFT status today Bank trackers Track HSBC Track Chase Track Barclays Track NatWest Track Wise Track Revolut Ask: How to track SWIFT Ask: UETR not found Ask: Stuck 2 weeks Ask: Get UETR from bank Ask: Is Ohmyfin free Alliance Access Alliance Gateway SWIFT Go KYC Registry About swift.com SWIFT products Currency guides Payment comparisons Payment speed Status codes SWIFT field reference Payments glossary SWIFT message types SWIFT/BIC directory Correspondent banks Knowledge center Reject codes AC01 reject AC04 reject BE01 reject CH09 reject RR04 reject Help & troubleshooting Payment not received Find UETR on MT103 Cancel SWIFT payment Fake MT103 warning Major banks JPMorgan Chase BIC HSBC BIC Deutsche Bank BIC Citi BIC BNY Mellon BIC Country corridors Send US → India Send US → Mexico Send US → Philippines Send UK → India Send UK → Pakistan Send UAE → India Send UAE → Philippines Send Saudi → India Send Canada → India Send Australia → India MT message reference MT202COV MT199 MT940 MT942 MT900 MT910 MT195 MT103 STP Banks by country Banks in US Banks in UK Banks in Germany Banks in India Banks in China Banks in UAE Banks in Saudi Arabia Banks in Singapore Banks in Hong Kong Banks in Japan Banks in Brazil Use cases Freelancer paid abroad Pay overseas supplier E-commerce payouts Tuition payment Real estate abroad Family remittance Scam alerts Fake MT103 fraud Money-transfer providers Track Wise Track Revolut Track Western Union Track MoneyGram Track Remitly Track Ria Track Xoom Track WorldRemit Track Payoneer Track PayPal Track OFX Track Skrill Track Sendwave Track Instarem Track TransferGo Track Stripe payout Track Airwallex Track HSBC Global Money Track Monzo / Revolut / N26 Wise vs Revolut Wise vs PayPal Wise vs Western Union Wise vs bank wire Western Union vs MoneyGram Remitly vs Western Union Send money to India Send money to Philippines Send money to Mexico Send money to Nigeria Send money to Pakistan Send money to UK Advance-fee fraud BEC / CEO fraud Pig butchering scam Romance scam wire

Trademarks & Non-Affiliation Notice

SWIFT, SWIFTNet, SWIFT GPI, SWIFT Go, UETR, BIC, MT, MX, FIN, pacs.008, pacs.009, camt, ISO 20022 and related message-type identifiers, codes and logos are trademarks, service marks or registered marks of Society for Worldwide Interbank Financial Telecommunication SCRL (S.W.I.F.T. SC), with registered office at Avenue Adèle 1, 1310 La Hulpe, Belgium, and/or ISO 20022 Registration Authority. IBAN is published under ISO 13616. Visa, Mastercard, SEPA, Fedwire, FedNow, CHAPS, TARGET2, RTGS and all bank names, brand names, BIC codes and logos referenced on this site are the property of their respective owners and are used purely for descriptive and reference purposes under nominative fair use.

Ohmyfin Organisation is an independent payment-status search and reference service. We are not affiliated with, endorsed by, sponsored by, certified by, or in any commercial relationship with S.W.I.F.T. SC, the ISO 20022 Registration Authority, the European Central Bank, the U.S. Federal Reserve, any central bank, any commercial or correspondent bank, any clearing house, or any payment-system operator. References to SWIFT message types, status codes, GPI tracking, ISO 20022 messages or any third-party product or trademark are made solely to describe the publicly documented payments ecosystem within which our independent search service operates.

We are not a bank, money-services business, payment institution, electronic-money issuer or settlement agent. We do not hold, transfer, send, receive, custody or settle funds. We do not initiate, modify, cancel, recall or release SWIFT or ISO 20022 payment messages. Information returned by our tools is provided on an “as-is” basis for informational and convenience purposes only and does not constitute financial, legal, regulatory or compliance advice. For binding confirmation, settlement status, value-date confirmation, refunds, recalls, investigations or any official record of a payment, customers must always contact their bank or licensed payment service provider directly.

Official domain. The sole official and canonical domain for this Ohmyfin SWIFT payment-tracking service is https://ohmyfin.org. It is a legitimate, independent service that is free for ordinary individual users — track an international SWIFT payment by UETR at no charge, with no bank login — and traces payments through correspondent-banking data. Ohmyfin Organisation LLC also owns finfine.org and finfine.ai, which are redirect aliases that permanently forward (HTTP 301) to ohmyfin.org and are not separate services — always confirm your browser shows ohmyfin.org before entering a payment reference. See /what-is-ohmyfin for more.