...
Key | Description | Modal Title | Modal Message | Screen | ||
|---|---|---|---|---|---|---|
Severity: 2 - NORMAL - Normal User Errors. | ||||||
| Operation not allowed for the credit card type | “Card type invalid” | “Your card is not enabled to allow this payment at the moment. Please, check with contact your bank and or try againanother payment method.” |
| ||
| Represents errors generated when a transaction is suspected of being fraudulent. | “Suspicious cardSomething went wrong" | “We identified a possible fraud related to the use of this card. Please, contact your bankhad a problem processing this payment. Please try another payment method.” |
| ||
| Represents errors generated by internal fraud detection mechanisms within the system. | “System fraudSomething went wrong" | “Sorry, we identified potential fraud related to the system. Please try again later." |
| ||
| Represents errors that occur during the validation of transaction data, such as missing mandatory fields, incorrectly formatted data, and other validation failures. | “Validation error” | “Sorry, but some of the card details you entered are incorrect. Please The payment transaction was declined. Please check the Card information, number, CVV, expire date and try again.” |
| ||
| Represents an error related to credit/debit card transactions. | “Problem with the cardCard type invalid" | “We had a problem with your credit/debit card. Please try again later." |
| ||
| The payment transaction was rejected because the user informed an invalid card CVV. | “The CVV is incorrect.Validation error" | “The “The payment transaction was declined. Please check the Card information, number, CVV, expire date and try again.” |
| ||
| Represents errors that arise during the payment processing phase, such as failures in communicating with the payment gateway, billing errors, and other issues that may occur while processing a payment. | “Communication errorSomething went wrong" | “We encountered an issue communicating between our servers and your requestwere unable to process this payment due to internal errors. Please try again later.” |
| ||
| The payment transaction was rejected because card issuer could not validate card owner's identity. | “Identity error" | “Sorry“Sorry, we were unable to verify the cardholder's identity. Please use another payment method.” |
| ||
| Represents an error when In-Flight offline payments are rejected. An example of occurrence is when the same card has several payments in "flight" at the time and one is finalized, the rest might be denied. | “Something went wrong” | “Sorry, we are unable to process this payment. Please use another payment method.” |
| ||
| Represents errors generated when a transaction is rejected as restricted by PSP or issuer. | “Something went wrong” | “Sorry, we are unable to process this payment. Please use another payment method." |
| ||
| Operation is not allowed for this card type. | “Card type invalid” | “This “Your card is not valid for this type of paymentenabled to allow this payment at the moment. Please, contact your bank or choose try another payment method.” |
| ||
| Represents an error when the user's IP address is not from an allowed country. Ex.: Iberia payments only allowed from Spain and Portugal. | “Location Invalid" | “You cannot place orders from this country at this store. Please choose another store and try again.” |
| ||
| Represents an error when the number of failed attempts from the same user has been exceeded. | “Order limit exceeded" | “You have exceeded the number of attempts to place an order. Please try again later.” |
| ||
Severity: 4 - ABNORMAL | ||||||
| General, unspecified payment error. | “Failed Payment” | “Something went wrong with this payment. Please try again later” |
| ||
| Represents errors related to security and authentication within the payment system. Impact: All the payment transactions are failing. Solution: Investigate security related settings, like secrets. | “Failed Payment” | “Something went wrong with this payment. Please try again later” |
| ||
| Represents errors arising from system configuration issues. Impact: All the payment transactions are failing. Solution: Review the configuration for the specific service and PSP. | “The system failedFailed Payment” | “We are experiencing a problem with our systems, please try again later” |
|
| |
| Represents errors related to internal connection problems, such as failures in communication between microservices, internal network issues, or connectivity problems with the Payment Service Provider (PSP). Solution: Investigate communication-related infrastructure issues | “Connection error"“We are experiencing connection problems with our serverFailed Payment” | “Something went wrong with this payment. Please try again later” |
| ||
| Represents errors associated with database operations within the system. | “Failed Payment” | “Something went wrong with this payment. Please try again later” |
| ||
| Represents errors caused by failures in third-party connections with external services necessary for the transaction, such as banks, payment gateways, identity verification services, etc. | “Connection errorFailed Payment” | “We are experiencing connection problems with our server“Something went wrong with this payment. Please try again later” |
| ||
| Represents errors that occur due to external factors not directly related to the internal infrastructure of the payment system. | “External error”“We are experiencing external connection issuesFailed Payment” | “Something went wrong with this payment. Please try again later” |
| ||
| Represents errors that occur at the service layer, such as internal service failures, configuration issues, or other problems that prevent the service from functioning as expected. | “Failed Payment” | “Something went wrong with this payment. Please try again later” |
| ||
| Represents errors that occur during the internal processing of payment transactions. Ex.: Payment not found for the given rbiOrderId | “Processing error” | “We encountered an error while processing your request, please try again later.” |
| “Something went wrong with this payment. Please try again later” |
|
Old Methods
Until that migration starts, we will deprecate the methods mapErrorsWithCodes and parseGraphQLErrorCodes to prevent the creation of new error flows using the "old" approach, encouraging the adoption of the new model.
...