Home > Codes



Countries:

Groups

Groups

Provider Codes:  Hide

Processing Codes



ACH/eCheck Notification of Change Codes (US)  
Code User Message Developer Message/Description
C01 Account number is incorrect or is formatted incorrectly
 Customer's account number is incorrect or malformatted.
C02 Due to merger or consolidation, a once valid transit/routing number must be changed
 Transit or routing number is not valid anymore and should be changed.
C03 Due to a merger or consolidation, the transit/routing number must be changed; and account number structure is no longer valid
 Transit or routing number should be changed. Account number structure is invalid.
C04 Customer has changed name or ODFI has submitted the name incorrectly
 Customer's name is incorrect or malformatted.
C05 Transaction code is incorrect and is causing entry to be routed to the wrong account application
 Transaction code is incorrect.
C06 Account number is incorrect and transaction is being routed to the wrong type of account
 Bank account number should be changed and transaction code should indicate posting to another account type (demand/savings).
C07 Due to a merger or consolidation, a transit/routing number must be changed; account number structure is no longer valid; and, the transaction should be routed to another account type
 Transit/routing number, bank account number and transaction code should be changed.
C08 Incorrect Foreign Receiving DFI Identification
 For IAT entries only which are not allowed to be originated at this time.
C09 Individuals ID number is incorrect
 Individual’s ID number is incorrect or malformatted.
C10 Due to Merger or consolidation, the company name carried on the file of the ODFI is no longer valid
 Company name is no longer valid and should be changed.
C11 Due to merger or consolidation, the company ID is no longer valid and should be changed
 Company ID is no longer valid and should be changed.
C12 Due to merger or consolidation, the company name and company ID are no longer valid
 Both the company name and company ID are no longer valid and should be changed.
C13 Entry Detail Record was correct, but information in the addenda record was unclear/formatted incorrectly (i.e., addenda information is not formatted in NSI or NACHA endorsed banking conventions)
 Addenda information is malformatted.
C61 Misrouted Notification of Change
 Notification of change has been refused due to misrouting.
C62 Incorrect Trace Number
 Notification of change has been refused due to incorrect trace number.
C63 Incorrect Company Identification Number
 Notification of change has been refused due to incorrect company ID.
C64 Incorrect Individual Identification Number
 Notification of change has been refused due to incorrect customer's ID.
C65 Incorrectly Formatted Addenda Information
 Notification of change has been refused due to malformatted addenda information.
C66 Incorrect Discretionary Data
 Notification of change has been refused due to incorrect discretionary data.
C67 Routing Number Not From Original Entry Detail
 Notification of change has been refused due to routing number mismatch.
C68 DFI Account Number Not from Original Entry Detail Record
 Notification of change has been refused due to DFI account number mismatch.
C69 Incorrect Transaction Code
 Notification of change has been refused due to incorrect transaction code.
AVS Response Codes  
Code User Message Developer Message/Description
00 AVS Error - Retry, System unavailable or Timed out
 A system error prevented any verification of street address or postal code.
40 Address not available (Address not verified)
 The card-issuing bank received the address but did not verify whether it was correct. This typically happens if the processor declines an authorization before the bank evaluates the address.
43 Street address not available (not verified), ZIP matches
 The card-issuing bank received the street address but did not verify whether it was correct. ZIP code matches.
44 Address failed
 Address verification has failed.
45 Street address and ZIP don't match
 Both street address and ZIP code provided do not match the information on file with the cardholder's bank.
46 Street address doesn't match, 5-digit ZIP matches
 Provided street address does not match the information on file with the cardholder's bank, but 5-digit ZIP code matches.
47 Street address doesn't match, 9-digit ZIP matches
 Provided street address does not match the information on file with the cardholder's bank, but 9-digit ZIP code matches.
4A Street address or ZIP doesn't match
 Street address or ZIP code provided does not match the information on file with the cardholder's bank.
4D Street address matches, ZIP does not
 Provided ZIP code does not match the information on file with the cardholder's bank, but street address matches.
4E Street address and 5-digit ZIP match
 Both street address and 5-digit ZIP code provided match the information on file with the cardholder's bank.
4F Street address and ZIP match
 Both street address and ZIP code provided match the information on file with the cardholder's bank.
53 Account holder name incorrect, billing postal code matches
 Provided account holder name does not match the information on file with the cardholder's bank, but billing postal code matches.
55 Unrecognized response
 Account holder name, billing address and postal code are all incorrect.
5C Account holder name incorrect, billing address matches
 Provided account holder name does not match the information on file with the cardholder's bank, but billing address matches.
5F Account holder name incorrect, billing address and postal code match
 Provided account holder name does not match the information on file with the cardholder's bank, but both billing address and postal code matches.
70 Account holder name matches
 Provided account holder name matches the information on file with the cardholder's bank.
73 Account holder name and billing postal code match
 Both account holder name and billing postal code provided match the information on file with the cardholder's bank.
7C Account holder name and billing address match
 Both account holder name and billing address provided match the information on file with the cardholder's bank.
7F Account holder name, billing address and postal code match
 All of the information provided match the information on file with the cardholder's bank.
80 AVS service not supported by issuer - Issuer doesn't participate in AVS
 AVS information was provided but the card-issuing bank does not participate in address verification.
C0 AVS not performed
 AVS verification has not been performed.
CSC Response Codes  
Code User Message Developer Message/Description
M Matches
 The CSC provided matches the information on file with the cardholder's bank.
N Not matches
 The CSC provided does not match the information on file with the cardholder's bank.
P Not processed
 CSC has not been processed.
S Should be present
 Issuer indicates that CSC data should be present on the card, but the merchant has indicated data is not present on the card.
U Issuer is not certified
 (1) Unknown issuer; (2) issuer is not certified for CSC; (3) issuer has not provided Visa/MasterCard with the CSC encryption keys.
X Unrecognized reason
 Error: response is unknown or unrecognized.
Direct Debit Response Codes  
Code User Message Developer Message/Description
F02 Operation code/transaction code/invalid file format/validation error
 1) Specified bank operation code is invalid;
2) Specified transaction code is either incorrect or invalid;
3) One of the specified fields is either incorrect or invalid;
4) Transaction data has not been validated by the processor.
F03 Indicated data incorrect
 One or more required identification fields' values are either incorrect or missing.
N01 Insufficient Funds
 Available balance is not sufficient to cover the amount of the debit entry.
N02 Account Closed
 Previously active account has been closed by customer or customer's bank.
N03 Routing number is incorrect
 Either customer's routing number is incorrect or DFI account number is incorrect.
N04 Incorrect or invalid account number
Specified account number is either incorrect (i.e. invalid IBAN of the Debtor) or invalid (entry may fail check digit validation or may contain an incorrect number of digits).
N05 Account blocked/frozen/deleted/blacklisted/Institution in Default
 Specified ACH account is either blocked, frozen, deleted or blacklisted or depository institution is in default.
N06 Incorrect account type
 Submitted transaction forbidden for this type of account.
N07 Instruction canceled/expired/Refer to payer/stop payment
1) Instruction has been canceled by payer or his bank;
2) Instruction has expired (occures when a service user attempts to convert a DDI which is shown as expired on the paying bank's database);
3) Refer to payer;
4) Payment has stopped.
N08 Transferred
 Financial institution receives entry destined for an account at a branch that has been transferred to another financial institution.
N09 Instruction re-instated/amended
 1) Paying bank may re-instate a cancelled DDI up to two months from cancelation;
2) Paying bank will advise amendment via ADDACS message.
N10 Cannot Trace
 Trace number is incorrect.
N11 Payer deceased
 Account holder is deceased (used in the event of a representative payee, guardian, or trustee).
N12 Payment Recalled/Chargeback/Return/No Agreement/No Confirmation
 1) Receiver of a recurring debit transaction has stopped payment on a specific ACH debit. RDFI should verify the receiver's intent when a request for stop payment is made to insure this is not intended to be a revocation of authorization;
2) Chargeback has been received;
3) There is one or more issues associated with return entry;
4) There is one or more issues associated with PAD agreement;
5) The payor has requested the debit to be returned as they have did not receive prenotification of a change to the PAD date or amount, or they did not receive written confirmation of a PAD Agreement executed by electronic means.
N13 Other/Misalignment
 Exception is not defined.
NM01 Mandate/advance notice
 1) Mandate data is either missing or incorrect;
2) Payer disputes time, amount or frequency of advance notice and has requested single payment to be countermanded.
Direct Debit Response Codes (Australia)  
Code User Message Developer Message/Description
1 Invalid BSB Number
 Specified BSB number is either incorrect or invalid.
2 Payment Stopped
 Receiver of a recurring direct debit transaction has stopped payment. To continue, the customer should contact their bank to allow debiting.
3 Account closed
 Previously active account has been closed by customer or customer's bank.
4 Customer deceased
 Customer has deceased (used in the event of a representative payee, guardian, or trustee).
5 No account/incorrect account #
 Account number is either incorrect or invalid.
6 Refer to customer
 Reason for non-payment needs to be established from the customer.
7 Deleted
 Specified direct debit account is deleted.
8 Invalid User ID Number
 Specified user ID is either incorrect or invalid.
9 Technically Invalid
 Customer's bank account does not allow debits.
XA Account Cancelled
 Account has been cancelled by a credit grantor.
Direct Debit Response Codes (Europe SEPA)  
Code User Message Developer Message/Description
AC01 Account Identifier incorrect (i.e. invalid IBAN of the Debtor)
 Specified account number is either incorrect or invalid.
AC02 Invalid Debtor Account Number
 Debtor account number is either invalid or missing.
AC03 Invalid Creditor Account Number
 Creditor account number is either invalid or missing.
AC04 Account closed
 Specified account is closed.
AC05 Closed Debtor Account Number
 Debtor account is closed.
AC06 Account blocked
 Specified account is blocked, posting of transactions is prohibited.
AC07 Closed Creditor Account Number
 Creditor account is closed.
AC08 Invalid Branch Code
 Branch code is either invalid or missing.
AC09 Invalid Account Currency
 Account currency is either invalid or missing.
AC10 Invalid Debtor Account Currency
 Debtor account currency is either invalid or missing.
AC11 Invalid Creditor Account Currency
 Creditor account currency is either invalid or missing.
AC12 Invalid Account Type
 Account type is either invalid or missing.
AC13 Debtor account is a consumer account
 Debtor account type is invalid. Used for SDD B2B collections only.
AC14 Invalid Creditor Account Type
 Creditor account type is either invalid or missing.
AG01 Direct Debit forbidden on this account for regulatory reasons
 Submitted transaction is forbidden for this type of account for regulatory reasons.
AG02 Operation code/transaction code/sequence type incorrect, invalid file format
 1) Bank operation code specified in the message is invalid;
2) Sequence type is incorrect;
3) SDD schemes: specified identification code of the scheme is incorrect.
AG03 Transaction Not Supported
 Specified transaction type is not supported or is not authorized on this account.
AG04 Invalid Agent Country
 Agent country code is either invalid or missing.
AG05 Invalid Debtor Agent Country
 Debtor agent country code is either invalid or missing.
AG06 Invalid Creditor Agent Country
 Creditor agent country code is either invalid or missing.
AG07 Unsuccessful Direct Debit
 Debtor account cannot be debited for a generic reason. Reason code may be used in general purposes and as a replacement for AM04 if debtor bank does not reveal its customer's insufficient funds for privacy reasons.
AG08 Invalid Access Rights
 Transaction has failed due to invalid or missing user or access rights.
AGNT Incorrect Agent
 Agent in the payment workflow is incorrect.
AM01 Zero Amount
 Transaction amount is equal to zero.
AM02 Not Allowed Amount
 Transaction amount is greater than allowed maximum.
AM03 Not Allowed Currency
 Specified currency code cannot be processed.
AM04 Insufficient Funds
 Available balance is not sufficient to cover the amount of the debit entry.
AM05 Duplicate collection
 Same SDD collection had been processed in the near past.
AM06 Too Low Amount
 Transaction amount is less than agreed minimum.
AM07 Blocked Amount
 Amount of funds available to cover specified transaction amount is insufficient.
AM09 Wrong Amount
 Received amount has not been agreed or expected.
AM10 Invalid Control Sum
 Sum of instructed amounts does not equal the control sum.
AM11 Invalid Transaction Currency
 Transaction currency is either invalid or missing.
AM12 Invalid Amount
 Transaction amount is either invalid or missing.
AM13 Amount Exceeds Clearing System Limit
 Transaction amount exceeds the limit set by a clearing system.
AM14 Amount Exceeds Agreed Limit
 Transaction amount exceeds limit agreed between bank and client.
AM15 Amount Below Clearing System Minimum
 Transaction amount is below minimum value of a clearing system.
AM16 Invalid Group Control Sum
 Control Sum at the Group level is invalid.
AM17 Invalid Payment Info Control Sum
 Control sum at the Payment Information level is invalid.
AM18 Invalid Number Of Transactions
 Number of transactions is either invalid or missing.
AM19 Invalid Group Number of Transactions
 Number of transactions at the Group level is either invalid or missing.
AM20 Invalid Payment Info Number Of Transactions
 Number of transactions at the Payment Information level is invalid.
AM21 Limit Exceeded
 Transaction amount exceeds limits agreed between bank and client.
ARDT Transaction has already been returned
 Specified transaction has already been returned.
BE01 Inconsistent With End Customer
 Identification of end customer is not consistent with associated account number.
BE04 Missing Creditor Address
 Specification of creditor's address, which is required for payment, is either missing or incorrect.
BE05 Identifier of the Creditor Incorrect
 Creditor identifier is not correct or has been changed without an amendment had been reported.
BE06 Unknown End Customer
 Specified end customer is not known at associated Sort/National Bank Code or does no longer exist.
BE07 Missing Debtor Address
 Specification of debtor's address, which is required for payment, is either missing or incorrect.
BE08 Missing Debtor Name
 Debtor name is missing.
BE09 Invalid Country
 Country code is either invalid or missing.
BE10 Invalid Debtor Country
 Debtor country code is either invalid or missing.
BE11 Invalid Creditor Country
 Creditor country code is either invalid or missing.
BE12 Invalid Country Of Residence
 Country code of residence is either invalid or missing.
BE13 Invalid Debtor Country Of Residence
 Country code of debtor's residence is either invalid or missing.
BE14 Invalid Creditor Country Of Residence
 Country code of creditor's residence is either invalid or missing.
BE15 Invalid Identification Code
 Identification code is either invalid or missing.
BE16 Invalid Debtor Identification Code
 Debtor or Ultimate Debtor identification code is either invalid or missing.
BE17 Invalid Creditor Identification Code
 Creditor or Ultimate Creditor identification code is either invalid or missing.
BE18 Invalid Contact Details
 Contact details are either invalid or missing.
BE19 Invalid Charge Bearer Code
 Charge bearer code for transaction type is invalid.
BE20 Invalid Name Length
 Name length exceeds local rules for specified payment type.
BE21 Missing Name
 Name is either invalid or missing.
BE22 Missing Creditor Name
 Creditor name is missing.
CNOR Creditor Bank is not registered under this BIC in the CSM
 Creditor bank is not registered under this BIC at the CSM. Contact the creditor bank.
CURR Incorrect Currency
 Currency of the pay­ment is incorrect.
CUST Requested by Customer
 Cancellation is requested by the debtor.
CUTA Cancel Upon Unable to Apply
 Cancellation requested because an investiga­tion request has been received and no remedi­ation is possible.
DNOR Debtor Bank is not registered under this BIC in the CSM
 Debtor Bank is not registered under this BIC in the CSM. Contact debtor to agree on another means of payment.
DS01 Electronic Signatures Correct
 Electronic signature is correct.
DS02 Order Cancelled
 An authorized user has cancelled the order.
DS03 Order Not Cancelled
 User’s attempt to cancel the order was not successful.
DS04 Order Rejected
 Order has been rejected by the bank side (for reasons concerning content).
DS05 Order Forwarded For Post processing
 Order is correct and can be forwarded for post processing.
DS06 Transfer Order
 Order was transferred to VEU.
DS07 Processing OK
 All actions concerning the order could be done by the EBICS bank server.
DS08 Decompression Error
 Decompression of the file was not successful.
DS09 Decryption Error
 Decryption of the file was not successful.
DS0A Data Sign Requested
 Data signature is required.
DS0B Unknown Data Sign Format
 Data signature for the format is invalid or not available.
DS0C Signer Certificate Revoked
 Signer certificate is revoked.
DS0D Signer Certificate Not Valid
 Signer certificate is not valid (is either revoked or not active).
DS0E Incorrect Signer Certificate
 Signer certificate is not present.
DS0F Signer Certification Authority Signer Not Valid
 Authority of the signer certification sending the certificate is unknown.
DS0G Not Allowed Payment
 Signer is not allowed to sign an operation of the specified type.
DS0H Not Allowed Account
 Signer is not allowed to sign for the specified account.
DS0K Not Allowed Number Of Transaction
 Transaction number is over the number allowed for this signer.
DS10 Signer 1 Certificate Revoked
 Certificate is revoked for the first signer.
DS11 Signer 1 Certificate Not Valid
 Certificate is not valid (is either revoked or not active) for the first signer.
DS12 Incorrect Signer 1 Certificate
 Certificate is not present for the first signer.
DS13 Signer Certification Authority Signer 1 Not Valid
 Authority of signer certification sending the certificate is unknown for the first signer.
DS14 User Does Not Exist
 User does not exist within the system.
DS15 Identical Signature Found
 Same signature has already been sent to the bank.
DS16 Public Key Version Incorrect
 Public key version is not correct. This code is returned when a customer sends signature files to the financial institution after conversion from an older program version (old ES format) to a new program version (new ES format) without having carried out reinitialisation with regard to a public key change.
DS17 Different Order Data In Signatures
 Order data in signatures don’t match.
DS18 Repeat Order
 File cannot be tested; the complete order has to be repeated. This code is returned in the event of a malfunction during the signature check, e.g. not enough storage space.
DS19 Electronic Signature Rights Insufficient
 User’s rights (concerning his signature) are insufficient to execute the order.
DS20 Signer 2 Certificate Revoked
 Certificate is revoked for the second signer.
DS21 Signer 2 Certificate Not Valid
 Certificate is not valid (is either revoked or not active) for the second signer.
DS22 Incorrect Signer 2 Certificate
 Certificate is not present for the second signer.
DS23 Signer Certification Authority Signer 2 Not Valid
 Authority of signer certification sending the certificate is unknown for the second signer.
DS24 Waiting Time Expired
 Waiting time expired due to incomplete order.
DS25 Order File Deleted
 Order file has been deleted by the bank server (for multiple reasons).
DS26 User Signed Multiple Times
 Same user has signed multiple times.
DS27 User Not Yet Activated
 User is not yet activated (technically).
DT01 Invalid Date
 Invalid date (e.g. wrong settlement date).
DT02 Invalid Creation Date
 Invalid creation date and time in Group Header.
DT03 Invalid Non Processing Date
 Invalid non-processing date (e.g. weekend or local public holiday).
DT04 Future Date Not Supported
 Future date is not supported.
DT05 Invalid Cut Off Date
 Associated message, payment information block or transaction was received after agreed processing cutoff date, i.e., date in the past.
DT06 Execution Date Changed
 Execution date has been modified in order for transaction to be processed.
DU01 Duplicate Message ID
 Message ID is not unique.
DU02 Duplicate Payment Information ID
 Payment Information Block is not unique.
DU03 Duplicate Transaction
 Transaction is not unique.
DU04 Duplicate End To End ID
 End To End ID is not unique.
DU05 Duplicate Instruction ID
 Instruction ID is not unique.
DUPL Duplicate Payment
 Submitted payment is a duplicate of another payment.
ED01 Correspondent Bank Not Possible
 Correspondent bank is not possible.
ED03 Balance Info Request
 Сomplementary balance information is requested.
ED05 Settlement Failed
 Settlement of the transaction has failed.
EMVL EMV Liability Shift
 Card payment is fraudulent and was not processed with EMV technology for an EMV card.
FF01 File Format incomplete or invalid
 1) XML file was not filled out completely or is inorrect;
2) There is a syntax error in the file;
3) Creditor bank or its intermediary bank did not complete a XSD check before submitting the file into the scheme.
FF02 Syntax Error
 Syntax error reason is provided as narrative information in the additional reason information.
FF03 Invalid Payment Type Information
 Payment Type Information is either invalid or missing.
FF04 Invalid Service Level Code
 Service Level code is either invalid or missing.
FF05 Operation code/transaction code type incorrect (Direct Debit Type (CORE, COR1) incorrect)
 SDD Core: specified identification code of the scheme (i.e. local instrument) is incorrect.
FF06 Invalid Category Purpose Code
 Category Purpose code is either invalid or missing.
FF07 Invalid Purpose
 Purpose is either invalid or missing.
FF08 Invalid End To End Id
 End to End ID is either invalid or missing.
FF09 Invalid Cheque Number
 Cheque number is either invalid or missing.
FF10 Bank System Processing Error
 File or transaction cannot be processed due to technical issues at the bank side.
FOCR Following Cancellation Request
 Designation for a return on the basis of a recall request.
FRAD Payment effected fraudulently
 Payment is fraudulent originated.
ID01 Corresponding Original File Still Not Sent
 Signature file was sent to the bank but the corresponding original file has not been sent yet.
LEGL Legal Decision
 Rejection on legal grounds.
MD01 No mandate
 1) Mandate does not exist;
2) B2B mandate have not been confirmed by the debtor;
3) Refund transaction is unauthorised (For SDD Core collections only);
4) Mandate has been cancelled.
MD02 Mandate data missing or incorrect
 1) Mandate data in the mandate related information is not identical to those in the mandate (amendments had not been communicated);
2) Mandate data is not consistent with version that has been already received for the UMR;
3) In case of mandate amendment: the original IBAN and the IBAN in the collection are the same.
MD03 Invalid File Format For Other Reason Than Grouping Indicator
 File format is either incomplete or invalid.
MD05 Collection Not Due
 Creditor or creditor's agent should not have collected the direct debit.
MD06 Disputed authorized transaction
 Unconditional refund of a transaction. Used for SDD Core collections only.
MD07 Debtor Deceased
 Debtor has deceased. Used for SDD Core collections only.
MD08 No Mandate Service By Agent
 Receiving agent does not offer specified mandate service.
MD09 No Mandate Service On Customer
 Account is not open to specified mandate service.
MD10 No Mandate Service For Specified
 Account is not open to specified mandate service for this particular creditor.
MD11 Unrecognised Agent
 Agent to whom the message needs to be forwarded cannot be located.
MD12 Not Unique Mandate Reference
 Mandate identification is not unique to the creditor.
MD13 Incorrect Customer Authentication
 There is a problem with the customer authentication.
MD14 Incorrect Agent
 Agent in the payment workflow is incorrect.
MD15 Incorrect Currency
 Specified currency is incorrect.
MD16 Requested By Customer
 Cancellation/amendment is requested by the debtor.
MD17 Requested By Initiating Party
 Cancellation/amendment is requested by the creditor.
MS02 Refusal by the Debtor
 Reason has not been specified by end customer.
MS03 Reason not specified
 Reason has not been specified by agent.
NARR Narrative
 Reason is provided as narrative information in the additional reason information.
NOAS No Answer From Customer
 There is no response from payee.
NOOR No Original Transaction Received
 Original credit transfer has never been received.
PART Partial Rejection Of Bulks
 Bulks are partially rejected.
PINL PIN Liability Shift
 Card payment is fraudulent and was processed as EMV transaction without PIN verification.
PY01 The Beneficiary Or The Ordering Bank Is Not Participant In The EBA
 Transaction cannot be processed because the beneficiary and/or the ordering bank is not reported as a direct or indirect participant in the EBA.
RC01 Bank Identifier (BIC) Incorrect
 Specified bank identifier code is mal-formatted or incorrect.
RC02 Invalid Bank Identifier
 Bank identifier is either invalid or missing.
RC03 Invalid Debtor Bank Identifier
 Debtor bank identifier is either invalid or missing.
RC04 Invalid Creditor Bank Identifier
 Creditor bank identifier is either invalid or missing.
RC05 Invalid BIC Identifier
 BIC identifier is either invalid or missing.
RC06 Invalid Debtor BIC Identifier
 Debtor BIC identifier is either invalid or missing.
RC07 Invalid Creditor BIC Identifier
 Creditor BIC identifier is either invalid or missing.
RC08 Invalid Clearing System Member Identifier
 Clearing System Member identifier is either invalid or missing.
RC09 Invalid Debtor Clearing System Member Identifier
 Debtor Clearing System Member identifier is either invalid or missing.
RC10 Invalid Creditor Clearing System Member Identifier
 Creditor Clearing System Member identifier is either invalid or missing.
RC11 Invalid Intermediary Agent
 Intermediary Agent is either invalid or missing.
RC12 Missing Creditor Scheme Id
 Creditor Scheme ID is either invalid or missing.
RF01 Not Unique Transaction Reference
 Transaction reference is not unique within the message.
RJCT Complete Rejection Of Bulks
 Bulks are rejected completely.
RR01 Regulatory Reason
 Specification of the debtor’s account or unique identification needed for reasons of regulatory requirements is insufficient or missing.
RR02 Regulatory Reason
 Specification of the debtor’s name and/or address needed for regulatory requirements is insufficient or missing.
RR03 Regulatory Reason
 Specification of the creditor’s name and/or address needed for regulatory requirements is insufficient or missing.
RR04 Regulatory Reason
 Only to be used for Regulatory Reason other than RR01, RR02 or RR03.
RR05 Regulatory Information Invalid
 Regulatory or Central Bank Reporting information is either missing, incomplete or invalid.
RR06 Tax Information Invalid
 Tax information is either missing, incomplete or invalid.
RR07 Remittance Information Invalid
 Remittance information structure does not comply with rules for specified payment type.
RR08 Remittance Information Truncated
 Remittance information is truncated to comply with rules for specified payment type.
RR09 Invalid Structured Creditor Reference
 Structured creditor reference is either invalid or missing.
RR10 Invalid Character Set
 Supplied character set is not valid for specified country and payment type.
RR11 Invalid Debtor Agent Service ID
 Identification of a bank proprietary service is either invalid or missing.
RR12 Invalid Party ID
 Identification required within specified country or payment type is either invalid or missing.
SL01 Specific Service offered by the Debtor Bank
 All debtor-invoked consumer-right rejects creditor blocking, collection amount limitations and collection frequency limitations.
SL02 Specific Service offered by Creditor Agent
 Due to specific service offered by the Creditor Agent.
SVNR Service Not Rendered
 Card payment is returned since rendered cash amount was not correct or goods or a service was not rendered to the customer, e.g. in an ecommerce situation.
TA01 Transmisson Aborted
 Transmission of the file was not successful and had to be aborted for technical reasons.
TD01 No Data Available
 There is no data available for downloading.
TD02 File Non Readable
 File cannot be read (e.g. unknown format).
TD03 Incorrect File Structure
 File format is either incomplete or invalid.
TECH Technical problems resulting in erroneous credit transfer
 Techinal problems resulting in erroneous SDDs.
TM01 Invalid Cut Off Time
 Associated message was received after agreed processing cutoff time.
TS01 Transmission Successful
 Technical transmission of the file was successful.
TS04 Transfer To Sign By Hand
 Order was transferred to pass by accompanying note signed by hand.
UPAY Undue Payment
 Payment is not justified.
VR01 Transaction data integrity validation error
 Transaction data has not been validated by the processor.
XD19 Incorrect IBAN
 IBAN format is invalid. Issued if the country code is a valid ISO or SEPA country code but structure of IBAN or check digits is incorrect.
XD75 Unauthorised element in the following combination
 There is an unauthorised element in the following combination.
XT13 Incorrect file structure
 Transaction contains at least one unsupported field or at least one mandatory field is missing from the transaction.
XT27 Incorrect BIC
 Transaction contains at least one element with a BIC that is not SEPA-reachable.
XT33 Incorrect XML field
 The content of at least one XML element is not in the format required. The invalid XML field is indicated by the
error code.
XT43 Incorrect type of direct debit
 Type of direct debit is incorrect.
XT53 Verification of the creditor identifier failed
 Verification of creditor indentifiers in structure/checksum has failed.
XT73 Invalid Country Code
 Two characters forming the country code do not constitute a valid ISO or SEPA country code.
XT74 Invalid underlying original transaction
 Underlying original transaction is invalid. Further check is required.
XT75 Invalid status of underlying original transaction
 Status of underlying original transaction is invalid. No further action is required.
XT77 The originally instructed amount was not found or does not match the original transaction amount
 The originally instructed amount was not found or does not match the original transaction amount.
XT78 Amount validation failed
 Transaction amount validation has failed.
XT79 Debtor Agent is not permitted to receive direct debits
 Debtor agent is not permitted to receive direct debits.
XT80 Creditor Agent is not permitted to send direct debits
 Creditor agent is not permitted to send direct debits.
XT85 No Settlement Cycle Available
 Settlement cycles are not available.
XT90 Invalid use of a Technical BIC
 Technical BIC usage is not valid.
XT99 Direct debit rejected for other reasons
 Credit transfer was rejected for other reasons.
XX01 Processing Cancelled
 Transaction processing has been cancelled by a customer.
Direct Debit Response Codes (UK BACS)  
Code User Message Developer Message/Description
0 Refer to payer
 Reason for non-payment need to be established from the payer.
1 Instruction canceled
Paying bank has cancelled an instruction.
2 Payer deceased
 Account holder is deceased (used in the event of a representative payee, guardian, or trustee).
3 Account transferred
 Account has been transferred to a new bank or building society.
4 Advance notice disputed
 Payer disputes time, amount or frequency of advance notice and has requested single payment to be countermanded.
5 No Account
Account number is not recognised at the paying bank.
6 No Instruction
 Instruction does not exist on paying bank's database.
7 Amount differs
 Payer states the amount of the direct debit differs from the amount in the advance notiice to payer.
8 Amount not yet due
 Payers states date of debiting is in advance of the due date specified in the advance notice to the payer.
9 Presentation overdue
 1) Payer states date of presentation is more than 3 working days after due date in advance notice to payer;
2) Re-presentation of unpaid direct debit is more than one month from original direct debit processing day.
A Service user differs
 Identity of service user differs from DDI.
B Account Closed
 Payer has closed an account for an unknown reason.
C Account transferred to a different branch of bank/building society
 New account details need to be supplied to the service user.
D Advance notice disputed
 Payer disputes time, amount or frequency of advance notice and has requested single payment to be countermanded.
E Instruction amended
 Paying bank will advise amendment via ADDACS message.
F Invalid account type
 Paying bank dose not allow direct debits on this type of account.
G Bank will not accept Direct Debits on this type of Account
Paying bank does not allow direct debits on this type of account.
H Instruction has expired
 Occurs when a service user attempts to convert a DDI which is shown as expired on the paying bank's database.
I Payer reference is not unique
 Paying bank has matched the DDI to an existing DDI with a similar reference that has more or fewer characters.
K Instruction canceled by paying bank
 Paying bank has cancelled the DDI.
L Incorrect payer's Account Details
 1) The sort code or account number has failed the modulus check;
2) The sort code does not exist;
3) The account number is not all numeric or is all zeros;
4) The account type is invalid.
M Transaction Code/User Status incompatible
Transaction codes, which are not allowed whilst in this status, have been sent.
N Transaction disallowed at payer's branch
Paying banks have disallowed the set-up of DDIs at the branch in field 1 of the transaction. Service user should refer back to their payer and obtain a DDI for a different account.
O Invalid reference
 The reference in one of the DDI record fields does not comply with the AUDDIS rules.
P Payer's Name not present
 Validation has detected that payer's name field is blank. A payer's name should always be entered.
Q Servise user's name blank
 Validation has detected that servise user's name field is blank. A servise user's company or tranding name should always be entered.
R Instruction re-instated
 Paying bank may re-instate a cancelled DDI up to two months from cancelation.
V Transaction data integrity validation error
 Transaction data has not been validated by the processor.
X Processing Cancelled
 Transaction processing has been cancelled by a customer.
Direct Debit Response Codes (US ACH)  
Code Type User Message Developer Message/Description
E03 Soft Transaction data integrity validation error
 Transaction data has not been validated by the processor.
E05 Hard Bank account is blacklisted
 ACH account is blacklisted.
R01 Soft Insufficient Funds
 Available balance is not sufficient to cover the dollar amount of the debit entry.
R02 Hard Account Closed
 Previously active account has been closed by customer or customer's bank.
R03 Hard No Account/Unable to Locate Account
 Account structure is valid and passes editing process, but does not correspond to individual or is not an open account (this can also be because the account type is wrong).
R04 Hard Invalid Account Number
 The account number is not valid. The transaction may have failed the digit validation or may contain an incorrect number of digits.
R05 Hard Unauthorized debit to consumer account using corporate SEC Code
 A CCD debit entry was transmitted to a consumer account and was not authorized by the consumer.
R06 Hard ODFI Requests Return
 ODFI has requested RDFI to return the ACH entry (optional to RDFI).
R07 Hard Revoked Authorization
 Consumer, who previously authorized ACH payment, has revoked authorization from originator. Must be returned no later than 60 days from settlement date and customer must sign affidavit.
R08 Hard Stop Payment or Stop on Source Document
 Receiver of a recurring debit transaction has stopped payment on a specific ACH debit. RDFI should verify the receiver's intent when a request for stop payment is made to insure this is not intended to be a revocation of authorization.
R09 Soft Uncollected Funds
 Sufficient book or ledger balance exist to satisfy dollar value of the transaction in process of collection brings available or cash reserve balance below dollar value of the debit entry.
R10 Hard Advised as Unauthorized
 Customer has authorized RDFI that originator of transaction is not authorized to debit account. Must be returned no later than 60 days from settlement date of original entry and customer must sign affidavit.
R11 Hard Check Safekeeping
 Used when returning a check safekeeping entry, RDFI should use appropriate field in addenda to specify reason for return (i.e, "exceeds dollar limit," "stale date," etc).
R12 Hard Account at Other Branch
 Financial institution receives entry destined for an account at a branch that has been sold to another financial institution.
R13 Hard RDFI not qualified to participate
 Financial institution is not qualified to participate in ACH or the routing number is incorrect.
R14 Hard Death of Representative Payee
 Account holder is deceased (used in the event of a representative payee, guardian, or trustee).
R15 Hard Death of Beneficiary or Account Holder
 (1) The beneficiary is the person entitled to the benefits and is deceased. The beneficiary may or may not be the account holder; (2) the account holder (acting in a non-representative payee capacity) is an owner of the account and is deceased.
R16 Hard Account Frozen
 Funds unavailable due to specific action by the RDFI or by legal action.
R17 Hard File Record Edit Criteria (Specify)
 Fields not edited by the ACH operator are edited by the RDFI. Fields causing processing error must be identified in the addenda record of return.
R18 Hard Improper Effective Entry Date
 The date entered in the ACH transaction record is invalid and the transaction cannot be processed. The effective entry date for a debit entry is more than one banking day after the processing date.
R19 Hard Amount Field Error
 The payment was entered for an amount of $0, or a paper-check conversion (ARC or BOC) was entered for over $25,000.
R20 Hard Non-Transaction Account
 ACH entry is destined for a non-transaction account (i.e., an account against which transactions are prohibited or limited).
R21 Hard Invalid Company ID
 The identification number used in the company identification field is not valid.
R22 Hard Invalid Individual ID Number
 In CIE and MTE entries, the individual ID number is used by the receiver to identify the account. The receiver has indicated to the RDFI that the number with which the originator was identified is not correct.
R23 Hard Credit Entry Refused by Receiver
 Receiver refuses credit entry because of one of the following conditions:
  • minimum amount required by receiver has not been remitted;
  • exact amount required has not been remitted;
  • the account is subject to litigation and the receiver will not accept the transaction;
  • acceptance of the transaction results in an overpayment;
  • the originator is not known by the receiver;
  • the receiver has not authorized this credit entry to this account.
R24 Hard Duplicate Entry
 RDFI has received what appears to be a duplicate entry (i.e., trace number, date, dollar amount and/or other data matches another transaction).
R25 Hard Addenda Error
 Improper formatting of the addenda record information.
R26 Hard Mandatory Field Error
 For a TEL or WEB ACH transaction, the name of the account holder was not provided. For a CCD transaction, the name of the company was not provided.
R27 Hard Trace Number Error
 Original entry trace number is not valid for return entry or addenda trace numbers do not correspond with entry detail record.
R28 Hard Routing Number Check Digit Error
 The bank routing number is invalid.
R29 Hard Corporate Entry Unauthorized
 RDFI has been notified by receiver (nonconsumer) that entry was not authorized.
R30 Hard RDFI Not Participant in Program
 The customer’s bank does not participate in the ACH network.
R31 Hard ODFI Permits Late Return
 RDFI has been notified by ODFI that ODFI agrees to accept a return entry beyond normal return deadline.
R32 Hard RDFI Non-Settlement
 The RDFI is not able to settle the entry (customer’s bank rejected the transaction).
R33 Hard Return of XCK Entry
 RDFI, at its discretion, returns an XCK entry. This return reason code may only be used to return XCK entries. An XCK entry may be returned up to 60 days after its settlement date.
R34 Hard Limited Participation DFI
 The RDFI's participation has been limited by a federal or state supervisor.
R35 Hard Return of Improper Debit Entry
 ACH charge entries are not permitted on loan accounts.
R36 Hard Return of Improper Credit Entry
 ACH refund entries (with the exception of reversals) are not permitted for use with the WEB code.
R37 Hard Source Document Presented for Payment
 The source document to which an ARC, BOC, or POP entry relates has been presented for payment.
R38 Hard Stop Payment on Source Document
 Stop payment has been placed on a check used for an ARC entry.
R39 Hard Improper Source Document
 The RDFI determines that the source document used for an ARC, BOC or POP entry to its receiver’s account is improper pursuant to source documents subsections.
R40 Hard Return of ENR Entry by Federal Government Agency
 Federal government agency received an ENR believed to be fraudulent and then returned the ENR to the DFI.
R41 Hard Invalid Transaction Code
 Transaction code value is invalid.
R42 Hard Routing Number/Check Digit Error
 Routing number value is invalid.
R43 Hard Invalid DFI Account Number
 Bank account number value is invalid.
R44 Hard Invalid Individual ID Number
 Merchant ID value is invalid.
R45 Hard Invalid Individual Name
 Individual name value is invalid.
R46 Hard Invalid Representative Payee Indicator
 Representative payee indicator value is invalid.
R47 Hard Duplicate Enrollment
 The same enrollment flow was initiated more than once.
R50 Hard State Law Affecting RCK Acceptance
 RDFI is in one of the states that have not accepted the гniform сommercial сode and hasn't 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 Hard Item is Ineligible; Notice not Provided; Signature Not Genuine; Item Altered; Amount of Entry not Accurately Obtained
 An RCK entry may be considered to be ineligible; the originator did not provide notice; all signatures on the item to which the RCK entry relates are not authentic or authorized, or the item to which the RCK entry relates has been altered; the amount of the RCK entry was not accurately obtained from the item.
R52 Hard Stop Payment on Item
 RDFI determines that a stop payment has been placed on the item to which the RCK entry relates. RDFI has 60 days following settlement to return.
R53 Hard Item and ACH Entry Presented for Payment
 In addition to an RCK entry, the item to which the RCK entry relates has also been presented for payment. The Receiver may request immediate credit from the RDFI for an RCK entry for the reason described above. The request must be made in writing within 15 days after the RDFI sends or makes available to the Receiver information relating to that debit entry. The Receiver must also provide the RDFI with a written statement under penalty of perjury, that both the RCK entry and the item to which it relates were presented for payment.
R61 Hard Misrouted Return
 Return entry was sent by RDFI to an incorrect ODFI routing number.
R62 Hard Incorrect Trace Number
 Trace number found in positions 07-21 in the addenda record of the return is different from the trace number of the original entry.
R63 Hard Incorrect Dollar Amount
 Dollar amount in the entry detail record of the return is different from the dollar amount of the original entry.
R64 Hard Incorrect Individual ID
 Individual ID number reflected in the entry detail record of the return is different from the individual ID number used in the original entry.
R65 Hard Incorrect Transaction Code
 Transaction code in the entry detail record of the return is not the return equivalent of the transaction code in the original entry. All entries must be returned as received: i.e., credit as credit, debit as debit, demand as demand, savings as savings.
R66 Hard Incorrect Company ID
 Company ID number used in the company/batch header record of the return is different from the ID number used in the original entry.
R67 Hard Duplicate Return
 ODFI has received more than one return entry for the same original entry.
R68 Hard Untimely Return
 Return entry did not meet the return deadline.
R69 Hard Multiple Errors
 Two or more fields are incorrect (i.e. original entry trace number, amount, individual ID number, company ID and/or transaction code).
R70 Hard Permissible Return Not Accepted
 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 Hard Misrouted Dishonored Return
 ODFI misrouted the dishonored return entry to the wrong RDFI using an incorrect routing number.
R72 Hard Untimely Dishonored Return
 ODFI did not submit the dishonored return entry within the 5 day deadline.
R73 Hard Timely Original Return
 RDFI certifies that the original return entry was submitted within the applicable deadline.
R74 Hard Corrected Return
 RDFI is correcting a previous return entry that was dishonored using return code R69 because it contained incomplete or incorrect information.
R75 Hard 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 Hard 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 Hard Cross Border 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;
  • invalid transaction type value.
R81 Hard Non-Participant in Cross Border 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 IAT entries.
R82 Hard Invalid Foreign Receiving DFI Identification
 The reference used to identify the foreign receiving DFI of an outbound IAT entry is invalid.
R83 Hard Foreign Receiving DFI Unable to Settle
 The IAT entry is being returned due to settlement problems in the foreign payment system.
R84 Hard 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:
  • 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.
R95 Hard Merchant profile configuration issue
 Specified merchant profile was configured incorrectly.
R96 Hard Incorrect merchant setup
 Specified merchant is not set up correctly for the submitted transaction.
R97 Hard Unmapped Returns
 Specified processor's response code is not recognized by the system. The respective request of a received code clarification needs to be addressed to the processor.
R98 Hard Non Participating Bank
 ACH has been returned by non-participating bank.
R99 Hard Transaction rejected by processor
 Submitted transaction has been rejected by the processor.
X01 Soft Processing Cancelled by User
 Transaction processing has been cancelled by a customer.
Direct Debit/eCheck Response Codes (Canada ACH)  
Code Type User Message Developer Message/Description
900 Hard Account information incorrectly entered
 Account information has been entered incorrectly.
901 Hard Insufficient Funds
 Available balance is not sufficient to cover the dollar amount of the debit entry.
902 Hard Account not Found
 The account could not be found and is closed, or that's an older style cheque that doesn't meet the requirements of the Canadian Payments Association.
903 Hard Payment Stopped/Recalled
 Receiver of a recurring debit transaction has stopped payment on a specific ACH debit. RDFI should verify the receiver's intent when a request for stop payment is made to insure this is not intended to be a revocation of authorization.
904 Hard Post/Stale Dated
905 Hard Account Closed
 Previously active account has been closed by a customer or customer's bank.
907 Hard No Debit Allowed
 The receiving financial institution does not allow electronic debit through this type of account.
908 Hard Funds Not Cleared
 The payor/payee has deposited a cheque to their account that has not cleared. The payee did not have enough clear funds in the account to cover the debit amount.
909 Hard Currency/Account Mismatch
 The currency of the transaction does not match the currency of the account.
910 Hard Payor/Payee Deceased
 Account holder is deceased (used in the event of a representative payee, guardian, or trustee).
911 Hard Account Frozen
 Funds unavailable due to specific action by the RDFI or by legal action.
912 Hard Invalid/Incorrect Account No
 The account number is not valid. The transaction may have failed the digit validation or may contain an incorrect number of digits.
914 Hard Incorrect Payor/Payee Name
 The payor/payee name on the transaction does not match the account holder’s name.
915 Hard No Agreement Existed - Business/Personal Refused
 The payor has requested the debit to be returned as they have not signed a PAD agreement authorizing the debit.
916 Hard Not in accordance with Agreement - Personal
 The payor has requested the debit to be returned as the debit has not been issued in accordance with the PAD agreement the customer signed.
917 Hard Agreement Revoked - Personal
 The payor has requested the debit to be returned as they have cancelled the PAD agreement authorizing the debit.
918 Hard No Confirmation/Pre-Notification - Personal
 The payor has requested the debit to be returned as they have did not receive pre-notification of a change to the PAD date or amount, or they did not receive written confirmation of a PAD Agreement executed by electronic means.
919 Hard Not in accordance with Agreement - Business
 The payor has requested the debit to be returned as the debit has not been issued in accordance with the PAD agreement the customer signed.
920 Hard Agreement Revoked - Business
 The payor has requested the debit to be returned as they have cancelled the PAD agreement authorizing the debit.
921 Hard No Pre-Notification - Business
 The payor has requested the debit to be returned as they have did not receive pre-notification of a change to the PAD date or amount, or they did not receive written confirmation of a PAD Agreement executed by electronic means.
922 Hard Customer Initiated Return - Credit Only
 The payee has requested the credit to be returned.
990 Hard Institution in Default
996 Hard Chargeback
 Chargeback has been received.
Payment Card Response Codes  
Code Type User Message Developer Message/Description
A01 Good Approved: XXXXXX (approval code)
 Transaction has been approved.
A02 Good Credit Posted
 Credit has been posted on a cardholder’s account.
A03 Good Void Posted (Auth Reversed)
 Void has been posted on a cardholder’s account (with authorization reversal).
A04 Good No Update
No updates have been made as a result of account updater operation.
A05 Good Partially Approved
 Transaction has been partially approved as a result of split payment.
A06 Good Void Posted (Auth Not Reversed)
 Void has been posted on a cardholder’s account (without authorization reversal).
A07 Good Partial Void Posted
 Partial void has been posted on a cardholder’s account.
A08 Good Partial Refund Posted
 Partial refund has been posted on a cardholder’s account.
A09 Good Incremental Auth Posted
 Increment has been posted on a cardholder’s account.
A10 Good Request Accepted
 Request has been accepted.
A11 Soft Approval (Reversal failed)
 1) Initial transaction was approved by a processor and a subsequent reversal was rejected (void failed).
2) User set partial authorization logic as disabled while submitting a transaction, a processor sent partial auth as a transaction response and a subsequent reversal was rejected.
For both cases, make sure to submit refund API request for the transaction that has received A11 response code.
A21T Soft Offline Approval (Sale Posted)
 Sale transaction has been approved offline.
A22T Soft Offline Approval (Credit Posted)
 Credit card transaction has been approved offline.
D01 Soft Denied by customer's bank
 Transaction has been denied by cardholder's bank.
D02 Hard Invalid Expiration Date
 Cardholder has entered invalid or malformatted expiration date.
D03 Soft Insufficient Funds
 Specified credit card does not have sufficient funds.
D04 Hard Hold - Pick up card
 The cardholder’s bank has declined the transaction and requested cardholder’s credit card to be retained.
D05 Hard Invalid card number
 Specified credit card number is invalid or does not exist.
D06 Hard No account
 Specified credit card number is associated with account that does not exist.
D07 Soft Incorrect PIN
 Entered PIN is incorrect.
D08 Soft CSC is invalid
 CSC value is invalid.
D09 Soft Duplicate Transaction
 The cardholder’s bank has declined the transaction as this transaction appears to be a duplicate transmission.
D10 Hard Card reported lost/stolen
 The cardholder’s bank has declined the transaction and requested the cardholder’s credit card to be retained because the card was reported lost or stolen.
D11 Hard Card reported stolen
 The cardholder’s bank has declined the transaction and requested the cardholder’s credit card to be retained because the card was reported stolen.
D12 Soft Service not allowed
 Cardholder's credit card or merchant processing account is not configured for the specified type of transaction.
D13 Hard Stop Recurring
 Cardholder requested stop of specific recurring payment.
D15 Soft Maximum transaction limit is exceeded
 Maximum transaction limit is exceeded at the moment. Try processing your transaction tomorrow.
D16 Hard Card is Expired
 A transaction was processed on an expired card.
D17 Soft Re-enter Transaction
 An unknown error occurred during the authorization process. Transaction needs to be re-entered.
D18 Soft Bad Amount
 Specified amount value is invalid. Amount must be a positive number.
D19 Soft Unmapped decline
 Specified processor's response code is not recognized by the system. The respective request of a received code clarification needs to be addressed to the processor.
D21 Soft Pin Try Exceeded
 Cardholder has entered the incorrect PIN more than three times.
D22 Hard Refund was not processed/received
 Refund was not processed successfully or has not been received by the cardholder.
D24 Hard Chargeback received
 Chargeback has been received.
D25 Soft Refund limit is reached for the day
 Speified merchant has reached the refund limit allowed per day on the account.
D26 Soft Settlement Failed
 Submitted transaction cannot be settled. Re-check entered account information and try again.
D27 Hard Transaction Error
 Submitted transaction has failed.
D28 Soft Cashback limit exceeded/Cashback unavailable
 Specified amount exceeds cashback limit or cashback is not available.
D29 Soft Card is restricted
 Specified credit card has some restrictions.
D30 Soft Call for Authorization
 To proceed with the transaction, call for authorization is needed to confirm the validity of the card.
D31 Soft Declined due to fraud rules
 Specified credit card appears to be fraudulent.
D32 Soft Declined due to fraud engine decision
 Transaction has been declined because of fraud detected by a fraud engine.
D33 Soft Incorrect merchant setup
 Specified merchant is not set up correctly for the submitted transaction.
D34 Soft Merchant profile configuration issue
Specified merchant profile was configured incorrectly.
D35 Soft Card chip decline
 Transaction has been declined by the chip (for EMV cards only).
D40 Soft AVS Verification Failed
 Address information submitted for tokenization transaction has not passed AVS verification successfully.
D41 Soft Processing Error
 A connection error occurred after the transaction has been submitted.
D42 Soft Data encryption/decryption error
 One or more fields specified in the transaction cannot be encrypted or decrypted.
D43 Soft Account blocked/frozen/inactive
 Specified account has been either blocked, frozen or deactivated.
D44 Soft MAC key synchronization error or MAC value is incorrect
 MAC key used in the transaction is either missing or invalid.
E02 Soft Processing Network Unavailable
 Processing network is temporarily unavailable.
E03 Soft Transaction data integrity validation error
 Batch transaction data is invalid.
E04 Soft Refund limit is reached for the day
 Specified merchant has reached the refund limit allowed per day on the account.
E06 Soft Card is blacklisted
 Payment card is blacklisted.
E07 Soft Tokenization not supported
 Tokenization is not supported by a processor.
E08 Soft Declined by processor
 Direct debit transaction has been declined by a processor.
E09 Soft Processing Network Error
 Error ocurred during the connection process after the transaction was submitted.
E10 Soft 3D Secure Verification Failed
 3D Secure verification has failed.
E31 Soft Declined due to pre-processing rules
 Transaction has been declined due to the pre-processing rules
X01 Hard Processing Cancelled by User
 Transaction processing has been cancelled by a cardholder.
X02 Soft Pending processing
 Batch transaction is still processed on a processor's side.
X03 Soft 3D Secure Verification Required
 3D Secure verification is required.
X04 Soft Processing cancelled: the request has expired.
 Transaction processing has been cancelled due to a user being inactive for a time period specified as a timeout (default: 15 minutes).
Tokenization Error Response Codes  
Code User Message Developer Message/Description
P01 Invalid Card Number / Invalid Account Number
 Specified accountNumber value is either invalid or malformatted. If a payment card has been used, then Invalid Card Number message is shown, if a bank account - Invalid Account Number.
P02 Invalid Expiration Date / Invalid Routing Number
Specified accountAccessory value is either invalid or malformatted. If a payment card has been used, then Invalid Expiration Date message is shown, if a bank account - Invalid Routing Number.
P03 Incorrect account setup
 Configured tokenization credentials are either invalid or malformatted.
P04 Token not found
 Specified token is either invalid or not found within the system.
P19 Unmapped response code
 Response code returned by the underlying processor has no mapping within the system.
P20 Encryption certificate validation error
 Either Intermediate or P2PE certificate is invalid.
Copyright © United Thinkers. (UniPay - Payment Gateway Software)
All Logos and Trademarks used or mentioned on this page are copyrighted property of their respective owners and are used for display purposes only.