[Test Cases] Detailed payment error messages feature

Owned by Hellen Rodrigues Magalhaes
Last updated: Sept 24, 2024
3 min read

Whitelabel

 

Scenario

Scenario Title

Pre- condition

How to execute(step-by-step)

Scenario

Scenario Title

Pre- condition

How to execute(step-by-step)

1

[Mapped errors][Message Description] - Check if the custom description is displayed on the error modal

  1. Mapped errors on Lokalise file according to the table below.

  2. Back-end FF on LD enabled.

  1. Access the WL and go to the payment screen.

  2. Select credit card option.

  3. On CVV type the <CVV> and confirm.

  4. Check if the <Expected Message Description> is displayed on the error modal.

CVV

Mapped errors

Description (Sent from backend)

Expected Message Key

Expected Message Description

102

error.PAYMENT.2.001

Operation not allowed for the credit card type

error.PAYMENT.2.001

 

 

error.PAYMENT.2.002

General fraud error

error.PAYMENT.2.002

 

 

error.PAYMENT.2.003

General system fraud error

error.PAYMENT.2.003

 

 

error.PAYMENT.2.004

General validation error

error.PAYMENT.2.004

 

 

error.PAYMENT.2.100

General card error

error.PAYMENT.2.100

 

111

error.PAYMENT.2.100.001

CVC2 block incorrect

error.PAYMENT.2.100.001

 

 

error.PAYMENT.2.101

General payment processing error

error.PAYMENT.2.101

 

115

error.PAYMENT.2.101.001

Card issuer could not validate card owner

error.PAYMENT.2.101.001

 

 

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

 

 

error.PAYMENT.2.102

General payment restriction error

error.PAYMENT.2.102

 

 

error.PAYMENT.2.102.001

Operation not allowed for the credit card type

error.PAYMENT.2.102.001

 

 

error.PAYMENT.2.102.002

Country (customer IP address) not allowed

error.PAYMENT.2.102.002

 

 

error.PAYMENT.2.102.003

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

error.PAYMENT.2.102.003

 

 

error.PAYMENT.4.000

General PSP error

error.PAYMENT.4.000

 

 

error.PAYMENT.4.002

General configuration error

error.PAYMENT.4.002

 

 

error.PAYMENT.4.003

General connection error

error.PAYMENT.4.003

 

 

error.PAYMENT.4.004

General database error

error.PAYMENT.4.004

 

 

error.PAYMENT.4.005

General external connection error

error.PAYMENT.4.005

 

 

error.PAYMENT.4.006

General external error

error.PAYMENT.4.006

 

 

error.PAYMENT.4.007

General service error

error.PAYMENT.4.007

 

 

error.PAYMENT.4.008

General payment process error

error.PAYMENT.4.008

 

 

Scenario

Scenario Title

Pre- condition

How to execute(step-by-step)

Scenario

Scenario Title

Pre- condition

How to execute(step-by-step)

2

[Non-Mapped errors][Message Description] - Check if the message description is displayed on the error modal

  1. Mapped and non-mapped errors on Lokalise file according to the table below.

  2. Back-end FF on LD enabled.

  1. Access the WL and go to the payment screen.

  2. Select credit card option.

  3. On CVV type the <CVV> and confirm.

  4. Check if the <Expected Message Description> is displayed on the error modal.

CVV

Non-mapped errors

Mapped errors

Description (Sent from backend)

Expected Message Key

Expected Message Description

102

error.PAYMENT.2.001

error.PAYMENT.default

error.PAYMENT.2

Operation not allowed for the credit card type

error.PAYMENT.2

 

111

error.PAYMENT.2.100.001

error.PAYMENT.default

error.PAYMENT.2

error.PAYMENT.2.100

CVC2 block incorrect

error.PAYMENT.2.100

 

111

error.PAYMENT.2.100.001

error.PAYMENT.default

error.PAYMENT.2

CVC2 block incorrect

error.PAYMENT.2

 

115

error.PAYMENT.2.101.001

error.PAYMENT.default

error.PAYMENT.2

error.PAYMENT.2.100

error.PAYMENT.2.101

Card issuer could not validate card owner

error.PAYMENT.2.101

 

 

error.PAYMENT.2.101.002

error.PAYMENT.default

error.PAYMENT.2.101.003

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

 

 

error.PAYMENT.4.002

error.PAYMENT.4

General configuration error

error.PAYMENT.4

 

 

error.PAYMENT.4.003

error.PAYMENT.default

General connection error

error.PAYMENT.4

 

 

 

Scenario

Scenario Title

Pre- condition

How to execute(step-by-step)

Scenario

Scenario Title

Pre- condition

How to execute(step-by-step)

3

[Mapped errors][Message Title] - Check if the message title is displayed on the error modal

  1. Mapped errors on Lokalise file according to the table below.

  2. Back-end FF on LD enabled.

  1. Access the WL and go to the payment screen.

  2. Select credit card option.

  3. On CVV type the <CVV> and confirm.

  4. Check if the <Expected Message Description> is displayed on the error modal.

CVV

Mapped errors

Description (Sent from backend)

Expected Message Key

Expected Message Description

102

error.PAYMENT.2.001.title

Operation not allowed for the credit card type

error.PAYMENT.2.001.title

 

 

error.PAYMENT.2.002.title

General fraud error

error.PAYMENT.2.002.title

 

 

error.PAYMENT.2.100.title

General card error

error.PAYMENT.2.100.title

 

111

error.PAYMENT.2.100.001.title

CVC2 block incorrect

error.PAYMENT.2.100.001.title

 

115

error.PAYMENT.2.101.001.title

Card issuer could not validate card owner

error.PAYMENT.2.101.001.title

 

 

error.PAYMENT.4.000.title

General PSP error

error.PAYMENT.4.000.title

 

 

error.PAYMENT.4.002.title

General configuration error

error.PAYMENT.4.002.title

 

 

 

Scenario

Scenario Title

Pre- condition

How to execute(step-by-step)

Scenario

Scenario Title

Pre- condition

How to execute(step-by-step)

4

[Non-Mapped errors][Message Title] - Check if the message title is displayed on the error modal

  1. Mapped and non-mapped errors on Lokalise file according to the table below.

  2. Back-end FF on LD enabled.

  1. Access the WL and go to the payment screen.

  2. Select credit card option.

  3. On CVV type the <CVV> and confirm.

  4. Check if the <Expected Message Description> is displayed on the error modal.

CVV

Non-mapped errors

Mapped errors

Description (Sent from backend)

Expected Message Key

Expected Message Description

102

error.PAYMENT.2.001.title

error.PAYMENT.title

error.PAYMENT.2.title

Operation not allowed for the credit card type

error.PAYMENT.2.title

 

111

error.PAYMENT.2.100.001.title

error.PAYMENT.title

error.PAYMENT.2.title

error.PAYMENT.2.100.title

CVC2 block incorrect

error.PAYMENT.2.100.title

 

111

error.PAYMENT.2.100.001.title

error.PAYMENT.title

error.PAYMENT.2.title

CVC2 block incorrect

error.PAYMENT.2.title

 

115

error.PAYMENT.2.101.001.title

error.PAYMENT.title

error.PAYMENT.2.title

error.PAYMENT.2.100.title

error.PAYMENT.2.101.title

Card issuer could not validate card owner

error.PAYMENT.2.101.title

 

 

error.PAYMENT.2.101.002.title

error.PAYMENT.title

error.PAYMENT.2.101.003.title

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

 

 

error.PAYMENT.4.002.title

error.PAYMENT.4.title

General configuration error

error.PAYMENT.4.title

 

 

error.PAYMENT.4.003.title

error.PAYMENT.title

General connection error

error.PAYMENT.title

 

 

Analytics

 

Scenario

Scenario Title

Pre- condition

How to execute(step-by-step)

Scenario

Scenario Title

Pre- condition

How to execute(step-by-step)

5

Analytics - Check if the new event and its attributes are being sent properly to mParticle/Amplitude according to the table below.

  1. Mapped and non-mapped errors on Lokalise file according to the table below.

  2. Back-end FF on LD enabled.

  3. mParticle/Amplitude access

  1. Access the WL and go to the payment screen.

  2. Select credit card option.

  3. On CVV type the <CVV> and confirm.

  4. Check if the new event and its attributes are being sent properly to mParticle/Amplitude according to the table below.

 

 

Event

Attributes

CVV

Name

Error Code

Message

Path

Response Title

Response Description

102

Error

error.PAYMENT.2.001

Operation not allowed for the credit card type

/cart/payment

 

 

 

Error

error.PAYMENT.2.002

General fraud error

/cart/payment

 

 

 

Error

error.PAYMENT.2.100

General card error

/cart/payment

 

 

111

Error

error.PAYMENT.2.100.001

CVC2 block incorrect

/cart/payment

 

 

 

Error

error.PAYMENT.2.101

General payment processing error

/cart/payment

 

 

115

Error

error.PAYMENT.2.101.001

Card issuer could not validate card owner

/cart/payment

 

 

 

Error

error.PAYMENT.2.102

General payment restriction error

/cart/payment

 

 

 

Error

error.PAYMENT.2.102.001

Operation not allowed for the credit card type

/cart/payment

 

 

 

Error

error.PAYMENT.4.000

General PSP error

/cart/payment

 

 

 

Error

error.PAYMENT.4.002

General configuration error

/cart/payment

 

 

 

Error

error.PAYMENT.4.003

General connection error

/cart/payment

 

 

 

Error

error.PAYMENT.default

-

/cart/payment

 

 

 

Error

error.PAYMENT.title

-

/cart/payment

 

 

 

Error

error.PAYMENT.2.title

-

/cart/payment