Support Services

Transaction and Settlement 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. 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:

StatusDescription
Authorized

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

CompleteeCheck verification was performed and the results were positive (POS) or unknown (UNK).
DeclinedTransaction was declined for reasons detailed in Response Code and Response Description.
FailedeCheck verification was performed and the results were negative (NEG) or the transaction failed for reasons detailed in the Response Code and Response Description.
FundedeCheck item was funded to or from the merchant's bank account.
ReadyTransaction was received and is awaiting origination (echeck) or settlement (credit card).
RejectedeCheck item has been rejected or returned by the client's financial institution. Merchant will not be funded for the item.
ReviewTransaction was unable to be settled due to a merchant configuration issue. Please contact Customer Service to resolve (1-469-675-9920 x1).
SettledCredit Card item has been funded to the merchant's bank account.
SettlingeCheck item has been originated and Forte is awaiting the settlement results.
UnfundedPreviously funded echeck item has been returned and funding was reversed.
VoidedThe 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. 

CodeDescriptionCommentsTest Parameters
A01APPROVEDTransaction approved/completed 
A03PARTIAL AUTHORIZATIONTransaction approved for a partial authorization (CC only)Not available
U02ACCOUNT NOT APPROVEDCustomer 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
U02TRN NOT APPROVEDRouting 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
U03DAILY TRANS LIMITMerchant daily limit exceeded (EFT only)Not available
U04MONTHLY TRANS LIMITMerchant monthly limit exceeded (EFT only)Not available
U05AVS FAILURE ZIPCODEAVS state/zip code check failedSend a regionand postal_code that do not match
U06AVS FAILURE AREACODEAVS state/area code check failedSend a regionand postal_code that do not match
U07AVS FAILURE EMAILAVS anonymous email check failedSend an email from a hotmail.com email address.
U08DAILY VELOCITYMerchant 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. 
U09WINDOW VELOCITYMerchant 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. 
U10DUPLICATE TRANSACTIONTransaction has the same attributes as another transaction within the time set by the merchantSend the same transaction twice within five minutes
U11RECUR TRANS NOT FOUNDTransaction types 40-42 onlyNot available
U12UPDATE NOT ALLOWEDOriginal transaction not voidable or captureableSend a void transaction for a declined transaction
U13ORIG TRANS NOT FOUNDTransaction to be voided or captured not foundSend void transaction for the following trace number: 00000000-0000-0000-0000-000000000000
U14BAD TYPE FOR ORIG TRANSVoid/capture and original transaction types do not agree (CC/EFT)Send a void credit card transaction for an echeck transaction
U15ALREADY VOIDED
ALREADY CAPTURED
Transaction was previously voided or capturedVoid the same transaction twice
U18UPDATE FAILEDVoid or Capture failedSend a transaction for 19.18 or 1918
U19INVALID TRNAccount ABA number is invalidSend echeck transaction with routing_number=123456789
U20INVALID CREDIT CARD NUMBERCredit card number is invalidSend a credit card transaction with account_number=1111111111111111
U21BAD START DATEDate is malformedSend a transaction with scheduling data but a start date of 13/1/2008 or 1/1/2001
U22SWIPE DATA FAILURESwipe data is malformed 
U23INVALID EXPIRATION DATEMalformed expiration dateSend Credit Card transaction with expire_month=13
U25INVALID AMOUNTNegative amountSend a transaction for a negative amount
(-1.00)
U26INVALID DATAInvalid data present in transactionSend a void transaction with authorization_amount=.
U27CONV FEE NOT ALLOWEDMerchant sent a convenience fee but is not configured to accept one 
U28CONV FEE INCORRECTMerchant configured for convenience fee but did not send one 
U29CONV FEE DECLINEDConvenience fee transaction failed - SplitCharge model only 
U30PRINCIPAL DECLINEDPrincipal transaction failed - SplitCharge model only 
U51MERCHANT STATUSMerchant is not "live"Send a transaction for a non-live account
U52TYPE NOT ALLOWEDMerchant 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
U53PER TRANS LIMITTransaction amount exceeds merchant's per transaction limit (EFTs only)Send a transaction that exceeds the merchant's echeck limit(s)
U54INVALID MERCHANT CONFIGMerchant's configuration requires updating - call Customer SupportSend a transaction for 19.54 or 1954
U80PREAUTH DECLINETransaction was declined due to preauthorization (Forte Verify) resultSend a transaction for 19.80 or 1980
U81PREAUTH TIMEOUTPreauthorizer not responding (verify transactions only)Send a transaction for 19.81 or 1981
U82PREAUTH ERRORPreauthorizer error (verify transactions only)Send a transaction for 19.82 or 1982
U83AUTH DECLINETransaction was declined due to authorizer declinationSend a transaction for 19.83, 1983, or 1.33
U84AUTH TIMEOUTAuthorizer not respondingSend a transaction for 19.84 or 1984
U85AUTH ERRORAuthorizer errorSend a transaction for 19.85 or 1985
U86AVS FAILURE AUTHAuthorizer AVS check failedSend a transaction for 19.86 or 1986
U87AUTH BUSYAuthorizing vendor busy, may be resubmitted (CC only)Send a transaction for 19.87 or 1987
U88PREAUTH BUSYVerification vendor busy, may be resubmitted (type 26 only)Send a transaction for 19.88 or 1988
U89AUTH UNAVAILVendor service unavailable (CC only)Send a transaction for 19.89 or 1989
U90PREAUTH UNAVAILVerification service unavailable (type 26 only)Send a transaction for 19.90 or 1990
X02VOIDEDA batch transaction was voidedNot available
F01MANDATORY FIELD IS MISSINGRequired field is missing 
F03INVALID FIELD NAMEValue is not allowed 
F04INVALID FIELD VALUEValue is not allowed 
F05DUPLICATE FIELDField is repeated in message 
F07CONFLICTING FIELDFields cannot both be present 
E10INVALID MERCH OR PASSWDMerchant ID or processing password is incorrect 
E20MERCHANT TIMEOUTTransaction message not received (I/O flush required?) 
E55INVALID TOKENSpecified token was invalid, could not be located or may have been deleted 
Client Token TransactionsFor 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 TransactionsFor payment token transactions where no client token is specified, the payment token must be clientless. 
Both Client and Payment Tokens PresentFor transactions with client and payment tokens, the specified payment token is not associated with the client or is clientless. 
E90BAD MERCH IP ADDROrigination IP is not on merchant's approved IP list 
E99INTERNAL ERRORAn 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). 

CodeDescriptionDetails
R01INSUFFICIENT FUNDS The balance is not sufficient to cover the value of the transaction
R02ACCOUNT CLOSEDA previously open account has been closed
R03NO ACCOUNTThe account is closed or doesn't match the name submitted
R04INVALID ACCOUNT NUMBERThe account number structure is invalid
R05PRENOTE NOT RECEIVEDPre-notification was not received
R06RETURNED PER ODFIODFI has requested RDFI to return this item
R07AUTHORIZATION REVOKEDAccount holder has revoked the company's authorization
R08PAYMENT STOPPEDAccount holder has stopped payment on this single transaction
R09UNCOLLECTED FUNDSBalance is sufficient, but can't be released until uncollected items are collected
R10NO AUTHORIZATIONAccount holder advises that the transaction is not authorized
R11CHECK SAFEKEEPING RETURNReturn of a check safekeeping entry return
R12BRANCH SOLDThe account is at a branch that was sold to another financial institution
R13RDFI NOT QUALIFIEDRDFI not qualified to participate
R14DECEASEDThe account holder is deceased
R15BENEFICIARY DECEASEDThe beneficiary entitled to benefits is deceased
R16ACCOUNT FROZENFunds are unavailable due to action by RDFI or other legal action
R17FILE 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.
R18IMPROPER EFFECTIVE ENTRY DATEEntries have been presented prior to the first available processing window for the effective date.
R19AMOUNT FIELD ERRORThe Amount field was improperly formatted in the request.
R20NON-TRANSACTION ACCOUNTPolicies/regulations restrict activity to this account
R21INVALID COMPANY ID NUMBERThe company ID information is not valid. This code normally returns for a customer-initiated entries (CIE).
R22INVALID INDIVIDUAL ID NUMBERThe individual ID used by receiver is incorrect. This code normally returns for customer-initiated entries (CIE).
R23PAYMENT REFUSEDThe account holder refuses the transaction because the amount is inaccurate for another legal reason
R24DUPLICATE ENTRYThe transaction appears to be a duplicate item
R25ADDENDA ERRORThe addenda record information was improperly formatted in the request.
R26MANDATORY ERRORThe transaction is missing data from a mandatory field
R27TRACE NUMBER ERRORThe 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.
R28INVALID TRNThe Transit Routing Number is invalid
R29CORPORATE NOT AUTHORIZEDThe corporate receiver has notified RDFI that the Corp entry is not authorized
R30RDFI NOT PARTICIPANT IN CHECK TRUNCATION PROGRAMThe receiving financial institution does not participate in the automated check safekeeping application.
R31ODFI PERMITS LATE RETURNRDFI rejected an entry that the ODFI had accepted (applies to CCD and CTX only)
R32RDFI NON-SETTLEMENTThe RDFI cannot settle the entry.
R33RETURN OF XCK ENTRYThe 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.
R34LIMITED PARTICIPATION RDFIA federal or state ACH Network Supervisor has limited the RDFI's participation.
R35RETRUN OF IMPROPER DEBIT ENTRYA user or customer attempted to initiate an ACH debit for a customer-initiated entry (CIE), which is not permitted (except for reversals).
R36RETURN OF IMPROPER CREDIT ENTRYACH refund entries (with the exception of reversals) are not permitted for use with the WEB code.
R37SOURCE DOCUMENT PRESENTED FOR PAYMENTThe source document to which an ACH entry relates has been presented for payment.
R38STOP PAYMENT ON SOURCE DOCUMENTThe RDFI has determined a Stop Payment Order has been placed on the source document to which the ARC or BOC entry relates.
R39IMPROPER SOURCE DOCUMENTThe 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.
R40Return 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.
R41INVALID 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.
R42ROUTING 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.
R43INVALID 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.
R44INVALID 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.
R45INVALID 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.
R46INVALID 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.
R47DUPLICATE ENROLLMENT (ENR ONLY)The entry is a duplicate of an Automated Enrollment entry (ENR) previously initiated by a participant in the automated enrollment program.
R50STATE LAW AFFECTING RCK ACCEPTANCEThis 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.
R51NOTICE 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.
R52STOP PAY ON ITEM (ADJUSTMENT ENTRIESThis code is primarily for Re-Presented Check Entries (RCK). The RDFI has determined that a Stop Payment Order has been placed on the item.
R53ITEM AND ACH ENTRY PRESENTED FOR PAYMENTThis 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.
R56INVALID TRANSACTION DATEThe date specified is invalid
R57STALE DATEThe transaction is too old for processing
R61MISROUTED RETURNThe 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).
R62INCORRECT TRACE NUMBERThe 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.
R63INCORRECT DOLLAR AMOUNTThe dollar amount in the Entry Detail Record of the return entry is different from the dollar amount of the original entry.
R64INCORRECT INDIVIDUAL IDENTIFICATIONThe 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.
R65INCORRECT TRANSACTION CODEThe 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.)
R66INCORRECT COMPANY IDENTIFICATIONThe 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.
R67DUPLICATE RETURNThe ODFI has received more than one return for the same entry.
R68UNTIMELY RETURNThe return entry has not been sent within the timeframe established by these rules.
R69FIELD 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.

R70PERMISSIBLE RETURN ENTRY NOT ACCEPTEDThe 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.
R71MISROUTED DISHONOR RETURNThe ODFI misrouted the Dishonored Return entry to the wrong RDFI using an incorrect routing/transit number.
R72UNTIMELY DISHONOR RETURNThe ODFI did not submit the Dishonored Return entry within the five-day deadline.
R73TIMELY ORIGINAL RETURNThe RDFI certifies that the original return entry was submitted by the applicable deadline.
R74CORRECTED RETURNThe RDFI is correcting a previous return entry that was dishonored using return code R69, because it contained incomplete or incorrect information.
R75ORIGINAL RETURN NOT A DUPLICATEThe 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).
R76NO ERRORS FOUNDThe original return entry did not contain the errors indicated by the ODFI in the dishonored return entry bearing return code R69 (field errors).
R80CROSS-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
R81NON-PARTICIPANT IN CROSS-BORDER PROGRAMThe cross-border entry is being returned because the Originating Gateway Operator does not have an agreement with the ODFI to process cross-border entries.
R82INVALID FOREIGN RECEIVING DFI IDENTIFICATIONThe reference used to identify the Foreign Receiving DFI of an outbound cross-border entry is invalid.
R83FOREIGN RECEIVING DFI UNABLE TO SETTLEThe cross-border entry is being returned due to settlement problems in the foreign payment system.
R84ENTRY 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
R95OVER LIMITThis transaction is over your authorized limit
R96ACCOUNT ON HOLDThis company account is on hold
R97RDFI DOES NOT PARTICIPATERDFI does not allow this type of transaction
R98INVALID PASSWORDThe password supplied was invalid
R99DECLINED UNPAID ITEMSThis 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. 

CodeDescriptionComments
S01FUNDED (1st attempt)Transaction funded on the first attempt.
S02FUNDED (2nd attempt)Transaction funded on the second attempt.
S03FUNDED (3rd attempt)Transaction funded on the third attempt.

Did you find it helpful? Yes No

Send feedback
Sorry we couldn't be helpful. Help us improve this article with your feedback.