Common Payment Gateway Errors

Connecting to payment gateways helps to facilitate smooth and secure transactions. However, encountering errors during the payment process is not uncommon. Payments can fail for reasons like invalid authentication, insufficient funds, using a restricted or expired card, etc.

Let's look at some common payment errors across platforms and understand why they happen. Knowing these helps you figure out what went wrong, fix it, and prevent it from happening again.

Understanding Common Payment Gateway Errors

Stripe

You may encounter the following errors in processing the payments through the Stripe payment gateway:

Authentication_required: This error occurs when a card is declined because the transaction requires additional authentication.

Card_not_supported: When a card does not support a particular type of purchase, this error is encountered.

Currency_not_supported: This error arises when the card does not support the specified currency.

Duplicate_transaction: This error indicates that a transaction with an identical amount and credit card information was submitted very recently.

For more error codes, please refer to Stripe Decline Codes.

Moneris

You may encounter the following errors in processing the payments through the Moneris payment gateway:

54: This error occurs when the card is expired.

38/75: This error occurs when the maximum number of PIN retries is exceeded.

20/40/58: This error indicates an invalid transaction.

41/43/62: Errors related to lost or stolen cards are represented by these codes.

For more error codes, please refer to Moneris Response Codes.

Authorize.Net

You may encounter the following errors in processing the payments through the Authorize.Net payment gateway:

I00002: This error indicates that the subscription has already been canceled.

I00004: When no records are found, this error is returned.

I00008: This error suggests that the Payment Gateway Account service has already been declined

I00009: This error is returned if the API User already exists.

E00011: This error indicates that the access is denied. You do not have the appropriate permissions

For detailed error codes, please refer to Authorize.Net Documentation.

Global Payments

You may encounter the following errors in processing the payments through the Global Payments payment gateway:

101: This error occurs when the bank declines the payment due to insufficient funds or incorrect card data.

501: This error indicates that the transaction has already been processed.

505: This error occurs when you have entered an incorrect refund password.

508: This error occurs in case of an incorrect hash. Please check your code and the Developers’ documentation.

511: This error indicates that the system is unable to connect to the merchant's response URL.

For further information on response codes, visit Global Payments Developer Resources.