1Introduction

This manual describes the installation, the configuration and the usage of the payment module for e-Commerce and DocData.

Before you can start with the installation please make sure that you hold all the necessary data. You need:

• DocData Merchant Name
• DocData Merchant Password
• e-Commerce Payment module from sellxed.com/shop
• Login data to your server and shop

Note that you must use at least PHP version 5.6 for our plugins. PHP 8 or higher is currently not supported.

1.1Procedure of the installation

With this document you'll get all the information you need for the installation of the module. For the implementation of the module you should follow the checklist strickly. Only like that you can ensure a safe usage in accordance to all security regulations.

1. Configuration of the DocData Settings
2. Configuration of the main module
3. Configuration of all the accepted Payment method with the authorization methods included
4. Process a test order
5. Activation of yourDocData account

2Configuration DocData - Backend

You'll find an overview about transactions and settings in the backend from DocData:

• Test environment: https://test.docdatapayments.com/ps/com.tripledeal.paymentservice.backoffice.Login
• Live environment: https://backoffice.docdatapayments.com/ps/com.tripledeal.paymentservice.backoffice.Login

2.1Configuration of the main module

Fill the merchant name and merchant password in the main configuration of the module You can there additionally choose a default. The default CSS matches the deposited standard CSS configuration in DocData. You can overwrite these setiings in theconfiguration of the payment method.

Choose if you want to process the payments in live or test mode.

2.2Configuration of the payment methods

You can undertake various adjustments for each payment method.

Please keep in mind that in case you want to use the Payment Method Bank Transfer or Open Invoice (Klarna and AfterPay) you need to activate the feature extendedStatusRequests at DocData.

2.2.1CSS ID

Define for each payment method your CSS ID, which you have already set in the backend of DocData. You can define the CSS profile under Settings > Edit Look and Feel

Figure 2.1: Create CSS profiles under settings > Edit Look and Feel.

2.2.2Payment Profile

With the payment profile you can select a payment method for the payment page. To do so you need to create a profile for each payment method in the backend of DocData.

Under Edit > Payment method and names you can create profiles and assign to every profile a payment method. Fill in the name of the profile into the configuration of the payment method. This results in the pre selected display of this payment method.

Figure 2.1: Creation of payment profiles to select the payment method under Edit > Payment method and names.

You'll find more information to the configuration of the payment methods and the significance of the particular settingshere.

2.3Activation of the Cron Jobs

Since the DocData doesn't send notification answers it can happen that the customer closes the window before finishing the transaction. In this case we recommend to install Cron Jobs in your shop. Further information you'll find in the chapterCron Job

2.4Testing and Activation of the Module

After the activation and configuration of the payment methods, test your module with the test datayou find in the manual. If the tests were successful, switch to Live in your main module.

3Module Installation and Update in the e-Commerce Shop

3.1Installation

At this time you should already be in possession of the module. Should this not be the case, you can download the necessary files in your customer account in the sellxed shop (Menu "My Downloads Downloads"). In order to install the module in your shop, please carry out the following steps:

1. Download the plugin. The download can be found in your sellxed.com account under "My Downloads".
2. Unzip the archive you have just downloaded.
3. In the unzipped folder navigate to the folder "files"
4. For some shops there are different versions of the plugin provided. If this is the case open the folder which corresponds to your shop version.
5. Using your preferred FTP client upload entire content of this folder into the root directory of your shop. For some shops there is a specific folder containing the plugins. If that is the case upload the plugin into this folder. Make sure that the folders aren't replaced but merely merged.
6. If you haven't yet done so, log back into your shop.

3.2Updates and Upgrades

You have direct and unlimited access to updates and upgrades during the duration of your support contract. In order to receive constant information about available updates we ask you to subscribe to our RSS feed that we publish for your module.

More information regarding the subscription of this RSS feed can be found under: http://www.sellxed.com/en/updates_upgrades.

We only recommend an update if something doesn't work in your shop, if you want to use new feature or if there is a necessary security update.

3.2.1Update Checklist

We ask you to strictly comply with the checklist below when doing an update:

1. Always do a backup for your database and your files in your shop
2. Use always a test system to test the update process.
3. Wait until all the files are copied to the shop, clear the cache if there is one in your shop and then visit the configuration page of the main module so that the update process will be initialized.

Depending on the version it could be that the database has to be migrated. We recommend you therefore, to perform the updates in times when the shop is not visited too frequently by your customers.

3.2.2Update Instructions

Please always read the update instruction. Those instructions can be found in the changelog. If there are no special remarks, you can proceed by just overwriting the files in your system.

4Module Configuration in the e-Commerce Shop

The configuration consists of two steps. The first step is the configuration of the main module with all the basic settings (cf. Configuration of the Main Module). During the second step you can then carry out individual configurations for each payment method . This allows for full flexibility and perfect adaptation to your processes.

4.1Basic Module Configuration

Activate the plugin by selecting the module E-commerce DocData in the Plugin menu.

The settings for the basic module can be found at DocData > DocData . Fill out the fields, you should have already entered the necessary data in the DocData backend or you received it as part of your correspondence with DocData. Each option is explained in more detail in a short info text in the shop.

4.2Payment Method Configuration

After the basic module has been configured successfully, you can proceed to the payment settings. The payment methods you want to accept in your shop can be adjusted at Settings > Store > Payments . Every payment method is listed individually. Activate the payment methods you would like to provide in your shop by ticking the corresponding boxes on the right side. Individual changes can be made for each payment method to adjust it to your processes.

4.3Direct Capturing of Transactions

The option "Capture" allows you to specify if you wish to debit payments directly or if you first wish to authorise them and then debit the payment at a later point.

Depending on your acquiring contract, a reservation is only guaranteed for a specific period of time. Should you fail to debit the payment within that period, the authorisation may therefore no longer be guaranteed. Further information on this process can be found below.

4.4Uncertain Status

You can specifically label orders for which the money is not guaranteed to be received. This allows you to manually control the order before shipment.

4.4.1Setting the order state

For each payment method you may select in which state the order should be set to depending on the booking state. This is the initial state of the order.

4.5Optional: Validation

Note: It can be that this option is not visible in your module. In this case just ignore this section.

With the option 'Validation' you can define the moment when the payment method should be made visible to the customer during the checkout process. This setting is relevant for modules where the usage depends on the customer's compliance with specific preconditions. For example, if a solvency check has to be carried out or if the payment method is only available in certain countries. In order for the credit check or address validation to also work with European characters, the charset of the "Blowfish mode" must be set to "UTF-8" for certain PSP settings.

You have the choice between these options:

• Validation before the selection of the payment method: A validation verification is carried out before the customer selects the payment method. If the customer does not fulfill the requirements, the payment method is not displayed
• Validation after selection of the payment method: The verification of the compliance occurs after the selection of the payment method and before the confirmation of the order
• During the authorisation: The validation verification is carried out by DocData during the authorisation process. The payment method is displayed in any case

5Settings / Configuration of Payment Methods

5.1General Information About the Payment Methods

The plugin contains the most common payment methods. In case a desired payment method is not included per default, please contact us directly.

In order to be able to use a payment method, it must be activated in your account with DocData as well as in your shop. Information about the configuration of the payment methods can be found further above.

Below you can find important information for specific payment methods that deviate from the standard process.

5.2Information on Payment Status

For each payment method you can define an initial payment status (status for authorized payments etc.). You hereby define the payment status for each state depending on the processing type of the order (captured, authorized, etc.). It's the initial status which the order assumes. Depending on the mutation carried out by you, the status can change.

5.2.1Order status "pending" / imminent payment (or similar)

Orders with the status 'pending DocData' are pending orders. Orders are set to that status if a customer is redirected in order to pay but hasn't returned successfully or the feedback hasn't reached your shop yet (Customer closed window on the payment page and didn't complete payment). Depending on the payment method these orders will automatically be transformed into cancelled orders and the inventory will be cleared (so long as the Cronjob is activated). How long this takes depends on the characteristics of the payment method and cannot be configured.

If you have a lot of pending orders it usually means that the notifications from your webserver to DocData are being blocked. In this case check the settings of your firewall and ask the Hoster to activate the IPs and User Agents of DocData.

5.2.2Order status "cancelled"

Orders with the status "cancelled" have either been set to that status automatically due to a timeout, as described above, or have been cancelled directly by the customer.

6The Module in Action

Below you will find an overview of the most important features in the daily usage of the DocData module.

6.1Useful Information on Transactions

For each order processed with our module you can access an overview of the most important transaction information. Among other things, this allows you to identify each corresponding order to each transaction displayed in the backend.

You can find the orders at Dashboard > Store Sales.

Figure 6.1: Transaction information in WordPress E-Commerce.

6.2Capture / Cancel Orders

6.2.1Capturing and Cancelling Orders

In order to capture orders, open the order first (Dashboard > Store Sales) and then open the transaction information. Enter the amount you want to capture into the input field. By clicking on Capture the card is charged directly.

An order can be cancelled by clicking "Cancel Transaction" and the transaction as well as the reserved amount is released on the customer's card immediately.

Figure 6.1: Cancelling and capturing orders

6.3Order Refunds

In order to refund an order, open the transaction information (see above).

You can refund individual items or an arbitrary amount by adjusting the total amount or the number of items.

Figure 6.1: Refunds in WooCommerce for DocData.

6.4Transaction History

Every action within the transaction management is processed through the module. Information on each transaction can be viewed in the corresponding order.

Figure 6.1: Transaction overview in the transaction history.

6.5Using Invoice Details of a Processor

In the following context you can view or embed the "payment details" of for example an "Open Invoice" transaction:

6.5.1e-Commerce Order Confirmation (E-Mail)

The "payment information" will be visible in the default "order confirmation e-mail" of e-Commerce.

6.5.2e-Commerce Invoice (PDF)

The "payment information" will be visible in the default e-Commerce-Invoice.

6.5.3e-Commerce-Backend (Transaction details)

Figure 6.1: Transaction details within e-Commerce.

6.5.4e-Commerce Success-Page

Figure 6.1: Payment information on the e-Commerce "Success-Page".

6.6Cron Job Setup

In order to activate the time-controlled plugin functions (e.g. update service, deleting pending orders etc.) you have to set up cron jobs in e-Commerce. The update function is especially relevant - it allows you to fetch subsequent transaction changes at DocData via the API. Please keep in mind that additional options might have to be activated.

The module uses the default e-Commerce cron. Information on the setup can be found here.

7Testing

Before switching from test to live mode it is important that you test the module extensively.

7.1Test Data

8Errors and their Solutions

You can find detailed information under http://www.sellxed.com/en/faq. Should you not be able to solve your problem with the provided information, please contact us directly under: http://www.sellxed.com/en/support

8.1The Referrer URL appears in my Analytics Tool

When a customer and the notification are redirected via Header Redirection, the DocData Referrer URL might appear in your Analytics Tool thus hiding the original traffic source. However, most Analytic Tools are able to minimize this problem.

In case you are using Google Analytics as reporting tool, this step by step guide may help you to exclude the URLs: under bullet point 4.

9Error Logging

The module will log different unexpected errors or information depending on the configured level. If there is any issue with the module, this log can help identify the cause.

9.1Log Levels

You can configure the log level in the DocData settings.

• Error: Logs unexpected errors only. (Default)
• Info: Logs extended information.
• Debug: Logs information helpful for debugging.

9.2Log Location

The log file is stored in the logs folder of this plugin wp-content/plugins/plugins/ecommerce_docdatacw/logs. Please make sure the path exists and it is writable by the webserver.

10Advanced Information

This section of the manual is for advanced usage of the module. The content is for advanced users with special requirements. Everything in this section is optional and not required for the daily usage of the module.

10.1Transaction Object

This section describes how to extract information from a transaction, if you need it for further processing. E.g. you require more information of the transaction for further processing an order in your ERP system.

The code snippets in this section assume your script resides in the root folder of the shop with the default shop folder structure.

require_once( dirname(__FILE__) . '/wp-load.php' );

require_once ABSPATH.'wp-content/plugins/ecommerce_docdatacw/classes/DocDataCw/Util.php';

$transactionById = DocDataCw_Util::getTransactionById($transactionId);
$transactionObject = $transactionById->getTransactionObject();

$transactionByExternal = DocDataCw_Util::getTransactionByExternalId($externalId);
$transactionObject = $transactionByExternal->getTransactionObject();

$transactionsByOrder = DocDataCw_Util::getTransactionsByOrderId($orderId);
foreach($transactionsByOrder as $transaction){
	$transactionObject = $transaction->getTransactionObject();
	//Do something with each object
}