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:

Copied!
<?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 typeComments
1Internal error, a general errorThe request couldn’t be processed - please contact Worldpay for further assistance.
2Parse error, invalid XMLThe 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.
3The amount is invalid.
4Security violationThis 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
5The 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.
6One or more orders within a batch submission are invalid.
7The contents of the <paymentdetails> element are invalid.The returned error message within the CDATA tag should be examined in order to determine the exact cause.
8Service not available.The service is currently unavailable.

RFI/Dispute errors

These error codes are specific tosubmitting a dispute attachment:

Error codeError message
5Could not find order.
5Could not get payment for the order – that is, payment for the order could not be found.
5Not a RFI payment – that is, not in the State 'request for information'.
5No dispute or chargeback defence material was sent. Please specify a valid defence text and try again.
5Error while updating the dispute, the dispute was not sent.
5File too large. Maximum allowed is: 4 Kbytes.
5Invalid file type. Only the following are supported: zip, doc, docx, jpg, jpeg, png, gif, tiff, pdf, txt.
5XML submission too large.
8Defence uploads facility unavailable for 10 minutes after each submission.

Flexible account variables errors

These error codes are specific toflexible account variables:

Error codeError messageDescription
7You 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.
7AllowDynamicMCC property is disabled for this merchantYou have tried to submit <dynamicMCC> but you haven't told us you want this feature activated.
7AllowDynamicInterationType property is disabled for this merchantYou have tried to submit <dynamicInterationType> but you haven't told us you want this feature activated.
73DS data can only be submitted for an ecom transaction typeYou 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.