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
Code | Description | Comments | Test Parameters |
Approved | |||
A01 | APPROVED | Transaction approved/completed | |
A03 | PARTIAL AUTHORIZATION | Transaction approved for a partial authorization (CC only) | Not available |
A05 | OVERALL MATCH | The business name or full name provided exactly or closely matches the database record | |
A06 | PARTIAL MATCH | The full name or business name conditionally (partially) matches the database record | |
Declined | |||
N01 | NO INFO | The Routing and account numbers are found in the database, but no names are associated with these. | |
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 |
TRN NOT APPROVED | Routing number passes checksum test but not valid for ACH | Send echeck sale transaction with the following data: - routing_number=064000101 | |
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 regionand postal_code that do not match |
U06 | AVS FAILURE AREACODE | AVS state/area code check failed | Send a regionand 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 |
U16 | SETTLEMENT PROCESS STARTED | Void attempted after the start of the settlement process | |
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 |
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 | |
U32 | INVALID WALLET TYPE | Invalid Wallet Type present in the transaction | Send a transaction with wallet type values out of ApplePay, GooglePay or SamsungPay |
U33 | INVALID WALLET SOURCE | Wallet source is invalid | Send a transaction with wallet source values other then InApp, Web |
U34 | INVALID WALLET CRYPTOGRAM | Wallet cryptogram in invalid. Length of cryptograms for different card brands:
Amex <= 56 characters | Send a transaction with digital wallet cryptogram. Where Length of cryptograms for different card brands is not as show below:
Disc,JCB,Diner <= 40 characters Amex <= 56 characters |
U35 | INCORRECT MARKET TYPE | Market type must be ecommerce for digital wallet transcations | N/A |
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 |
U57 | DIGITAL WALLET NOT CONFIG | Merchant is not configured for digital wallets, but the request is populated with wallet specific fields | N/A |
U58 | SPECIFIC WALLET TYPE NOT CONFIG | Merchant is not configured for a specific wallet type, but the request has it | N/A |
U59 | INCORRECT WALLET CONFIG | Merchant is incorrectly configured to accept wallet payments, but the processor does not support digital wallets | N/A |
U78 | DISALLOWED ACH SEC CODE | Indicates that the SEC code passed in with the ACH transaction is not allowed for the merchant account | Send a transaction with SEC code XYZ |
U80 | PREAUTH DECLINE | Transaction was declined due to preauthorization (Forte Verify) result | Send a transaction for 19.80 or 1980 |
NO MATCH | The name(s) received in the inquiry (Authenticate) message do not match any of the name fields for the record. Or invalid account number Or Bad account. | ||
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 |
U91 | CREDIT CARD NOT ALLOWED | Merchant account is configured to process only debit cards. Credit cards are not allowed. | Not available |
U92 | DEBIT CARD NOT ALLOWED | Merchant account is configured to process only credit cards. Debit cards are not allowed. | Not available |
U93 | DECRYPT INPUT ERROR | Caused by an error during decryption | Send the same encrypted card data twice |
Formatting Error | |||
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 | |
Fatal Error | |||
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 | |
Pending | |||
P01 | PENDING | Timeout due to issues with customer or merchant PayPal account. Our system will check for updates for 29 days, and we expect the transaction to be set to approved or declined before that period, according to PayPal procedures and policies. | Send a transaction for 9.97 |
P02 | PENDING | Timeout due to communication from merchant/Forte to PayPal. Our system will check for updates for 29 days, and we expect the transaction to be set to approved or declined before that period after the communication issues are solved. |
Transaction Return Codes
Code | Description | Comments |
R01 | ACCOUNT CLOSED | The available and/or cash reserve balance is not sufficient to cover the dollar value of the debit Entry. |
R02 | ACCOUNT CLOSED | A previously active account has been closed by action of the customer or the RDFI. |
R03 | NO ACCOUNT/ UNABLE TO LOCATE ACCOUNT | The account number structure is valid, and it passes the check digit validation, but the account number does not correspond to the individual identified in the Entry, or the account number designated is not an existing account. |
R04 | INVALID ACCOUNT NUMBER STRUCTURE | The account number structure is not valid. |
R05 | UNAUTHORIZED DEBIT TO CONSUMER ACCOUNT USING CORPORATE SEC CODE | CCD or CTX debit Entry was Transmitted to a Consumer Account of the Receiver and was not authorized by the Receiver. |
R06 | RETURNED PER ODFI’S REQUEST | The ODFI has requested that the RDFI return an Erroneous Entry, or a credit Entry originated without the authorization of the Originator. |
R07 | AUTHORIZATION REVOKED BY CUSTOMER | The RDFI’s customer (the Receiver) revoked the authorization previously provided to the Originator for this debit Entry. |
R08 | PAYMENT STOPPED | The Receiver has placed a stop payment order on this debit Entry. |
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 debit Entry.. |
R10 | CUSTOMER ADVISES ORIGINATOR IS NOT KNOWN TO RECEIVER AND/OR ORIGINATOR IS NOT AUTHORIZED BY RECEIVER TO DEBIT RECEIVER’S ACCOUNT | The RDFI has been notified by the Receiver that the Receiver does not know the identity of the Originator; has no relationship with the Originator; or has not authorized the Originator to debit his account. For ARC and BOC entries, the RDFI has been notified by the Receiver that the signature on the source document is not authentic, valid, or authorized. For POP Entries, the RDFI has been notified by the Receiver that the signature on the written authorization is not authentic, valid, or authorized. |
R11 | CUSTOMER ADVISES ENTRY NOT IN ACCORDANCE WITH THE TERMS OF THE AUTHORIZATION | The RDFI has been notified by the Receiver that 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 (for example, the entry is for an amount different than authorized; the entry was initiated for settlement earlier than authorized; the entry is part of an Incomplete Transaction; the debit entry was improperly reinitiated; for ARC, BOC, or POP entries: ineligible source document, notice was not provided; amount of the entry was not accurately obtained from the source document. The Reversing Entry was improperly initiated by the Originator or ODFI. The Receiver did not affirmatively initiate a Subsequent Entry in accordance with the terms of the Standing Authorization. |
R12 | ACCOUNT SOLD TO ANOTHER DFI | A financial institution received an Entry to an account that was sold to another financial institution. |
R13 | INVALID ACH ROUTING NUMBER | Entry contains a Receiving DFI Identification or Gateway Identification that is not a valid ACH routing number. |
R14 | REPRESENTATIVE PAYEE DECEASED OR UNABLE TO CONTINUE IN THAT CAPACITY | The representative payee is either deceased or unable to continue in that capacity. The beneficiary is not deceased. |
R15 | BENEFICIARY OR ACCOUNT HOLDER (OTHER THAN A REPRESENTATIVE PAYEE) DECEASED | (1) The beneficiary is deceased; or (2) the account holder is deceased. |
R16 | ACCOUNT FROZEN/ENTRY RETURNED PER OFAC INSTRUCTION | (1) Access to the account is restricted due to specific action taken by the RDFI or by legal action; or (2) OFAC has instructed the RDFI or Gateway to return the Entry. |
R17 | FILE RECORD EDIT CRITERIA/ENTRY WITH INVALID ACCOUNT NUMBER INITIATED UNDER QUESTIONABLE CIRCUMSTANCES/RETURN OF IMPROPERLY-INITIATED REVERSAL) | (1) Field(s) cannot be processed by RDFI; (2) the Entry contains an invalid DFI Account Number (account closed/no account/unable to locate account/invalid account number) and is believed by the RDFI to have been initiated under questionable circumstances; or (3) either the RDFI or Receiver has identified a Reversing Entry as one that was improperly initiated by the Originator or ODFI. |
R18 | IMPROPER EFFECTIVE ENTRY DATE | (1) 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 (2) the Effective Entry Date for a debit Entry is more than one Banking Day after the processing date. |
R19 | AMOUNT FIELD ERROR | (1) Amount field is non-numeric. (2) 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. (3) Amount field is zero in an Entry other than a Prenotification, DNE, ENR, Notification of Change, Return, dishonored Return, contested dishonored Return, or zero dollar CCD, CTX, or IAT Entry. (4) Amount field is greater than $25,000 for ARC, BOC, and POP Entries. |
R20 | NON-TRANSACTION ACCOUNT | ACH Entry to a non- Transaction Account. |
R21 | INVALID COMPANY IDENTIFICATION | The Identification Number used in the Company Identification Field is not valid. |
R22 | INVALID INDIVIDUAL ID NUMBER | The Receiver has indicated to the RDFI that the number with which the Originator was identified is not correct. |
R23 | CREDIT ENTRY REFUSED BY RECEIVER | Any credit Entry that is refused by the Receiver may be returned by the RDFI. |
R24 | DUPLICATE ENTRY | 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 ERROR | Addenda Record Indicator value is incorrect. Addenda Type Code is invalid, out of sequence, or missing, Number of Addenda Records exceeds allowable maximum, Addenda Sequence Number is invalid. |
R26 | MANDATORY FIELD ERROR | Erroneous data or missing data in a mandatory field. |
R27 | TRACE NUMBER ERROR | (1) Original Entry Trace Number is not present in the Addenda Record on a Return or Notification of Change Entry; or (2) Trace Number of an Addenda Record is not the same as the Trace Number of the preceding Entry Detail Record. |
R28 | ROUTING NUMBER CHECK DIGIT ERROR | The check digit for a routing number is not valid. |
R29 | CORPORATE CUSTOMER ADVISES NOT AUTHORIZED | The RDFI has been notified by the Receiver (Non- Consumer) that a specific Entry has not been authorized by the Receiver. |
R30 | RDFI NOT PARTICIPANT IN CHECK TRUNCATION PROGRAM | The RDFI does not participate in a Check Truncation Program. |
R31 | PERMISSIBLE RETURN ENTRY (CCD AND CTX ONLY) | The RDFI may return a CCD or CTX Entry that the ODFI agrees to accept. |
R32 | RDFI NON-SETTLEMENT | The RDFI is not able to settle the Entry. |
R33 | RETURN OF XCK ENTRY | This Return Reason Code may only be used to return XCK Entries and is at the RDFI’s sole discretion. |
R34 | LIMITED PARTICIPATION DFI | The RDFI’s participation has been limited by a federal or state supervisor. |
R35 | RETURN OF IMPROPER DEBIT ENTRY | Debit Entries (with the exception of Reversing Entries) are not permitted for CIE Entries or to loan accounts. |
R36 | RETURN OF IMPROPER CREDIT ENTRY | ACH credit Entries (with the exception of Reversing Entries) are not permitted for use with ARC, BOC, POP, RCK, TEL, and XCK. |
R37 | SOURCE DOCUMENT PRESENTED FOR PAYMENT | The source document to which an ARC, BOC, or POP Entry relates has been presented for payment. |
R38 | STOP PAYMENT ON SOURCE DOCUMENT | The RDFI determines a stop payment order has been placed on the source document to which the ARC or BOC Entry relates. |
R39 | IMPROPER SOURCE DOCUMENT/SOURCE DOCUMENT PRESENTED FOR PAYMENT | The RDFI determines that: (1) the source document used for an ARC, BOC, or POP Entry to its Receiver’s account is improper, or (2) an ARC, BOC, or POP Entry and the source document to which the Entry relates have both been presented for payment and posted to the Receiver’s account. |
R40 | RETURN OF ENR ENTRY BY FEDERAL GOVERNMENT AGENCY | This Return Reason Code may only be used to return ENR Entries and is at the Federal Government Agency’s sole discretion. |
R41 | INVALID TRANSACTION CODE | Either the Transaction Code included in Field 3 of the Addenda Record does not conform to the ACH Record Format Specifications contained in Appendix Three (ACH Record Format Specifications) or it is not appropriate with regard to an Automated Enrollment Entry. |
R42 | ROUTING NUMBER/CHECK DIGIT ERROR | The Routing Number and the Check Digit included in Field 3 of the Addenda Record is either not a valid number or it does not conform to the Modulus 10 formula. |
R43 | INVALID DFI ACCOUNT NUMBER | The Receiver’s account number included in Field 3 of the Addenda Record must include at least one alphameric character. |
R44 | INVALID INDIVIDUAL ID NUMBER/IDENTIFICATION NUMBER | The Individual ID Number/Identification 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 | The name of the consumer or company provided in Field 3 of the Addenda Record either does not match a corresponding name in the Federal Government Agency’s records or fails to include at least one alphameric character. |
R46 | INVALID REPRESENTATIVE PAYEE INDICATOR | The Representative Payee Indicator Code included in Field 3 of the Addenda Record has been omitted or it is not consistent with the Federal Government Agency’s records. |
R47 | DUPLICATE ENROLLMENT | The Entry is a duplicate of an Automated Enrollment Entry previously initiated by a DFI. |
R50 | STATE LAW AFFECTING RCK ACCEPTANCE | (1) The RDFI is located in a state that has not adopted Revised Article 4 of the Uniform Commercial Code (1990 Official Text) and has not revised its customer agreements to allow for Electronic presentment; or (2) the RDFI is located within a state that requires all canceled Checks to a specific type of account to be returned to the Receiver within the periodic statement. |
R51 | ITEM RELATED TO RCK ENTRY IS INELIGIBLE OR RCK ENTRY IS IMPROPER | An RCK Entry is considered to be ineligible or improper. |
R52 | STOP PAYMENT ON ITEM RELATED TO RCK ENTRY | A stop payment order has been placed on the item to which the RCK Entry relates. |
R53 | ITEM AND RCK ENTRY PRESENTED FOR PAYMENT | 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. |
R62 | RETURN OF ERRONEOUS OR REVERSING DEBIT | The Originator’s/ODFI’s use of the reversal process has resulted in, or failed to correct, an unintended credit to the Receiver. |
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 time frame established by these Rules. |
R69 | FIELD ERROR(S) | One or more of the field requirements are incorrect. |
R70 | PERMISSIBLE RETURN ENTRY NOT ACCEPTED/RETURN NOT REQUESTED BY ODFI | The ODFI has received a Return Entry identified by the RDFI as being returned with the permission of, or at the request of, the ODFI, but the ODFI has not agreed to accept the Entry or has not requested the return of the Entry. |
R71 | MISROUTED DISHONORED RETURN | The financial institution preparing the dishonored Return Entry (the ODFI of the original Entry) has placed the incorrect Routing Number in the Receiving DFI Identification field. |
R72 | UNTIMELY DISHONORED RETURN | The dishonored Return Entry has not been sent within the designated time frame. |
R73 | TIMELY ORIGINAL RETURN | The RDFI is certifying that the original Return Entry was sent within the time frame designated in these Rules. |
R74 | CORRECTED RETURN | The RDFI is correcting a previous Return Entry that was dishonored using Return Reason Code R69 (Field Error(s)) because it contained incomplete or incorrect information. |
R75 | RETURN NOT A DUPLICATE | The Return Entry was not a duplicate of an Entry previously returned by the RDFI. |
R76 | NO ERRORS FOUND | The original Return Entry did not contain the errors indicated by the ODFI in the dishonored Return Entry. |
R77 | NON-ACCEPTANCE OF R62 DISHONORED RETURN | The RDFI returned both the Erroneous Entry and the related Reversing Entry, or the funds relating to the R62 dishonored Return are not recoverable from the Receiver. |
R80 | IAT ENTRY CODING ERROR | The IAT Entry is being returned due to one or more of the following conditions:
|
R81 | NON-PARTICIPANT IN IAT PROGRAM | The IAT Entry is being returned because the Gateway does not have an agreement with either the ODFI or the Gateway’s customer to transmit Outbound IAT Entries. |
R82 | INVALID FOREIGN RECEIVING DFI IDENTIFICATION | The reference used to identify the Foreign Receiving DFI of an Outbound IAT Entry is invalid. |
R83 | FOREIGN RECEIVING DFI UNABLE TO SETTLE | The IAT Entry is being returned due to settlement problems in the foreign payment system. |
R84 | ENTRY NOT PROCESSED BY GATEWAY |
For Outbound IAT Entries, the Entry has not been processed and is being returned at the Gateway’s discretion because either (1) the processing of such Entry may expose the Gateway to excessive risk, or (2) the foreign payment system does not support the functions needed to process the transaction. |
R85 | INCORRECTLY CODED OUTBOUND INTERNATIONAL PAYMENT | The RDFI/Gateway has identified the Entry as an Outbound international payment and is returning the Entry because it bears an SEC Code that lacks information required by the Gateway for OFAC compliance. |
Transaction Settlement Codes
Code | Description | Comments |
C00 | CHARGEBACK | Customer has disputed part or all of the transaction. The charge is returned to the customer's card that was used for payment. |
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. |