Worldpay UK Implementation guide
15 minutes to read
|
🛈 Important This topic applies only to Worldpay UK |
This section guides you through the discrete implementation steps in order to complete a successful implementation.
Specification
Review the specification for the MAX Pay Global payment connector to ensure it meets your requirements, prior to deployment.
Retail Realm prerequisites
- MAX Pay Global for Dynamics 365 Finance / Commerce LCS packages.
- MAX Pay Global test / production licenses.
Prerequisite tasks and information required
You will require the following prerequisite pieces of information and tasks to be completed prior to implementing MAX Pay Global:
|
Item |
Task/Description |
Required |
From |
Sample value |
|
IPC 2.3.1 |
Install and correctly pre-configure the IPC on the designated Windows PC where the Hardware station (Local or Shared) will reside. |
Yes |
Worldpay UK |
|
|
Payment device |
You will require a Payment device that is supported with the IPC software. Contact WorldpayUK. |
Yes |
Worldpay UK |
|
|
Test cards |
Ensure you have WorldpayUK specific test cards to use during your test phase |
Yes |
Worldpay UK |
|
|
IPC IP address |
The IP Address of the IPC. Normally the IPC is installed on the same Windows PC as the POS and the ip address would be the loopback address. Where the IPC is installed on a shared hardware station or centralized deployment model, you would need the ip address of that machine/IPC instance. |
Yes |
Worldpay UK |
127.0.0.1 |
|
IPC port |
The IPC is normally configured to use the interfacing socket and the IPC assigns a port for this, to allow MAX Pay Global to communicate to it. You will need this during the Hardware profile / Register (Terminal parameter) configuration. |
Yes |
Worldpay UK |
10000 |
|
Merchant code |
Omni channel scenarios: For each entity (e.g. Store), you will require the Merchant code. This is used within the various profiles and determines which Merchant account funds are deposited to. Omni channel scenarios not supported: Merchant code is not required for simple cash and carry transactions. |
Yes |
Worldpay UK |
RetailComp |
|
Service API url |
Omni channel scenarios: you will require service API url. Test: https://secure-test.worldpay.com/jsp/merchant/xml/paymentService.jsp Production: https://secure.worldpay.com/jsp/merchant/xml/paymentService.jsp Omni channel scenarios not supported: Service API url is not required for simple cash and carry transactions. |
Yes |
Worldpay UK |
|
|
User name |
Omni channel scenarios: You will require a user name that is associated with the above Merchant code. Omni channel scenarios not supported: user name is not required for simple cash and carry transactions. |
Yes |
Worldpay UK |
|
|
Password |
Omni channel scenarios: You will require a password that is associated with the above Merchant code. Omni channel scenarios not supported: Password is not required for simple cash and carry transactions. |
|
|
|
|
Installation id |
Omni channel scenarios: You will require an installation id that is associated with the above Merchant code. Omni channel scenarios not supported: Installation id is not required for simple cash and carry transactions. |
Yes |
Worldpay UK |
|
|
|
|
|
|
|
Installation steps
This section describes the specific installation steps