NMI Implementation guide
15 minutes to read
🛈 Important This topic applies only to NMI |
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 for NMI to ensure it meets your requirements, prior to deployment.
Prerequisites
- MAX Pay Global for Dynamics 365 Finance / Commerce LCS packages.
- Payment provider details for your test/production Merchant account (see below).
- You will require a MAX Pay Global license (types: test or production).
Prerequisite tasks and information required
You will require the following pieces of information:
Item |
Task |
Reqd. |
From |
Sample value |
Public Key |
Create a Public security key (Tokenization, not checkout) Use this value in the Payment services Profile |
Yes |
NMI Portal -> Home / Gateway Options / Security Keys > Add a New Public Key |
knE8FC-46ay95-eq2jrR-Yj6wR4 |
Private key |
Create a new Private security key (API, not Cart key) Use this value in the Payment services Profile |
Yes |
NMI Portal -> Home / Gateway Options / Security Keys > Add a New Private Key |
U7Su36C2u6qFpBErNR5sjWaz87g6P6sn |
Configure AVS |
Task: Configure AVS rules on the NMI portal |
Optional |
NMI Portal -> |
|
Configure CVV |
Task: Configure CVV rules on the NMI portal |
Optional |
NMI Portal -> |
|
API Response variables |
Use system default API response format |
Yes |
NMI Portal > |
|
Test mode |
Enable and Disable test mode from the NMI Portal |
Yes |
NMI Portal > |
|
Licensing
Ensure that you have obtained correct license for your deployment before you start. Refer to this section for further details.
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 |
There are no specific Shared parameters for NMI |
|
6 |
Configure Payment services |
Yes |
|
|
7 |
Configure Call center |
Optional |
|
Only carry this out if you are using Call enter |
9 |
Apply license(s) |
Yes |
|
Applying the licensing is required prior to performing a payment transaction but not required to install and configure |
10 |
Perform a test transaction |
Yes |
|
Once you have completed your configuration, perform a test transaction |
Testing
Please see below for test card numbers you can use. Please always refer to the Payment provider's web site for up to date test card numbers and decline trigger values.
Card type |
Card number |
|
Visa |
4111111111111111 |
|
MasterCard |
5431111111111111 |
|
Discover |
6011601160116611 |
|
American Express |
341111111111111 |
|
Diner's Club |
30205252489926 |
|
JCB |
3541963594572595 |
|
Maestro |
6799990100000000019 |
|
Credit card expiration |
10/25 |
|
Trigger values |
|
|
Decline |
Less than 1.00 |
|
Fatal error message |
Invalid card number |
|
AVS Match |
Address1: 888 |
|
CVV Match |
CVV: 999 |
|
|
|
|