Payment Transaction Response Codes

This is sent to acknowledge that the submitted transaction has been received.

Note: This response applies only to V10.x versions of the API.

No action required.

The authorized amount is less than the requested amount.

Offline approval issued while the terminal is unable to communicate with the issuer.

Offline approval issued while the terminal is unable to communicate with the issuer.

The payment status inquiry was successful.

Approval of the Buy Now Pay Later transaction depends upon the successful completion of the BNPL provider checkout page by the shopper.

The consumer did not complete the BNPL checkout form in a timely manner (checkout URL expired). You can submit a new BNPLAuthorizationRequest to try again.

There is a problem with the card or PINless Debit network. Contact the network for more information.

There is a problem with the issuer network. Please contact the issuing bank.

There is a temporary problem with your submission. Please re-submit the transaction.

You submitted the transaction to a Hot-Hot URL, but are not configured for multi-site processing.

We were unable to process the transaction due to a transitory communication issue to an internal or external service. Please try submitting the transaction again.

The card does not have enough funds to cover the transaction.

The total amount of the original Authorization has been used.

Appears in Declined Transaction report.

You should retry the transaction after waiting 1 hour.

You should retry the transaction after waiting 24 hours.

You should retry the transaction after waiting 2 days.

You should retry the transaction after waiting 4 days.

You should retry the transaction after waiting 6 days.

You should retry the transaction after waiting 8 days.

You should retry the transaction after waiting 10 days.

There is an unspecified problem, contact the issuing bank.

There is an unspecified problem; contact AMEX.

There is an unspecified problem; contact Diners Club.

There is an unspecified problem; contact Discover.

There is an unspecified problem; contact JBS.

There is an unspecified problem; contact Visa or Mastercard.

Some data is out of date; contact the issuer to update this information.

This transaction exceeds the daily approval limit for the card.

There is an unspecified problem; contact the phone number provided.

There is an unspecified problem with the submitted PIN. Confirm value and retry.

The PIN did not change. Please retry.

Mastercard identified the card number as belonging to a multi-use virtual card and approved the transaction (MAC code of 43).

Mastercard identified the card number as belonging to a multi-use virtual card and generated a soft decline (MAC code of 43).

The submitted card number indicates a non-reloadable, prepaid card. Returned when the transaction declined and has a MAC code of 40.

The submitted card number indicates a single-use virtual card. Returned when the transaction declined and has a MAC code of 41.

Cardholder data is incorrect; contact the issuing bank.

The submitted card number indicates a non-reloadable, prepaid card. Returned when the transaction approved and has a MAC code of 40.

The submitted card number indicates a single-use virtual card. Returned when the transaction approved and has a MAC code of 41.

This is a Mastercard specific decline code associated with the MAC (Merchant Advice Code). The MAC value is either unknown or null. Contact the issuing bank for additional information.

This is a Mastercard specific decline code associated with the MAC (Merchant Advice Code). The MAC value is either unknown or null. Contact the issuing bank for additional information.

This is a Mastercard specific decline code associated with the MAC (Merchant Advice Code). The MAC value is either unknown or null. Contact the issuing bank for additional information.

The card is invalid or expired. Contact cardholder to update information.

The transaction is not permitted, or the card is not available for use. Verify the information and resubmit the transaction.

A Query transaction response indicating that the original transaction was found.

A Query transaction response indicating that the original transaction was not found.

A Query transaction response indicating that the original transaction was found, but the final response information is not yet available.

A Query transaction response indicating that you are not enabled for use of the Query transaction.

When submitting a Query transaction, you must include either the origId or origCnpTxnId.

When submitting a Query transaction with the showStatusOnly flag set to Y, you must include the origCnpTxnId element.

This method of payment does not support incremental auths.

You set the authIndicator in the initial auth to Estimated. You must set the authIndicator in any subsequent auths to Incremental.

You used the message structure for an initial auth. Resubmit the transaction using the message structure for an incremental auth.

You cannot submit an incremental auth if the initial auth did not include an authIndicator value of Estimated.

Resubmit the transaction using the cnpTxnId from the initial, estimated auth.

The incremental auth increased the transaction total to a value above the maximum transaction amount allowed.

The allowed MCC white list does not include the submitted MCC. Resubmit the transaction with an allowed MCC, or ask your Relationship Manager about adding the submitted MCC to the white list.

This is an Account Updater response indicating a set-up problem that must be resolved prior to submitting another request file. Escalate this to your Relationship Manager.

Your organization is not certified or enabled for IIAS/FSA transactions.

An unspecified error was returned by the issuer. Please retry the transaction and if the problem persist, contact the issuing bank.

The issuer indicated that the gift card should be removed from use.

The specified amount is invalid for this transaction.

The reversal transaction was unsuccessful.

Contact your Relationship Manager.

The submitted card was reported as lost and should be removed from use.

The submitted card was reported as stolen and should be removed from use.

The specified Gift Card is not available for use.

The Deactivate transaction is invalid for the specified card.

The submitted card is already active.

The submitted card has not been activated.

The submitted card has already been deactivated.

The activate or load amount exceeds the maximum allowed for the specified gift Card.

The activate transaction is not valid or can no longer be reversed.

The transaction referenced in the reversal transaction does not exist.

The transaction was declined because it was submitted with the incorrect security code.

The transaction would violate the law.

The transaction is a duplicate of a previously submitted transaction.

Appears in Declined Transaction report.

Contact your Relationship Manager.

The BIN is no longer valid.

No balance remains on gift Card.

The Gift Card has been seized by the government while resolving an estate.

You attempted to use a Closed Loop Gift Card reversal transaction to reverse a credit card transaction. For example, you cannot use a Deposit Reversal transaction to reverse a Capture. To reverse a credit card Capture transaction, use a Credit transaction.

Issuer reported message format is incorrect. Contact your Relationship Manager.

System error - try again later.

The refund is tied to a deposit that is still in pending state or the state is in doubt. You can retry the refund at a later time.

The refund is tied to a deposit that failed.

The refund is tied to a deposit that succeeded, but was declined by PayPro.

You must use the Gift Card version of these transactions for Gift Cards (i.e., giftCardCapture, giftCardCredit, and giftCardAuthReversal).

The account number is not valid; contact the cardholder to confirm information or inquire about another form of payment.

The payment type was selected as one card type (e.g. Visa), but the card number indicates a different card type (e.g.

Mastercard).

This is a card present response, but in a card not present environment. Do not process the transaction and contact the issuing bank.

The card has been designated as lost or stolen; contact the issuing bank.

The card is expired.

The original Authorization is no longer valid, because it has expired. You can not perform an Authorization Reversal for an expired Authorization.

Appears in Declined Transaction report.

The card has a restriction preventing approval for this transaction. Please contact the issuing bank for a specific reason.

You may also receive this code if the transaction was declined due to FraudSight Prior Fraud Advice Filtering and you are using a schema version V8.10 or older.

This transaction is being declined due the operation of the FraudSight Prior Chargeback Card Filtering Service or the card has a restriction preventing approval if there are any chargebacks against it.

This transaction is being declined due the operation of the FraudSight Prepaid Card Filtering service.

The track data is not valid.

The deposit is already referenced by a chargeback; therefore, a refund cannot be processed against the original transaction.

Appears in Declined Transaction report.

This transaction is being declined due the operation of the FraudSight International Card Filtering Service.

This is returned when the transaction involves a US based merchant processing Canadian transactions has a transaction that uses a US card.

This transaction is being declined due the operation of the FraudSight Auth Fraud Velocity Filtering Service.

This refund transaction is a duplicate for one already processed automatically by the Fraud Chargeback Prevention Service (FCPS).

Appears in Declined Transaction report.

The submitted card is under sanction and cannot be processed.

This transaction is being declined due the operation of the Auth Fraud Advice Filtering Service.

This transaction is being declined due the operation of the FraudSight Auth Fraud AVS Filtering Service.

The expiration date is invalid

The card is not allowed to make purchases from this merchant (e.g. a Travel only card trying to purchase electronics).

The transaction is not permitted; contact the issuing bank.

The system also returns this code if you attempt to use a Void transaction to cancel a Gift Card transaction.

The card number references an issuer that does not exist. Do not process the transaction.

The PIN provided is invalid.

Appears in Declined Transaction report

The transaction is not permitted; contact the issuing bank.

(Referring to a debit card) The incorrect PIN has been entered excessively and the card is locked.

Merchant does not allow that card type or specific transaction.

Recurring/Installment Payments no longer accepted by the card issuing bank.

This payment type is not accepted by the issuer.

For a Cardholder Authorized Terminal Transaction the POS capability must be set to magstripe.

For a Cardholder Authorized Terminal Transaction the POS Cardholder ID must be set to nopin.

You can not perform an Authorization Reversal transaction for this payment type.

For a merchant initiated reversal against an American Express authorization, the reversal amount must match the authorization amount exactly.

Retry the transaction.

>The transaction amount is invalid (too high, too low, or above merchant transaction limit). For example, less than 0 for an authorization, or less than .01 for other payment types.

The amount submitted with this FSA/Healthcare transaction is invalid. The FSA amount must be greater than 0, and cannot be greater than the transaction amount.

The billing descriptor prefix submitted is not valid.

Appears in Declined Transaction report.

The billing descriptor is not valid because you are not authorized to send transactions with custom billing fields.

Appears in Declined Transaction report.

The Report Group specified in the transaction is invalid, because it is either not in the defined list of acceptable Report Groups or there is a mis-match between the Report Group and the defined Billing Descriptor.

The issuing bank has put a temporary hold on the card.

There is an unspecified problem; contact the issuing bank for more details.

Note: This code can be a hard or soft decline, depending on the method of payment, and other variables.

Card Present transaction that requires a picture ID match.

The CVV2/CID is invalid.

You are not certified to submit 3-D Secure transactions.

Submitted Level III data is bad or missing.

The FSA Transactions submitted does not contain the <healtcareIIAS> data element.

The transaction was declined due to the security code (CVV2, CID, etc) not matching.

There were no transactions found with the specified Transaction Id.

Appears in Declined Transaction report.

The authorization for this transaction is no longer available. Either the authorization has already been consumed by another capture, the authorization has expired, or the cardholder revoked the authorization.

Appears in Declined Transaction report.

This transaction cannot be voided; it has already been delivered.

Appears in Declined Transaction report.

This transaction (both capture and refund) has been voided.

Appears in Declined Transaction report.

The submitted account number is invalid. Confirm the original account number or check NOC for new account number.

The amount of the credit is greater than the capture, or the amount of this credit plus other credits already referencing this capture are greater than the capture amount.

Appears in Declined Transaction report.

NACHA rules allow two redeposit attempts within 180 days of the settlement date of the initial deposit attempt. This threshold has been exceeded.

Appears in Declined Transaction report.

NACHA rules only allow redeposit attempts against deposits returned for Insufficient or Uncollected Funds.

Appears in Declined Transaction report.

The check number is invalid.

The redeposit attempted against an invalid transaction type.

Appears in Declined Transaction report.

There is a problem with the system. Contact your Relationship Manager.

Do not send additional redeposit transactions, since the original transaction was processed.

Appears in Declined Transaction report.

The transaction was intercepted because it is being auto recycled by the Recycling Engine. While designated a Soft Decline, the system always intercepts submitted transactions, while the Recycling Engine is active.

The transaction was intercepted because auto recycling has completed with a final decline.

The submitted transaction contained a surcharge and the merchant is not enabled for surcharging.

The use of a surcharge is only allowed for Visa and Mastercard methods of payment.

You cannot apply a surcharge to a transaction using a debit or prepaid card.

The surcharge in the submitted transaction exceeded the maximum allowed for a surcharge.

The SEPA Direct Debit processing network declined the transaction for unspecified reasons. Some possible reasons are: insufficient funds, IBAN/Name disagreement, red flag on account, etc.

The secondary amount exceeded the sale amount in the submitted transaction.

The submitted method of payment does not allow the use of Convenience Fees.

The secondary amount must be a positive integer.

Transactions set to allow partial authorizations cannot include a secondary amount.

If the associated sale or capture transaction included a secondary amount, an associated partial refund must include a secondary amount.

If the associated sale or capture transaction did not included a secondary amount, you cannot include a secondary amount on an associated refund.

Worldpay is experiencing issues communicating with the SEPA Direct Debit network. Please retry the transaction.

The e-mail address provided is not valid. Verify that it was entered correctly.

Some accountFundingTransactionType values are allowed only for specific MCCs. Please refr to accountFundingTransactionType for additional information.

Some methods of payment only allow specific accountFundingTransactionType values. Please refr to accountFundingTransactionType for additional information.

Mastercard requires the submission of all receiver fields for an account funding transaction.

The Recurring Request was invalid, which invalidated the transaction. The Response Code and Message in the Recurring Response contains additional information.

The recurring request was processed successfully.

The original payment transaction was declined, so the recurring payments have not been scheduled.

Appears in Declined Transaction report.

The plan specified in the recurring request was invalid.

The scheduled recurring payment has been processed successfully.

The referenced subscription Id does not exist.

Appears in Declined Transaction report.

The specified Add On code already exists.

Appears in Declined Transaction report.

Multiple createAddOn requests submitted with the same Add On Code.

The Add On code specified does not exist.

Appears in Declined Transaction report.

The Discount Code supplied in the updateDiscount or deleteDiscount transaction does not exist.

Appears in Declined Transaction report.

Multiple createDiscount requests submitted with the same Discount Code.

The supplied Start Date is invalid.

You are not registered for the use of the Recurring Engine.

The transaction did not include data needed for update operation.

The submitted billing date is either before the current date or otherwise invalid.

The specified Discount code already exists.

The specified Plan Code already exists.

An Account Updater response indicating the Account Number changed from the original number.

The account was closed. Contact the cardholder directly for updated information.

An Account Updater response indicating the Expiration date for the card has changed.

An Account Updater response indicating the issuing bank does not participate in the update program

An Account Updater response indicating you should contact the cardholder directly for updated information.

An Account Updater response indicating no match was found in the updated information.

An Account Updater response indicating there have been no changes to the account information.

The cardholder requested that no updates be included for their account.

The connection to the decryption service is currently unavailable. Please retry the transaction and/or contact your Relationship Manager.

Our attempt to decrypt the card information failed. Please retry the transaction.

The submitted data is invalid.

The submitted publicKeyHash element does not match any configured entries. Contact your Implementation Consultant.

Worldpay was unable to decrypt the submitted information.

Worldpay was unable to decrypt the submitted card number and/or CVV.

The transaction was declined because the resulting FraudSight Fraud Filter Score was below the acceptable threshold set in the merchant’s policy.

The issuing bank declined the transaction as suspected fraud.

There was an unspecified problem with the transaction. Please contact your Worldpay Relationship Manager.

Amazon was unavailable. Please retry the transaction.

Amazon declined the transaction.

The submitted Amazon token is invalid or you do not have access to this token. Please correct the token value before resubmitting the transaction.

Your organization is not enabled for the use of Amazon Pay. Please contact your Relationship Manager.

A PayPal response indicating the transaction failed due to an issue with primary funding source (e.g. expired Card, insufficient funds, etc.).

NOTE: The Response Message associated with Response Code 602 is inaccurate due to a remapping of PayPal Response Codes. Please read the description below for the recommended action when receiving Response Code 602.

The transaction could not be completed for one of the following reasons:

• The billing address associated with the financial Instrument could not be confirmed.
• The transaction exceeds the card limit.
• The transaction was denied by the card issuer.

You should establish error handling logic that directs the customer to contact PayPal to resolve the issue with their account.

A PayPal response indicating the Billing Agreement ID is invalid.

A PayPal response indicating the issuer is unavailable.

A PayPal response indicating the transaction failed due to an issue with the buyer account.

A PayPal response indicating the need to correct the authorization ID before resubmitting.

A PayPal response indicating your account is configured to decline transactions without a confirmed address. request another payment method or contact eCommerceSupport@vantiv.com to modify your account settings.

A PayPal response indicating account unauthorized payment risk.

A PayPal response indicating PayPal is unable to process the payment. Buyer should contact PayPal with questions.

A PayPal response indicating no further authorizations/captures can be processed against this order. A new order must be created.

A PayPal response indicating one of these potential refund related issues: duplicate partial refund must be less than or equal to original or remaining amount, past time limit, not allowed for transaction type, consumer account locked/inactive, or complaint exists - only a full refund of total/remaining amount allowed. Contact eCommerceSupport@vantiv.com for specific details.

A PayPal response indicating you do not have permissions to make this API call.

A PayPal response indicating you cannot capture against this authorization. You need to perform a brand new authorization for the transaction.

A PayPal response indicating missing parameters are required. Contact eCommerceSupport@vantiv.com for specific details.

A PayPal response indicating the need to check the validity of the authorization ID prior to reattempting the transaction.

A PayPal response indicating you should capture against a previous authorization.

A PayPal response indicating the transaction amount exceeds the merchant’s account limit. Contact eCommerceSupport@vantiv.com to modify your account settings.

A PayPal response indicating the buyer needs to add another funding sources to their account.

A PayPal response indicating there are issues with the buyer’s primary funding source.

Contact your Relationship Manager to adjust your PayPal merchant profile preferences.

There is a problem with your username and password. Contact eCommerceSupport@vantiv.com.

A PayPal response indicating you should contact the consumer for another payment method.

The terminal Id submitted with the POS transaction is invalid.

At this time, we support PINless Debit transaction only for recurring transactions.

PINless Debit does not support partial authorizations. You can resubmit the transaction without using the partial auth flag.

You are not enabled for PINless Debit processing. Please consult your Relationship Manager for additional information about this feature.

The customer has cancelled the transaction or recurring payment.

Unspecified decline. Please re-try the transaction.

The transaction exceeded the allowed activity on the account. You can retry the transaction later.

A PayPal Credit response indicating the customer is under 18 years of age based upon the date of birth.

A PayPal Credit response indicating the billing address is outside the United States.

A PayPal Credit response indicating that the billing address does not match the shipping address.

A PayPal Credit or PINless Debit response indicating the transaction is declined, because it is not in US dollars.

A PayPal Credit response indicating the account is on the negative file.

A PayPal Credit response indicating a blocked agreement account status.

A PayPal Credit response indicating that the account holder does not have sufficient credit available for the transaction amount.

A PayPal Credit response indicating that there are one or more problems with the submitted data.

A PayPal Credit response indicating one or more required data elements are missing.

Also, returned for a Direct Debit transaction that is missing a required data element. For example, failure to include the name element in an echeckSale or echeckCredit transaction would result in this code being returned.

A PayPal Credit response indicating that some data was formatted incorrectly.

A PayPal Credit response indicating the T&C version is invalid.

A PayPal Credit response indicating that the transaction is a duplicate.

A PayPal Credit response indicating that you should verify the billing address.

A PayPal Credit response indicating the customer account is inactive.

A PayPal Credit response indicating that the referenced authorization is invalid.

A PayPal Credit response indicating that an authorization already exists for the transaction.

Your current MCC does not allow lodging transactions. Please consult your Relationship Manager.

You submitted a negative value for the

<duration> element. Correct the error and resubmit the transaction.

Although the schema does not require the submission of the

<hotelFolioNumber> element, if you do include it, you must specify a value (i.e., null not allowed). Please either add a valid value or remove the element and resubmit the transaction.

There is a problem with the submitted check-in date (for example, 2018-02-32). Please correct the date and resubmit the transaction.

There is a problem with the submitted check-out date (for example, 2018-02-32). Please correct the date and resubmit the transaction.

There is a problem with the submitted check-in or check-out date (for example, 2018-02-32). Please correct the date(s) and resubmit the transaction.

The check-out date you submitted was before the check-in date. Correct the error and resubmit the transaction.

You submitted a negative value for the

<numAdult> element. Correct the error and resubmit the transaction.

You submitted a negative value for the

<roomRate> element. Correct the error and resubmit the transaction.

You submitted a negative value for the

<roomTax> element. Correct the error and resubmit the transaction.

For Visa the maximum duration is 99 (2-digits).

The card number was successfully registered and a token number was returned.

The card number was previously registered for tokenization.

Note: You also receive this response code when using a low value token in a transaction, because the system registers the PAN at the time it creates the LVT.

The token is valid.

The stored value for CVV2/CVC2/CID has been successfully updated.

The card number submitted for tokenization is invalid.

Your organization is not authorized to use tokens.

The token number submitted with this transaction was not found.

The submitted token is invalid.

Your organization is not authorized for Direct Debit tokenization.

The submitted checkoutId is invalid.

The submitted checkoutId was not found. The low value token is only good for 24 hours and may have expired.

An unknown error caused the use of checkoutId to fail.

The amount in the submitted Capture exceeds 115% of the authorized amount.

Appears in Declined Transaction report.

Tax Billing elements are allowed only for MCC 9311.

Missing taxType element

You must be either MCC 6012 or 6051 to designate a Visa transaction as Debt Repayment (debtRepayment element set to true).

The routing number submitted does not match the number submitted when the token was created. Verify the routing number and resubmit the transaction.

An eProtect response indicating that the Registration ID submitted is invalid.

An eProtect response indicating that the Registration ID has expired (Registration IDs expire 24 hours after being issued).

Your organization is not authorized to use eProtect.

You have submitted the maximum number of update token requests within a rolling 30 day period.

You exceeded the maximum number of tokens (16) allowed for this shopper.

There is an unspecified token registration error; contact your Relationship Manager

There is an unspecified token use error; contact your Relationship Manager.

The Direct Debit routing number submitted with this transaction has failed validation.

The customer name is required for SEPA transactions.

The customer name must be a minimum of two characters for SEPA transactions.

The Billing Country code is required for SEPA transactions.

The submitted International Bank Account number is invalid. Please correct the number and resubmit the traction.

The customer email address is required for SEPA transactions.

You must provide a Mandate reference for standard and BYOM recurring SEPA deposit transactions.

The Mandate reference is invalid. It must conform to the following format: 1 to 35 characters consisting of alphanumeric, colon, question mark, forward slash, plus, parenthesis, comas, period, space, and dash. The applicable regular expression is: ^[A-Za-z0-9:?/+(),. -]{1,35}$

You must provide a Mandate URL for SEPA Bring Your Own Mandate deposit transactions (both one-time and recurring).

The Mandate URL must start with https and be followed by 5 to 120 characters adhering to the following regular expression: ^https://.{5,120}$

You must provide a Mandate signature date for SEPA Bring Your Own Mandate deposit transactions (both one-time and recurring).

You must provide a Mandate signature date earlier than or the same as the current date with the following format: YYYY-MM-DD.

Worldpay returns this message when you submit multiple first Bring Your Own Mandate recurring transactions with the same mandate reference. The mandate references among the recurring transactions for a single merchant must be unique.

Worldpay returns this message when you submit a subsequent or final standard recurring transaction before a first standard recurring is processed and confirmed.

Worldpay returns this message when you submit a first or subsequent recurring transaction after we received a final recurring. The life cycle of a recurring mandate ends after the processing of a final recurring deposit transaction. This applies to both standard and Bring Your Own Mandate recurring transactions.

Worldpay returns this message when you submit a subsequent or final recurring with a different IBAN than the IBAN used in the first recurring transaction. This applies to both standard and Bring Your Own Mandate recurring transactions.

Note: If a customer wants to use a different IBAN for a recurring SEPA mandate, they must use a request for another mandate reference using this new IBAN.

Some of the alternative payment methods restrict the allowed consumer's billing country codes. For example, iDEAL only allows country code NL.

The submitted transaction uses the Canadian Interac network and requires the inclusion of an expiration date.

This transaction type is not support for the Canadian Interac network.

We do not support refunds for Interac transaction unless we also processed the capture.

The transaction you tried to void is in a Held state. You can not void a transaction in this state. You must first resolve the hold.

There are insufficient funds in the FBO Settlement Account to cover the Funding Instruction. Wait for additional funds to settle to the account and then resubmit the transaction.

Typically, this response occurs only for new FBO Settlement accounts that do not yet have any settled transactions and were not pre-funded (i.e., no balance yet recorded for the account). Wait for additional funds to settle to the account or pre-fund the account and then resubmit the transaction.

The card you submitted in the Fast Access Funding instruction cannot receive funds using this method.

A transaction can not contain both the ccdPaymentInformation and ctxPaymentInformation elements.

Please retry the transaction.

We do not support the following Funding Instructions in Canada:

• Physical Check Credit/Debit
• Reserve Credit/Debit
• Vendor Credit/Debit

Canadian merchants cannot use CTX or CCD elements. Remove the CTX or CCD records from the request.

You submitted a Canadian account number using more than 12 digits, which is not allowed. Check the account number and resubmit using 12 or less digits.

The submitted funding instruction transaction is not supported.

A Direct Debit response indicating the account is on the negative file.

A Direct Debit response indicating that this transaction was declined.

A Direct Debit response indicating that your Merchant Profile does not allow the requested operation. Contact your Relationship Manager for additional information.

A Direct Debit response indicating the customer’s checking account does not accept ACH transactions.

A Direct Debit response indicating the customer’s checking account does not accept ACH transactions or site drafts.

A Direct Debit response indicating that the dollar amount of this transaction exceeds the maximum amount specified in your Merchant Profile. Contact your Relationship Manager for additional information.

A Direct Debit response indicating that your organization is not authorized to perform eCheck verifications. Contact your Relationship Manager for additional information.

A Direct Debit response indicating that the first and last name of the customer is required for eCheck verifications.

A Direct Debit response indicating that the company name is required for verifications on corporate accounts.

A Direct Debit response indicating that the phone number of the customer is required for echeck verifications.

This code is returned if the merchant submits a Visa generated token.

This code is returned if the transaction involves a Visa Private Label card.

If processed, the rejected transaction would exceed the daily limit (amount) for Direct Debit captures.

Please resubmit the transaction tomorrow.

If processed, the rejected transaction would exceed the daily limit (amount) for Direct Debit credits.

Please resubmit the transaction tomorrow.

The designated account is not eligible for real-time payments.

The submitted transaction requires Customer Authentication.

Use a Void transaction.

This transaction originated on the Core platform, which does not support this transaction type.

The referenced (by the cnpTxnId) parent transaction does not exist. Verify the Id and resubmit with correct value.

This transaction type has not been enabled for Visa.

This transaction type has not been enabled for Mastercard.

This transaction type has not been enabled for American Express.

This transaction type has not been enabled for Discover.

This transaction type is not supported.

The transaction is held. You must contact your Relationship Manager for information about the reason.

Add the missing address information and resubmit the transaction.

The region code is invalid.

The country code is invalid.

The referenced credit card account is invalid.

Resubmit the transaction after correcting the MCC.