Description: The following procedure will help you set up Payment Services for Shift4 Payment Connector.
When adding the new payment service, the Shift4 Connector will be available from the Connector dropdown in the back office. Most fields under the Payment service account can be left with their default values.
The Connector Version will auto-populate to ‘UTGCONTROLLED’ (UTG Server-to-Server Tokenization), therefore if you would like to use i4Go, this will need to be changed to ‘I4GOCONTROLLED’ (i4Go iFrame Tokenization). Additionally, the PaymentAcceptPageURL will need to be changed to your environment path (Backoffice URL), with additional sub-directories to denote the connector version you’re using. It should look something like this https://{Your Environment}.cloudax.dynamics.com/{I4Go or UTG Sub-directories} (See Table 1 for more details).
The Shift4 Connector Payment service is also used by the Channel Payment Parameters form, which is a custom page created for the connector to perform access token exchanges. This form requires that all steps below be completed in order for it to identify the gateway endpoints being used to perform the token exchange.
- Navigate to Modules > Accounts Receivable > Payments setup > Payment services.
- Select New to create a new Payment service account for the Shift4Connector.
- If one already exists, choose that instead and skip to Step 7 to configure its settings.
- Under Payment Service, enter a unique name(i.e., ‘Shift4’).
- Select the Shift4Connector from the Payment connector dropdown.
- Make sure that all Electronic Payment types are assigned to a journal for your environment; in the example below, we are using Customer Payment. Once done, select Save.
- Select the X button at the top-right of the Electronic payment types screen to navigate back to the Payment services and set the "Default processor for new credit cards" toggle to Yes.
- Fill in the Payment service account section according to Table 1. Once done, select Save.
Table 1: Payment service account fields
| Field | Description | Value |
| Assembly Name | Auto populated the name of the assembly for the Dynamics 365 Payment Connector for Shift4. | Default value of “Shift4.Payment.Connector.Portable, Version={ConnectorVersion}, Culture=neutral, PublicKeyToken=null” |
| Service account ID | This identifier is stamped on payment transactions and identifies the merchant properties that downstream processes (such as invoicing) should use. This can be set to any Alpha/numeric value though we strongly suggest using the Shift4 MID for ease of use. |
Important: Do not change this value if merchant already began processing payments with it as sales orders will record this data for reference in the future such as voids and linked refunds |
| Merchant ID | Values used by the end-users to identify the Merchant Account this payment service should be tied to. This field is not used by the Payment Connector to identify the account; only the Access Token is. | The default value is a random GUID, should not be changed after creation of connector instance |
| TestEnvironmentUrl | The UAT Gateway endpoint for REST. | Default value of "utgapi.shift4test.com" |
| ProdEnvironmentUrl | The Prod Gateway endpoint for REST. | Default value of "utg.shift4api.net" |
| Supported Currencies | Currencies that the connector should process. | Default value of "USD" |
| Support Tender Types | Enter the tender types that the connector should process. | Default value of "Visa;MasterCard;Amex;Discover;Debit;GiftCard" |
| InferfaceVersion | The version that shows up in LTM Audit Trail as the source. | Default value of "1.0" |
| InterfaceName | The interface name that shows up in LTM Audit Trail as the source. | Default value of "Microsoft Dynamics 365" |
| Host IP | IP Address of the UTG (not applicable for Call Center). | Default value of "127.0.0.1" |
| Host PORT | Port Address of the UTG (not applicable for Call Center). | Default value of "277" |
| CompanyName | The company name that shows up in LTM Audit Trail as the source. | Default value of "Amicis Solutions" |
| CardTypeMappings | Used to map the card types in D365 to their respective types on the connector. |
Ensure this is set to AMEXPRESS=AX;DISCOVER=NS;GIFTCARD=GC; MASTER=MC;VISA=VS;DEBIT=DB;EXTGC=YC |
| Connector Version | Determines which Payment Connector type you will use (I4GO or UTG Controlled). |
UTGCONTROLLED for SRED (Default) For UTG Server-to-Server Tokenization method I4GOCONTROLLED for SRED with i4go For i4GO iFrame Tokenization Method |
| ImmediateCapture | If true, the authorization will be captured immediately as the order is submitted. If this is set to False, the authorization happens when the order is submitted and captured once invoiced. | True (Default) or False |
| API Options | Used to modify the request being made to the Gateway. Multiple API Options can be configured separated by semi-colons with no spaces. See the API Options section for more information. | Default value of "ALLOWPARTIALAUTH;RETURNEXPDATE;DISABLEMCE" |
| SupportCardTokenizations | True (Default) or False | |
| PaymentAcceptPageUrl | The URL where the payment connector parameters are hosted. |
For SRED with UTG Controlled (Default) {Backoffice environment URL}/Resources/Html/CardPage.html For SRED with I4GO Controlled {Backoffice environment URL}/Resources/Html/Shift4CardPage.html |
| I4GOUrl | The UAT/Prod Gateway endpoint for i4Go. |
This will need to be set accordingly based on the environment being used for this payment connector. For Certify/UAT For Production |
| IsCvvOptional | Requires CVV to be provided in order to authorize the transaction in D365. | True (Default) or False |
| Environment | Test/Prod |
Test - For Shift4 UAT environments (Default) Prod - For Shift4 production environments |
| TerminalType | Default value of "UTG" | |
| ConnectionTimeout | Default value set to 120000 | |
| Access Token | The {Access Token} | |
| AppInsightInstrumentationKey | Can be used for logging Requests/Responses from D365 using Application Insights in Azure. | Optional. Used for debugging in test/UAT. Not recommended for Prod. Refer to the Application Insights overview to find out more. |
| UseDefaultAdressForPayment | When this option is set to True, it will allow the payment connector to use the billing address on the customer profile to use for AVS. | True (Default) or False |
- At the bottom of the page, you will see options to configure AVS and CVV settings. These are Microsoft enabled prompts and can be enabled or disabled based on your business necessities.
Note: We recommend keeping these settings off as this data can also be captured from the IDTech device. AVS is also done using the Customer’s address on file when the UseDefaultAdressForPayments feature in the payment connector is enabled.
Comments
0 comments
Please sign in to leave a comment.