Add the Shift4 Connector to eCommerce Channel for Dynamics 365

Description: The payment connector is also added to the online store from the Online stores form, and it is configured with minimal additional steps.

---

1. Navigate to Modules > Retail and Commerce > Channels > Online Stores.
2. Scroll to Payment accounts, select + Add, then choose the Shift4Connector option from the drop-down menu.

3. Set the Default processor for new credit cards toggle to Yes.
4. Fill in the Payment service account section according to Table 1 section below.

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 provided
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.	Default value provided
TestEnvironmentUrl	The UAT Gateway endpoint for REST.	Default value provided
ProdEnvironmentUrl	The Prod Gateway endpoint for REST.	Default value provided
Supported Currencies	Currencies that the connector should process.	Default value provided
Support Tender Types	Enter the tender types that the connector should process.	Default value provided
InferfaceVersion	The version that shows up in LTM Audit Trail as the source.	Default value provided
InterfaceName	The interface name that shows up in LTM Audit Trail as the source.	Default value provided
Host IP	IP Address of the UTG (not applicable for Call Center).	Default value provided
Host PORT	Port Address of the UTG (not applicable for Call Center).	Default value provided
CompanyName	The company name that shows up in LTM Audit Trail as the source.	Default value provided
CardTypeMappings	Used to map the card types in D365 to their respective types on the connector.	Default value of 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).	Default value provided
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 provided
SupportCardTokenizations		True (Default) or False
PaymentAcceptPageUrl	The URL where the payment connector parameters are hosted.	Default value provided
I4GOUrl	The UAT/Prod Gateway endpoint for i4Go.	Default value provided
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 provided
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. Not recommended for Prod.
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

5. Once finished, select Save, and proceed to apply these changes to the eCommerce module by following these steps for Distribution Schedule jobs.