Menu

Testing WPG Token Transactions

All merchants using Account Updater in combination with Worldpay WPG tokens must perform the tests detailed below.

To test Account Updater transactions using WPG token data:

  1. Submit Account Updater Requests for each orderId using the values in the Supplied Data Elements column of the Account Updater WPG Token Test Data table.

  2. Verify that the response values for the Account Updater acknowledgment Response match those shown in the Key Response Elements of the Account Updater WPG Token Test Data table. Receiving the matching Acknowledgment Response indicates that you formatted your Account Updater Request properly.

    To accelerate the testing process, the AU simulator in the Pre-Live environment closes any sessions every hour and produces a response file. Because of this behavior, if you submit multiple Account Updater Request files in the same day, the system generates multiple response files for the same MID/day.

  3. The Pre-Live environment constructs an AU Response file every hour for the requests submitted in the previous hour. For example, the response file created at 1:00 PM ET contains responses for requests submitted between 12:00 PM ET and 12:59 PM ET. Verify that the information, contained in the response files, matches the AU response information shown in the Key Response Elements of the Account Updater Token Test Data table.

Note: Once you begin processing in the production environment, a response file contains Visa, MasterCard, and Discover information. You receive one completion response file per day per merchantId.

Account Updater Access Worldpay Token Test Data

orderIdSupplied Data ElementsKey Response Data
38<cnpToken>1931000170096729987</cnpToken>
Acknowledgement Response:
<response>000</response>
<message>Approved</message>
AU File Response:
<response>500</response>
<message>The account number was changed</message>
<updatedToken> (parent element)
<cnpToken>2831000165434120000</cnpToken>
<type>VI</type>
<bin>445701</bin>
<expDate>0150</expDate>
<originalToken> (parent element)
<cnpToken>1931000170096729987</cnpToken>
<type>MC</type>
<bin>519456</bin>
<expDate>1250</expDate>
39<cnpToken>1921001896543215432</cnpToken>Acknowledgement Response:
<response>000</response>
<message>Approved</message>
AU File Response:
<response>501</response>
<message>The account was closed</message>
<originalToken> (parent element)
<cnpToken>1921001896543215432</cnpToken>
<type>MC</type>
40<cnpToken>1941001896543219978</cnpToken>Acknowledgement Response:
<response>000</response>
<message>Approved</message>
AU File Response:
<response>502</response>
<message>The expiration date was changed</message>
<updatedToken> (parent element)
<cnpToken>2854300165434120230</cnpToken>
<expDate>0150</expDate>
<type>MC</type>
<bin>511201</bin>
<originalToken> (parent element)
<cnpToken>1941001896543219978</cnpToken>
<expDate>1250</expDate>
<type>MC</type>
<bin>511201</bin>
41<cnpToken>1941001326543216757</cnpToken>
Acknowledgement Response:
<response>000</response>
<message>Approved</message>
AU File Response:
<response>506</response>
<message>No changes found</message>
42<cnpToken>1781001896543123345</cnpToken>
Acknowledgement Response:
<response>000</response>
<message>Approved</message>
AU File Response:
<response>505</response>
<message>No match found</message>
43<cnpToken>1841001896543219001</cnpToken>
Acknowledgement Response:
<response>000</response>
<message>Approved</message>
AU File Response:
<response>503</response>
<message>The issuing bank does not participate in the update program</message>
44<cnpToken>2941001896543210022</cnpToken>
Acknowledgement Response:
<response>000</response>
<message>Approved</message>
AU File Response:
<response>504</response>
<message>Contact the cardholder for updated information</message>
<originalCard> (parent element)
<cnpToken>2941001896543210022</cnpToken>
45<cnpToken>2953001896543210388</cnpToken>
Acknowledgement Response:
<response>823</response>
<message>Token was invalid</message>