Three recent donors have received this error message from the credit card donation form, before their data is sent to GC. This is a relatively uncommon error, but it would be good to know whether to advise the donors to retry their donation, or if it points towards something that we need to fix.
This error message covers a wide range of conditions, and as we see new error codes, they should be interpreted by backend code and translated into a reasonable donor-facing action or error message. Usually, that just means "try again" vs "we can tell you that this will never work".
Some errors we've been seeing, and notes on the correct response.
|code||count (Dec 1-14th)||donor meaning||our meaning|
|400120||2425||5 second delay||Regenerate a new order ID--backend retry should result in success|
|410110||16||try again||Unknown order (maybe a lost API call?)|
|430339||112||contact donate@||"contact globalcollect", looks like a bad payment method combination|
|430403||97||try again||Unable to authorize, but try again|
|430327||7||contact donate@||Invalid amount--but we don't allow editing the amount. Flag.|
|20000000||43||contact donate@||Flag: Our form and API call were broken, we're missing a parameter.|
|21000050||36||try again (?)||We failed to validate a field, e.g. CVV sufficiently before passing it along.|
|21000080||223||contact donate@||Invalid country code, this is a serious issue. Flag.|
|21000130||10 (all nl)||contact donate@||Invalid email address. Our validation failed.|
|21000240||44||contact donate@||"field too short", this is an unrecoverable error on our side and should be flagged.|
For unknown errors, let's deliver the "contact us" message instead of recommending that the donor try again.