Versions Compared

Old Version 1

changes.mady.by.user de Sousa Santos, Rodrigo

Saved on

compared with

New Version Current

changes.mady.by.user Raphael Ferreira Gomes

Saved on

Key

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

Overview

Currently, issues on our platform are presented through error modal events in Amplitude. While this approach is functional, it has significant limitations, focusing only on the appearance of the modal and failing to provide a clear view of the actual source of the problems. Error modals can represent both front-end and back-end failures, arising from various factors such as configuration errors, improper implementation, partner integrations, and user-induced errors. Currently, there is no clear path to understand fluctuations in error modals, which hinders the team's ability to identify friction points that users experience on our platform.

We will implement a protocol to send errors with an initial layer of granularity to mParticle, allowing for more effective use in Amplitude, providing immediate insights into the causes of variations and enabling deeper analysis.

To address these issues, a list of error codes has been proposed for documentation:

Paycomet

Lokalise Key

Description

Screen

102

error.PAYMENT.2.001

Operation not allowed for the credit card type

 

image-20241001-045844.pngImage Added

 

130

error.PAYMENT.2.100

Represents an error related to credit/debit card transactions.

 

 

image-20241001-050256.pngImage Added

 

111

error.PAYMENT.2.100.001

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

 

 

Screenshot 2024-10-02 at 08.26.26.pngImage Added

 

 

115

error.PAYMENT.2.101.001

The payment transaction was rejected because card issuer could not validate card owner's identity.

 

 

Screenshot 2024-10-02 at 09.56.53.pngImage Added

 

 

 

1367

error.PAYMENT.2.101.002

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.

 

 

 

Screenshot 2024-10-09 at 01.02.59.pngImage Added

 

1192

error.PAYMENT.2.102.002

Represents an error when the user's IP address is not from an allowed country.

Ex.: Iberia payments only allowed from Spain and Portugal.

 

 

 

Screenshot 2024-10-10 at 12.23.57.pngImage Added

 

 

1202

error.PAYMENT.2.102.003

Represents an error when the number of failed attempts from the same user has been exceeded.

 

Screenshot 2024-10-09 at 01.06.27.pngImage Added

 

1196

error.PAYMENT.2.102.002

Authorization from different country than card issuer, not allowed

 

Screenshot 2024-10-09 at 01.07.27.pngImage Added

 

  

Info

This feature has a flag called enable-rbi-error-2 which should be enabled to be used.

To enable, this flag please contact your CSM.

Analytics

event

Name

Value

name

ERROR

type

Other = 8

attributes

Name

e.g. Value

'Error Code'

PAYMENT.2.001

Name

CVC2 block incorrect

Path

/cart/payment

'Response Title' (modal title)

title: Uh oh!

'Response Description' (modal description - User-friendly Messages)

description: The CVC number is incorrect. Please look carefully at your card details. This number is 3 figures and is usually on the back of your card. If the charge has been pre-authorized on your card, we will reimburse you within a maximum period of seven days.