Tokenisation errors

All functionality can be tested in our test environment, but in test tokens have a 7 day lifespan.

Error Responses

Errors that relate to tokenisation are displayed in your response as:

Copied!
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE paymentService PUBLIC "-//WorldPay//DTD WorldPay PaymentService v1//EN"
 "http://dtd.WorldPay.om/paymentService_v1.dtd">
<paymentService version="1.4" merchantCode="MYMERCHANT">
  <reply>
    <orderStatus orderCode="ExampleOrder1">
      <error code="2">
        <![CDATA[authenticatedShopperID is required for a create token request]]>
      </error>
    </orderStatus>
  </reply>
</paymentService>

Error codes

CodeErrorDescription
1Internal errorInternal errors originate with the Worldpay payment service, and are usually addressed quickly. If you encounter an internal error, we recommend that you try submitting the XML message again after a brief period.
1Internal error: token was not createdInternal errors originate with the Worldpay payment service, and are usually addressed quickly. If you encounter an internal error, we recommend that you try submitting the XML message again after a brief period.
1Internal error: token not foundInternal errors originate with the Worldpay payment service, and are usually addressed quickly. If you encounter an internal error, we recommend that you try submitting the XML message again after a brief period.
2Admin Code not enabled for tokenisationYou have submitted a create token request, but the Tokenisation service has not been enabled on your account. Please contact your Relationship Manager.
2cvc data cannot be storedYou have attempted to store a cvc as part of an update token request, or create a token without a payment request. A shopper's cvc cannot be stored.
2Merchant code not enabled for tokenisationYou have submitted a create token request, but your Merchant Code is not enabled in a token group. Please contact your Relationship Manager.
2authenticatedShopperID is required for a create token requestYou have submitted a create token request, but have not sent through an <authenticatedShopperID>. This is a mandatory field when creating a shopper token.
2authenticatedShopperID is required for an update token requestYou have submitted an update token request, but have not sent through an <authenticatedShopperID>. This is a mandatory field when updating a shopper token.
2authenticatedShopperID is required for a use token requestYou have submitted a use token request, but have not sent through an <authenticatedShopperID>. This is a mandatory field when using a shopper token.
2authenticatedShopperID must not be present when tokenScope = merchantYou have submitted a request, but have included an <authenticatedShopperID> for a merchant token. <authenticatedShopperID>is only accepted for shopper tokens.
2cardNumber cannot be updatedYou have submitted an update token request and included the <cardNumber>. You cannot update a <cardNumber>.
2authenticatedShopperID cannot be emptyYou have submitted a create token request, but have not sent through any content in <authenticatedShopperID>. This field must contain at least 1 character.
2authenticatedShopperID cannot contain more than 64 charactersThe <authenticatedShopperID> you submitted contains more than the maximum of 64 characters.
2authenticatedShopperID cannot start with an underscoreThe <authenticatedShopperID> you submitted begins with an underscore, which is not permitted.
2authenticatedShopperID contains invalid characterThe <authenticatedShopperID> you submitted contains invalid data. The <authenticatedShopperID> must contain only the ISO-latin1 subset of the UTF-8 characters and there must be no white space.
2paymentTokenExpiry must not be present with shortLifeMinsYou have submitted the <paymentTokenExpiry> element with the <shortLifeMins> element.
2tokenEventReference cannot be emptyYou have submitted a <tokenEventReference> that contains no data. Although this element is optional, if submitted, it must contain at least one character.
2tokenEventReference can only contain alphanumeric characters and underscoresYou have submitted a <tokenEventReference> that contains invalid data.
2tokenEventReference cannot start with an underscoreThe <tokenEventReference> you submitted begins with an underscore, which is not permitted.
2tokenEventReference cannot contain more than 64 charactersYou have submitted a <tokenEventReference> that contains more than the permitted maximum of 64 characters.
2tokenReason cannot be emptyYou have submitted a <tokenReason> that contains no data. Although this element is optional, if submitted, it must contain at least one character.
2paymentTokenID cannot be emptyYou have submitted a <paymentTokenID> with no data in it.
5cardNumber is required for a create token requestYou have submitted a create token request, but have not sent through the <cardNumber>. This is a mandatory field when creating a token.
5cardNumber must not be present for this requestYou have submitted a <cardNumber> for a use token request. This field must not be present.
5expiryDate is required for a create token requestYou have submitted a create token request, but have not sent through an <expiryDate>. This is a mandatory field when creating a token.
5expiryDate is in the pastYou have submitted a create token request, but the <expiryDate> is in the past (card expired).
5Maximum number of updates exceeded for this tokenYou have submitted the maximum number of update token requests within a rolling 30 day period.

Note: If you have a business need to submit more than the maximum number of update token requests within a rolling 30 day period, this functionality can be provided. For more information, please contact your Relationship Manager or email corporatesupport@worldpay.com.

5Maximum number of tokens exceeded for this shopperThe maximum amount of sixteen tokens allowed for this shopper have been exceeded.
5Token does not existThe token you have tried to use either doesn’t exist, or has expired (which happens after a period of 4 years).
7Cannot tokenise [payment method]An indication of where the payment method will be specified is highlighted in green.
This indicates that you have tried to tokenise a payment method that is not currently supported by tokenisation.
For example Cannot tokenise [KONBINI-SSL]