The fields required to allow real-time processing of credit card authorizations and settlements (including High Availability Fallback transactions) with all major credit cards with your credit card processor 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 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, JPY900, PD900, JPD900, etc).

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 1SCC or 1SCR.

Currency Code – (required when currency is turned on within your environment) currency code column may not appear if currency is off within your environment.  Field represents currency associated to merchant account.  Each merchant account may only have one currency associated to it.  Definition of currency associated to merchant account is done at moment of merchant account setup within gateway.

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. CREDITCARD_7_0_0)

Processor Level – (required) for 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.

The Provider Settings Form Exit is used 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: DV920, PY920, PD920.

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

API Path - (required) specify the path where the libcurl library is installed and located on the JDE Enterprise server (e.g. C:\curl7.50.3\libcurl.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]/Services/PaymentProcessingService.asmx)

The CC Processor exit is used to define which processors will be considered for Credit Card Reconciliation.  Reconciliation is available for PayPal merchants when the following are defined:

Connection Name - (required) an entry for each connection that will be reconciled

Card Type - each card type that will be considered for reconciliation

Processor Name - the processor name exactly as it appears in the merchant account 

Max Lines - the maximum number of detail lines that may be passed (as per your processor) when processing level 3.  The details of each line will be passed until the Max is reached.  Then, all remaining lines will be summarized into one line and passed.

Bank ID - a unique identifier for reconciliation (for example 001)

Date Transaction - Initially the date to being pulling reconciliation date from the gateway.  This date is updated automatically each time the reconciliation process runs.

Time Transaction - Initially the time to being pulling reconciliation date from the gateway.  This time is updated automatically each time the reconciliation process runs.

The CC Group Key form exit is used to define a grouping of connections. Typically when a new credit card is entered and stored as a credit card on file the PN Reference is stored for later use.  However, the Payflow™ processor which was used to obtain the PN Reference is not stored. Thus if your company utilizes multiple Payflow™ processors you may encounter an issue when the processor being used for the current transaction is not the same processor used to obtain the credit card on file PN Reference.  This is because PN Reference numbers are not shared across Payflow™ processors. To alleviate this issue you may create a Connection Group here.  Please note your merchant accounts must be "cross-vid" before the connection group will work.  

Connection Name - (required) an entry for each connection that will be added to a group

Credit Card Group Key - (required) The name of the group

API Secure Token information is required to submit valid transactions to PPC from and trusted source. This can be defined on PQ67SYS1 using the API Auth form exit with the following options:

Provider Name - (required) module configuration description. (e.g. CREDITCARD_7_0_0)

Environment – (required) specify the EnterpriseOne™ environment name to be used for the connection. Ex: DV920, PY920, PD920.

API Token – (required) specify the API Token generated by Payment Processing Console.