What does ACSC mean in SWIFT GPI?

ACSC (AcceptedSettlementCompleted) means the payment has been fully settled and credited to the beneficiary's account. This is the final successful status — the funds have arrived.

What does ACSP mean in SWIFT GPI?

ACSP (AcceptedSettlementInProcess) means the payment has been accepted by the beneficiary bank and settlement is in progress. The funds are being processed but have not yet been credited to the final account.

What does ACWP mean in SWIFT GPI?

ACWP (AcceptedWithoutPosting) means the payment has been accepted but will not be posted to the beneficiary's account — for example when the funds are being held for compliance checks or the account is blocked.

What does ACCP mean in SWIFT GPI?

ACCP (AcceptedCustomerProfile) means the payment instruction has been accepted and is compliant with the receiving institution's rules and the customer's profile. It is an intermediate confirmation that processing is continuing normally.

What does RJCT mean in SWIFT GPI?

RJCT (Rejected) means the payment has been rejected by a bank in the correspondent chain. A rejection code is usually included. Common reasons include sanctions screening, invalid account details, or compliance failures. Contact your originating bank immediately for a resolution.

What does PDNG mean in SWIFT GPI?

PDNG (Pending) means the payment is awaiting processing at a bank in the chain. This is often caused by a cut-off time being missed, a bank holiday, or a compliance hold. The payment has not failed — it is queued.

What does PART mean in SWIFT GPI?

PART (PartiallyAccepted) means the payment instruction has been partially accepted. This can occur when only a portion of the funds has been credited, or when a batch payment is split across multiple transactions.

What does CANC mean in SWIFT GPI?

CANC (Cancelled) means the payment has been cancelled. This may have been initiated by the originating bank, the beneficiary bank, or as the result of a compliance or fraud check. Contact your bank for the specific reason.

What does ACWC mean in SWIFT GPI?

ACWC (AcceptedWithChange) means the payment has been accepted but with a modification — for example the value date or the amount was altered by a bank in the chain during processing.

What does XTND mean in SWIFT GPI?

XTND (Extended) means the payment processing deadline has been extended. A bank in the chain requires more time to complete the transaction — for example because of compliance review or correspondent bank delays.

SWIFT Status Codes: ACCC, ACSP, RJCT Explained

SWIFT GPI and ISO 20022 payments communicate their state using a small set of standardised codes defined in the pacs.002 message (Payment Status Report). Every bank in the payment chain updates the status as they process or forward the funds. Ohmyfin reads these codes and translates them into plain English for you.

Main GPI / ISO 20022 Status Codes pacs.002 TxSts

These are the top-level codes that describe the overall state of a payment. Every cross-border wire will pass through one or more of these on its way to the beneficiary.

Code	Full ISO Name	What it means	Final?
ACCC	AcceptedSettlementCompletedCreditor	The beneficiary's account has been credited. This is the final success status — the money has arrived.	Yes ✓
ACSC	AcceptedSettlementCompleted	Settlement is complete between agents, but the beneficiary bank has not yet credited the customer account. Expect ACCC shortly.	Near
ACSP	AcceptedSettlementInProcess	The payment has been accepted by a bank in the chain and settlement is underway. Funds are moving between correspondent banks.	No
ACWP	AcceptedWithoutPosting	The bank accepted the payment but has not posted it to the beneficiary account yet. Common during after-hours, FX conversion, or internal processing queues.	No
ACWC	AcceptedWithChange	Accepted, but a change was applied — typically a fee deduction, currency conversion, or field correction by the bank. Check the accompanying detail code.	No
ACCP	AcceptedCustomerProfile	An initial validation of the beneficiary profile passed. This is an early pre-settlement status — real settlement still needs to happen.	No
ACFC	AcceptedFundsChecked	The payer's funds have been verified as available. A pre-authorisation step used by some originating banks before submitting to the network.	No
ACIS	AcceptedAndIntegrityCheckSucceeded	The message passed all format and integrity checks at the receiving bank. Processing continues.	No
PDNG	Pending	The payment is paused, waiting for further action. A sub-reason code (e.g. AWMD, AWMR) explains why — compliance review, missing docs, or queued past cut-off.	No
RJCT	Rejected	A bank in the chain rejected the payment. Always accompanied by an ISO 20022 reason code (see table below) explaining exactly why. Funds will be returned to the sender.	Yes ✗
CANC	Cancelled	The payment was cancelled before settlement completed — usually because the sender (or a bank acting on their behalf) issued an MT n92 / camt.056 recall message.	Yes ✗
FOCR	FollowingCancellationRequest	A return of funds was initiated following a cancellation/recall request. The sending bank will receive the money back.	Yes ✗
BLCK	Blocked	The beneficiary account is blocked (frozen by the beneficiary bank, usually for compliance or legal reasons). The payment cannot be credited.	Yes ✗
PNDG	PendingDelivery	Variant of PDNG used by some banks to indicate the instruction has been received but delivery to the next agent is pending — e.g. waiting for a correspondent window to open.	No
RCVD	Received	The payment instruction has been received by the bank and queued for processing. No settlement action has taken place yet.	No
PART	PartiallyAccepted	Used in bulk file processing — some transactions in a batch were accepted and some were not. Rarely seen in single wire tracking.	No
NMAS	NotMatchingASide	The payment doesn't match an expected counterpart or mandate. Typically a bank-internal validation failure that surfaces on an FX or PvP trade.	Yes ✗

SWIFT GPI Sub-Codes ACSP/Gxxx

When a GPI member bank reports ACSP, it can append one of these sub-codes to give more granular detail about what stage the payment is at.

Sub-Code	Meaning	What to do
ACSP/G000	The payment was forwarded to the next GPI-member correspondent bank.	Normal progress — the next bank will post its own status update soon.
ACSP/G001	The payment was forwarded to a bank that is not a GPI member.	GPI tracking ends here. Contact your bank for further updates once it leaves the GPI network.
ACSP/G002	Credit is pending and may not occur today. The bank has accepted the payment but has not yet posted it — often a manual review queue.	Wait 1 business day. If no ACCC update appears, contact your bank to request an investigation.
ACSP/G003	The bank is waiting for documents (e.g. purpose declaration, invoice, beneficiary ID) before crediting the account.	The beneficiary bank typically contacts the beneficiary for the required documentation.
ACSP/G004	The payment is waiting for the cover (nostro) funds to arrive before it can be credited.	Normal in correspondent-bank chains. The MT202 COV / pacs.009 cover should settle within the same day.
ACSP/G001/RETN	The payment has left the GPI network and a return has been initiated by the non-GPI bank.	Funds are coming back. Expect them in your account within 1–5 business days depending on the non-GPI bank.

PDNG Reason Codes Why is my payment pending?

When a payment shows PDNG, a reason code should accompany it. These are the most common ones.

Code	Name	Explanation
AWMD	AwaitingMandatoryDocumentation	The bank is waiting for a mandatory document — typically a purpose declaration, invoice, or KYC form — before it can release the payment.
AWMR	AwaitingManualReview	A compliance officer or AML analyst is reviewing the payment manually. Common for large amounts, new beneficiaries, or high-risk corridors.
INDM	IndemnityRequested	The bank requires an indemnity letter before processing — e.g. if beneficiary account details are ambiguous.
LEGL	LegalReasonPending	A legal hold has been placed on the payment — court order, sanctions investigation, or regulatory freeze.
AUTH	AwaitingAuthorisation	The payment is awaiting internal authorisation at the bank — a second approver, a limits breach approval, or a compliance sign-off.
CUST	AwaitingCustomerInstruction	The bank needs additional instructions from the ordering customer — e.g. clarification of beneficiary details or payment purpose.
INTL	InternalProcessing	The bank's own internal systems are processing the payment — netting, end-of-day batch, or internal accounting. Expected to clear shortly.
WAIT	WaitingForSettlementWindow	The payment has been queued because the relevant settlement system (e.g. RTGS, CHAPS, TARGET2) is not currently open. Will release at next window open.

ISO 20022 Rejection & Return Reason Codes Accompanies RJCT

Every RJCT (rejected) status carries one of these reason codes. It tells you exactly why the bank rejected the payment and — critically — whether you need to resend or whether the funds will come back automatically.

Account & Creditor Issues (AC / BE)

Code	Name	Explanation	Action
AC01	IncorrectAccountNumber	The account number (IBAN or BBAN) is structurally invalid or does not exist at the receiving bank.	Correct the account number and resend.
AC03	InvalidCreditorAccountNumber	The format of the creditor account number doesn't comply with the local clearing rules.	Verify IBAN/BBAN format for the destination country.
AC04	ClosedAccountNumber	The account exists but has been closed. Funds cannot be credited.	Obtain a new account number from the beneficiary.
AC06	BlockedAccount	The account is frozen — by a court order, sanctions enforcement, or the bank's own risk controls.	The beneficiary must resolve the block with their bank.
AC13	InvalidDebtorAccountType	The debtor's account type (e.g. savings vs. current) is not eligible for this type of payment.	Use an eligible account type.
AC14	InvalidCreditorAccountType	The beneficiary account type cannot receive this payment — e.g. a savings account not eligible for international transfers.	Ask beneficiary to provide a different account.
BE01	InconsistentWithEndCustomer	The name on the payment doesn't match the name on the account. Common with stricter name-matching banks (UK, NL, etc.).	Correct the beneficiary name to exactly match their account.
BE04	MissingCreditorAddress	A beneficiary address is required for this payment type (e.g. US wire to certain banks) but was not provided.	Add the beneficiary's full address to the payment.
BE05	UnrecognisedInitiatingParty	The originator bank is unknown to the beneficiary bank, or the originator is not licensed to send this payment type.	Contact your bank — may be a correspondent banking issue.
BE06	UnknownEndCustomer	The beneficiary cannot be identified at the receiving bank.	Confirm account number and beneficiary name with the recipient.
BE07	MissingDebtorAddress	The sender's address is required but missing.	Your bank needs to include your registered address on the payment.
BE08	MissingDebtorName	The payment is missing the sender's name.	Your bank needs to include your name in the payment fields.
BE16	InvalidDebtorIdentificationCode	The sender's ID code (LEI, tax number, etc.) is invalid or not recognised.	Provide a valid identifier to your bank.
BE17	InvalidCreditorIdentificationCode	The beneficiary's ID code is invalid.	Correct the beneficiary identifier.

Amount & Currency Issues (AM)

Code	Name	Explanation	Action
AM01	ZeroAmount	The payment amount is zero — not permitted.	Enter a valid amount greater than zero.
AM02	NotAllowedAmount	The amount is not permitted for this type of payment — e.g. exceeds a regulatory threshold or the account's limits.	Split into smaller payments or request a limit increase.
AM03	NotAllowedCurrency	The currency is not accepted for this payment channel or by the beneficiary bank.	Convert to a supported currency (usually USD or EUR).
AM04	InsufficientFunds	The sender's account does not have enough funds to cover the payment and all fees.	Top up your account and resubmit.
AM05	Duplication	This payment appears to be a duplicate of one already submitted. The bank has rejected it to prevent double payment.	Verify with your bank whether the original payment went through.
AM06	TooLowAmount	The amount is below the minimum permitted for this payment type or corridor.	Increase the amount or use a different transfer method.
AM09	WrongAmount	The instructed amount doesn't match the amount in the transaction details.	Correct the amount field and resubmit.
AM10	InvalidControlSum	In a batch file, the sum of individual transactions doesn't match the stated control total.	Reconcile the batch totals before resubmitting.
AM12	InvalidAmount	The amount field contains an invalid format (e.g. too many decimal places for the currency).	Correct the amount format for the target currency (e.g. JPY has no decimals).
AM14	AmountExceedsClearingSystemLimit	The amount exceeds the maximum allowed by the clearing system used (e.g. CHAPS high-value limit).	Split into multiple payments or use a different clearing route.

Format & Technical Issues (FF / CH / AG / DT / ED)

Code	Name	Explanation	Action
FF01	InvalidFileFormat	The payment message contains invalid characters, wrong field lengths, or a format that doesn't comply with the SWIFT MT or ISO 20022 standard.	Your bank's system needs to fix the message format.
FF03	InvalidPaymentTypeInformation	The combination of payment type, local instrument, and service level is invalid or not supported by the receiving bank.	Adjust the payment type or service level with your bank.
CH09	MissingRequiredField	A mandatory field (e.g. BIC, amount, currency, beneficiary name) is absent from the payment instruction.	Ask your bank to include all required fields before resubmitting.
CH10	MissingRequiredField	Similar to CH09 — a different mandatory element is missing (exact field depends on context).	Confirm which field is missing with your bank.
CH11	CreditorIdentifierIncorrect	The creditor's identifier (LEI, tax ID, IBAN) is present but incorrect.	Verify and correct the beneficiary identifier.
CH16	MaximumNumberOfTransactionsExceeded	The batch file contains more transactions than the clearing system or receiving bank allows in one file.	Split the batch into smaller files.
AG01	TransactionForbidden	This type of transaction is not permitted between these two banks on this channel — often a regulatory restriction.	Contact your bank to find an alternative route.
AG02	InvalidBankOperationCode	The bank operation code in the payment is not valid or not supported by the receiving bank.	Your bank's operations team needs to correct the message.
DT01	InvalidDate	The value date or execution date in the payment is invalid — e.g. a past date, a non-business day, or a date too far in the future.	Correct the date and resubmit.
ED01	CorrespondentBankNotPossible	No valid correspondent banking relationship exists between the sending and receiving bank for this currency or corridor.	Your bank needs to use a different correspondent route.
ED05	SettlementFailed	Settlement between the two banks failed — typically a Nostro/Vostro funding issue or a clearing system outage.	Your bank should retry; if persistent, contact their correspondent banking desk.
RC01	BankIdentifierIncorrect	The SWIFT BIC (bank identifier code) is wrong — either the bank doesn't exist, is not SWIFT-connected, or the BIC format is invalid.	Verify the beneficiary bank's correct 8 or 11-character BIC.
RC08	InvalidClearingSystemMemberIdentifier	The ABA routing number, sort code, or other clearing system ID is invalid or doesn't match the BIC.	Correct the routing number for the destination country's clearing system.
TM01	CutOffTime	The payment arrived after the bank's RTGS / clearing cut-off time. It was not rejected permanently — it will typically be requeued for the next business day.	No action needed — the bank will retry the next business day.
RF01	NotUniqueTransactionReference	The payment reference (e.g. UETR or end-to-end ID) has already been used for another transaction.	Generate a new unique reference and resubmit.

Regulatory, Compliance & Mandate Issues (RR / MD / CN / SL)

Code	Name	Explanation	Action
RR01	MissingDebtorAccountOrIdentification	Regulatory rules (e.g. FATF travel rule, EU funds transfer regulation) require the sender's account or ID but it is missing.	Your bank must include full originator information in the payment.
RR02	MissingDebtorNameOrAddress	The sender's name and/or address are required by regulation but not included.	Provide your full name and registered address to your bank.
RR03	MissingCreditorNameOrAddress	The beneficiary's name and/or address are required by regulation (e.g. US beneficiary) but not included.	Add the beneficiary's full name and address to the payment.
RR04	RegulatoryReason	A regulatory authority has blocked or rejected the payment — sanctions screening, AML flag, or capital control. The exact reason may not be disclosed.	Contact your bank's compliance team. Further investigation is required.
RR09	MissingDebtorIdentification	The sender's identification (tax ID, LEI, passport number) is required but missing.	Provide your identification document to your bank.
RR10	MissingCreditorIdentification	The beneficiary's identification is required but missing.	Obtain the beneficiary's identification and include it.
MD01	NoMandate	There is no valid mandate (authorisation) for this direct debit or recurring payment.	Set up a mandate with the debtor's bank before retrying.
MD02	MissingMandatoryInformationInMandate	The direct debit mandate exists but is missing required information.	Update the mandate with all required fields.
MD06	RefundRequestByEndCustomer	The beneficiary (or debtor in a direct debit) has requested a refund — authorised under SEPA consumer protection rules.	Funds will be returned to the sender. No further action needed.
MD07	EndCustomerDeceased	The bank has been notified that the account holder is deceased. The account cannot receive new credits.	Stop further payments to this account and deal with the estate directly.
CN01	AuthorisationCancelled	The authorisation for this payment was cancelled — either by the customer, their bank, or a regulatory authority.	Re-obtain authorisation before resubmitting.
SL01	DueToSpecificServiceOfferedByDebtorAgent	The payment was returned because of a specific service or restriction offered by the sending bank (e.g. a spending limit or service restriction).	Contact your bank to remove the restriction.
SL02	DueToSpecificServiceOfferedByCreditorAgent	The beneficiary bank applies a specific service (e.g. a whitelist-only policy) that prevented crediting this sender.	The beneficiary must instruct their bank to allow payments from your institution.
SL11	CreditorNotOnWhitelistOfDebtor	The beneficiary is not on the sender's approved recipient list — used in some controlled/corporate payment environments.	Add the beneficiary to the approved list.
SL12	DebtorNotOnWhitelistOfCreditor	The sender is not on the beneficiary bank's approved sender list.	Contact the beneficiary bank to be added to their list.

Fraud, Security & Other Rejections (FRAD / CUST / NOAS / MS / NARR)

Code	Name	Explanation	Action
FRAD	FraudulentOrigin	The bank suspects the payment originates from fraud — e.g. an account takeover or APP (authorised push payment) scam detection.	Contact your bank's fraud team immediately. Do not retry without speaking to them first.
NOAS	NoAnswerFromCustomer	The bank contacted the customer for authorisation or clarification but received no response within the required time.	Resubmit with explicit authorisation or contact your bank.
NOCM	NotCompliant	The payment is not compliant with AML, sanctions, or internal policy rules at the receiving bank.	Contact your bank's compliance team for guidance.
LEGL	LegalDecision	A legal authority (court, regulator, law enforcement) has ordered the payment to be blocked or returned.	Seek legal advice. No bank-level fix is possible without the legal order being lifted.
CUST	RequestedByCustomer	The customer themselves requested cancellation/return of the payment.	If you didn't request this, contact your bank immediately — may indicate unauthorised activity.
UPAY	UnduePayment	The payment was made in error or without a valid legal basis. The beneficiary bank is returning it.	Funds will be returned automatically. Verify the original payment was intentional.
TPNR	TransactionProhibited	This type of transaction is prohibited — either by the bank's policy, the country's regulations, or sanctions.	Contact your bank to understand the specific prohibition.
MS02	NotSpecifiedReasonCustomerGenerated	The return reason is not specified — generated by the customer (beneficiary or debtor). Used when no more precise code applies.	Contact the other party or your bank for more detail.
MS03	NotSpecifiedReasonAgentGenerated	The return reason is not specified — generated by a bank in the chain. Used when no more precise code applies.	Request your bank to investigate with the returning bank.
NARR	Narrative	The reason is provided as free text (narrative) in the message rather than a coded reason. Check the payment details for the specific explanation.	Read the accompanying narrative text from the rejection message.
TECH	TechnicalProblem	A technical failure at the bank or clearing system prevented processing. Not a permanent rejection — should be retried.	Your bank will typically retry automatically. If not resolved in 24h, contact them.
SYAD	SystemAdvisory	The system flagged the payment for advisory review — often a soft alert rather than a hard reject. May be combined with PDNG.	Monitor for an update. If it remains SYAD for more than 24h, contact your bank.

Track your payment on Ohmyfin — free

* SWIFT and GPI are trademarks of S.W.I.F.T. SC, La Hulpe, Belgium. ISO 20022 is a standard of the International Organization for Standardization. Ohmyfin Organisation is independent and not affiliated with S.W.I.F.T. SC, the ISO 20022 Registration Authority, or any bank. Status codes and reason codes are reproduced for reference purposes from publicly available ISO and SWIFT documentation.

SWIFT & ISO 20022 Payment Status Codes

Payment Tracker