Worldpay

Setting up Worldpay

Foxy supports two Worldpay account types, and they are different products with different documentation:

• WorldPay (Corporate Account) uses Worldpay's Worldpay Payments Gateway (WPG) XML Direct integration. This is the one most Foxy stores need.

• WorldPay (Business Account) uses Business Gateway 350, which Worldpay list as available in the UK only.

You need an account that can use the XML Direct functionality, which may require a Corporate Account rather than a Business Account. This is because Foxy hosts the secure checkout page, which lets you customize it to match your site, rather than relying on the Worldpay hosted page.

If you have questions about setting up your Worldpay account, contact Worldpay support.

Merchant code

If you get the error "The payment gateway returned an invalid HTTP status code: 401" while checking out, you probably entered an incorrect merchant code or XML password. Be careful with the merchant code — it's not the same as your login. The merchant code can be found in the status panel:

XML password

You'll need to obtain your XML password.

For a business account you can find your password under the Installations menu:

The password for a corporate account can be found under the Profile > Merchant Environment menu:

3-D Secure v2

To enable 3-D Secure v2 for your Foxy store, you need 3DS Flex enabled within your Worldpay account. To action this, contact Worldpay support and request it be enabled for your account.

Once enabled, they'll provide the three values you need to enter into your Worldpay settings in the Foxy administration: issuer, encryption key and orgunitid. You'll need to make sure 3d secure options is set to enabled within your gateway settings for those three fields to be visible.

Other requirements for your site

Worldpay require the following details on your store website:

• Your company's registration name

• Your company's registered office address

• A contact telephone number

• An email address

They also require a refund policy. In Worldpay's own words:

We have been unable to locate a suitable refund policy. Under WorldPay regulations you must let your customers know that under certain circumstances a refund will be given at the discretion of the management. You can state that customers are not 'entitled' to a refund once they are using the service, but there may be circumstances where a refund is deemed necessary - e.g. technical problems where the customer is not getting the service they believed they signed up for. Please therefore amend all references to refunds by adding that 'refunds may occasionally be offered at the discretion of the management', or something similar

Testing

Obtaining a test account

Foxy provides shared test credentials for Worldpay, so in most cases you don't need your own Worldpay test account to run test transactions. In the Foxy administration, enable the Use default test account option on your Worldpay settings and Foxy will use its own test merchant code, XML password and 3-D Secure values. Test transactions are sent to Worldpay's test environment, never to your live account.

If you'd rather test against your own Worldpay test account, contact Worldpay support to have one set up, then enter its credentials in your test settings. You can also create a free Worldpay developer account to explore their APIs and documentation.

Note that Worldpay's test environment is rate limited and is not intended for load or stress testing.

Simulating different results

A number of different cases can be tested by entering the following values as the cardholder first name on the order:

• REFUSED simulates a refused payment

• REFERRED simulates a refusal with the refusal reason "referred"

• FRAUD simulates a refusal with the refusal reason "fraud suspicion"

• ERROR simulates a payment that ends in error

• 3D makes the test environment act as if the card is participating in 3-D Secure, so the directory responds as enrolled

• NO3D makes the test environment act as if the card is not participating in 3-D Secure, so the directory responds as not enrolled

All other cardholder names simulate an authorised payment.

Captures and refunds can be simulated through the Worldpay Merchant Interface. Use the Capture or Refund button on the Payment Details screen of an authorised or captured test payment.

Worldpay document further options in their test values reference.

Test card numbers

These test card numbers can only be used in the test environment, and should be used with an expiry date up to seven years in the future. Worldpay's test cards do not have a card verification code, so you may need to allow checkout without a CSC/CVV while testing.

• Visa — 4111 1111 1111 1111 and 4444 3333 2222 1111

• Mastercard — 5555 5555 5555 4444 and 5454 5454 5454 5454

• American Express — 343434343434343

• Maestro — 6759649826438453 (no issue number, uses a start date)

• Diners — 36148900647913

• Discover — 6011000400000000

• JCB — 3528000700000000

• Dankort — 5019717010103742

• Airplus — 122000000000003 and 192000000000008

• Carte Bleue — 5555 5555 5555 4444

• Laser — 630490017740292441

Worldpay maintain the current list in their test card numbers reference.

Going live

Worldpay accounts are not live by default. You request activation from Worldpay, who run compliance checks on your site before enabling real payments — which is why the site requirements above matter. Business Account holders can follow Worldpay's go live guide. Once your Worldpay account is live, turn off Use default test account and enter your own live merchant code and XML password.

Troubleshooting & interpreting response codes

"missing info for 3D-secure transaction: acceptHeader"

If you get the following error and don't plan to use 3-D Secure, ask Worldpay to disable 3-D Secure on your account:

Invalid payment details : missing info for 3D-secure transaction: acceptHeader (7)

"invalid HTTP status code: 401"

See Merchant code above — this almost always means the merchant code or XML password is wrong. The merchant code is not your login.

For anything else, contact Worldpay support.