Configure the payment workflow

Check that the JDD service user has Internet access

The JDD service user is the user that runs the "Print Job Data Dispatcher" service. It is recommended that you change the user only when:

1. The user has a local system account. And

2. You want to use the file hosting services and/or the payment providers. The user must have Internet access.

A number of services will be restarted when the user is changed. Orders that are being submitted by customers will become corrupt. The following services will be restarted:

• The Message Queuing service

• The Print Job Data Dispatcher service

1. Click [System] - [Services settings] - [Advanced infrastructure].

2. The read-only text box displays the current JDD service user. Click [Test connection] to test if the user has Internet access.

   You can change the user:

   1. Click the [Change] button.

   2. Select the domain and user name. For example, you can select the user that runs the services of PRISMAdirect. The user must have Internet access if you want to use the file hosting services and/or the payment providers.

      Type the password. Letters in passwords must be typed using the correct case.

      

   3. Click button [OK] and click [Test connection] to test if the user has Internet access.

      

   4. Click [OK].

3. Click [Save].

Select the payment providers for PRISMAdirect

1. Click [System] - [Connectivity] - [Payment providers].

2. Enable option [Use payment providers] to enable payment for PRISMAdirect.

3. Select which payment providers will be available for PRISMAdirect.

   

4. Configure the credentials for the SQL server. The application creates a payment report per payment provider and stores them on the SQL server.

   The same SQL server is used for the accounting workflow, see [System] - [Accounting and reporting] - [Accounting] - [Accounting workflow]. When you change the settings for the SQL server in that dialogue, the settings will also change in this dialogue and vice versa.

   1. Define the [Computer name \ instance name:].

      With this option, you define where the payment reports are stored. For example: SQL_server_name\SQL_server_instance_name.

   2. You have to define how the [Order processing] connects to the SQL server. The authentication type depends on the location of the SQL server:

      Location of the SQL server	Description
      Local SQL server	SQL authentication (recommended) Type the account credentials of an existing login account for the SQL server.
      Remote SQL server inside the domain	Windows authentication (recommended) The Windows user credentials are used for the authentication. The user is not prompted for a user name and password.
      SQL server outside the domain	SQL authentication (mandatory) Type the account credentials as defined by the customer for the SQL server.

   3. Type the password of user sa. You have defined the password for user sa when you installed PRISMAdirect.

      Accounting information can be collected when the user has system administration rights on the accounting database.

   4. [Test connection]

      Click this button to test the connection to the SQL server.

5. Click [Save].

Configure the payment providers per web server

You have to configure the [Payment providers] for each web server.

1. Click [System] - [Web submission] - <web server> - [Payment providers].

2. Option [Use payment providers]

   • Enabled

     You can enable one or more payment providers for the concerning web server. For example: PayPal.

   • Disabled

     For example, your company uses a local area network. You can disable the payment providers in this dialogue since your Web server has no Internet access. The customer does not receive an "unable to connect" message from the payment provider.

3. Configure each payment provider.

   Click on the bar of the payment provider that you want to configure. For example: PayPal. The bar expands and you can fill in the required settings. Each payment provider delivers the required settings to you when you create a merchant account.

   

4. Click [Save].

Enable payment per web shop

1. Click [Web shop] - <web shop> - [Pricing] - [Payment].

2. Enable option [Enable payment]. Customers have to pay their orders before they can submit their orders via the web shop. The payment providers as defined for the web server are available for the customers.

   You can customise this setting for one or more user groups. See procedure Optionally, you can customise the payment settings per user group.

   

3. Click [Save].

Optionally, you can customise the payment settings per user group

1. Click [User management] - [User groups] - [User group settings].

2. Click on the bar of the user group that you want to customise. The user group expands.

3. Scroll to section [Enable payment].

4. A customer can be part of a user group. The settings of the user group overwrite the payment settings of each web shop.

   • Web shop

     The user group uses the value of setting [Enable payment] as defined for the web shop.

   • Custom = Yes

     Payment is enabled for each web shop for the concerning user group. A requirement is that the payment providers are configured, see procedure Configure the payment providers per web server.

   • Custom = No

     Payment is disabled for each web shop for the concerning user group.

   

5. Click [Save].