Logs & Errors
...
| Error message | Description |
|---|---|
| 3dsecure authentication failed | 3dsecure authentication failed |
| 3-d secure problem: parameter 'rreq', 'eci' is missing | Idiotisk fejl fra Clearhaus som vi selv bør preempte. Det betyder at 3-D Secure v2 authentication ikke gik igennem |
| 3-d secure problem: parameter 'rreq', 'transStatus' (R) indicate authentication reject by issuer | 3-D Secure v2 gik ikke igennem fordi ACS'en sagde "reject" hvilket betyder at man skal stoppe med at forsøge at indløse |
| 3-d secure problem: pares has invalid ucaf | 3-D Secure v1 gik ikke igennem. Igen en skodbesked fra Clearhaus |
| 3dss: required data element missing: Elements failed validation (acctNumber does not match "^[0-9]{13,19}$") | 3-D Secure v2 kunne ikke startes fordi PAN'et ikke var mellem 13 og 19 karakterer |
| 3dss: required data element missing: Required elements are missing (acquirerMerchantID is required if messageCategory is 01) | Kunden har ikke indtastet sit merchant ID i dashboardet |
| 3dss: transaction data not valid: No RReq has been received (No response from directory server yet) | ... |
| 3dss: transaction data not valid: Unknown BIN (No CRD found, card with BIN 411111 is not enrolled with any known DS) | Kortet falder ikke i nogen kendte PAN ranges i 3-D Secure v2 |
| 3dss: transaction id not recognised: No transaction found (ID expired after 80 seconds or no preauth request performed) | 3-D Secure v2 er timed out |
| acs: format of one or more data elements is invalid according to the specification: Data element not in the required format or [...] | ... |
| veres=N | Kortet er ikke signed up til 3-D Secure v1 |
| ds: Access denied, invalid endpoint (acquirerBIN, acquirerMerchantID not recognized) | ... |
Error messages
Error messages are displayed in the payment window. Banks are inconsistent and unpredictable, but we do our very best to parse and translate their error codes. Here is a complete list of error messages, that your customers can receive in our payment window:
| Code | Error message | Description |
|---|---|---|
| invalid card | Invalid card details. Please verify your card details and try again. | The card number, CVC or expiration date is incorrect. |
| card expired | The card has expired. Please use a different card. | The card has expired. |
| declined | The card was declined. Please verify your card details and try again. | The card was declined by the acquiring bank, the card issuer or the bank. |
| insufficient funds | Payment was rejected by your bank. Your card has insufficient funds. | The transaction was rejected by the customer's bank due to insufficient funds, that is, there was not enough money or credit available to cover the payment. |
| limit exceeded | Payment was rejected by your bank. Your withdrawal limit has been exceeded. | The transaction was rejected by the customer's bank. The customer has surpassed their withdrawal limit. |
$method not supported | Unfortunately, we do not support $method. Please choose a different payment method. | The customer tried to pay with a payment method that you do not support, e.g. Apple Pay. This is typically because you forgot to enable it in our dashboard. |
$card not supported | Unfortunately, we do not support $card. Please use a different card. | The customer tried to pay with a payment card that you do not support. |
| 3dsecure failed | 3-D Secure authentication failed. Please try again or use a different card. | 3-D Secure authentication failed. |
$service failed | $service failed. Please try again or use a different payment method. | The specified service or payment method failed. |
| upstream error | An error occurred at the bank. Please wait a moment and try again. | An error occurred at the acquiring bank, the card issuer or the bank. |
| phase error | An error occurred. This may be because you have opened the page in multiple windows. | Phase errors are when someone opens the payment window, while it is busy in another state. |
| internal error | An error occurred while processing your request. Please wait a moment and try again. | An error occured at Scanpay. |
| network error | No connection to the server. Please check your internet connection and try again. | No connection to our servers. |
API Errors
The API is designed to be fault-tolerant and forgiving.
| Code | HTTP Body | Description |
|---|---|---|
| 400 | invalid json | Invalid JSON. |
| 400 | missing items | Missing items array in payment link API request. |
| 400 | invalid items.total | Invalid or missing total field. |
| 403 | invalid apikey | Invalid API key. |
| 408 | Request Timeout | The request timed out after 8 seconds. |
| 413 | Request Entity Too Large | The request body was larger than 32 kB. |
| 400 | Request Header Or Cookie Too Large | The request HTTP headers were larger than 4 kB |
| 500 | internal server error | Technical issue or scheduled downtime. Please try again. |