Home > Appendix B: ACH Return Codes > Directory of ACH Return Codes

Directory of ACH Return Codes

The Return Codes and NACHA Definitions included below are all quoted directly from 2009 ACH Rules: A Complete Guide To Rules & Regulations Governing the ACH Network (National Automated Clearing House Association, 2009)

 The ACH Return Codes can be associated with ACH payment processing.  This is not a complete list of ACH Return Codes-- those related only to government payments, ATMs, ACH credits, paper check conversion, or inter-bank communications have been omitted. R01   Insufficient Funds

NACHA Definition:

The available and/or cash reserve balance is not sufficient to cover the dollar value of the debit entry.

What it Means: There were insufficient funds in your customer’s account to complete the transaction. You will see this type of ACH Return displayed in PaySimple with a Return Reason of “Non Sufficient Funds” or “NSF.”

What to Do: You can direct the ACH processor to automatically re-submit transactions returned for insufficient funds.  This setting is attached to your ACH Processing Account, and is not included in your PaySimple system settings. If your account was not initially configured for an automatic re-submit, please contact Customer Care so that we can make the appropriate adjustment with your ACH processor. Note that if you configure automatic re-submit, you run the risk of the transaction being returned again, and incurring a second ACH Return fee.

 

You can also contact your customer for a different form of payment, or ask them for a date when the account will contain funds so that you can manually submit the transaction again.

 

If you have not yet shipped the goods or provided the services covered by the payment, you may want to wait to do so until you have confirmation of a settled payment.

 When you re-submit a R01 or R09 (NSF) transaction you can only re-submit for the original transaction amount-- you CANNOT add in the ACH Return Fee assessed to your company.  If you want to collect this fee from your customers it must be authorized as a SEPARATE ACH transaction and you must manually enter this transaction in PaySimple.

However, you are allowed to include the following statement in your Terms & Conditions so that when your customers authorize the initial transaction, they also authorize a second transaction to collect the ACH Return Fee in the case of a R01 or R09 (NSF) transaction.

In the case of an ACH Transaction being rejected for Non Sufficient Funds (NSF) I understand that {your company name} may at its discretion attempt to process the charge again within 30 days, and agree to an additional {insert $} charge for each attempt returned NSF which will be initiated as a separate transaction from the initial authorized payment.

 

R02   Account Closed

NACHA Definition:

A previously active account has been closed by action of the customer or the RDFI.

What it Means: The bank account you attempted to charge is closed, and you cannot re-submit this transaction.

What to Do: Contact your customer for a different bank account, or for another form of payment.If you have not yet shipped the goods or provided the services covered by the payment, you may want to wait to do so until you have confirmation of a settled payment.

 

R03   No Account/Unable to Locate Account

NACHA Definition:

The account number structure is valid and it passes the check digit validation, but the account number does not correspond to the individual identified in the entry, or the account number designated is not an existing account.

What it Means: When entering the transaction, the Routing Number, Bank Account Number, and/or the Customer Name was entered incorrectly.  re-submit this transaction.

What to Do: Contact your customer and confirm the Routing Number, Bank Account Number and the exact name on the bank account. (You may want to ask your customer to fax a copy of a voided check so that you can double-check these values yourself.) If this information does not exactly match what you initially entered, make changes and submit a NEW payment. If you did enter everything correctly, please contact Customer Care so that we can further investigate the problem.

 

R04   Invalid Account Number

NACHA Definition:

The account number structure is not valid. The entry may fail the check digit validation or may contain an incorrect number of digits.

What it Means: When entering the transaction, the Bank Account Number entered was definitely wrong.  You cannot re-submit this transaction.

What to Do: Contact your customer and obtain the correct bank account number. (You may want to ask your customer to fax a copy of a voided check so that you can double-check the bank account number yourself.)Submit a NEW payment using the corrected bank account number.

 

R05   Unauthorized Debit to Consumer Account Using Corporate SEC Code

NACHA Definition:

A CCD, CTX, or CBR debit entry was transmitted to a Consumer Account of the Receiver and was not authorized by the Receiver. [A CCD or CTX debit entry was transmitted to a Consumer Account of the Receiver and was not authorized by the Receiver.] The Receiver may request immediate credit from the RDFI for an unauthorized debit. The request must be made in writing within fifteen (15) days after the RDFI sends or makes available to the Receiver information pertaining to that debit entry. The Receiver must also provide the RDFI with a written statement, pursuant to subsection 8.6.6 (Receiver's Written Statement), that the debit entry was not authorized by the Receiver. For purposes of this code and related Operating Rules provisions, a debit entry was not authorized by a Receiver if (1) the authorization requirements of Article Two, subsection 2.1.2 (Receiver Authorization and Agreement) have not been

met; (2) the debit entry was initiated in an amount greater than that authorized by the Receiver; or (3) the debit entry was initiated for settlement earlier than authorized by the Receiver. An unauthorized debit entry does not include a debit entry initiated with fraudulent intent by the Receiver or any person acting in concert with the Receiver. An RDFI using this return reason code must transmit the return entry by its ACH Operator's deposit deadline for the return entry to be made available to the ODFI no later than the opening of business on the banking day following the sixtieth calendar day following the Settlement Date of the original entry.

What it Means: An ACH Transaction entered as “CCD” was attempted against a consumer’s personal bank account, and the consumer reported the transaction to the bank as not authorized.  Ordinarily a “CCD” transaction has a 3-day window in which the transaction can be disputed, but this code directs the bank to honor the return if it is entered within 60 days of the original transaction.  This is done because the transaction was incorrectly coded as “CCD” when entered.  “CCD” is used only when charging a business bank account.  This is an “unauthorized” return code, and will result in your account being assessed the ACH Chargeback Fee. (See ACH Chargeback Return Codes.)You cannot re-submit this transaction.  Any additional transactions you attempt to process against this account will also be returned unless your customer specifically instructs his bank to accept them.

What to Do: Contact your customer and resolve any issues that caused the transaction to be disputed.You can ask the customer for a different form of payment, or ask to debit a different bank account. If you need to debit the same bank account, instruct your customer to call the bank and remove the block on transactions your company initiates.  Then contact PaySimple Customer Care and inform them that the block has been lifted. You will be informed when it is permissible to re-submit the transaction. When you do, be certain to use the proper ACH Type for a personal bank account and NOT the “CCD” type. (See Appendix A: Authorizing Transactions for detailed information on ACH Types.) Unfortunately, there is no dispute resolution available to you within the ACH Network. customer continues to claim the transaction was not authorized, but you have proof that it was properly authorized, you will need to sue your customer in Small Claims Court to collect.  If you decide to take this course of action, please contact PaySimple Customer Care to obtain a copy of the statement your customer submitted to the bank-- You will need this document to pursue your case.

 

R06   Returned per ODFI's Request

NACHA Definition:

The ODFI has requested that the RDFI return the ACH entry. If the RDFI agrees to return the entry, the ODFI must indemnify the RDFI according to Article Eight (Recall, Stop Payment, Recredit, and Adjustment) of these Rules.

What it Means: The bank that submitted a transaction on your behalf is asking your customer’s bank to reverse it.  This typically happens if there is a technical problem during processing that causes transactions to be submitted incorrectly.  In rare instances it can also happen if the bank suspects it is being used to submit fraudulent transactions.  You cannot re-submit this transaction.

What to Do: Contact PaySimple Customer Care to determine why the bank asked that the payment be returned.

 

R07   Authorization Revoked by Customer

NACHA Definition:

The RDFI's customer (the Receiver) has revoked the authorization previously provided to the Originator for this particular transaction. The Receiver may request immediate credit from the RDFI for an unauthorized debit. The request must be made in writing within fifteen (15) days after the RDFI sends or makes available to the Receiver information pertaining to that debit entry. The Receiver must also provide the RDFI with a written statement that the authorization for the debit entry has been revoked by the Receiver. The RDFI must return the rescinded transaction to its ACH Operator by its deposit deadline for the adjustment entry to be made available to the ODFI no later than the opening of business on the banking day following the sixtieth calendar day following the Settlement Date of the original entry. This code and related Operating Rule provisions apply to Consumer entries only. (Note: This Return Reason Code may not be used for POP entries, Single-Entry WEB entries, or TEL entries.)

What it Means: Your customer reported to the bank that the transaction was not authorized because they revoked your authorization to process the payment prior to the transaction date.This code can only be used on one-time or recurring transactions processed against a consumer’s personal bank account with an ACH Type of PPD, or on a recurring transaction with an ACH type of WEB.  Typically you will see this return code when a customer revokes authorization for a recurring payment schedule, and you continue to process payments as part of that schedule.This is an

“unauthorized” return code, and will result in your account being assessed the ACH Chargeback Fee. (See ACH Chargeback Return Codesfor more information.)You cannot re-submit this transaction.  Any additional transactions you attempt to process against this account will also be returned unless your customer specifically instructs his bank to accept them

What to Do: Immediately suspend any recurring payment schedules entered for this bank account.  This will prevent additional transactions from being returned while you address the issue with your customer.  Then contact your customer and resolve any issues that caused the transaction to be disputed or the schedule to be cancelled.You can ask the customer for a different form of payment, or ask to debit a different bank account. certain to get proper authorization from your customer to debit the new account. (See Authorizing Echeck (ACH) Transactions for more information on how to do this.)If you need to debit the same bank account, instruct your customer to call the bank and remove the block on transactions your company initiates.  Then contact PaySimple Care and inform them that the block has been lifted.  You will be informed when it is permissible to re-submit the transaction.Unfortunately, there is no dispute resolution available to you within the ACH Network. customer continues to claim the transaction was not authorized, but you have proof that it was properly authorized, you will need to sue your customer in Small Claims Court to collect.  If you decide to take this course of action, please contact PaySimple Customer Care to obtain a copy of the statement your customer submitted to the bank-- you will need this document to pursue your case.

 

R08   Payment Stopped  

NACHA Definition:

The Receiver of a debit transaction has the right to stop payment on any specific ACH debit. A stop payment request should be handled in accordance with the provisions of Article Eight (Recall, Stop Payment, Recredit, and Adjustment) of these Rules. The RDFI should verify the Receiver's intent when a request for stop payment is made to ensure this is not intended to be a revocation of authorization (R07). A stop payment order shall remain in effect until the earliest of the following occurs: a lapse of six months from the date of the stop payment order, payment of the debit entry has been stopped, or the Receiver withdraws the stop payment order.

What it Means: Your customer instructed its bank not to honor a specific transaction they previously authorized you to process.  This instruction to the bank must

be made BEFORE the transaction is actually processed. You cannot re-submit this transaction, but you can process additional new payments against this account.

What to Do: Contact your customer and resolve any issues that caused the transaction to be stopped. To minimize the risk of additional returned transactions, it is a good idea to make certain that your customer understands your billing procedures, and agrees not to stop future payments.You can re-enter the returned transaction again with proper authorization from your customer.  You can also ask your customer for a different form of payment.

 

R09   Uncollected Funds  

NACHA Definition:

Sufficient book or ledger balance exists to satisfy the dollar value of the transaction, but the dollar value of transactions in the process of collection (i.e., uncollected checks) brings the available and/or cash reserve balance below the dollar value of the debit entry.

What it Means: There were insufficient funds in your customer’s account to complete the transaction.

What to Do: You can direct the ACH processor to automatically re-submit transactions returned for insufficient funds.  This setting is attached to your ACH Processing Account, and is not included in your PaySimple 3.0 settings.  If your account was not initially configured for an automatic re-submit, please contact Customer Care so that we can make the appropriate adjustment with your ACH processor.  Note that if you configure automatic re-submit, you run the risk of the transaction being returned again, and incurring a second ACH Return fee.You can also contact your customer for a different form of payment, or ask them for a date when the account will contain funds so that you can manually submit the transaction again.

 

If you have not yet shipped the goods or provided the services covered by the payment, you may want to wait to do so until you have confirmation of a settled payment.

 

R10   Customer Advises Not Authorized, Notice Not Provided, Improper Source Document, or Amount of Entry

Not Accurately Obtained from Source Document  

NACHA Definition:

For entries to Consumer Accounts that are not ARC, BOC, POP, or RCK entries, the RDFI has been notified by its customer, the Receiver, that the Originator of a given transaction has not been authorized to debit his account.....The Receiver may request immediate credit from the RDFI for an unauthorized debit. The request must be made in writing within fifteen (15) days after the RDFI sends or makes available to the Receiver information pertaining to that debit entry. The Receiver must also provide the RDFI with a written statement, pursuant to subsection 8.6.6 (Receiver's Written Statement), that the debit entry was not authorized by the Receiver. For purposes of this code and related Operating Rules provisions, a debit entry was not authorized by the Receiver if (1) the authorization requirements of Article Two, subsection 2.1.2 (Receiver Authorization and Agreement) have not been met; (2) the debit entry was initiated in an amount greater than that authorized by the Receiver; or (3) the debit entry was initiated for settlement earlier than authorized by the Receiver. An unauthorized debit entry does not include a debit entry initiated with fraudulent intent by the Receiver or any person acting in concert with the Receiver. The RDFI must return the rescinded transaction to its ACH Operator by its deposit deadline for the adjustment entry to be made available to the ODFI no later than the opening of business on the banking day following the sixtieth calendar day following the Settlement Date of the original entry....OR for ARC and BOC entries, the RDFI has been notified by its customer, the Receiver, that (1) the Receiver opted out of check conversion, (2) the required notice was not provided by the Originator in accordance with Article Three, subsection 3.7.1 (Notice Obligation) or subsection 3.8.1 (Notice Obligation), (3) the source document used for the debit entry is improper pursuant to subsection 3.7.2 (Source Documents) or subsection 3.8.2 (Source Documents), or (4) the amount of the ARC or BOC entry was not accurately obtained from the source document. The Receiver may request immediate credit from the RDFI for an ARC or BOC entry for the reasons described above. The request must be made in writing within fifteen (15) days after the RDFI sends or makes available to the Receiver information relating to that debit entry. The Receiver must also provide the RDFI with a written statement, pursuant to subsection 8.6.6.1 (Receiver's Written Statement for ARC and BOC Entries), that (1) the Receiver optedout of check conversion, (2) the required notice was not provided, (3) the source document used for the debit entry is improper, or (4) the amount of the ARC or BOC entry was not accurately obtained from the source document. An RDFI using this Return Reason Code must transmit the return entry by its ACH Operator's deposit deadline for the return entry to be made available to the ODFI no later than the opening of business on the banking day following the sixtieth calendar day

following the Settlement Date of the ARC or BOC entry...

What it Means: Your customer submitted a signed document to the bank stating that the transaction was not authorized, or that the transaction was entered for an amount different than the authorized amount, or was submitted before the authorized date. (See Authorizing Echeck (ACH) Transactionsinformation about authorization requirements.) This is an “unauthorized” return code, and will result in your account being assessed the ACH Chargeback Fee. ( See ACH Chargeback Return Codes for more information.)You cannot re-submit this transaction.  Any additional transactions you attempt to process against this account will also be returned unless your customer specifically instructs his bank to accept them.

What to Do: Immediately suspend any recurring payment schedules entered for this bank account.  This will prevent additional transactions from being returned while you address the issue with your customer.  Contact your customer and resolve any issues that caused the transaction to be disputed.You can ask the customer for a different form of payment, or ask to debit a different bank account.   Be certain to get proper authorization from your customer to debit the new account. (See Authorizing Echeck (ACH) Transactions) for more information on how to do this.)If you need to debit the same bank account, instruct your customer to call the bank and remove the block on transactions your company initiates. contact PaySimple Customer Care and inform them that the block has been lifted.  You will be informed when it is permissible to re-submit the transaction.Unfortunately, there is no dispute resolution available to you within the ACH Network.  If your customer continues to claim the transaction was not authorized, but you have proof that it was properly authorized, you will need to sue your customer in Small Claims Court to collect.  If you decide to take this course of action, please contact PaySimple Customer Care to obtain a copy of the statement your customer submitted to the bank-- you will need this document to pursue your case.

 

R12   Account Sold to Another DFI  

NACHA Definition:

A financial institution may continue to receive entries destined for an account that has been sold to another financial institution. Because the RDFI no longer maintains the account and is unable to post the entry, it should return the entry to the ODFI.

What it Means: Your customer’s account was sold to another bank but the Customer Record in PaySimple was not updated with the new bank information, so the payment you processed was sent to the old bank and cannot be honored.

What to Do: Contact your customer to obtain new Routing Number and Bank Account Number information, then enter a NEW transaction using the updated account numbers.

 

R13   Invalid ACH Routing Number

NACHA Definition:

Entry contains a Receiving DFI Identification or OGO Identification that is not a valid ACH routing number.

What it Means: The Routing Number entered for the transaction is invalid and does not belong to any bank in the ACH Network.

What to Do: Your PaySimple 3.0 system is designed to validate routing numbers prior to submitting transactions for processing--so you should never see this reason code.If you do see the code, double-check that you entered the Routing Number correctly, and contact your customer to confirm it if necessary.  Then submit a NEW payment using the correct routing number.If you have confirmed that the routing number you entered is correct, contact PaySimple Customer Care so that we can investigate the problem.

 

R16   Account Frozen

NACHA Definition:

Access to the account is restricted due to specific action taken by the RDFI or by legal action.

What it Means: The payment cannot be honored because the account has been frozen and no transactions can be processed against it.

What to Do: Contact your customer to obtain a different form of payment. You will not be able to process transactions using this bank account until it is un-frozen.

 

R17   File Record Edit Criteria (Specify)

NACHA Definition:

Some fields that are not edited by the ACH Operator are edited by the RDFI. If the entry cannot be processed by the RDFI, the field(s) causing the processing error must be identified in the addenda record information field of the return.

What it Means: Your customer’s bank had a technical problem with the ACH transaction record submitted for this payment.

What to Do: Contact PaySimple Customer Care so that we can investigate the problem.

 

R18   Improper Effective Entry Date

NACHA Definition:

The effective entry date for a credit entry is more than two banking days after the banking day of processing as established by the Originating ACH Operator...The effective entry date for a debit entry is more than one banking day after the processing date.

What it Means: The date entered in the ACH transaction record is invalid and the transaction cannot be processed.

What to Do: The PaySimple 3.0 system is designed to submit scheduled transactions only on the exact date they are scheduled to occur, so you should never see this return code.If you do see this code, please contact PaySimple Customer Care so that we can investigate further.

 

R19   Amount Field Error  

NACHA Definition:

Amount field is non-numeric...Amount field is not zero in a prenotification, DNE, ENR, Notification of Change, Refused Notification of Change, or zero dollar entry....Amount field is zero in an entry other than a prenotification, DNE, ENR, Notification of Change, Refused Notification of Change, Return, Dishonored Return, Contested Dishonored Return, or zero dollar entry....Amount field is greater than $25,000 for ARC, BOC, and POP entries.

What it Means: The payment was entered for an amount of $0, or a paper-check conversion (ARC or BOC) was entered for over $25,000.

What to Do: The PaySimple 3.0 system is designed to prevent zero dollar transactions and transactions over $25,000, so you should never see this error.If you do see this code for a transaction under $25,000, please contact PaySimple Customer Care so that we can investigate further.

 

NOTE:  You should not be converting paper checks to ACH transactions in PaySimple 3.0.  The system does not support the ACH Transaction types used with paper checks.  If you did process a paper check as an ACH Transaction, your customer can claim that the payment was not authorized.

 

R20   Non-Transaction Account  

NACHA Definition:

The ACH entry destined for a non-transaction account, as defined in Regulation D, would include either an account against which transactions are prohibited or limited or a pass-through where the entry is for a credit union or thrift organization and Regulation E descriptive requirements cannot be met.

What it Means: The bank account you entered cannot be used for ACH Payments.

What to Do: Contact your customer to obtain authorization to charge a different bank account. (Be certain that your customer confirms the account is enabled for ACH transactions.) Or, ask for a different form of payment.

 

R24   Duplicate Entry

NACHA Definition:

The RDFI has received what appears to be a duplicate entry; i.e., the trace number, date, dollar amount and/or other data matches another transaction. This code should be used with extreme care. The RDFI should be aware that if a file has been duplicated, the Originator may have already generated a reversal transaction to handle the situation.

What it Means: There was a technical error that caused your transaction to be transmitted twice, or your customer’s bank thinks that such an error occurred.

What to Do: Contact PaySimple Customer Care so we can investigate the problem.

 

R26   Mandatory Field Error

NACHA Definition:

Individual Name contains all spaces or all zeros (MTE, TEL, and WEB entries)....Check Serial Number contains all spaces or all zeros (ARC, BOC, POP, RCK, or XCK entries)....

What it Means: For a TEL or WEB ACH Transaction, the name of the account holder was not provided.  

What to Do: The PaySimple 3.0 system is designed to prevent you from submitting transactions with these fields missing.  If you see this error, there was likely a technical problem.  Please contact Customer Care so that we can investigate further.

 

R28    Routing Number Check Digit Error

NACHA Definition:

The Check Digit for a Routing Number is not valid.

What it Means: The bank routing number is invalid.

What to Do: The PaySimple 3.0 system is designed to prevent you from submitting transactions with invalid routing numbers, but in rare cases you may see this error.  Double check the routing number entered, and if necessary confirm it with your customer. (You may want to ask your customer to fax a copy of a voided check so that you can double-check the value yourself.)If you’ve corrected a data entry error, you can enter the payment again as a NEW transaction.If you’ve confirmed the routing number was entered correctly on the original transaction, please contact Customer Care so that we can investigate further.

 

R29   Corporate Customer Advises Not Authorized  

NACHA Definition:

The RDFI has been notified by the Receiver (non-consumer) that a specific transaction has not been authorized by the Receiver.

What it Means: The company you attempted to debit has notified the bank that the transaction was not authorized.  Or, you attempted to debit a business bank account that is not enabled for ACH transactions.This is an “unauthorized” return code, and will result in your account being assessed the ACH Chargeback Fee.  See ACH Chargeback Return Codes

for more information.You cannot re-submit this transaction.  Any additional transactions you attempt to process against this account will also be returned unless your business customer specifically instructs his bank to enable the account for ACH transactions.

What to Do: Immediately suspend any recurring payment schedules entered for this bank account.  This will prevent additional transactions from being returned while you address the issue with your customer.  Contact your customer and resolve any issues that caused them to claim the transaction was unauthorized,  then have your customer call the bank and remove the block on transactions your company initiates. problem is account configuration, ask your customer to have the business bank account enabled for ACH transactions. Then contact PaySimple Customer Care and inform them that the block has been lifted. You will be informed when it is permissible to re-submit the transaction.Alternately, you can ask the customer for a different form of payment, or ask to debit a different bank account.   Be certain to get proper authorization from your customer to debit the new account. (See Authorizing Echeck (ACH) Transactions for more information on how to do this.)Unfortunately, there is no dispute resolution available to you within the ACH Network.  If your customer continues to claim the transaction was not authorized, but you have proof that it was properly authorized, you will need to sue your customer in Small Claims Court to collect.

 

R32   RDFI Non-Settlement   

NACHA Definition:

The RDFI is not able to settle the entry

What it Means: Your customer’s bank rejected the transaction.

What to Do: Have your customer contact the bank to find out what caused the problem.  When the problem is remedied you can re-submit the payment as a NEW ACH transaction.  You can also ask your customer for authorization to charge a different bank account, or ask for an alternate form of payment.

 

R34    Limited Participation DFI    

NACHA Definition:

The RDFI's participation has been limited by a federal or state supervisor

What it Means: Your customer’s bank is not able to process the ACH payment you initiated.

What to Do: Ask your customer for authorization to charge a different bank account, or ask for an alternate form of payment.

 

R37    Source Document Presented for Payment     

NACHA Definition:

The source document to which an ARC, BOC, or POP entry relates has been presented for payment. The Receiver may request immediate credit from the RDFI for an ARC, BOC, or POP entry for the reason described above. The request must be made in writing within fifteen (15) days after the RDFI sends or makes available to the Receiver information relating to that debit entry. The Receiver must also provide the RDFI with a written statement that the source document was presented for payment. An RDFI using this return reason code must transmit the return entry by its ACH Operator's deposit deadline for the return entry to be made available to the ODFI no later than the opening of business on the banking day following the sixtieth calendar day following the Settlement Date of the ARC, BOC, or POP entry.

What it Means: A paper check was converted to an ACH transaction, and was also submitted in paper form to the bank for standard processing-- thus the same payment was processed twice.You will see this error if your customer notifies the bank that a check they wrote was converted to ACH in addition to being processed normally. Additionally, the bank can identify the duplication and assign this code without notifying your customer first. The bank will then “return” the ACH transaction and refund the customer's account, or will simply not process the duplicate transaction.

What to Do: Check your records to determine if you accidentally entered an ACH transaction for a paper check that you took the check to the bank. did, then this “return” remedied the error, and you don’t need to take any further action.If you’re sure you did not take the check to the bank (for example, you still have the original in your files), contact your customer to resolve the mistake--keeping in mind that the bank may have issued the return without the customer’s knowledge.NOTE:  As of March 2010, this code will be counted as an unauthorized “chargeback.”  However, you should not be converting paper checks to ACH transactions in PaySimple 3.0.  The system does not support the ACH Transaction types used with paper checks.  If you did process a paper check as an ACH Transaction, your customer can claim that the payment was not

authorized.  Contact PaySimple Customer Care for assistance with this transaction.