Knowledge Base

Welcome to the SmarterCommerce documentation portal

What can we help you find?

SMARTERCOMMERCE

Search and Learn about Unified Commerce and Our SmarterCommerce Solutions
Payment Processing

PayPal® Express Checkout Connection Settings


The fields required allowing real-time processing of credit card authorizations and settlements with all major credit cards with your credit card processor (PayPal® Payflow™) are set within the credit card processor integration application (PQ67SYS1.) 

The following fields are marked as required for integration with your credit card processor: 

Business unit – may be left blank as the system default.  If a specific merchant ID is required by business unit then setup a specific record per business unit of the sales order header.

Environment – (required) specify the EnterpriseOne environment name to be used for the connection (e.g. PY900, PD900).


Payment Instrument – (required) indicates various methods of payment such as credit card or check.  Values used here must match payment instruments assigned special handling code value of 1SCP.

Currency Code – (required when currency is turned on within your environment) currency code column may not appear if the currency is off within your environment.  The field represents currency associated to the PayPal® Payflow™ account.  Each Payflow™ account may only have one currency associated to it.  Definition of currency associated with Payflow™ account is done at the moment of merchant account setup within PayPal®.

Connection Name – (required) a name defined by the company that describes the purpose of the connection (e.g. PayPal® Testing – used for test transactions)

Provider Name – module configuration description. (e.g. PAYPALPAYMENTS_7_0_0)

Processor Level – (required) PayPal® Payflow™ payment services supports passing purchasing card level 2 information (such as purchase order number, tax amount, and general charge description) and purchasing card level 3 information (sales order and line items details) in the settlement file.  Valid options are: 


     1   Basic credit card processing 

     2   Purchasing card level 2 processing 

     3   Purchasing card level 3 processing

Data Item – field represents address book category code to be utilized as an override to the default processor level found in the processor level field as discussed above.  To override the default processor level by customer, place the appropriate address book user defined code alias (AC01 – AC30) in this field.  This will represent the processor level override address book category code.  Then select the address book category code value within the address book representing the override processor level. 

 

Additionally, from the PQ67SYS1 application take the Provider Settings Form Exit to define the following fields required for each credit card processing server which will be utilized:  

Server Name - (required) an entry needs to be created for each credit card processing server which is configured.  If live and test transactions will run from the same server then multiple entries will be needed. 

Environment – (required) specify the EnterpriseOne™ environment name to be used for the connection. Ex: DV900, PY900, PD900.

Provider Name - module configuration description. (e.g. PAYPALPAYMENTS_7_0_0)

API Path - (required) specify the path where Credit Card Interop.dll is installed and located on the credit card processing server (e.g. d:\\SmarterCommerce\\Premier.Payments.Interop\\SCAPICC40.dll.) Your system administrator can provide this information .

URL path - (required) specify the URL where the web service is installed. (https://[Windows Application Server]/[Virtual Directory] / PaymentProcessingService.asmx)

Bring It All Together

We bring together digital commerce, retail and call center channels with a united approach that leverages the power of onmi-channel while prioritizing JD Edwards connectivity.

CONNECT WITH AN EXPERT