Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

User Role

Description

User

User will be placing successful orders on Whitelabel

Developer user

User responsible for enabling the FF on the Launch Darkly (LD) and setting which cards are accepted for each brand and country

Key

CVV

Paycomet

Description

Modal Title

Modal Message

Modal CTA

Screen

Severity: 2 - NORMAL - Normal User Errors.

error.PAYMENT.2.001

130

Original operation not found. Could not refund

Operation not allowed for the credit card type

Card type invalid

Your card is not enabled to allow this payment at the moment. Please, contact your bank or try another payment method.

"Pay another way”

image-20240920-201130.pngImage Removed

error.PAYMENT.2.002

Represents errors generated when a transaction is suspected of being fraudulent.

Something went wrong"

We had a problem processing this payment. Please try another payment method.

"Pay another way”

image-20240920-201716.pngImage Removed

error.PAYMENT.2.003

Represents errors generated by internal fraud detection mechanisms within the system.

Something went wrong"

We had a problem processing this payment with this payment method. Please contact your bank support or try another payment method"

"Pay another way”

image-20240920-201956.pngImage Removed

error.PAYMENT.2.004

Represents errors that occur during the validation of transaction data, such as missing mandatory fields, incorrectly formatted data, and other validation failures.

Validation error

The payment transaction was declined. Please check the card name, card number, CVV, expire date and try again.

"Review Informations”

image-20240924-033807.pngImage Removed

error.PAYMENT.2.100

Represents an error related to credit/debit card transactions.

Card type invalid"

Your card is not enabled to allow this payment at the moment. Please, contact your bank or try another payment method."

"Go back”

image-20240920-202324.pngImage Removed

error.PAYMENT.2.100.001

111

CVC2 block incorrect

The payment transaction was rejected because the user informed an invalid card CVV.

Validation error"

The payment transaction was declined. Please check the card name, card number, CVV, expire date and try again.

"Review Informations”

image-20240924-033807.pngImage Removed

error.PAYMENT.2.101

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.

Something went wrong"

We were unable to process this payment due to internal errors. Please try again later.

"Go back”

image-20240920-202742.pngImage Removed

error.PAYMENT.2.101.001

115

Card issuer could not validate card owner

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 authorize payment and try again.”

"Go back”

image-20240924-035210.pngImage Removed

error.PAYMENT.2.101.002

1367

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.

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.

"Go back”

image-20240920-203032.pngImage Removed

error.PAYMENT.2.102

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."

"Go back”

image-20240920-203935.pngImage Removed

error.PAYMENT.2.102.001

102

Operation not allowed for the credit card type

Operation is not allowed for this card type.

Card type invalid

“Your card is not enabled to allow this payment at the moment. Please, contact your bank or try another payment method.”

"Pay another way”

image-20240920-204034.pngImage Removed

error.PAYMENT.2.102.002

1192

Country (customer IP address) not allowed

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"

“Sorry, we had a problem related to your location and this store. Please choose a nearest store and try again.”

"Choose another Store”

image-20240924-035443.pngImage Removed

error.PAYMENT.2.102.003

1202

Number of failed attempts (last 30 minutes) from the same ip address exceeded

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.”

"Go back”

image-20240911-222800.pngImage Removed

Severity: 4 - ABNORMAL

error.PAYMENT.4.000

General, unspecified payment error.

Failed Payment

“Something went wrong with this payment. Please try again later”

"Go back”

image-20240911-234208.pngImage Removed

error.PAYMENT.4.001

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”

"Go back”

image-20240911-234210.pngImage Removed

error.PAYMENT.4.002

Represents errors arising from system configuration issues.

Impact: All the payment transactions are failing.

Solution: Review the configuration for the specific service and PSP.

Failed Payment

“Something went wrong with this payment. Please try again later

"Go back”

image-20240911-234208.pngImage Removed

error.PAYMENT.4.003

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

Failed Payment

“Something went wrong with this payment. Please try again later”

"Go back”

image-20240911-234208.pngImage Removed

error.PAYMENT.4.004

Represents errors associated with database operations within the system.

Failed Payment

“Something went wrong with this payment. Please try again later”

"Go back”

image-20240911-234214.pngImage Removed

error.PAYMENT.4.005

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.

Failed Payment

“Something went wrong with this payment. Please try again later”

"Go back”

image-20240911-234208.pngImage Removed

error.PAYMENT.4.006

Represents errors that occur due to external factors not directly related to the internal infrastructure of the payment system.

Failed Payment

“Something went wrong with this payment. Please try again later”

"Go back”

image-20240911-234208.pngImage Removed

error.PAYMENT.4.007

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”

"Go back”

image-20240911-234208.pngImage Removed

error.PAYMENT.4.008

Represents errors that occur during the internal processing of payment transactions.

Ex.: Payment not found for the given rbiOrderId

Failed Payment

“Something went wrong with this payment. Please try again later”

"Go back”

image-20240911-234208.pngImage Removed

...

Analytics user

User responsible for checking the events on mParticle/Amplitude.

Whitelabel

In order to perform these scenarios, it will be necessary to manipulate the content of the Lokalise existing on the local environment according to the pre-conditions for each test case:

We will be able to use Paycomet’s instruction to simulate some of the mapped errors. In this case, we need to use the CVV field and enter the code informed by Paycomet. The codes are availabe on this document.

If there is no code available to test, we will need to use a mock in order to simulate the errors.

Analytics