15 minutes to read

🛈 Important

This topic applies only to Clover

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

  1. MAX Pay Global for Dynamics 365 Finance / Commerce LCS packages.
  2. 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

Client id

Enter the ClientID from your app which is created in your clover account.

Yes



Client Secret

Enter the ClientID from your app which is created in your clover account.

Yes



Authorization code

Enter the Authorization code from your app which is created in your clover account.

Yes



Access token

This is generated using Generate access token button given in Payment service

Yes



Payment api

Enter the url given in this document.

Yes



PublickeyAPI

Enter the url given in this document.

Yes



AccessTokenAPI

Enter the url given in this document.

Yes



Device

You will require a Payment device.  Devices must be sourced via Clover to ensure they have software installed and the necessary injection keys.

Yes



Test cards

Clover test cards.

Yes



Merchant portal

Access to Clover portal.

Yes









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

Package deployment


3

Configure Retail scheduler

Yes

Initializing the retail scheduler


4

Configure Shared parameters (Common)

Yes

Configuring shared parameters


5

Configure the shared parameters for your chosen payment provider

Yes



6

Configure Payment services

Yes

Payment services


7

Configure Commerce POS

Optional


Only carry out this if you are using Commerce and using the Point of sale

8

Configure Call center

Optional


Only carry this out if you are using Call enter

9

Configure e-Commerce

Optional


Only carry this out if you are using Microsoft e-Commerce Store Front

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


Next topic