Below are the most common errors which you will find reported in the ePDQ back office:
This error means that the referrer we detected is not a URL. The merchant has entered the URL field in the “Data and origin verification” tab, “Checks for e-Commerce” section of his Technical Information page. The merchant is sending us the form with the hidden fields containing the order information from a different page from the one(s) entered in the URL field in the “Data and origin verification” tab, “Checks for e-Commerce” section.
This error means that our server has not detected a referrer in the request we received. The merchant is sending us order details, but we do not know where they originated from. Please ensure that no methods are being used that block the referrer information (payment page in pop up, special web server configuration, customer’s browser configuration, etc.). If the customer’s browser does not send the referrer information, we can bypass the referrer check if a SHASIGN is present and correct (see SHA-IN signature).
You will receive this error message if the SHASIGN sent in the hidden HTML fields for the transaction does not match the SHASIGN calculated at our end, using the details of the order and the additional string (password/passphrase) entered in the SHA-IN Signature field in the “Data and origin verification” tab, “Checks for e-Commerce” section of the Technical Information page.
You will receive this error message if the “SHASIGN” field in the hidden HTML fields is empty. Still, an additional string (password/passphrase) has been entered in the SHA-IN Signature field in the “Data and origin verification” tab, “Checks for e-Commerce” section of the Technical Information page, indicating you want to use an SHA signature with each transaction.
PSPID not found or not active
This error means that the value you have entered in the PSPID field does not exist in the respective environment (test or production), or the account has not yet been activated.
The data you entered is not correct. Please retry
Check if the username and password for the API-user are correct. We recommend that you make a new API user account and use their details in the plugin settings.
no (for instance: no PSPID)
This error means that the value you sent for the obligatory field is empty.
[parameter] too long (for instance: currency too long)
This error means that the value in your field exceeds the maximum length.
amount too long or not numeric: … OR Amount not a number
This error means that the amount you sent in the hidden fields either exceeds the maximum length or contains invalid characters such as ‘.’ or, ‘’.
NCERRORPLUS=Overflow in refund requests
In case the requested refund amount is higher than what is available on the balance.