CardConnect Implementation guide
15 minutes to read
|
🛈 Important This topic applies only to CardConnect |
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 CardConnect 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).
- If you are deploying a Payment terminal (e.g. Cards) at Retail POS, you will require an appropriate Test or Production device and test cards.
- 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/Description |
Required |
From |
Sample value |
|
Test device |
You will need a test device from your provider. You will also need appropriate test cards. |
Yes |
CardConnect |
See spec. |
|
Card mapping |
You will need to decide which card/payment method types you wish to accept and this will drive the card mapping |
Yes |
See documentation |
|
|
MerchantID |
For each entity (e.g. Store), you will require the Merchant ID. This is used within the various profiles and determines which Merchant account funds are deposited to. |
Yes |
CardConnect |
Test12345 |
|
Username and password |
You will require a username and password that is associated with the above Merchant ID |
Yes |
CardConnect |
Testing111 *********** |
|
Auth key |
You will require an Auth key |
Optional |
CardConnect |
Required if creating Customer tokens at the Point of Sale. Refer to specific sections herein |
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 |
|
|
|
5 |
Configure the shared parameters for your chosen payment provider |
Yes |
|
|
|
6 |
Configure Payment services |
Yes |
|
|
|
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 |
Testing
For a full range of card numbers and trigger values, visit https://developer.cardpointe.com/guides/cardpointe-gateway#testing-your-integration