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:
Erros description | Paycomet Error Code |
|---|---|
Operation not allowed for the credit card type | 102 |
Card issuer could not validate card owner | 115 |
CVC2 block incorrect | 111 |
Operation not allowed for the credit card type | 130 |
Country (customer IP address) not allowed | 1192 |
Number of failed attempts (last 30 minutes) from the same ip address exceeded | 1202 |
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 | 1367 |
Authorization from different country than card issuer, not allowed | 1196 |
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.