Transaction Codes


Transaction Status Codes

The status of a transaction will change depending on the following factors:

  1. Was the transaction accepted or rejected for processing?
  2. Which part of the status cycle the transaction is in?

 

The status cycle for a typical ACH transaction is Ready > Settling > Funded. The status cycle for a typical credit card transaction is Ready > Settled. After being sent out by Forte for processing, the status may change to one of the following:

Status Description
Authorized

The customer's payment was authorized. To complete the sale, the item must be captured from the transaction's detail page.

Complete eCheck verification was performed and the results were positive (POS) or unknown (UNK).
Declined Transaction was declined for reasons detailed in Response Code and Response Description.
Failed eCheck verification was performed and the results were negative (NEG) or the transaction failed for reasons detailed in the Response Code and Response Description.
Funded eCheck item was funded to or from the merchant's bank account.
Ready Transaction was received and is awaiting origination (echeck) or settlement (credit card).
Rejected eCheck item has been rejected or returned by the client's financial institution. Merchant will not be funded for the item.
Review Transaction was unable to be settled due to a merchant configuration issue. Please contact Customer Service to resolve (1-469-675-9920 x1).
Settled Credit Card item has been funded to the merchant's bank account.
Settling eCheck item has been originated and Forte is awaiting the settlement results.
Unfunded Previously funded echeck item has been returned and funding was reversed.
Voided The transaction was voided and the item will not be originated or settled.

 

Transaction Response Codes

When a transaction is submitted for processing, Forte immediately returns one of the following responses. Transactions that are accepted for processing return the A01 response code. Transactions that are rejected for processing return the "U" response codes.

Code Description Comments Test Parameters
A01 APPROVED Transaction approved/completed  
A03 PARTIAL AUTHORIZATION Transaction approved for a partial authorization (CC only)  
E10 INVALID MERCH OR PASSWD Merchant ID or processing password is incorrect. Ensure you've entered the correct credentials. This error prevents phishing attempts for valid Merchant IDs.  
E20 MERCHANT TIMEOUT The transaction message not received because of a connection failure in reading data. Please re-try after some time. You may increase the wait time limit on the Merchant Settings.  
E55 INVALID TOKEN

Specified token was invalid, could not be located, or may have been deleted. This error can be caused by one of hte following issues on the Merchant side:

  • Client Token Transactions - For client token transactions where neither payment fields nor a payment token were specified, the client record does not have a default payment method matching the transaction type. Set a default payment method for the transaction type or send the paymethod token in the message.

  • Payment Token Transactions - For payment token transactions where no client token is specified, the payment token must be clientless. There is no client associated with the payment token. It’s a Null/0 in the customer token column in the database. Refer to Understanding Tokens for more details.

  • Both Client and Payment Tokens Present - For transactions with client and payment tokens, the specified payment token is not associated with the client or is clientless. There is no client associated with the client or payment token. It’s a Null/0 in the customer token column in the database. Refer to Understanding Tokens for more details.

 
E99 INTERNAL ERROR An unspecified error has occurred. This is an unhandled exception. Please reach out to our Tech Support at 866-290-5400 option 5.  
F01 MANDATORY FIELD IS MISSING Required field is missing. See the Response Description field for the missing field (e.g., pg_response_description=MANDATORY FIELD MISSING:ecom_payment_card_type). Add the missing field and try again.  
F03 INVALID FIELD NAME Value is not allowed. See the Response Description field for the invalid field name (e.g. pg_response_description=INVALID FIELD NAME:ecom_payment_card_type). Update the field name and try again.  
F04 INVALID FIELD VALUE Value is not allowed. See the Response Description field for the invalid field value (e.g., pg_response_description=INVALID FIELD VALUE:ecom_payment_card_type). NOTE: An incorrect value was passed for the ecom_payment_card_type; for example VIS instead of VISA. Provide a valid field value and try again.  
F05 DUPLICATE FIELD A field is repeated in the message. See the Response description for the duplicate field (e.g., pg_response_description=DUPLICATE FIELD:ecom_payment_card_type). NOTE: In this example, the field ecom_payment_card_type was passed more than once. Remove the duplicate field and try again.  
F07 CONFLICTING FIELD Field cannot both be present. See the Response Description field for the conflicting field (e.g., pg_response-description = CONFLICTING FIELD: _____)  
U01 MERCH AUTH REVOKED Merchant not allowed to access customer account (EFT only)  
U02 ACCOUNT NOT APPROVED

The customer is either:

  1. Attempting to process an echeck payment from a bank account that does not process payments (such as a Federal Reserve Bank). This scenario is rare.

  2. The customer account is in Forte's "Known Bad Accounts" database (eCheck only). The "Known Bad Accounts" database is a list of checking accounts that have previously returned responses indicating the accounts are invalid (i.e., R02: ACCOUNT CLOSED, R03: NO ACCOUNT, and/or R04: INVALID ACCOUNT NUMBER). Merchants and Partners can request that Forte remove an account from the "Known Bad Accounts" database by calling customer service at 800-337-3060 option 1.

For scenario A, send an echeck sale transaction with the following data:

  • routing_number=064000101
  • account_number=Any account number

For scenario B, sendan echeck sale transaction with the following data:

  • routing_number=021000021
  • account_number=987654321
U03 DAILY TRANS LIMIT Merchant daily limit exceeded (EFT only).  
U04 MONTHLY TRANS LIMIT Merchant monthly limit exceeded (EFT only)  
U05 AVS FAILURE ZIPCODE AVS state/area code check failed. Ensure that you've entered the correct zip code and state abbreviation. Send a regionand postal_code that do not match
U06 AVS FAILURE AREACODE AVS state/area code check failed. Ensure that you've entered the correct area code for the phone number and state abbreviation. Send a regionand phone that do not match
U07 AVS FAILURE EMAIL AVS anonymous email check failed. Ensure the customer's provided email address is not from a free service like hotmail.com or gmail.com. Send an email from a hotmail.com email address.
U08 DAILY VELOCITY Merchant has exceeded the maximum number of transactions per hour, which may indicate a security problem. This error rarely occurs, but if you receive it, contact Forte by calling Customer Service at 800-337-3060 option 1.  
U09 WINDOW VELOCITY Merchant has exceeded the maximum number of transactions per hour, which may indicate a security problem. This error rarely occurs, but if you receive it, contact Forte immediately by calling Customer Service at 800-337-3060 option 1.  
U10 DUPLICATE TRANSACTION The transaction has the same attributes (e.g., authorization amount, payment method, billing address, etc) as another transaction within the time set by the merchant in Dex echeck settings. If you do not set a Duplicate Timeout time, Forte defaults to five minutes. Send the same transaction twice within five minutes
U11 RECUR TRANS NOT FOUND The recurring transaction cannot be found. This error will trigger when a recurring transaction cannot be identified when attempting to suspend, activate, or delete a recurring transaction within a schedule.  
U12 UPDATE NOT ALLOWED

The original transaction is not voidable or captureable. Transactions in the following statuses can be neither voided nor captured:

  • Complete

  • Declined

  • Failed

  • Funded

  • Rejected

  • Settled

  • Settling

  • Unfunded

  • Voided

Send a void transaction for a declined transaction
U13 ORIG TRANS NOT FOUND The original transaction that you are attempting to void or capture cannot be found. Ensure the original_transaction_id included in the request is correct. Send void transaction for the following trace number: 00000000-0000-0000-0000-000000000000
U14 BAD TYPE FOR ORIG TRANS This error occurs when you attempt to void or capture a credit card transaction with the authorization code from an echeck transaction or when you attempt to void or capture an echeck transaction with the authorization code from a credit card transaction. Send a void credit card transaction for an echeck transaction
U15 ALREADY VOIDED
ALREADY CAPTURED
Transaction was previously voided or captured Void the same transaction twice
U18 UPDATE FAILED The void or capture operation failed due to a malformed request. Ensure the authorization number and amount match the original transaction you wish to void or capture. Send a transaction for 19.18 or 1918
U19 INVALID TRN The provided Bank Routing Number is invalid. Ensure you entered the correct routing number and try again. Send echeck transaction with routing_number=123456789
U20 INVALID CREDIT CARD NUMBER The provided credit card number is invalid. Re-enter it and try again. Send a credit card transaction with account_number=1111111111111111
U21 BAD START DATE The start date of the submitted schedule is in the past or is not in MM/DD/YYYY format. Schedule start dates must be today's date or greater. If you do not specify this value, Forte uses today's date. Send a transaction with scheduling data but a start date of 13/1/2008 or 1/1/2001
U22 SWIPE DATA FAILURE The provided swipe data is malformed. This could mean it's missing characters or was not copied over correctly. Re-swipe the card and attempt the transaction again.  
U23 INVALID EXPIRATION DATE The provided expiration date is malformed. Expiration dates must conform to MM/YYYY or MM/YY formatting and be a valid future date. Send Credit Card transaction with expire_month=13
U25 INVALID AMOUNT The authorization amount is negative. Send a transaction for a negative amount
(-1.00)
U26 INVALID DATA The transaction request contains invalid data. This could mean you've included fields that are not part of the objects in the request or fields that are irrelevant to the request. Double-check the request before submitting it again. Send a void transaction with authorization_amount=.
U27 CONV FEE NOT ALLOWED The merchant sent a convenience fee but is not configured to accept one. Only convenience fee merchants can accept convenience fees.  
U28 CONV FEE INCORRECT The merchant is configured for a convenience fee and either did not send one or sent the incorrect amount for the convenience fee. Convenience fees can be either a set amount or a percentage of the authorization amount.  
U29 CONV FEE DECLINED The convenience fee transaction of a SplitCharge service model failed. The SplitCharge service model is where two transactions are processed: one amount is for the principle, and the other is for the service fee. This error triggers when the service fee transaction (i.e., the charge that goes to Forte) fails to process.  
U30 PRINCIPAL DECLINED The principal transaction of a SplitCharge failed. The SplitCharge service model is where two transactions are processed: one amount is for the principle, and the other is for the service fee. This error triggers when the principal amount of the transaction (i.e., the charge that goes to the merchant) fails to process.  
U51 MERCHANT STATUS This error occurs when a merchant attempts an operation that is not available in the sandbox environment (e.g., disputes can only be retrieved in Live). You may not be live because of contract or testing issues. To check your live status, call Forte's Customer Service Team at 800-337-3060 option 1. Send a transaction for a non-live account
U52 TYPE NOT ALLOWED This error occurs when a credit-card-only merchant attempts to send an echeck transaction or when an echeck-only merchant attempts to send a credit card transaction. Check your merchant configuration in Dex to determine what services your configured to use. Send a transaction of a type (credit card or echeck) that the account is not allowed to process
U53 PER TRANS LIMIT The transaction amount exceeds the merchant's maximum transaction limit (echecks only). To proceed with the transaction, the merchant must complete the Over Transaction Limit Notification form and fax it to the number listed on the form. Send a transaction that exceeds the merchant's echeck limit(s)
U54 INVALID MERCHANT CONFIG Your merchant account's configuration requires updating. Call Forte's Customer Service Team at 800-337-3060 option 1.  
U56 CARD TYPE NOT ALLOWED You merchant account does not support the provided credit card brand. Call Customer Service at 800-337-3060 option 1 to update your merchant configuration settings.  
U78 DISALLOWED ACH SEC CODE Merchant accounts are configured for specific SEC codes. Most merchants are configured to support WEB, TEL, PPD, and CCD SEC codes. When a merchant attempts to send a non-configured SEC code (e.g., BOC or ATX), this error is triggered. Send a transaction with SEC code "XYZ"
U80 PREAUTH DECLINE Transaction was declined due to a pre-authorization (Forte Verify) result. Forte Verify is a subscription service that looks up the status of an echeck account to determine if the customer account is valid and in good standing. To view the specific reason why an account was declined, see the preauth_result, preauth_desc, and preauth_neg_report fields in the response. Send a transaction for 19.80 or 1980
U81 PREAUTH TIMEOUT The pre-authorizer is not responding (Forte Verify transactions only). This error indicates that the Forte Verify service has timed out and cannot retrieve a value for the preauth_result. Wait 5-10 minutes before retrying the transaction. Send a transaction for 19.81 or 1981
U82 PREAUTH ERROR Pre-authorizer error (Forte Verify transactions only). This error indicates the Forte Verify pre-authorizer is experiencing a problem. Wait 5-10 minutes before retrying the transaction. If the error persists, submit a ticket to Forte Customer Service. Send a transaction for 19.82 or 1982
U83 AUTH DECLINE The transaction was declined by the authorizer. To determine the reason for the declination, contact the number on the back of the card. Send a transaction for 19.83, 1983, or 1.33
U84 AUTH TIMEOUT The authorizer is not responding. Wait 5-10 minutes before retrying the transaction. Send a transaction for 19.84 or 1984
U85 AUTH ERROR Authorizer error. This error indicates that the authorizer is experiencing a problem. Wait 5-10 minutes before retrying the transaction. If the error persists, submit a ticket to Forte Customer Service. Send a transaction for 19.85 or 1985
U86 AVS FAILURE AUTH The authorizer's address verification services failed. Ensure the billing address for the transaction was correctly submitted and try again. Send a transaction for 19.86 or 1986
U87 AUTH BUSY The authorizing vendor is busy. Wait 5-10 minutes and resubmit the transaction (credit cards only). Send a transaction for 19.87 or 1987
U88 PREAUTH BUSY The verification vendor is busy. Wait 5-10 minutes and resubmit the transaction (Forte Verify transactions only). Send a transaction for 19.88 or 1988
U89 AUTH UNAVAIL The authorization service is unavailable. Wait 5-10 minutes and resubmit the transaction (credit cards only). Send a transaction for 19.89 or 1989
U90 PREAUTH UNAVAIL The verification vendor is busy. Wait 5-10 minutes and resubmit the transaction (Forte Verify transactions only). Send a transaction for 19.90 or 1990
X02 VOIDED A batch transaction was voided. Not available

 

Transaction Return Codes

Forte uses NACHA specification return codes that indicate whether the consumer portion of the payment has been returned or rejected. Some common returns are a closed bank account, invalid bank account, insufficient funds, or a dispute. If a payment is unsuccessful, Forte usually receives the return message from the ACH network within 2 to 4 business days of payment submission. For more information on return codes, please refer to the latest NACHA guide which can be found at http://www.nacha.org (subscription required).

Code Description Comments
R01 INSUFFICIENT FUNDS The balance is not sufficient to cover the value of the transaction
R02 ACCOUNT CLOSED A previously open account has been closed by the action of the customer or the RDFI. Contact the customer for a different bank account. If the customer insists that the account is valid, advise the customer to contact his/her bank.
R03 NO ACCOUNT The account is closed or doesn't match the name submitted
R04 INVALID ACCOUNT NUMBER The account number structure is invalid. The entry may fail the check digit validation or may contain an incorrect number of digits. Check that the account number entered is correct or contact the customer for a different account number. If the customer insists the account is valid, advise the customer to contact his/her bank.
R05 PRENOTE NOT RECEIVED

Pre-notification was not received for a corporate account. Merchant must send a pre-note ($0 transaction).

R06 RETURNED PER ODFI The ODFI has requested that the RDFI return this item due to an erroneous entry. (An erroneous entry can be a duplicate entry, dollar amount mismatch, order payment to or from a receiver different than the receiver, etc)
R07 AUTHORIZATION REVOKED BY CUSTOMER

The consumer, who previously authorized the ACH payment, has revoked authorization from the Originator (must be returned no later than 60 days from settlement date and the customer must sign an affidavit). To resolve this error:

  • 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 canceled.

  • 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.

R08 PAYMENT STOPPED Account holder has stopped payment on this single transaction
R09 UNCOLLECTED FUNDS A sufficient ledger balance exists to satisfy the dollar value of the transaction, but the available balance is below the dollar value of the debt entry. Contact the customer for a different account. Customer must contact his/her bank if uncollected items on this account have already been collected.
R10 NO AUTHORIZATION Account holder advises that the transaction is not authorized
R11 CHECK SAFEKEEPING RETURN Return of a check safekeeping entry return. Please verify the addenda record to know the exact reason for return (i.e., 'exceeds dollar amount', 'stale date', etc.).
R12 BRANCH SOLD

Contact the customer for a different routing number. Customer must contact his/her bank to obtain a new routing number

R13 RDFI NOT QUALIFIED The financial institution is not qualified to participate in ACH or the routing number is incorrect. Contact customer for a different routing number. Customer must contact his/her bank to obtain a new routing number
R14 DECEASED The account holder is deceased
R15 BENEFICIARY DECEASED The beneficiary entitled to benefits is deceased
R16 ACCOUNT FROZEN Funds are unavailable due to action by RDFI or other legal action. Contact the customer for a different account. Customer must contact and work with hid/hrt bank to unfreeze the account.
R17 FILE RECORD EDIT CRITERIA (SPECIFY) Some fields in the request 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. The field(s) causing the processing error is identified in the returned field.
R18 IMPROPER EFFECTIVE ENTRY DATE Entries have been presented prior to the first available processing window for the effective date. NOTE: 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 (or) The Effective Entry Date for a debit entry is more than one banking day after the processing date.
R19 AMOUNT FIELD ERROR Amount field was improperly formatted in the request. NOTE: The Amount field is non-numeric. The Amount field is not zero in a Prenotification, DNE, ENR, Notification of Change, Refused Notification of Change, or zero dollar CCD, CTX, or IAT entry. The Amount field is zero in an entry other than those mentioned above and in a Return and Dishonoured Return. The Amount field is greater than $25,000 for ARC, BOC, POP Entries.
R20 NON-TRANSACTION ACCOUNT Policies/regulations restrict activity on this account. Contact the customer for a different account.
R21 INVALID COMPANY ID NUMBER The company ID information is not valid. This code normally returns for a customer-initiated entries (CIE).
R22 INVALID INDIVIDUAL ID NUMBER The individual ID used by receiver is incorrect. This code normally returns for customer-initiated entries (CIE).
R23 PAYMENT REFUSED

The account holder refuses the transaction because the amount is inaccurate for another legal reason

R24 DUPLICATE ENTRY The transaction appears to be a duplicate item. 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).
R25 ADDENDA RECORD

The addenda record information was improperly formatted in the request:

  • Addenda Type Code is invalid, out of sequence, or missing,

  • Number of Addenda Records exceeds allowable maximum.

  • Addenda Sequence Number is invalid.

R26 MANDATORY ERROR The transaction is missing data from a mandatory field. Mandatory fields vary depending on the type of transaction.
R27 TRACE NUMBER ERROR The Trace Number in the original entry is not valid for the return entry or the Addenda Trace Numbers do not correspond with entry detail record.
R28 INVALID TRN The Transit Routing Number is invalid
R29 CORPORATE NOT AUTHORIZED The corporate receiver has notified RDFI that the Corp entry is not authorized
R30 RDFI NOT PARTICIPANT IN CHECK TRUNCATION PROGRAM The receiving financial institution does not participate in the automated check safekeeping application.
R31 ODFI PERMITS LATE RETURN The RDFI rejected an entry that the ODFI had accepted (applies to CCD and CTX only). If an RDFI receives written notification from a Receiver that a CCD or CTX entry that was debited to the Receiver's account was, in whole or in part, not authorized by the Receiver, the RDFI may transmit a Return Entry to the ODFI after the time for return has expired, provided that the ODFI agrees, either verbally or in writing, to accept the late Return Entry.
R32 RDFI NON-SETTLEMENT The RDFI is not able to settle the entry. Customer to contact their bank to resolve the issue.
R33 RETURN OF XCK ENTRY The RDFI had decided to return a Destroyed Check Entry (XCK). An XCK return can be initiated by midnight of the 60th day following the settlement date of the entry.
R34 LIMITED PARTICIPATION RDFI A federal or state ACH Network Supervisor has limited the RDFI's participation. The merchant must obtain a different payment method from the customer. The customer must contact his/her bank to resolve the issue.
R35 RETURN OF IMPROPER DEBIT ENTRY A user or customer attempted to initiate an ACH debit for a customer-initiated entry (CIE), which is not permitted (except for reversals).
R36 RETURN OF IMPROPER CREDIT ENTRY ACH refund entries (with the exception of reversals) are not permitted for use with the WEB code.
R37 SOURCE DOCUMENT PRESENTED FOR PAYMENT The source document to which (ACH entry) an ARC, BOC, or POP Entry relates has been presented for payment. For Example, the source document used for entry was not an eligible source document, the check that was used as a source document for the entry was paid by RDFI, etc.
R38 STOP PAYMENT ON SOURCE DOCUMENT The RDFI has determined a Stop Payment Order has been placed on the source document to which the ARC or BOC entry relates.
R39 IMPROPER SOURCE DOCUMENT The RDFI has determined that the source document (share draft or check) used for an ARC, BOC or POP entry is not eligible for conversion, or the share draft has already been paid as a normal check posting.
R40 RETURN OF ENR ENTRY BY FEDERAL GOVERNMENT AGENCY (ENR ONLY) The Federal Government Agency has decided to return an Automated Enrollment entry (ENR). This return reason code only applies to ENR entries.
R41 INVALID TRANSACTION CODE (ENR ONLY) Either the transaction code included in Field 3 of the Addenda Record does not conform to the ACH Record Format Specifications, or the transaction code is not appropriate for Automated Enrollment entries.
R42 ROUTING NUMBER/CHECK DIGIT ERROR (ENR ONLY) The Routing Number and Check Digit included in Field 3 of the Addenda Record is either not a valid number or does not conform to the Modulus 10 formula.
R43 INVALID DFI ACCOUNT NUMBER (ENR ONLY) The customer's account number included in Field 3 of the Addenda Record must include at least one alphanumeric character.
R44 INVALID INDIVIDUAL ID NUMBER (ENR ONLY) The Individual ID Number provided in Field 3 of the Addenda Record does not match a corresponding ID number in the Federal Government Agency’s records.
R45 INVALID INDIVIDUAL NAME / COMPANY NAME (ENR ONLY) The customer name provided in Field 3 of the Addenda Record either does not match a corresponding name in the Federal Government Agency’s records or does not include at least one alphanumeric character.
R46 INVALID REPRESENTATIVE PAYEE INDICATOR (ENR ONLY) The Representative Payee Indicator Code included in Field 3 of the Addenda Record has been omitted or is not consistent with the Federal Government Agency’s records.
R47 DUPLICATE ENROLLMENT (ENR ONLY) The entry is a duplicate of an Automated Enrollment entry (ENR) previously initiated by a participant in the automated enrollment program.
R50 STATE LAW AFFECTING RCK ACCEPTANCE This code is only for Re-Presented Check Entries (RCK). The RDFI is located in a state that has not accepted and adopted the Uniform Commercial Code and has not revised its consumer agreements to allow for electronic presentment, OR the RDFI is in a state that requires all canceled checks to be returned in the consumer statement.
R51 NOTICE NOT PROVIDED/
SIGNATURE NOT AUTHENTIC/
ITEM ALTERED/INELIGIBLE FOR
CONVERSION (ADJUSTMENT ENTRIES)
This code is primarily for Re-Presented Check Entries (RCK). The item is ineligible, or the Originator did not provide notice, or all signatures on the item are not authentic or authorized, or the item has been altered.
R52 STOP PAY ON ITEM (ADJUSTMENT ENTRIES This code is primarily for Re-Presented Check Entries (RCK). The RDFI has determined that a Stop Payment Order has been placed on the item.
R53 ITEM AND ACH ENTRY PRESENTED FOR PAYMENT This code is primarily for Re-Presented Check Entries (RCK). In addition to an RCK entry, the item to which the RCK entry relates has also been presented for payment.
R61 MISROUTED RETURN The financial institution preparing the return entry (the RDFI of the original entry) has placed the incorrect Routing Number in the Receiving DFI Identification field (positions 04-12— including Check Digit—of the Entry Detail Record).
R62 INCORRECT TRACE NUMBER The Trace Number found in positions 07-21 in the Addenda Record of the return entry is different from the trace number of the original entry.
R63 INCORRECT DOLLAR AMOUNT The dollar amount in the Entry Detail Record of the return entry is different from the dollar amount of the original entry.
R64 INCORRECT INDIVIDUAL IDENTIFICATION The Individual Identification Number reflected in the Entry Detail Record of the return entry is different from the Individual Identification Number/Identification Number used in the original entry.
R65 INCORRECT TRANSACTION CODE The Transaction Code in the Entry Detail Record of the return entry is not the return equivalent of the Transaction Code in the original entry. All entries must be returned as received: e.g., credit as credit, debit as debit, demand as demand, savings as savings.)
R66 INCORRECT COMPANY IDENTIFICATION The Company Identification number used in the Company/Batch Header Record of the return entry is different from the Company Identification number used in the original entry.
R67 DUPLICATE RETURN The ODFI has received more than one return for the same entry.
R68 UNTIMELY RETURN The Return Entry has not been sent within the timeframe established by these rules. The ODFI must transmit a Dishonored Return Entry to its ACH Operator within five banking days after the Settlement Date of the Return Entry.
R69 FIELD ERRORS Two or more of the following fields—Original Entry Trace Number, Amount, Individual Identification Number/Identification Number, Company Identification, and/or Transaction Code—are incorrect.
R70 PERMISSIBLE RETURN ENTRY NOT ACCEPTED The ODFI has received a CCD or CTX return entry identified by the RDFI as being returned with the permission of the ODFI, but the ODFI has not agreed to accept the entry. This code may be used only to dishonor a return containing an R31 return reason code.
R71 MISROUTED DISHONOR RETURN The ODFI misrouted the Dishonored Return entry to the wrong RDFI using an incorrect routing/transit number.
R72 UNTIMELY DISHONOR RETURN The ODFI did not submit the Dishonored Return entry within the five-day deadline.
R73 TIMELY ORIGINAL RETURN The RDFI certifies that the original return entry was submitted by the applicable deadline.
R74 CORRECTED RETURN The RDFI is correcting a previous return entry that was dishonored using return code R69, because it contained incomplete or incorrect information: DI Account Number, Original Entry Trace Number, Amount, Individual Identification Number/Identification Number, Company Identification, Effective Entry Date and/or Transaction Code.
R75 ORIGINAL RETURN NOT A DUPLICATE The original return entry was not a duplicate of an entry previously returned by the ODFI. This code may be used by the RDFI to contest an entry dishonored by the ODFI using return code R67 (duplicate return).
R76 NO ERRORS FOUND The original return entry did not contain the errors indicated by the ODFI in the dishonored return entry bearing return code R69 (field errors).
R80 CROSS-BORDER PAYMENT CODING ERROR

The cross-border entry is being returned due to one or more of the following conditions:

  • Invalid Foreign Exchange Indicator

  • Invalid ISO Originating Currency Code

  • Invalid ISO Destination Currency Code

  • Invalid ISO Destination Country Code

  • Invalid Transaction Type Code

R81 NON-PARTICIPANT IN CROSS-BORDER PROGRAM The cross-border entry is being returned because the Originating Gateway Operator does not have an agreement with the ODFI to process cross-border entries.
R82 INVALID FOREIGN RECEIVING DFI IDENTIFICATION The reference used to identify the Foreign Receiving DFI of an outbound cross-border entry is invalid.
R83 FOREIGN RECEIVING DFI UNABLE TO SETTLE The cross-border entry is being returned due to settlement problems in the foreign payment system.
R84 ENTRY NOT PROCESSED BY GATEWAY

For outbound International ACH Transaction (IAT) entries, the entry has not been processed and is being returned at the gateway’s discretion because either:

  • The processing of such an entry may expose the gateway to excessive risk.

  • The foreign payment system does not support the functions needed to process the transaction.

R95 OVER LIMIT This transaction is over your authorized limit.
R96 ACCOUNT ON HOLD This company account is on hold.
R97 RDFI DOES NOT PARTICIPATE The RDFI does not allow this type of transaction.
R98 INVALID PASSWORD The password supplied was invalid.
R99 DECLINED UNPAID ITEMS This account or ID has been declined due to unpaid items.

 

Transaction Settlement Codes

Merchants can configure their account to make up to 2 additional recollect attempts. For example, if a check is returned for insufficient funds, a merchant may configure recollection attempts on the following 1st and 15th of the month.

Code Description Comments
S01 FUNDED (1st attempt) Transaction funded on the first attempt.
S02 FUNDED (2nd attempt) Transaction funded on the second attempt.
S03 FUNDED (3rd attempt) Transaction funded on the third attempt.
X02 VOIDED A batch transaction was voided.
X03 REJECTED The transaction was rejected for settlement.