The errors which may arise when using Client Side Encryption, and what they mean.
These are the validation errors which can be encountered when a shopper makes a payment through a web browser, or an Android or iOS App. You should decide on what text to show the shopper if an error arises:
|Error Code||Description||Related 'data-worldpay' attribute|
|101||A credit or debit card number is mandatory||number|
|102||Card number should contain between 12 and 20 numeric characters||number|
|103||The card number entered is invalid||number|
|201||The security code is invalid||cvc|
|301||The expiry month is not included||exp-month|
|302,'Expiry Month' must contain exactly 2 numbers||exp-month|
|303,'Expiry Month' should be between 01 and 12||exp-month|
|304||The 'Expiry Year' is not included||exp-year|
|305,'Expiry Year' must contain exactly 4 numbers||exp-year|
|306,'Expiry Month' and 'Expiry Year' together must be a date in the future||exp-month and exp-year|
|401,'Card Holder' name is mandatory||name|
|402,'Card Holder' name cannot exceed thirty (30) characters||name|
Note: The Worldpay error handler is designed as a final additional check, and is not intended to replace your own validation.
These are the XML error responses which relate directly to CSE:
|CSE Key is disabled||A disabled CSE key has been used to make a payment. You need to update your page to use an enabled key.|
|An internal CSE service error has occurred||Either:|
- You are trying to use a key that doesn't exist.
- The decryption failed. This could be if you did not correctly copy your public key, or if the data was altered after encryption.
Feedback or bugs to report?
Ask our developer community.
Search our documentation, API references and articles.