...
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 your bank and try again.” |
|
| Represents errors generated when a transaction is suspected of being fraudulent. | “Suspicious card" | “We identified a possible fraud related to the use of this card. Please, contact your bank.” |
|
| Represents errors generated by internal fraud detection mechanisms within the system. | “System fraud" | “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 try again.” |
|
| Represents an error related to credit/debit card transactions. | “Problem with the card" | “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." | “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 error" | “We encountered an issue communicating between our servers and your request. Please try again.” |
|
| The payment transaction was rejected because card issuer could not validate card owner's identity. | “Identity error" | “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. | |||
| Represents errors generated when a transaction is rejected as restricted by PSP or issuer. | |||
| Operation is not allowed for this card type. | “Card invalid” | “This card is not valid for this type of payment. Please contact your bank or choose 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 failed” | “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 server. 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 error” | “We are experiencing connection problems with our server. 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 issues. 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.” |
|
...
| Code Block | ||
|---|---|---|
| ||
const errorCodeRBI = parseGraphQLRBIError(error);
recordRBIErrorEvents({ rbiErrors: errorCodeRBI }); |
Creating the RBI error on frontend
| Code Block | ||
|---|---|---|
| ||
const errorCodeRBI = new RbiError2('Paypal modal error', 'PAYMENT', '2.000'); // with Modal openErrorDialog({ rbiError: errorCodeRBI }); // without modal recordRBIErrorEvents({ rbiErrors: errorCodeRBI }); |
POC
Message Description
...
Key
...
Description (Sent from backend)
...
Message Description (Modal description - User-friendly Messages)
...
error.PAYMENT.title (Default title)
...
-
...
error.PAYMENT.default (Default description)
...
-
...
error.PAYMENT.2.001
...
Operation not allowed for the credit card type
...
error.PAYMENT.2.002
...
General fraud error
...
error.PAYMENT.2.003
...
General system fraud error
...
error.PAYMENT.2.004
...
General validation error
...
error.PAYMENT.2.100
...
General card error
...
error.PAYMENT.2.100.001
...
CVC2 block incorrect
...
error.PAYMENT.2.101
...
General payment processing error
...
error.PAYMENT.2.101.001
...
Card issuer could not validate card owner
...
error.PAYMENT.2.101.002
...
When the same card has several payments in "flight" at the time that one is finalized, the rest are denied with this code. This restriction is for security.
...
error.PAYMENT.2.102
...
General payment restriction error
...
error.PAYMENT.2.102.001
...
Operation not allowed for the credit card type
...
error.PAYMENT.2.102.002
...
Country (customer IP address) not allowed
...
error.PAYMENT.2.102.003
...
Number of failed attempts (last 30 minutes) from the same ip address exceeded
...
error.PAYMENT.4.000
...
General PSP error
...
error.PAYMENT.4.002
...
General configuration error
...
error.PAYMENT.4.003
...
General connection error
...
error.PAYMENT.4.004
...
General database error
...
error.PAYMENT.4.005
...
General external connection error
...
error.PAYMENT.4.006
...
General external error
...
error.PAYMENT.4.007
...
General service error
...
error.PAYMENT.4.008
...
More details on Github: Generic Errors, Paycomet Error Map, and PSP Error
...