WORLDPAY

WorldPay Gateway Guide

R
Written by Rowen D
Updated over a week ago

Services and Compatibility

Payment Gateway Company Name: WorldPay
Services that work with ChargeAutomation:  

  • Corporate Gateway,

  • Business Gateway

Services that do not work with ChargeAutomation: 

  • If recurring is important to you, avoid being set up with two MID’s. You should put all transactions (new and recurring) through just the one MID.

Supported operations: ✅Purchase, Authorize, Capture, Refund, Void, Verify, Store, General Credit
Supported payment types: ✅Credit Card
3D Secure 1 Supported: ✅Yes
3D Secure 2 Supported: ❎No
Regions: ✅Asia Pacific, Europe, Middle East, North America
API endpoint URL: https://secure.worldpay.com/jsp/merchant/xml/paymentService.jsp

Authentication and Security

Specific names for credentials: Login, Password

Additional steps needed to activate? Turn off the capture delay setting. (See notes)

Onboarding Merchants in:

  •  Hong Kong

  •  United Kingdom

  •  Australia

  •  Andorra

  •  Argentina

  •  Belgium

  •  Brazil

  •  Canada

  •  Switzerland

  •  China

  •  Colombia

  •  Costa Rica

  •  Cyprus

  •  Czech Republic

  •  Germany

  •  Denmark

  •  Spain

  •  Finland

  •  France

  •  Gibraltar

  •  Greece

  •  Hungary

  •  Ireland

  •  India

  •  Italy

  •  Japan

  •  Liechtenstein

  •  Luxembourg

  •  Monaco

  •  Malta

  •  Malaysia

  •  Mexico

  •  Netherlands

  •  Norway

  •  New Zealand

  •  Panama

  •  Peru

  •  Poland

  •  Portugal

  •  Sweden

  •  Singapore

  •  Slovenia

  •  San Marino

  •  Turkey

  •  United States Minor Outlying Islands

  •  Holy See

Additional Notes

For US based acquiring accounts, see WorldPay US.

There is a setting in your WorldPay Merchant Interface called Capture Delay which is set to on by default within Worldpay. You’ll need to login and turn that setting off.

In addition, if you tell WorldPay you are working with ChargeAutomation you can usually bypass the need to do a full test transaction before being pushed into production. Lastly, you’ll want to be approved for the “XML Invisible” installation.

Using Visa and Mastercard cards retained with ChargeAutomation falls under Stored Credentials regulations.

Did this answer your question?