...
How to find Disbursement Reject and Return Codes
Step 1: Dashboard → MerchantsNavigate to the Merchants page.
Step 2: Click on the desired Merchant to be taken to the Merchant Overview Page and access their Merchant Profile page.
Step 3: Click on the Withdrawals tab from the Account Overview sub-menu on the bottom left of the Merchant Overview . Then, click on a listed disbursement with a status of FAILED to view its Withdrawal Details page.
Step 4: Click on a returned transaction from the Withdrawal Returns or Withdrawal History sections. Step 5: Under the revealed Alerts section, you will see message and an ACH Return code under the Message column. See the the time of the return (Created), the type of decline (Code), and the supporting reason or explanation (Message).
You can view a complete list of Disbursement (ACH) Return Codes below.:
Expand |
---|
title | Click here to see all Disbursement (ACH) Return Codes |
---|
|
...
Expand |
---|
|
CODE | CATEGORY | DESCRIPTION | AUTO BLOCK | REMOVABLE BLOCK | ONLY APPLIES TO AFFECTED MERCHANT | APPLIED PLATFORM WIDE | R01 | NSF
| Insufficient funds in account | NO | | | | R02 | BADACCOUNT
| Account is closed | YES | NO | | YES | R03 | BADACCOUNT
| No account on file | YES | NO | | YES | R04 | BADACCOUNT
| Invalid account number | YES | NO | | YES | R05 | UNAUTHORIZED
| Unauthorized debit to consumer account | YES | YES | YES | | R06 | UNAUTHORIZED
| Returned at request of ODFI | YES | YES | YES | | R07 | UNAUTHORIZED
| Authorization revoked by customer | YES | YES | YES | | R08 | UNAUTHORIZED
| Payment stopped | YES | YES | YES | | R09 | NSF
| Insufficient collected funds in account being charged | NO | | | | R10 | UNAUTHORIZED
| Customer advises not Authorized, notice not provided, improper source document, or amount of entry not accurately obtained from source document | YES | YES | YES | | R11 | BADACCOUNT
| Check truncation return | YES | NO | | YES | R12 | BADACCOUNT
| Account sold to another financial institution | YES | NO | | YES | R13 | BADACCOUNT
| Invalid ACH routing number | YES | NO | | YES | R14 | UNAUTHORIZED
| Representative payee is deceased or cannot continue in that capacity | YES | YES | YES | | R15 | UNAUTHORIZED
| Beneficiary or account holder other than representative payee deceased | YES | YES | YES | | R16 | UNAUTHORIZED
| Account funds have been frozen | YES | YES | YES | | R17 | BADACCOUNT
| Item returned because of invalid data; refer to addenda for information | YES | NO | | YES | R18 | GENERAL
| Improper effective date | NO | | | | R19 | GENERAL
| Amount error | NO | | | | R20 | UNAUTHORIZED
| Account does not allow ACH transactions or limit for transactions has been exceeded | YES | YES | YES | | R21 | BADACCOUNT
| Invalid company identification | YES | NO | | YES | R22 | BADACCOUNT
| Invalid individual ID | YES | NO | | YES | R23 | UNAUTHORIZED
| Credit entry refused by receiver | YES | YES | YES | | R24 | GENERAL
| Duplicate entry | NO | | | | R25 | BADACCOUNT
| Addenda record error | YES | NO | | YES | R26 | BADACCOUNT
| Mandatory field error | YES | NO | | YES | R27 | BADACCOUNT
| Trace number error | YES | NO | | YES | R28 | BADACCOUNT
| Routing/transit number check digit error | YES | NO | | YES | R29 | UNAUTHORIZED
| Corporate customer advised not authorized | YES | YES | YES | | R30 | GENERAL
| RDFI not participant in check truncation program | NO | | | | R31 | UNAUTHORIZED
| Permissible return entry | YES | YES | YES | | R32 | GENERAL
| RDFI non-settlement | NO | | | | R33 | UNAUTHORIZED
| Return of item | YES | YES | YES | | R34 | GENERAL
| Limited participation ODFI | NO | | | | R35 | GENERAL
| Return of improper debit entry | NO | | | | R36 | GENERAL
| Return of improper credit entry | NO | | | | R37 | GENERAL
| Source document presented for payment | NO | | | | R38 | GENERAL
| Stop payment on source document | NO | | | | R39 | BADACCOUNT
| Improper source document | YES | NO | | YES | R40 | UNAUTHORIZED
| Return of item by government agency | YES | YES | YES | | R41 | BADACCOUNT
| Invalid Transaction Code | YES | NO | | YES | R42 | BADACCOUNT
| Routing/transit number check digit error | YES | NO | | YES | R43 | BADACCOUNT
| Invalid account number | YES | NO | | YES | R44 | BADACCOUNT
| Invalid individual ID | YES | NO | | YES | R45 | BADACCOUNT
| Invalid individual name or company name | YES | NO | | YES | R46 | BADACCOUNT
| Invalid representative payee indicator code | YES | NO | | YES | R47 | BADACCOUNT
| Duplicate enrollment | YES | NO | | YES | R50 | GENERAL
| State law affecting RCK acceptance | NO | | | | R51 | UNAUTHORIZED
| Item is ineligible, notice not provided, signature not genuine, or original item altered for adjustment entry | YES | YES | YES | | R52 | UNAUTHORIZED
| Stop payment on item | YES | YES | YES | | R53 | GENERAL
| Item and ACH entry presented for payment | NO | | | | R61 | GENERAL
| Misrouted return - RDFI for original entry has placed incorrect routing/transit number in RDFI identification field | NO | | | | R62 | GENERAL
| Incorrect trace number | NO | | | | R63 | GENERAL
| Incorrect dollar amount | NO | | | | R64 | GENERAL
| Incorrect individual identification | NO | | | | R65 | GENERAL
| Incorrect transaction code | NO | | | | R66 | GENERAL
| Incorrect company identification | NO | | | | R67 | GENERAL
| Duplicate return | NO | | | | R68 | BADACCOUNT
| Untimely return - return was not sent within the established timeframe | YES | NO | | YES | R69 | BADACCOUNT
| Field errors | YES | NO | | YES | R70 | UNAUTHORIZED
| Permissible return entry not accepted | YES | YES | YES | | R71 | BADACCOUNT
| Misrouted dishonored return -incorrect routing/transit number in RDFI identification field | YES | NO | | YES | R72 | GENERAL
| Untimely return - dishonored return was not sent within the established timeframe | NO | | | | R73 | GENERAL
| Timely original return - RDFI certifies the original return entry was sent within established timeframe for original returns | NO | | | | R74 | GENERAL
| Corrected return - RDFI is correcting a previous return entry that was dishonored because it contained incomplete or incorrect information | NO | | | | R75 | GENERAL
| Original return not a duplicate | NO | | | | R76 | GENERAL
| No errors found | NO | | | | R80 | BADACCOUNT
| Cross-border payment coding error | YES | NO | | YES | R81 | GENERAL
| Non-participant in cross-border program | NO | | | | R82 | BADACCOUNT
| Invalid foreign RDFI identification | YES | NO | | YES | R83 | BADACCOUNT
| Foreign RDFI unable to settle | YES | NO | | YES | R84 | GENERAL
| Cross-border entry not processed by originating gateway operator | NO | | | | R94 | GENERAL
| Administrative return item was processed and resubmitted as a photocopy | NO | | | | R95 | GENERAL
| Administrative return item was processed and resubmitted as a MICR-Split | NO | | | | R97 | GENERAL
| Administrative return item was processed and resubmitted with corrected dollar amount | NO | | | | R98 | GENERAL
| Indicates a return PAC (pre-authorized check); RDFI provides a text reason and indicated a new account number on the PAC itself | NO | | | | R99 | GENERAL
| Indicates a return PAC (pre-authorized check); RDFI provides a text reason on the PAC itself for which there is no equivalent return reason code | NO | | | |
|
...
For Bank Accounts Placed on Hold As A Result of a Return
Please review the the following categories for next steps.
The returns are separated into three categories: NSF
, BAD ACCOUNT
, and UNAUTHORIZED
.
Once each Action Steps section is completed, submit a Support Ticket for the hold to be lifted with the bank letter attached.
A separate action is taken per category:
...
Return Category | Description | Action Steps |
---|
NSF
| The system will not place a hold. Future transactions are permitted. | N/A |
BAD ACCOUNT
|
...
| A block is placed on the account. |
...
Note |
---|
Due to this reject category type, the block can’t be removed. If there is an exception the block will take up to an additional 2 business days to lift outside the initial Support Ticket submission |
|
...
Note |
---|
Due to NACHA regulations, Payrix Support is unable to lift blocks without bank letter consent for both debits and credits if your first attempt to whitelist is unsuccessful. |
If the reject falls under BAD ACCOUNT
and UNAUTHORIZED
, the merchant will need to provide:
...
a request to their bank whitelisting the (below) funding IDs and;
...
Info |
---|
A bad account reject will typically happen because the banking information on file is not correct. It is best practice to validate that the correct banking information is on file prior to submitting a ticket. If the banking information is deemed incorrect, changing the bank account to the correct information will be an immediate release of the hold. Note: All bank changes may trigger an additional risk hold review. |
| The Merchant will need to provide: Proof of banking information that matches the banking information on file. A letter from their issuing bank that validates that the bank account no longer falls under the reject category that we received.
|
UNAUTHORIZED
| A block is placed on this merchants ability to utilize this bank account for debits or credits. This block can be lifted after Payrix has received proper approvals to debit or credit the bank account | The Merchant will need to: Request that their issuing bank whitelists WorldPay Funding IDs (shown below). A request for a letter from their issuing bank to Payrix Support
|
...
...
to credit and debit the account
|
...
Tip |
---|
Worldpay Funding IDs Send the following funding IDs to your bank in order to have whitelist disbursements (ACH payouts Payouts) to your account: |
Note |
---|
Due to NACHA regulations, Payrix Support is unable to lift blocks without bank letter consent for both debits and credits if your first attempt to whitelist is unsuccessful. |