Worldpay Express specification
|
🛈 Important This topic applies only to Worldpay Express |
|
Item |
Support |
Notes |
|
Region(s) |
USA/Canada |
|
|
Gateway or Processor |
Gateway and Processor |
|
|
Processor / Acquirer supported |
Worldpay |
Please contact us for up to date support |
|
Provider website |
Yes |
|
|
Omni channel tokenization between in-store and on-line |
Yes |
|
|
Gift card program via provider |
Yes |
|
|
System status |
|
|
|
Channel support |
|
|
|
D365 Finance (A/R - SOP) |
Yes |
|
|
Commerce – Call center |
Yes |
|
|
Commerce – Online Storefront |
Yes |
|
|
Store Commerce |
Yes |
|
|
External e-Commerce |
Yes |
|
|
Headquarters payments |
|
|
|
Hosted payment page support |
Yes |
|
|
Full EMV device support |
Yes |
Utilized when using Call center to support in-person payments |
|
Azure service support |
Not required |
|
|
Point of Sale |
|
|
|
Store Commerce supported |
Yes |
|
|
Cloud POS supported |
Yes |
|
|
Android Hybrid App POS supported |
Contact us |
|
|
Android POS all-in-one devices available |
Contact us |
|
|
iOS Store Commerce / Devices supported |
Contact us |
|
|
Custom Operations |
Yes |
|
|
Payment terminal devices |
|
|
|
Supported devices |
Various devices from Ingenico and Verifone. Processor dependent. |
Refer to Worldpay documentation for further details. |
|
Device connectivity |
Wifi, RJ45 cable, Bluetooth |
*Connectivity is device specific. Refer to specific device specification. |
|
Local/cloud connectivity |
Local (Direct) and Cloud |
|
|
Offline processing on the payment terminal |
Yes1 |
Using triPOS Direct |
|
Payment methods accepted |
Cards brands: All major credit and debit cards. |
|
|
US Pin Debit |
Yes |
|
|
Wallet support |
ApplePay GooglePay |
|
|
Entry methods |
Swipe Dip/enter (Chip) Contactless (NFC) Manually keyed into the payment terminal |
|
|
Third party application required |
triPOS Direct |
|
|
Line display support |
Not supported by Worldpay |
|
|
Signature capture support |
Yes |
|
|
Bypass pin debit |
Yes |
|
|
Microsoft Dynamics 365 payment compatibility |
|
|
|
Omni channel payments supported |
Yes |
|
|
Omni-channel commerce order payments supported |
Yes |
|
|
Reconciliation available via MAX Pay Controller |
Yes |
|
|
Provider specific details |
|
|
|
Customer token profiles (Vaulted token) |
Yes |
|
|
Merchant portal |
Yes |
Production only |
|
Test account available |
Yes |
Sign up via Worldpay |
|
MPG additional non-standard value-added functionality |
|
|
|
Tokenization (“card on file”) at the Point of Sale |
Yes |
|
|
Customer Token list and card management at the Point of sale |
Yes |
|
|
One-time tokens for Call center payments |
Yes |
The ability not to store (hide) Customer tokens for certain sales orders. |
|
Credit card token and payment line import from a 3rd party system (e.g., external e-Commerce platform) |
Yes |
|
|
Payment terminal devices at Call center |
Yes |
Use “Call center as a POS” to acquire a token from the payment terminal. |
|
Call center multiple MIDs per Legal entity |
Yes |
|
|
Call center pre-pay default management |
Yes |
|
|
Capture electronic signature from the payment terminal for on-account transactions at the Point of sale |
Yes |
|
|
Consolidated unique Customer token from POS generated sales orders |
Yes |
|
|
Provider value-added services |
|
|
|
Token import from another provider |
Contact Worldpay |
|
|
PCI and Security Status |
|
|
|
General statement |
MAX Pay Global does not collect, process, transmit or store any Card Holder Data (CHD). For in-person payments, MPG uses either triPOS Direct or triPOS Cloud. In both instances, the Worldpay device interacts with the payment holder. Credit card data is encrypted at the point of entry and Worldpay and triPOS are responsible for transmitting that to the Worldpay gateway. Worldpay has validated this with the PCI council as a Point-to-point encrypted solution. See below In a back office or e-Commerce environment, MAX Pay Global uses Worldpay’s Express hosted payment page to interact with the payment holder. MAX Pay Global does not collect, process, transmit or store any CHD. Where payment holder details are stored against the customer (e.g. “Card on file/Credential on file”), or where details are stored about a particular transaction, only a Worldpay non-sensitive Token is stored for future use. |
|
|
Worldpay PCI Council Certification |
P2PE Validated |
|
|
|
|
|
Notes
- Offline Store and Forward is supported on Store Commerce and with triPOS Direct, in either Automatic or Manual forward modes.
Disclaimer
This page details the general specification for this Provider. Specifications are subject to change without notice and all information has been verified correct at the time of compilation. E&OE