We recommend using the MD5 setting for additional security. The transaction information will include an encrypted value that is used to check that data sent to Worldpay has not been modified.
Installation and Updating
↑ Back to topSetup and Configuration
↑ Back to top




- Change ‘Store-builder used’ to ‘Other’
- Set ‘store-builder: if other – please specify’ as ‘WooCommerce’
- ‘Payment Response URL’ will be found in your WooCommerce settings for the gateway plugin. Make sure you copy this exactly as it is shown.
- Tick ‘Payment Response enabled?’
- Tick ‘Enable Recurring Payment Response’
- Tick ‘Enable the Shopper Response’
- ‘Payment Response password’ needs to be set using the same value from your WooCommerce settings
- ‘MD5 secret for transactions’ needs to be set using the same value from your WooCommerce settings – if you have left it blank in your WooCommerce settings then you can leave it blank here.
- ‘SignatureFields’ needs to be set using the same value from your WooCommerce settings – if you have left the MD5 secret blank in your WooCommerce settings then you can leave this blank.

Signature Fields
↑ Back to topUsing Pre-Auth
↑ Back to top
WorldPay FuturePay – WorldPay & Subscriptions
↑ Back to top- Subscriptions can only be modified if there is more than 2 weeks for the next payment.
- Subscriptions with a regular payment schedule of less than 2 weeks between payments CANNOT be modified. They can only be cancelled.
- Cart cannot contain more than one subscription but can contain a subscription product and an ordinary product.
- Subscriptions can be cancelled from your WooCommerce admin or from the customer’s My Account page. To do this you MUST APPLY TO WORLDPAY for a Remote Administration Installation ID and enter the ID and password in to your settings. If you don’t enter a valid Remote Administration Installation ID and password, you can cancel the subscription in your WooCommerce admin but also need to cancel in your Worldpay FuturePay admin area.

URL Submission Method
↑ Back to top
Security Column
↑ Back to top
- C : CVS check
- P : Postcode check
- A : Address check
- W : Country check
- 0 : Not supported (yellow colour)
- 1 : Not checked (yellow colour)
- 2 : Matched (green colour)
- 4 : Not matched (red colour)
Customization
↑ Back to topNote: This is a Developer level section. If you are unfamiliar with code and filters and resolving potential conflicts, select a WooExpert or Developer for assistance. We are unable to provide support for customizations under our Support Policy.
Adding Custom Arguments Sent To Worldpay
↑ Back to topadd_filter( 'woocommerce_worldpay_args', 'custom_woocommerce_worldpay_args', 10, 2 );
function custom_woocommerce_worldpay_args( $worldpay_args, $order ) {
$worldpay_args['MC_test_field'] = 'This should show up somewhere';
return $worldpay_args;}
You will need to login to Worldpay and modify the email templates to use this additional information. your field name should be prefixed with “MC_” as in the example above.
You should not modify the standard fields, these are required by Worldpay and changing them could prevent your customer from checking out.
Troubleshooting
↑ Back to topCustomer is not redirected back to your website after payment
↑ Back to topAre you using CloudFlare?
↑ Back to top
How to create a resultY.html file in the Worldpay file manager
↑ Back to top
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
<html> | |
<head> | |
<meta http-equiv='Refresh' content='2; Url="<WPDISPLAY ITEM=MC_callback>&MC_order=<WPDISPLAY ITEM=MC_order>&transId=<WPDISPLAY ITEM=transId>&transStatus=<WPDISPLAY ITEM=transStatus>&transTime=<WPDISPLAY ITEM=transTime>&authAmount=<WPDISPLAY ITEM=authAmount>&authCurrency=<WPDISPLAY ITEM=authCurrency>&rawAuthMessage=<WPDISPLAY ITEM=rawAuthMessage>&rawAuthCode=<WPDISPLAY ITEM=rawAuthCode>&callbackPW=<WPDISPLAY ITEM=callbackPW>&cardType=<WPDISPLAY ITEM=cardType>&countryMatch=<WPDISPLAY ITEM=countryMatch>&AVS=<WPDISPLAY ITEM=AVS>&MC_transactionNumber=<WPDISPLAY ITEM=MC_transactionNumber>&futurePayId=<WPDISPLAY ITEM=futurePayId>&futurePayStatusChange<WPDISPLAY ITEM=futurePayStatusChange>"'> | |
<title>Payment Successful</title> | |
</head> | |
<h1>Payment Successful</h1> | |
<a href="<WPDISPLAY ITEM=MC_callback>&MC_order=<WPDISPLAY ITEM=MC_order>&transId=<WPDISPLAY ITEM=transId>&transStatus=<WPDISPLAY ITEM=transStatus>&transTime=<WPDISPLAY ITEM=transTime>&authAmount=<WPDISPLAY ITEM=authAmount>&authCurrency=<WPDISPLAY ITEM=authCurrency>&rawAuthMessage=<WPDISPLAY ITEM=rawAuthMessage>&rawAuthCode=<WPDISPLAY ITEM=rawAuthCode>&callbackPW=<WPDISPLAY ITEM=callbackPW>&cardType=<WPDISPLAY ITEM=cardType>&countryMatch=<WPDISPLAY ITEM=countryMatch>&AVS=<WPDISPLAY ITEM=AVS>&MC_transactionNumber=<WPDISPLAY ITEM=MC_transactionNumber>&futurePayId=<WPDISPLAY ITEM=futurePayId>&futurePayStatusChange<WPDISPLAY ITEM=futurePayStatusChange>">Go back to the site</a> | |
<WPDISPLAY ITEM=banner> | |
<WPDISPLAY ITEM=footer.html> | |
</html> |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
<html> | |
<head> | |
<meta http-equiv='Refresh' content='2; Url="<WPDISPLAY ITEM=MC_callback>/?MC_order=<WPDISPLAY ITEM=MC_order>&transId=<WPDISPLAY ITEM=transId>&transStatus=<WPDISPLAY ITEM=transStatus>&transTime=<WPDISPLAY ITEM=transTime>&authAmount=<WPDISPLAY ITEM=authAmount>&authCurrency=<WPDISPLAY ITEM=authCurrency>&rawAuthMessage=<WPDISPLAY ITEM=rawAuthMessage>&rawAuthCode=<WPDISPLAY ITEM=rawAuthCode>&callbackPW=<WPDISPLAY ITEM=callbackPW>&cardType=<WPDISPLAY ITEM=cardType>&countryMatch=<WPDISPLAY ITEM=countryMatch>&AVS=<WPDISPLAY ITEM=AVS>&MC_transactionNumber=<WPDISPLAY ITEM=MC_transactionNumber>&futurePayId=<WPDISPLAY ITEM=futurePayId>&futurePayStatusChange<WPDISPLAY ITEM=futurePayStatusChange>"'> | |
<title>Payment Successful</title> | |
</head> | |
<h1>Payment Successful</h1> | |
<a href="<WPDISPLAY ITEM=MC_callback>/?MC_order=<WPDISPLAY ITEM=MC_order>&transId=<WPDISPLAY ITEM=transId>&transStatus=<WPDISPLAY ITEM=transStatus>&transTime=<WPDISPLAY ITEM=transTime>&authAmount=<WPDISPLAY ITEM=authAmount>&authCurrency=<WPDISPLAY ITEM=authCurrency>&rawAuthMessage=<WPDISPLAY ITEM=rawAuthMessage>&rawAuthCode=<WPDISPLAY ITEM=rawAuthCode>&callbackPW=<WPDISPLAY ITEM=callbackPW>&cardType=<WPDISPLAY ITEM=cardType>&countryMatch=<WPDISPLAY ITEM=countryMatch>&AVS=<WPDISPLAY ITEM=AVS>&MC_transactionNumber=<WPDISPLAY ITEM=MC_transactionNumber>&futurePayId=<WPDISPLAY ITEM=futurePayId>&futurePayStatusChange<WPDISPLAY ITEM=futurePayStatusChange>">Go back to the site</a> | |
<WPDISPLAY ITEM=banner> | |
<WPDISPLAY ITEM=footer.html> | |
</html> |






BulletProof Security
↑ Back to topSorry, there was a problem processing your payment
↑ Back to top