Verifone UK Implementation guide
15 minutes to read
|
🛈 Important This topic applies only to Verifone UK (PAYware Ocius Sentinel or "POS Client") |
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 |
Required |
From |
Notes |
|
1 |
Test device |
Yes |
Verifone |
Obtain a suitable PED from Verifone UK with Test injected keys and P2PE Enabled. |
|
2 |
Test cards |
Yes |
Verifone |
You will need a range of test cards to match the card types you plan to accept |
|
3 |
Test trigger values |
Yes |
Verifone |
In the test environment, Verifone accepts test trigger values that can simulate certain conditions – e.g. a declined transaction |
|
4 |
POS Client software |
Yes |
Verifone |
You will require the POS Client software to be installed, configured, and working. POS Client is also known as PAYware Ocius Sentinel. |
|
5 |
POS Client config and license |
Yes |
Verifone |
You will require a license file from Verifone and a configuration file |
|
6 |
Tokenization enabled |
Yes |
Verifone |
The VerifoneUKConnector requires Tokenization to be enabled on the Verifone host side. |
|
|
|
|
|
|
Installation steps
This section describes the specific installation steps
|
# |
Item |
Required |
Navigation |
Notes |
|
1 |
Obtain the deployable packages from Retail Realm |
Yes |
Request these from your Retail Realm project manager |
|
|
2 |
Deploy the packages to your environment using LCS |
Yes |
|
|
|
3 |
Configure Retail scheduler |
Yes |
|
|
|
4 |
Configure Shared parameters (Common) |
Yes |
|
|
|
5 |
Configure the shared parameters for your chosen payment provider |
Yes |
|
|
|
6 |
Configure Payment services |
Yes |
Payment service payments are not supported but a Payment services profile is required |
|
|
7 |
Configure Commerce POS |
Yes |
|
Only carry out this if you are using Commerce and using the Point of sale |
|
8 |
Configure Call center |
N/A |
|
Not currently supported |
|
9 |
Configure e-Commerce |
N/A |
|
Not currently supported |
|
10 |
Apply license(s) |
Yes |
|
Applying the licensing is required prior to performing a payment transaction but not required to install and configure |
|
11 |
Perform a test transaction |
Yes |
|
Once you have completed your configuration, perform a test transaction |