Returned payments codes Only to be used in case national legislation (e g , data protection laws) does not allow the use of AC04, RR01, RR02, RR03 and RR04 Note: limit the use of the reason code MS03 and select the appropriate reason code in the list
UniPay Gateway Documentation Subscription has been returned Subscription has been updated successfully Customer's account number is incorrect or malformatted Transit or routing number is not valid anymore and should be changed Transit or routing number should be changed Account number structure is invalid Customer's name is incorrect or malformatted
Returned Payment Reasons · Banking Circle Help Centre When payments are returned to an account from the recipient bank a return code is usually stated in the reference field of the return SWIFT (field 70) Please see below table for guidance on reason codes: Account identifier invalid or incorrect (i e invalid IBAN or account number does not exist)
Reject Return – ISO 20022 payments In this article, we refer to the scenarios linked to RJCT (Reject) Transaction Status Reason – which utilizes either an ISO external Status Reason code (ExternalStatusReason1Code) or a proprietary reason For example, AC04 ‘Closed Account Number’ may complement an RJCT (Reject) Transaction Status
Return Codes - Lead | API Docs Details about processing or receiving wire returns This page includes the full list of supported return and rejection reason codes along with their corresponding enum values and descriptions
Payment Status Reason Codes - Goldman Sachs Developer When TxB provides a payment status, we may optionally describe the reason using the below codes: Customer account is not compliant with regulatory requirements, for example FICA (in South Africa) or any other regulatory requirements which render an account inactive for certain processing
MS01 Return and Rejection Codes Guide Reason codes include issues like invalid account numbers, amounts, beneficiaries, agreements, or dates The field aims to clearly communicate the reason a transaction was returned or rejected
FedNow Response Codes For Real Time Payments, each of the networks (RTP-TCH and FedNow) have their own unique responses to transfer messages The Platform application should be aware of these messages and deal with them accordingly Report request failed Review request, update and resubmit as needed
Global Payments status responses and error codes An error code identifies the reason that a request resulted in an error The following tables contain all the possible error codes and their descriptions for Global Payments: