Installation administration

This link enables you to navigate to the Other Actions area, at the bottom of the page (where you can activate your installation and edit the installation settings for the Production environment).

The ID for this installation. For example, 204596.

The Administration Code (ID). For example, CICERO.

This displays the company name that has been set by us for the Administration Code to which this installation is associated. This name will be displayed on the shopper confirmation email.
If you want to change the Company Name please contact us to discuss the change - various rules apply depending upon the type of company, for instance, a limited company has to show its limited status in the Company Name field.

The environment used to store the various details and settings for this integration. For example, TEST.

This is your own reference for this installation. This can be useful if you have multiple installations and you wish to easily distinguish them.

A text description you can enter and modify that will be shown to shoppers on the Payment Service pages. For example, Fred's Car Shop.

The integration method that this integration uses to connect to our system.

Also known as Verified by Visa. For more information, please refer to the Cardholder Authentication Guide.

Also known as MasterCard SecureCode. For more information, please refer to the Cardholder Authentication Guide.

The store-builder software, or shopping cart, that you use to collect the shopper's order and process their payment, via our payment service.

The store-builder software, or shopping cart, that you use, if this is not available in the Store-builder used list, above.

The web address URL for the Payment Notifications, sent via HTTP POST, that we use to return an HTTP notification to your system.

Enables you to return a Payment Notifications message to your system.

Specific to mobile payment pages. The web address URL that shoppers are sent to when they click the Shopper Redirect button. If you enable the button, this URL must be supplied.  For more information, see the Customising Mobile Guide.

If you cannot see this element, email: customeramendments@worldpay.com.

Specific to mobile payment pages. Adds a button to the payment result page that allows a shopper to return to your website (as specified in the Shopper Redirect URL setting). For more information, see the Customising Mobile Guide.

If you cannot see this element, email: customeramendments@worldpay.com.

Enables you to return a Payment Notifications message to your system that includes extra information about repeated payments, when a shopper makes a purchase via our Recurring Payments (FuturePay) service.

Note that the Payment Response enabled? setting for this integration must also be selected/enabled, as this setting enables/disables all Payment Notifications messages for the integration.

Enables you to use a Payment Notifications script to generate and display Result Pages to your shoppers. For more details, please refer to the Payment Response Guide.

We will suspend Payment Notifications if there are more than 200 consecutive Payment Notifications to your system. This box will show a tick if Payment Notifications have been suspended.

When you have fixed the problem, you can clear the Suspension of Payment Response checkbox and we will start sending Payment Notifications again. If the next Payment Notifications message is successful, then the Payment Response failure count (see below) will be reset to 0 (zero).

The total number of attempted payments made by shoppers, where we tried to return a Payment Notifications message to your system, but the message was not accepted by your system.

The count figure is reset to 0 when a Payment Notification succeeds.

The email address used to send our "Payment Notifications Failure Alert " message, when a shopper attempted to pay and we were unable to return a Payment Notifications message to your system.

Enables you to attach Payment Notifications log information to the "Payment Notifications Failure Alert " message that we send to you. This message is sent when a shopper attempted to pay and we were unable to return a Payment Notification to your system. The log information may assist your attempts to debug the Payment Notifications.

If you want confirmation emails, relating to just this installation, sent to you at a different address to that specified in Profile > Configuration Details enter it in this field.

Note that this email address will override the email address specified in Profile > Configuration Details for this installation only.

Enables extra security for the exchange rate files sent from Worldpay.

Confirm: Confirm the Info servlet password that you have entered.

Use Default: To remove the Info servlet password from use, select the Use default checkbox. This sets the password to an empty string.

This password is used to validate a Payment Notifications message.

When you enter a password here, this password is returned in the Payment Notification as the value of the callbackPW parameter.

Because the callbackPW value is known only by our payment service and you, you can verify the callbackPW value with a simple security check within your script.

To remove the Payment Notifications password from use, select the Use default checkbox. This sets the password to an empty string.

Confirm: Confirm the Payment Response password that you have entered.

Use Default: To remove the Payment Notifications password from use, select the Use default checkbox. This sets the password to an empty string.

When you enter a value for the MD5 secret, MD5 encryption becomes active for your purchase requests. For more details, please refer to the guide Submitting Transactions in the Redirect Model.

Confirm: Confirm the MD5 secret that you have entered.

Use Default: To remove the MD5 secret from use, select the Use default checkbox. This sets the secret to an empty string.

The SignatureFields parameter tells the Worldpay payment service, which values to use when checking your MD5 signature. The value you supply must be the same as that used to calculate your signature and will be a colon separated list of parameter names. This field will only accept alphanumeric characters along with custom parameters M_, C_ and MC_.

For more details please refer to the Hosted Payment Page (HTML Redirect) Guide.

Select this button to save the changes you have made.

The list box enables you to choose the environment you want to open, such as Production. Select the button to open the setup shown in the list box.

For more details, please refer to Test and Production - Setups.

When you have completed making changes to the Test setup settings, you can copy the settings to the Production setup using this button.

When you copy your Test settings, these will over-write your current Production settings. We advise you to print or record your current Production settings before you over-write them with your Test settings.

Note that the Copy to Production operation applies only to the Integration settings - it does not copy the Payment Service Page files to the Production Environment.

For more details, please refer to Test and Production - Setups.

This button opens the Activation Page, which enables you to specify your website URL and submit an activation request to go live.

Select this button when your testing is complete and you are ready for your Production integration to go live.

For more details, please refer to the Activation Details Page.

The list box enables you to choose the environment you want to open, such as Test. Select the button to open the setup shown in the list box.

For more details, please refer to Test and Production - Setups .