15 minutes to read

🛈 Important

This topic applies only to Moneris

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

Moneris Portal credentials

Obtain your username, storied and password from Moneris

https://esqa.moneris.com/mpg/index.php

Yes

Moneris


MOTO Moneris configuration

Configure the Moneris portal if you are using making payments related to Payment services (“MOTO”) – Sales order processing / Call center.

  1. Go to Vault tab > Select Hosted Vault Config from the list. 
  2. In the Hosted vault configuration page, Click Edit and enter the Response URL. (Less than 100 characters).

Optional

The Moneris Portal


Checkout id

You will require the Checkout id (for HQ and eCOM Payments only – this is not required for POS)

Yes

Moneris


Store id

You will require an id for each store you are deploying

Yes

Moneris


API Token

You will require an API token

Yes

Moneris


Merchant id

You will require the Merchant id number(s) for Retail Store (MPOS/CPOS)

Yes

Moneris


Payment terminal ip

You will require (to know) the ip address of your payment terminal

Yes

Your IT department


Payment terminal port

You will require to know the port number of your payment terminal

Yes

Moneris


ECR id

You will require the ECR id of your payment terminal

Yes

Moneris



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

Configure Operation buttons – these are required by Moneris

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 deploying e-Commerce Online store(s)

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