Payment services
|
🛈 Important The following must be completed before payments can be configured in any channel. |
This article describes how to setup the standard Microsoft form for Payment services. Payment services are specific to a given legal entity. Only one Payment service can be the default, meaning the one that is used when creating a new credit card from within Dynamics 365 back office. Authorizations and captures are always relative to the credit card used and hence the payment service used. When using payments at Retail POS, at least one default Payment service must be defined, whether you are using payments at back office or not. The Payment service and associated logic is a standard Microsoft entity and the way payments are conducted in MAX Pay Global follow that logic and workflow.
Prerequisites
Please ensure you have completed these standard Dynamics 365 configurations:
- Accounts receivable > Setup > Accounts receivable parameters
- Accounts receivable > Payments setup > Methods of payment
Set up a new processor for new credit cards
To process payments on Point of sale (POS) terminals, at a Call center or at e-Commerce, you must configure a new default Payment Service for new credit cards. Follow these steps.
- Sign-in to Headquarters, and go to Accounts receivable > Payments setup > Payment services.
- On the Action Pane, select New, and then, on the Setup tab, enter the following information.
- Payment service - Enter the name of the payment service to configure, e.g. "MPG". The chosen name is for indication purposes only.
- Payment connector - Select the MAX Pay Connector of your choice.
- On the Setup tab, continue to enter the following information.
|
Field |
Description |
Sample value |
|
Test mode |
When using a MAX Pay Global connector, in Test or Production, you should set this field to false. |
False |
|
Default processor for credit cards |
Specify whether this payment provider should be the default processor that's used for new credit cards. |
Yes |
|
Bypass payment processor for zero transaction |
Specify whether this payment provider should be skipped for transactions that have a 0 (zero) amount. |
Yes |
|
Override Merchant specific payment properties |
Specify whether this payment provider is enabled and configured to merge payment provider properties from an external source. Unless otherwise specified and documented, set this field to No |
No |
- On the Payment service account tab, enter the following information.
|
Field |
Description |
Req’d |
Auto set |
Sample value |
|
Assembly name |
Auto populated name of the assembly for the Dynamics 365 Payment Connector. |
Yes |
Yes |
RR.Dynamics.Retail.Payment.ProviderName.Portable, |
|
Assembly version |
The version of the assembly files |
Yes |
Yes |
3.2.0.0 |
|
File version |
This is Retail Realm's version number for the MAX Pay Global assemblies. This is variant of the version of Dynamics 365 Commerce version and the Retail Realm build number. e.g. 100.319.20010.32091 100.319.20010.32091 - these are referencing the Dynamics Commerce SDK version the assemblies were built against. 100.319.20010.32091 is the application version of MAX Pay Global (3.2.091) |
Yes |
Yes |
100.319.20010.32091 |
|
Serial number |
This field displays the License Serial number for the Payment services channel. |
Yes |
No |
E95XACFYKNF96C19C9APAK55K |
|
Copyright |
Copyright notice. |
Yes |
Yes |
Copyright © Retail Realm Distribution |
|
Connector name |
The name of the connector |
Yes |
Yes |
|
|
Service account id |
Auto populated unique identifier for the setup of the merchant properties. This identifier is stamped on payment transactions and identifies the merchant properties that downstream processes (such as invoicing) should use. |
Yes |
Yes |
Guid |
|
Provider id |
Do not overwrite. A default value is provided |
Yes |
Yes |
|
|
Supported currencies |
Currencies that are used within the payment connector |
Yes |
Yes |
USD;AUD;BRL;CAD;CHF;CNY;CZK;DKK;EUR;GBP;HKD;HUF;INR; |
|
Supported tender types |
This parameter lists each Electronic payment type separated by a semi-colon (see Payment services – Finishing up). This field is editable. |
Yes |
Yes |
AMEXPRESS;DISCOVER;GIFTCARD;MAESTRO;MASTER;VISA |
Note - care must be taken when deleting a Payment service profile. Any sales orders that reference a payment services profile will not be able to process payments, even if the profile is re-created.
Now, complete the remaining fields on the Payment service account tab.
These are specific to each Payment provider. Choose the appropriate link below for your Provider:
Payment services account - Braintree
Payment services account - CardConnect
Payment services account - Cybersource
Payment services account - Heartland
Payment services account - NMI
Payment services account - Payment Logistics
Payment services account - Shift4
Payment services account - Worldpay Express
Payment services account - Worldpay UK
Recommended content
|
Microsoft | Credit card setup, authorization, and capture This article provides an overview of credit card authorization in Microsoft Dynamics 365 Finance. It includes information about how to set up a payment service, add a credit card to a sales order, and void an authorization. |
|
Microsoft | Setup the Credit card payment service This Microsoft Learn article provides suplementary background information on how to configure Payment services. |
|
Microsoft | Accounts receivable home page This Microsoft Learn article provides navigation to a range of topics to assist your learning on how the standard Microsoft functionality applies to Credit card and other electronic payments that dictate how MAX Pay Global functions. |