Transaction Status Codes
The status of a transaction will change depending on the following factors:
- Was the transaction accepted or rejected for processing?
- Where is the transaction in the Transaction Lifecycle?
The transaction lifecycle for a typical ACH transaction is Ready > Settling > Funded. The lifecycle 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 (credit card only) | |
U02 | ACCOUNT NOT APPROVED | The customer is either:
| For scenario A, send an echeck sale transaction with the following data:
For scenario B, send an echeck sale transaction with the following data:
|
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 region and 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 region and 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:
| 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 a credit card transaction with the authorization code from an echeck transaction or when you attempt to void an echeck transaction with the authorization code from a credit card transaction. | Send a void credit card transaction for an echeck transaction |
U15 | ALREADY VOIDEDALREADY CAPTURED | The 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 and then attempt to void it for $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 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. | |
| 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 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 | Details |
|---|---|---|
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. Transactions can only be originated with open accounts. |
R03 | NO ACCOUNT | The account is closed or doesn't match the name submitted |
R04 | INVALID ACCOUNT NUMBER | The account number structure is not valid. The entry may fail the check-digit validation or may contain an incorrect number of digits. Obtain the correct bank account number. Submit a new payment using the corrected bank account number. |
R05 | UNAUTHORIZED DEBIT ENTRY | Account number structure not valid: entry may fail check digit validation or may contain incorrect number of digits. NOTE: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. To resolve this error:
|
R06 | RETURNED PER ODFI | 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 Five (Return, Adjustment, Correction, and Acknowledgment of Entries and Entry Information) of these Rules. If you receive this error, contact Forte Customer Service at 800-337-3060 option 1. |
R07 | AUTHORIZATION REVOKED | 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:
|
R08 | PAYMENT STOPPED | Account holder has stopped payment on this single transaction |
R09 | UNCOLLECTED FUNDS | A 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. To resolve this error you can attempt the transaction again (you will need to re-enter it as a new transaction) up to two times within 30 days of the original authorization date. |
R10 | NO AUTHORIZATION | Account holder advises that the transaction is not authorized |
R11 | CHECK SAFEKEEPING RETURN | This error is used by the RDFI to return an entry for which the Originator and Receiver have a relationship, and an authorization to debit exists, but there is an error or defect in the payment such that the entry does not conform to the terms of the authorization. (i.e., “an incorrect amount,” “payment was debited earlier than authorized” ). To resolve this issue, the originator can correct the underlying error, (e.g., correct the amount, the date, and resubmit the corrected entry as a new entry). No new authorization is needed from the customer. The new corrected entry must be submitted and originated within 60 days of the settlement date of the R11 Return Entry. |
R12 | BRANCH SOLD | The account is at a branch that was sold to another financial institution. A financial institution may continue to receive entries destined for an account at a branch that has been sold to another financial institution. Since the RDFI no longer maintains the account and is unable to post the entry, it should return the entry to the ODFI. To resolve this error:
|
R13 | RDFI NOT QUALIFIED | The financial institution is not qualified to participate in ACH or the routing number is incorrect. Confirm 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. |
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. To resolve this error you can obtain a different form of payment. You will not be able to process transactions using this bank account until it is unfrozen. |
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. |
R20 | NON-TRANSACTION ACCOUNT | 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. |
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 |
R25 | ADDENDA ERROR | The addenda record information was improperly formatted in the request. |
R26 | MANDATORY ERROR | The transaction is missing data from a mandatory field |
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. |
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. |
R35 | RETRUN 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 an ACH entry relates has been presented for payment. |
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 (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. |
R56 | INVALID TRANSACTION DATE | The date specified is invalid |
R57 | STALE DATE | The transaction is too old for processing |
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. |
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. |
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:
|
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:
|
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 | 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. |
| X03 | REJECTED | The transaction was rejected for settlement. The processor had a settlement issue that has been resolved. |