** Any error message containing the words DECLINED, REJECTED, DENIED, BLOCKED, or INSUFFICIENT FUNDS indicates a problem with the customer's card. In these cases, the customer will need to contact their card-issuing bank to resolve the issue. **
Authorize.net
Error: This Transaction has been declined
What it means: The card was declined by the card issuing bank.
How to Fix: Customer must contact their bank for more information or to resolve the issue.
Error: User authentication failed due to invalid authentication values
What it means: Authorize.net credentials are outdated or incorrect.
How to fix: Vendor must submit new Authorize.net credentials in the following form: https://overview.markettime.com/supported-third-party-gateways
Error: A duplicate transaction has been submitted
What it means: A charge was re-attempted after it was initially declined.
How to fix: Customer must contact their bank for more information on the initial decline or provide a new form of payment.
Error: The transaction has been declined because of an AVS mismatch. The address provided does not match the billing address of cardholder.
What it means: The billing address entered for the card does not match the address on file with the card issuing bank.
How to fix: The billing details will need to be verified with the customer and re-entered exactly as they have it recorded with their bank.
Error: There has been an error processing this transaction.
What it means: Authorize.net credentials are most likely outdated or invalid.
How to fix: Vendor must submit new Authorize.net credentials in the following form: https://overview.markettime.com/supported-third-party-gateways
Braintree
Error: CVV is required
What it means: There's a specific fraud setting that needs to be adjusted within their Braintree account.
How to fix: Vendor needs to follow the steps below to adjust a setting within their Braintree account:
- Login to Braintree
- Click the settings cog in the top right and select Fraud Management
- Click Options for the CVV pane
- Uncheck the "CVV not provided (I)" option and click Save
Error: BillingLocationCountryCode cannot be null or whitespace.
What it means: The billing country field is missing or invalid.
How to fix: Verify that the billing address included a valid country.
Error: Gateway Rejected: avs
What it means: The billing address entered for the card does not match the address on file with the card issuing bank.
How to fix: The billing details will need to be verified with the customer and re-entered exactly as they have it recorded with their bank.
CardConnect
Error: {"Message":"No error message was given - txnPayName =(MERCHANT NAME)- Please check your configuration"}
What it means: CardConnect credentials are outdated or incorrect.
How to fix: Vendor must submit new CardConnect credentials in the following form: https://overview.markettime.com/supported-third-party-gateways
CenPOS Native
Error: User must change password
What it means: The CenPOS Native Password has expired.
How to fix: Vendor must submit a new CenPOS Native Password in the following form: https://overview.markettime.com/supported-third-party-gateways
ChargeLogic
Error: There is a problem with your credentials. Please contact customer service.
What it means: ChargeLogic credentials are outdated or incorrect
How to fix: Vendor must verify credentials with ChargeLogic and submit their updated credentials in the following form: https://overview.markettime.com/supported-third-party-gateways
Chase Paymentech
Error: Precondition Failed: Security information is missing
What it means: Credentials are incorrect, or Hosted PCI is not setup as an approved 3rd party vendor for the Chase Paymentech account.
How to fix: Vendor must contact Chase Paymentech to verify their credentials and ensure Hosted PCI is setup as a 3rd party vendor.
Error: Merchant-Bin combination is not allowed to perform profile transactions
What it means: Account setup issue with Chase Paymentech
How to fix: Vendor must verify Merchant ID and BIN ID with Chase, and confirm account is setup to perform transactions.
Error: Merchant-Bin [xxxxxxxxxxxx]:[xxxxxx] is not active.
What it means: The Merchant ID or BIN ID provided for the integration is inactive.
How to fix: Vendor must contact Chase Paymentech to verify that the Merchant ID and BIN ID they provided are active.
Error: {"Message":" Request does not adhere to the DTD. Please correct and send again."}
What it means: For this error, Chase Paymentech states that payment processing may fail with international orders when the customer's issuing bank is using a different currency. May also be related to and incorrect Terminal ID or BIN ID.
How to fix: Vendor must verify the Currency, Terminal ID and BIN ID with Chase and re-submit their credentials in the following form: https://overview.markettime.com/supported-third-party-gateways
CyberSource
Error: REJECT
What it means: Generic Failure - Could be a card decline or invalid credentials.
How to fix: Contact MarketTime to test integration. If test is successful, vendor must contact CyberSource to get further clarification for the REJECT.
EBizCharge
Error: Could not tokenize
What it means: This error is related to an ongoing issue with the eBiz payment gateway integration. Our team has been working with eBiz and Hosted PCI to resolve this issue, but we have not yet reached a resolution.
How to fix: If this error occurs, a new payment term will need to be selected for the order. Alternatively, the vendor can explore switching to a different payment gateway solutions where this error will not occur.
Elavon
Error: This terminal or user ID is not permitted to process this transaction type.
What it means: This error could mean that the Elavon gateway credentials provided are incorrect, or that their Elavon account is not setup as an API user.
How to fix: Vendor must contact Elavon to confirm that their account is properly setup as an API user. The vendor may also need to re-submit new credentials for the API user account in the following form: https://overview.markettime.com/supported-third-party-gateways
FluidPay
Error: Customer Already Exists
What it means: The customer profile for the card already exists in the FluidPay system. This can occur if a card is initially tokenized with FluidPay, which creates and passes a Customer ID to the gateway, but the "Save Card To Retailer" checkbox is not selected in MarketTime. Now, when attempting to tokenize the same card on a new order, FluidPay is returning the "Customer Already Exists" error because the customer profile already exists in their system.
How to fix: The rep can use the "Card on File" term for the order, or the vendor can contact FluidPay to resolve on their end.
** To prevent this, always check Save Card to Retailer when first tokenizing a card in MarketTime **
HighRadius
Error: CVV2/CVC2 Failure
What it means: Invalid CVV.
How to fix: The CVV and card details will need to be verified with the customer and re-entered on the order.
JetPay / NCR
Error: 912 - Token Not Found
What it means: Invalid card format.
How to fix: The card details will need to be verified with the customer and re-entered on the order.
Merchant eSolutions
Error: Internal Error
What it means: Merchant eSolutions gateway credentials are outdated or inactive.
How to fix: Vendor must provide updated Merchant eSolutions credentials in the following form: https://overview.markettime.com/supported-third-party-gateways
Error: Invalid ID or Key
What it means: Merchant eSolutions credentials may be inactive, or their Merchant E account is not configured with the Payment Gateway API piece of Merchant eSolutions.
How to fix: Vendor must contact Merchant eSolutions to verify credentials and enable API access.
Error: Closed Account
What it means: Payment gateway account is closed.
How to fix: Vendor must contact Merchant eSolutions and submit updated credentials in the following form: https://overview.markettime.com/supported-third-party-gateways
Error: 03 - Do not retry
What it means: Incorrect card or billing information
How to fix: Verify all card and billing details with the customer and re-enter on the order.
Moneris
Error: CARD DECLINED * DO NOT RETRY
What it means: Card declined by issuing bank.
How to fix: Customer must contact their bank or provide a new form of payment.
Error: Payment Gateway not configured for the currency please contact HPCI to set up the correct Gateway detailsnull
What it means: Currency setup with gateway integration does not match the currency configured with their Moneris account.
How to fix: Currency Code (USD, CAD, etc.) will need to be verified with the vendor and updated in MarketTime.
Error: Transaction not allowed: Resolvertmp
What it means: Vault is not enabled in Moneris.
How to fix: Vendor must contact Moneris to have Vault enabled for their account.
Network Merchants (NMI)
Error: Authentication Failed
What it means: NMI credentials are invalid.
How to fix: Vendor must submit updated NMI credentials in the following form: https://overview.markettime.com/supported-third-party-gateways
Error: Your account is not setup to use the Customer Vault
What it means: The specific feature for securely storing customer payment information (the customer vault) is not enabled on their NMI account.
How to fix: Vendor must contact NMI to have the Customer Vault feature enabled.
Paya Connect
Error: Unable to verify vault service
What it means: Vault service has not been enabled for their Virtual Terminal Account.
How to fix: Vendor must contact Paya Support to have Vault service enabled.
Payfabric
Error: Unable to process the transaction. Gateway account does not exist.
What it means: Payfabric gateway credentials are incorrect
How to fix: Vendor must submit updated Payfabric credentials in the following form: https://overview.markettime.com/supported-third-party-gateways
Error: Unable to create a new card. The account number already exists
What it means: A card with the same account number already exists in the vendors Payfabric account.
How to fix: Customer can provide a new credit card for the order, or the vendor may contact Payfabric for resolution.
PayPal Payflow Pro
Error: Invalid Vendor Account
What it means: PayPal Payflow Pro gateway credentials are incorrect.
How to fix: Vendor must provide updated PayPal Payflow Pro credentials in the following form: https://overview.markettime.com/supported-third-party-gateways
Payroc
Error:
What it means: Card declined by card issuing bank.
How to fix: Customer must contact their bank or provide a new form of payment
PayTrace
Error: {"Message":"No error message was given - txnPayName = (MERCHANT NAME) - Please check your configuration"}
What it means: PayTrace gateway credentials are incorrect.
How to fix: Vendor must submit updated PayTrace credentials in the following form: https://overview.markettime.com/supported-third-party-gateways
Quickbooks
Error: {"Message":"Failed while trying to perform Sale transaction. - INPUT:null - reasonCode = AuthenticationFailed - [\"04f9a684e9fd46c2a97d8cb6100cff66\"]."}
What it means: Quickbooks Refresh token is invalid.
How to fix: Vendor must submit updated Quickbooks credentials in the following form: https://overview.markettime.com/supported-third-party-gateways
Sage Pay
Error: Unable to verify vault service
What it means: Vault service has not been enabled for their Virtual Terminal Account.
How to fix: Vendor must contact Paya Support to have Vault service enabled.
Stripe
Error: Sending credit card numbers directly to the Stripe API is generally unsafe. To continue processing use Stripe.js, the Stripe mobile bindings, or Stripe Elements. For more information, see https://dashboard.stripe.com/account/integration/settings. If you are qualified to handle card data directly, see https://support.stripe.com/questions/enabling-access-to-raw-card-data-apis
What it means: "Handle Card Information Directly" setting has not been enabled in Stripe.
How to fix: Vendor must contact Stripe to enable the "Handle Card Information Directly" setting. If DSS documentation is required, MarketTime can provide it to the vendor.
Error: {"Message":"MarketTimeSaleTransaction method failed while trying to perform Sale transaction - requires_action INNER EXCEPTION: no innerException.message[\"f4a32ad618554e3c87f5013950c92483\",\"ecd5f0051e3f4bea80518d3246f584bc\"]"}
What it means: Stripe Secret Key is no longer valid.
How to fix: Vendor must submit an updated Stripe Secret Key in the following form: https://overview.markettime.com/supported-third-party-gateways
Error: Failed to process Credit Card for the following reason:
{"Message":" Invalid response object from API: {\n \"error\": {\n \"code\": \"card_declined\",\n \"decline_code\": \"generic_decline\",\n \"docurl\": \"https://stripe.com/docs/error-codes/card-declined\",\n \"message\": \"Your card was declined.\",\n \"param\": \"\",\n \"requestlogurl\": \"https://dashboard.stripe.com/logs/reqBV8hr1bpoQKoXy?t=1682007649\",\n \"type\": \"carderror\"\n }\n}\n. (HTTP response code was 402). Additional details: none.; request-id: req_BV8hr1bpoQKoXy"}
What it means: Card was declined by card issuing bank. Example error above lists the decline code as generic_decline. However, this part may vary depending on why the card is being declined.
Error:"Your card does not support this type of purchase"
What it means: "Your card does not support this type of purchase" error involves checking if the card is a debit card, has cross-border restrictions or is an HSA or FSA card, then taking the corresponding action if it is.
Click here for for more information regarding this error.
Other decline codes may include:
Lost_card
Expired_card
Suspected_fraud
Insufficient_funds
Transaction_not_allowed
Please refer to the guide below for more information on the Stripe decline codes:
https://docs.stripe.com/declines/codes
How to fix: Customer must contact their bank or provide a new form of payment.
Trust Commerce
Error: Decline
What it means: This is a true "decline"; it almost always is a result of insufficient funds on the card.
How to fix: Customer must add funds to cover the charge or provide a new form of payment
Error: AVS
What it means: Address Verification System (AVS) failed; the address entered does not match the billing address on file with the card issuing bank.
How to fix: Verify billing details with the customer and re-enter exactly as recorded with their bank.
Error: {“Message”:” custid,password”}
What it means: Trust Commerce gateway credentials are incorrect.
How to fix: Vendor must submit updated Trust Commerce credentials in the following form: https://overview.markettime.com/supported-third-party-gateways
VersaPay
Error: {"Message":"{\\"error\\":\\"Please log in or create an account to continue.\\"}"}
What it means: VersaPay gateway credentials are incorrect.
How to fix: Vendor must submit updated credentials in the following form: https://overview.markettime.com/supported-third-party-gateways