Transaction Codes

Transaction Status Codes

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

Was the transaction accepted or rejected for processing?
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)	Not available
`U02`	`ACCOUNT NOT APPROVED`	Customer account is in Forte's "known bad" account list (EFT only)	Send echeck sale transaction with the following data: `routing_number=021000021` `account_number=987654321`
`U02`	`TRN NOT APPROVED`	Routing number passes checksum test but not valid for ACH	Send echeck sale transaction with the following data: `routing_number=064000101` `account_number=`Any account number
`U03`	`DAILY TRANS LIMIT`	Merchant daily limit exceeded (EFT only)	Not available
`U04`	`MONTHLY TRANS LIMIT`	Merchant monthly limit exceeded (EFT only)	Not available
`U05`	`AVS FAILURE ZIPCODE`	AVS state/zip code check failed	Send a `region`and `postal_code` that do not match
`U06`	`AVS FAILURE AREACODE`	AVS state/area code check failed	Send a `region`and `postal_code` that do not match
`U07`	`AVS FAILURE EMAIL`	AVS anonymous email check failed	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 immediately.
`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.
`U10`	`DUPLICATE TRANSACTION`	Transaction has the same attributes as another transaction within the time set by the merchant	Send the same transaction twice within five minutes
`U11`	`RECUR TRANS NOT FOUND`	Transaction types 40-42 only	Not available
`U12`	`UPDATE NOT ALLOWED`	Original transaction not voidable or captureable	Send a void transaction for a declined transaction
`U13`	`ORIG TRANS NOT FOUND`	Transaction to be voided or captured not found	Send void transaction for the following trace number: `00000000-0000-0000-0000-000000000000`
`U14`	`BAD TYPE FOR ORIG TRANS`	Void/capture and original transaction types do not agree (CC/EFT)	Send a void credit card transaction for an echeck transaction
`U15`	`ALREADY VOIDED/CAPTURED`	Transaction was previously voided or captured	Void the same transaction twice
`U18`	`UPDATE FAILED`	Void or Capture failed	Send a transaction for `19.18` or `1918`
`U19`	`INVALID TRN`	Account ABA number is invalid	Send echeck transaction with `routing_number=123456789`
`U20`	`INVALID CREDIT CARD NUMBER`	Credit card number is invalid	Send a credit card transaction with `account_number=1111111111111111`
`U21`	`BAD START DATE`	Date is malformed	Send a transaction with scheduling data but a start date of `13/1/2008` or `1/1/2001`
`U22`	`SWIPE DATA FAILURE`	Swipe data is malformed
`U23`	`INVALID EXPIRATION DATE`	Malformed expiration date	Send Credit Card transaction with `expire_month=13`
`U25`	`INVALID AMOUNT`	Negative amount	Send a transaction for a negative amount (`-1.00`)
`U26`	`INVALID DATA`	Invalid data present in transaction	Send a void transaction with `authorization_amount=.`
`U27`	`CONV FEE NOT ALLOWED`	Merchant sent a convenience fee but is not configured to accept one
`U28`	`CONV FEE INCORRECT`	Merchant configured for convenience fee but did not send one
`U29`	`CONV FEE DECLINED`	Convenience fee transaction failed - SplitCharge model only
`U30`	`PRINCIPAL DECLINED`	Principal transaction failed - SplitCharge model only
`U51`	`MERCHANT STATUS`	Merchant is not "live"	Send a transaction for a non-live `account`
`U52`	`TYPE NOT ALLOWED`	Merchant not approved for transaction type (CC or EFT)	Send a transaction of a type (credit card or echeck) that the account is not allowed to process
`U53`	`PER TRANS LIMIT`	Transaction amount exceeds merchant's per transaction limit (EFTs only)	Send a transaction that exceeds the merchant's echeck limit(s)
`U54`	`INVALID MERCHANT CONFIG`	Merchant's configuration requires updating - call Customer Support	Send a transaction for `19.54` or `1954`
`U80`	`PREAUTH DECLINE`	Transaction was declined due to preauthorization (Forte Verify) result	Send a transaction for `19.80` or `1980`
`U81`	`PREAUTH TIMEOUT`	Preauthorizer not responding (verify transactions only)	Send a transaction for `19.81` or `1981`
`U82`	`PREAUTH ERROR`	Preauthorizer error (verify transactions only)	Send a transaction for `19.82` or `1982`
`U83`	`AUTH DECLINE`	Transaction was declined due to authorizer declination	Send a transaction for `19.83`, `1983`, or `1.33`
`U84`	`AUTH TIMEOUT`	Authorizer not responding	Send a transaction for `19.84` or `1984`
`U85`	`AUTH ERROR`	Authorizer error	Send a transaction for `19.85` or `1985`
`U86`	`AVS FAILURE AUTH`	Authorizer AVS check failed	Send a transaction for `19.86` or `1986`
`U87`	`AUTH BUSY`	Authorizing vendor busy, may be resubmitted (CC only)	Send a transaction for `19.87` or `1987`
`U88`	`PREAUTH BUSY`	Verification vendor busy, may be resubmitted (type 26 only)	Send a transaction for `19.88` or `1988`
`U89`	`AUTH UNAVAIL`	Vendor service unavailable (CC only)	Send a transaction for `19.89` or `1989`
`U90`	`PREAUTH UNAVAIL`	Verification service unavailable (type 26 only)	Send a transaction for `19.90` or `1990`
`X02`	`VOIDED`	A batch transaction was voided	Not available
`F01`	`MANDATORY FIELD IS MISSING`	Required field is missing
`F03`	`INVALID FIELD NAME`	Value is not allowed
`F04`	`INVALID FIELD VALUE`	Value is not allowed
`F05`	`DUPLICATE FIELD`	Field is repeated in message
`F07`	`CONFLICTING FIELD`	Fields cannot both be present
`E10`	`INVALID MERCH OR PASSWD`	Merchant ID or processing password is incorrect
`E20`	`MERCHANT TIMEOUT`	Transaction message not received (I/O flush required?)
`E55`	`INVALID TOKEN`	Specified token was invalid, could not be located or may have been deleted
	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.
	Payment Token Transactions	For payment token transactions where no client token is specified, the payment token must be clientless.
	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.
`E90`	`BAD MERCH IP ADDR`	Origination IP is not on merchant's approved IP list
`E99`	`INTERNAL ERROR`	An unspecified error has occurred

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
`R03`	`NO ACCOUNT`	The account is closed or doesn't match the name submitted
`R04`	`INVALID ACCOUNT NUMBER`	The account number structure is invalid
`R05`	`PRENOTE NOT RECEIVED`	Pre-notification was not received
`R06`	`RETURNED PER ODFI`	ODFI has requested RDFI to return this item
`R07`	`AUTHORIZATION REVOKED`	Account holder has revoked the company's authorization
`R08`	`PAYMENT STOPPED`	Account holder has stopped payment on this single transaction
`R09`	`UNCOLLECTED FUNDS`	Balance is sufficient, but can't be released until uncollected items are collected
`R10`	`NO AUTHORIZATION`	Account holder advises that the transaction is not authorized
`R11`	`CHECK SAFEKEEPING RETURN`	Return of a check safekeeping entry return
`R12`	`BRANCH SOLD`	The account is at a branch that was sold to another financial institution
`R13`	`RDFI NOT QUALIFIED`	RDFI not qualified to participate
`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
`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.
`R18`	`IMPROPER EFFECTIVE ENTRY DATE`	Entries have been presented prior to the first available processing window for the effective date.
`R19`	`AMOUNT FIELD ERROR`	The Amount field was improperly formatted in the request.
`R20`	`NON-TRANSACTION ACCOUNT`	Policies/regulations restrict activity to this 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
`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.
`R31`	`ODFI PERMITS LATE RETURN`	RDFI rejected an entry that the ODFI had accepted (applies to CCD and CTX only)
`R32`	`RDFI NON-SETTLEMENT`	The RDFI cannot settle the entry.
`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: Invalid Foreign Exchange Indicator Invalid ISO Originating Currency Code Invalid ISO Destination Currency Code Iinvalid 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`	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.