Click here to search the entire website

General errors

The most common error codes are shown below, along with their messages. For queries about these and all other errors, contact your Implementation Manager.

Error Responses

Errors are displayed in our response as:

<?xml version="1.0" encoding="UTF-8"?>

<!DOCTYPE paymentService PUBLIC "-//WorldPay//DTD WorldPay PaymentService v1//EN"

  "http://dtd.WorldPay.com/paymentService_v1.dtd">

<paymentService version="1.4" merchantCode="ExampleCode1"> <!--The merchantCode you supplied originally-->

<reply>

    <orderStatus orderCode="ExampleOrder1"> <!--Not present for parse or security violation errors-->

  <error code="2">

   <![CDATA[Invalid address: Postal code is missing or empty.]]>

   </error>

    </orderStatus>

</reply>

</paymentService>

Common error codes

Error code no. Error type Comments

1

 

Internal error, a general error The request couldn’t be processed - please contact Worldpay for further assistance.
2 Parse error, invalid XML The XML couldn’t be parsed against the DTD. Ensure that the request conforms to the DTD, and that it's validated using an industry standard parser before submission to Worldpay.
3 The amount is invalid.  
4 Security violation

This error response is generated for one of the following reasons:

  • The login name (i.e. the merchant code used in the authentication process to access the payment service) doesn't match the merchant code in the root element <paymentService>

  • You are submitting a payment from an IP address that is not registered against your account

  • The environment to which you are submitting the transaction is not active, i.e. the account hasn't been activated in production

5 The contents of the order element are invalid. The returned error message within the CDATA tag should be examined in order to determine the exact cause.
6 One or more orders within a batch submission are invalid.
7 The contents of the payment element are invalid. The returned error message within the CDATA tag should be examined in order to determine the exact cause.
8 Service not available. The service is currently unavailable.

RFI/Dispute errors

These error codes are specific to submitting a dispute attachment:

Error code

Error message

5

Could not find order.

5

Could not get payment for the order – that is, payment for the order could not be found.

5

Not a RFI payment – that is, not in the State 'request for information'.

5

No dispute or chargeback defence material was sent. Please specify a valid defence text and try again.

5

Error while updating the dispute, the dispute was not sent.

5

File too large. Maximum allowed is: 4 Kbytes.

5

Invalid file type. Only the following are supported: zip, doc, docx, jpg, jpeg, png, gif, tiff, pdf, txt.

5

XML submission too large.

8

Defence uploads facility unavailable for 10 minutes after each submission.

Flexible account variables errors

These error codes are specific to flexible account variables:

Error code

Error message

Description

7

You cannot set this MCC through the API, please contact customer support.

You have tried to submit a MCC via <dynamicMCC>, but you haven't told us you want to make this MCC dynamic.
7 AllowDynamicMCC property is disabled for this merchant You have tried to submit <dynamicMCC> but you haven't told us you want this feature activated.
7 AllowDynamicInterationType property is disabled for this merchant You have tried to submit <dynamicInterationType> but you haven't told us you want this feature activated.
7 3DS data can only be submitted for an ecom transaction type You have tried to submit 3DS (3D Secure) authentication data when the type attribute of <dynamicInterationType> is not "ECOMMERCE". You can only send ecommerce transactions for 3DS authentication.