Transaction Status and Decline Codes

Modified on Mon, 1 Dec at 4:52 PM

This guide provides a comprehensive overview of the codes used in payment processing with CSG Forte. The document includes clear explanations for transaction status codes, transaction response codes, transaction return codes, transaction settlement codes, and cardholder verification codes such as address verification and card verification value codes (like AVS and CVV).

How to Use This Guide

1. Locate the code you see in your transaction response.

2. Read the description and recommended action.

3. If unresolved, contact CSG Forte Support.

Content

1. Understanding Payment Codes

1.1. Transaction Response Codes

1.1.1. Approved

1.1.2. Declined

1.1.3. Formatting Error

1.1.4. Fatal Error

1.1.5. Pending

1.2. Transaction Return Codes

1.3. Transaction Settlement Codes

2. Codes for Verifying Cardholder Information in Credit Card Transactions

2.1. Address Verification Codes (AVS)

2.2. International Address Verification Codes

2.3. Card Verification Value (CVV/CVV2) Codes

1. Understanding Payment Codes

This section presents the codes used to verify cardholder information during credit card transactions. These codes support the authenticity of each transaction and help reduce the risk of fraud by validating important data provided by the customer.

• Whether the transaction was accepted or rejected for processing

• The stage of the transaction within its lifecycle

For example:

• The lifecycle for a typical Automated Clearing House (ACH) transaction is: Ready → Settling → Funded.

• The lifecycle for a typical credit card transaction is: Ready → Settled.

After a transaction is sent for processing, its status may be updated to one of several options. The following table describes the main transaction status codes and their meanings.

Status	Description
Authorized	The payment request has successfully passed authorization checks. To finalize the transaction, the merchant needs to capture the authorized amount from the transaction details.)
Complete	eCheck verification was performed and the results were positive (POS) or unknown (UNK).
Decline	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	The payment amount has been transferred to or from the merchant’s bank account.
Ready	Transaction was received and it is awaiting origination (eCheck) or settlement (credit card).
Rejected	eCheck item has been rejected or returned by the client's financial institution. The merchant will not be funded for the item.
Review	Transaction was unable to be settled due to a merchant configuration issue. Please contact Customer Support to resolve (+1 866 290 5400 Option 1).
Settle	Credit Card transaction has been funded to the merchant's bank account.
Settling	eCheck item has been originated and CSG Forte is awaiting the settlement results.
Unfunded	Previously funded eCheck item has been returned and funding was reversed.
Voided	The transaction was stopped, so the item will not proceed to origination or settlement.

1.1. Transaction Response Codes

When a transaction is submitted for processing, CSG Forte immediately returns one of several possible responses. Codes beginning with the letter “A” indicate that the transaction was accepted for processing. Codes beginning with “U” indicate the transaction was rejected. “N” codes mean no information is available. “F” codes signal formatting errors, often caused by missing or incorrect fields. “E” codes denote processing exceptions that may require manual review. “P” codes indicate the transaction is pending, typically for PayPal transactions.

These codes are generated during transaction validation and help clarify whether the transaction was approved, rejected, or requires further action.

1.1.1. Approved

Code	Description	Comments
A01	Approved	Transaction approved/completed.
A03	Partial authorization	Transaction approved for a partial authorization (CC only).
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.

1.1.2. Declined

Code	Description	Comments	Test Parameters
N01	No info	The routing and account numbers are found in the database, but no names are associated with these.
U01	Merch auth revoked	Merchant not allowed to access customer’s account (EFT only)
U02	Account not approved	Customer’s account is in CSG 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 (a quick math check), but it is 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 ZIP code	AVS state/ZIP code check failed	Send a region and “postal_code” that do not match
U06	AVS failure area code	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 exceeded the maximum number of transactions per hour, which may indicate a security problem. This error rarely occurs, if presented contact CSG Forte immediately.
U09	Window velocity	Merchant exceeded the maximum number of transactions per hour, which may indicate a security problem. This error rarely occurs, if presented contact CSG Forte immediately.
U10	Duplicate transaction	Transaction with the same attributes as another transaction within the time set by the merchant	Send the same transaction twice within five minutes
U11	Recurring transaction not found	Recurring transactions only.	Not available
U12	Update not allowed	Original transaction not voidable or capturable	Send a void transaction for a declined transaction
U13	Original transaction 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 original transaction	Void/Capture and original transaction types do not agree (CC/EFT only)	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 US$19.18 or US$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 (US$-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)
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 than InApp, Web
U34	Invalid wallet cryptogram	“Wallet” cryptogram invalid. Length of cryptograms for different card brands. Visa and Mastercard are 28 characters, Discovery, JCB and Diners and 40 characters and Amex is 56 characters	Send a transaction with digital “Wallet” cryptogram. Where Length of cryptograms for different card brands is not as show in the column comments
U35	Incorrect market type	“Market” type must be ecommerce for digital wallet transactions
U36	Surcharging not supported	Merchant sent a surcharge fee but is not configured to accept one
U37	Cfee amount exceeded	The "Convenience Fee” (Cfee) amount of the refund transaction exceeds its respective amount in the original sale transaction.	Send a refund transaction for US$1.75 or US$175. Note: The “Service_fee_amount” field, if provided, should match the “service_fee_amount” configured for the location.
U38	Subtotal and tax amount exceeded	The "Subtotal & tax amount" of the refund transaction exceeds its respective amount in the original sale transaction.	Send a refund transaction for US$1.75 or US$175. Note: The “Service_fee_amount” field, if provided, should match the “service_fee_amount” configured for the location.
U39	Original authorized amount exceeded	Both “Convenience Fee” amount & "Subtotal & tax amount” of the refund transaction is exceeding their respective amounts in the original sale transaction.	Send a refund transaction for US$1.77 or US$177. Note: The “Service_fee_amount” field, if provided, should match the “service_fee_amount” configured for the location.
U40	Refund currently in progress	If two refunds are processed at the same time, the latest transaction will be declined with this error message.	Send a refund transaction for US$1.78 or US$178. Note: The “Service_fee_amount” field, if provided, should match the “service_fee_amount” configured for the location.
U41	Refunds apply only to settled/ settling/ funded transactions	Refund is applicable only if the original sale transaction status is Settled/ Settling/ Funded. For any case where the status is not Settled/ Settling/ Funded when attempting a refund, it will be declined with this error message.	Send a refund transaction for US$1.78 or US$178. Note: The “Service_fee_amount” field, if provided, should match the “service_fee_amount” configured for the location.
U42	Surcharge fee incorrect	Merchant configured for surcharge fee but did not send one
U43	Surcharge amount incorrect	The "Surcharge Fee amount" of the refund transaction exceeds its respective amount in the original sale transaction.
U51	Merchant status	Merchant is not "Live " (sometimes represented in the system as “L”)	Send a transaction for a non-live account
U52	Type not allowed	Merchant not approved for transaction type (CC or EFT only)	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 configuration	Merchant's configuration requires updating - call Customer Support	Send a transaction for US$19.54 or US$1954
U56	Card type not allowed	Merchant’s account does not support the provided credit card brand. Call Customer Support (configuration or settings update required).
U57	Digital wallet not config	Merchant not configured for digital wallets, but the request is populated with wallet specific fields
U58	Specific wallet type not config	Merchant is not configured for a specific “Wallet” type, but the request has it
U59	Incorrect wallet config	Merchant incorrectly configured to accept wallet payments, but the processor does not support digital wallets
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
U79	Blocked BIN	Transaction declined because the card BIN is currently blocked. If a merchant reaches out indicating declined transactions associated with this code, please respond using the appropriate canned response.
U80	Preauthorization decline	Transaction was declined due to preauthorization (Verify) result	Send a transaction for US$19.80 or US$1980
U80	No match	The names or account details entered do not match what the bank has on file.	Double-check the account and routing number
U81	Preauthorization timeout	Preauthorizer not responding (verify transactions only)	Send a transaction for US$19.81 or US$1981
U82	Preauthorization error	Preauthorizer error (verify transactions only)	Send a transaction for US$19.82 or US$1982
U83	Authorizer decline	Transaction was declined due to authorizer declination. The issuer or payment network determined that the transaction does not meet authorization criteria.	Send a transaction for US$19.83, US$1983, or US$1.33
U84	Authorizer timeout	The authorizer did not respond within the expected time frame.	Send a transaction for US$19.84 or US$1984
U85	Authorizer error	An error occurred on the authorizer’s side during processing.	Send a transaction for US$19.85 or US$1985
U86	AVS failure authorizer	The authorizer’s Address Verification Service (AVS) check failed.	Send a transaction for US$19.86 or US$1986
U87	Authorizer busy	Authorizing vendor busy, the transaction may be resubmitted (CC only)	Send a transaction for US$19.87 or US$1987
U88	Preauthorization busy	Verification vendor busy, the transaction may be resubmitted (type 26 only).	Send a transaction for US$19.88 or US$1988
U89	Authorization unavailable	The authorizing vendor’s service is unavailable (CC only)	Send a transaction for US$19.89 or US$1989
U90	Preauthorization unavailable	Verification service unavailable (type 26 only).	Send a transaction for US$19.90 or US$1990
U91	Credit card not allowed	Merchant account 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
U94	Decrypt timeout	Decryption process did not complete within the expected time frame.
U95	Decrypt error	Decryption failed due to invalid or corrupted encrypted data.
U99	Decrypt unavailable	Decryption service unavailable or encountered an unspecified error.

1.1.3. Formatting Error

Code	Description	Comments
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

1.1.4. Fatal Error

Code	Description	Comments
E10	Invalid merchant or password	The merchant credentials provided are invalid.
E20	Merchant timeout	Transaction message not received (Input/Output flush may be required)
E55	Invalid token	Specified token was invalid, could not be located or may have been deleted
	Client token transactions	No payment fields or token specified, and client record lacks a default payment method for this transaction type.
	Payment token transactions	If no client token is specified, the payment token must be clientless.
	Both client and payment token transactions	The payment token is not associated with the client or is clientless.
E90	Bad merchant IP address	Origination IP is not on merchant's approved IP list
E99	Internal error	An unspecified error has occurred.

1.1.5. Pending

Code	Description	Comments	Test Parameters
P01	Pending	The transaction is delayed due to issues with the customer’s or merchant’s PayPal account. The system will keep checking for updates for up to 29 days. During this time, PayPal should resolve the issue and set the transaction to either approved or declined, following PayPal’s policies.	Send a transaction for US$9.97
P02	Pending	Timeout due to communication from merchant/CSG 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.

1.2. Transaction Return Codes

NACHA return codes are used to indicate when a payment has been returned or rejected. These codes help identify the reason a transaction failed. If a payment does not go through, CSG Forte typically receives the return message from the Automated Clearing House network within two to four business days after submission.

Code	Description	Comments
R01	Insufficient funds	Available balance or cash reserve balance is not sufficient to cover the dollar value of the debit entry.
R02	Account closed	Account was previously active but has been closed by the customer or the Receiving Depository Financial Institution (RDFI).
R03	No account/ unable to locate account	Account number structure is valid and passes check digit validation, but account number does not correspond to the individual identified in the entry or does not exist.
R04	Invalid account number structure	Account number structure is not valid.
R05	Unauthorized debit to consumer account using corporate sec code	A CCD or CTX debit entry was transmitted to a consumer account and was not authorized by the receiver.
R06	Returned per ODFI’s request	Originating Depository Financial Institution (ODFI) has requested that RDFI returns an erroneous entry, or a credit entry originated without the authorization of the originator.
R07	Authorization revoked by customer	RDFI’s customer revoked the authorization previously provided to the originator for this debit entry.
R08	Payment stopped	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	RDFI has been notified by the receiver that the receiver does not know, has no relationship 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.
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 RFDI 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	The beneficiary is deceased, or the account holder is deceased.
R16	Account frozen/entry returned per OFAC instruction	Access to the account is restricted due to specific action taken by the RDFI or by legal action or 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	Field cannot be processed by RDFI, 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 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	"Effective Entry Date" for a credit entry is more than two banking days after the banking day of processing as established by the Originating ACH Operator; or the effective entry date for a debit entry is more than one banking day after the processing date.
R19	Amount field error	The amount field must contain a valid numeric value. It cannot be zero in entries that require a positive amount and cannot be non-zero in entries that should have zero amounts, such as prenotifications or notifications of change. For ARC, BOC, and POP entries, the amount must not exceed US$25,000.
R20	Non-transaction account	ACH entry to a non-transaction account.
R21	Invalid company identification	Identification Number used in the “Company Identification” field is not valid.
R22	Invalid individual ID number	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	RDFI has received what appears to be a duplicate entry; e.g., the trace number, date, dollar amount and/or other data matches another transaction.
R25	Addenda error	"Addenda Record Indicator" value is incorrect.
	Addenda error	"Addenda Type Code" is invalid, out of sequence, or missing.
	Addenda error	Number of "Addenda Records" exceeds allowable maximum.
	Addenda error	"Addenda Sequence Number" is invalid.
R26	Mandatory field error	Erroneous data or missing data in a mandatory field.
R27	Trace number error	Original entry trace number is not present in the "Addenda Record" on a return or notification of change entry; or 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	Check digit for a routing number is not valid.
R29	Corporate customer advises not authorized	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	RDFI does not participate in a "Check Truncation Program".
R31	Permissible return entry (CCD and CTX only)	RDFI may return a CCD or CTX entry that the ODFI agrees to accept.
R31	Permissible return entry (CCD and CTX only)	RDFI may return a CCD or CTX entry that the ODFI agrees to accept.
R32	RDFI non-settlement	RDFI is not able to settle the entry.
R33	Return of XCK entry	Only to be used to return XCK entries and it is at the RDFI’s sole discretion.
R34	Limited participation DFI	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	Source document to which an ARC, BOC, or POP entry relates has been presented for payment.
R38	Stop payment on source document	RDFI determines a stop payment request has been placed on the source document to which the ARC or BOC entry relates.
R39	Improper source document/source document presented for payment	RDFI determines that the source document used for an ARC, BOC, or POP entry to its receiver’s account is improper, or 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	Only to 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 the ACH Record Format Specifications or it is not appropriate with regard to an "Automated Enrollment" entry.
R42	Routing number/check digit error	"Routing Number" and the "Check Digit" included in field 3 of the "Addenda Record" are either not a valid number or it does not conform to the modulus 10 formula.
R43	Invalid DFI account number	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	"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	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 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.
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.
R62	Return of erroneous or reversing debit	ODFI’s use of the reversal process has resulted in, or failed to correct, an unintended credit to the receiver.
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	"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	"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.
R66	Incorrect company identification	"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	ODFI has received more than one return for the same entry.
R68	Untimely return	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	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	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	RDFI is certifying that the original return entry was sent within the time frame designated in these rules.
R74	Corrected return	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	Return entry was not a duplicate of an entry previously returned by the RDFI.
R76	No errors found	Original return entry did not contain the errors indicated by the ODFI in the dishonored return entry.
R77	Non-acceptance of R62 dishonored return	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: invalid "DFI"/"Bank Branch Country Code", invalid "DFI"/"Bank Identification Number Qualifier", invalid "Foreign Exchange Indicator", invalid "ISO Originating Currency Code", invalid "ISO Destination Currency Code", invalid "ISO Destination Country Code" or invalid "Transaction Type Code".
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	Outbound IAT entries, the entry has not been processed and is being returned at the gateway’s discretion because either the processing of such entry may expose the gateway to excessive risk, or the foreign payment system does not support the functions needed to process the transaction.
R85	Incorrectly coded outbound international payment	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.
R90	Entry returned due to RDFI’s sanctions compliance obligations
R95	Over limit	This transaction is over the 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	Password supplied was invalid
R99	Declined unpaid items	Account or ID has been declined due to unpaid items

1.3. Transaction Settlement Codes

Transaction settlement codes are used to describe the outcome of payment settlement processes. Accounts can be configured to allow up to two additional recollection attempts if a payment, such as a check, is returned due to insufficient funds. For example, recollection attempts may be scheduled on the first and fifteenth days of the month.

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.

2. Codes for Verifying Cardholder Information in Credit Card Transactions

2.1. Address Verification Codes (AVS)

When a transaction is submitted for address verification or card verification, one of the following responses may be received:

Code	Summary	Description	VISA	MasterCard	American Express	Discover
X	Match	Street address and 9-digit ZIP code both match		x
Y	Match	Street address and 5-digit ZIP code both match	x	x	x	x
A	Partial match	Street address matches, but both 5-digit and 9-digit ZIP code do not match	x	x	x	x
W	Partial match	Street address does not match, but 9-digit ZIP code matches		x		x
Z	Partial match	Street address does not match, but 5-digit ZIP code matches	x	x	x	x
N	No match	Street address, 5-digit ZIP code, and 9-digit ZIP code all do not match	x	x	x	x
U	System unavailable	Address information unavailable. Returned if non-US.	x	x	x	x
U	System unavailable	AVS is not available or the AVS for a US bank is not functioning properly.	x	x	x	x
R	System unavailable	Retry - Issuer's system unavailable or timed out	x	x	x
E	Invalid	AVS data is invalid	x
S	Not supported	US-issuing bank does not support AVS	x	x	x

***Note: A transaction may be approved even if the address or card verification information does not match. The Address Verification and Card Verification Value systems are intended to provide additional assurance when shipping products. Decisions regarding the supply of goods should be made based on the responses received from these verification systems.***

2.2. International Address Verification Codes

Code	Summary	Description
D	Match	Street address and 9-digit ZIP code both match
M	Match	Street address and 5-digit ZIP code both match
B	Partial match	Street address matches, but both 5-digit and 9-digit ZIP code do not match
P	Partial match	Street address does not match, but 9-digit ZIP code matches
C	Partial match	Street address does not match, but 5-digit ZIP code matches
I	No match	Street address, 5-digit ZIP code, and 9-digit ZIP code all do not match
G	System unavailable	Address information unavailable. Returned if non-US.
R	System unavailable	Retry - Issuer's system unavailable or timed out
E	Invalid	AVS data is invalid
S	Not supported	US-issuing bank does not support AVS

2.3. Card Verification Value (CVV/CVV2) Codes

Card Verification Value codes are security indicators used to verify the authenticity of the cardholder during credit card transactions. These codes reflect the result of the card verification check performed by the issuer and assist in determining whether a transaction should be approved, declined, or reviewed. Proper interpretation of these codes is essential for fraud prevention and compliance with payment card industry standards.

Code	Description
M	CVV2 Match
N	CVV2 No Match
P	Not Processed
S	Issuer indicates that CVV2 data should be present on the card, but the merchant has indicated that the data is not present on the card
U	Issuer has not certified for CVV2, or the Issuer has not provided Visa with the CVV2 encryption keys
Empty	Transaction failed because the merchant entered the wrong CVV2 number or did not enter any CVV2 number