1Introduction

This manual describes the installation, the configuration and the use of the payment module forOXID and giropay / paydirekt.

Before you begin with the installation make sure you have all the necessary data:

• You need an Owner Account for giropay / paydirekt for the Sandbox and / or the Live Account. You will receive this account directly from giropay / paydirekt.
• You need thegiropay / paydirekt payment module from www.sellxed.com/shop.

In case you don't have a contract with giropay / paydirekt yet, we will gladly provide you with one.

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

1.1Installation Procedure

This document provides you with all the necessary information regarding the installation of the module. You should follow the steps of the checklist carefully during the startup procedure. Only by doing so, the safe use in compliance with all the safety regulations can be ensured..

1. Configuration of the Sandbox and creating the technical accounts.
2. Configuration of the payment methods and the basic settings.
3. Carrying out a test order by means of the enclosed Test data at the end of this document.

1.2System Requirements

• PHP Version: 5.4.x or higher
• OpenSSL: Current version with support for TLS 1.2 or higher.
• fsockopen: The PHP function fsockopen must be enabled. The plugin must be able to connect to external systems over the Internet.
• PHP Functions: All common PHP functions must be enabled.

2Configuration giropay / paydirekt

2.1Sandbox and Live Platform for the Administration

You will find the administration and the display of the transactions, depending on the operating mode, via the following links. You need the Sandbox for the test payments.

• Sandbox:https://sandbox.paydirekt.de/merchant/.
• Live-Platform:https://www.paydirekt.de/merchant/.

2.2Configuration of the API Keys

If the test was successful repeat these steps for the live platform.

2.2.1Creating a Technical User

Log in at https://sandbox.paydirekt.de/merchant/ with the received access data. At Settings > User Administration you can add a new user or change existing rights. Add a new user or make sure that your Owner Account contains the functions Reporting, Reverse Transaction, Technician

To make the changes effective you need to log out and in again.

Figure 2.1: Edit the user role (icon).

2.2.2Generating API Keys and Secrets

When you log in you will find the API Keys under "Settings". Here you can generate a new API Key and a Secret Key. The API Key and the Secret Key will be shown to you once. Transfer the data directly into the main module.

Figure 2.1: Generating API Keys (Icon).

2.2.3Logo

Under Settings you can also upload your logo. The logo will be displayed in the e-mails and during the payment transaction.

2.2.4Transaction List

You now have access to the transactions on your home page. Please note that failed transactions won't be listed in the transaction list. You can also refund transactions from here. We recommend you don't do so via your shop though. Payments that you transfer back via the back end won't be synchronized with the shop and can't be refunded there anymore.

Figure 2.1: Transaction Overview

2.3Configuration of the Main Module

Navigate to the main module in your shop. Please fill in the following data into the corresponding sections:

• API Key (previously created by you)
• API Secret (previously created by you)

Save the data according to live or test mode.

2.4Activating the Payment Methods and Testing

Next you need to activate the payment method and run a test. Further information concerning the configuration of the payment methods and the meaning of each setting can be found here.

When you have activated the configuration of the payment methods you will run a test by means of the published test data in the manual. If all the tests were successful, switch the operating mode in the main module to Live.

3Module Installation and Update in the OXID 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 OXID 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.1Configuration of the Main Module

The settings for the main module can be found under Extensions > Module . Install the module by clicking Activate.

By clicking on the tab Settings you get to the configuration of the main module. Fill in the boxes by using the data that you have received from giropay / paydirekt and may have already saved in the backend of giropay / paydirekt. Each option is additionally explained in a short info text in the shop.

4.1.1Settings

4.1.1.1Update interval for payments

Payments may be updated periodically (interval in minutes). To use this feature you have to setup a cron job.

4.1.1.2Order Creation

Choose when the order should be created. If set to 'Before Payment', orders are created in any case. If set to 'After Payment', an order is created only if the payment is successful.

4.1.1.3Order ID

Use this setting to enforce the behaviour of unique order IDs, even if they are not.

4.1.1.4Delete Orders on Failure

Set to yes to delete the order when the authorization fails. Otherwise the internal order status is set to 'PAYMENT_FAILED'.

4.1.1.5Logging Level

Messages of this or a higher level will be logged.

4.1.2OXID 6 Installation

After uploading the plugin via S/FTP, log into your server via SSH and navigate to the root folder of OXID. In this directory, run the following commands so the plugin is available in the backend:

command vendor/console/bin oe:module:install-configuration source/modules/customweb/paydirektcw/

php vendor/bin/oe-console oe:module:activate paydirektcw

php vendor/bin/oe-console oe:module:apply-configuration

4.2Configuration of the Payment Module

After having successfully configured the main module, you can find the settings for the individual payment methods in your shop under Shop Settings > Payment Methods . Each method is listed individually.

Install the payment methods you wish to offer your customers. Open the payment method and tick the box next to Active.

By clicking on giropay / paydirekt Configuration, you can save different settings for each payment method and thereby optimally adapt the payment methods to your existing 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 giropay / paydirekt 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 giropay / paydirekt 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 giropay / paydirekt' 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 giropay / paydirekt are being blocked. In this case check the settings of your firewall and ask the Hoster to activate the IPs and User Agents of giropay / paydirekt.

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 giropay / paydirekt module.

6.1Useful Transaction Information on the Order

In the tab giropay / paydirekt Transactions you can find an overview of the transaction information. Among others, this information allows for the definite attribution of the orders to their corresponding transaction, seen in the backend of giropay / paydirekt.

Figure 6.1: Transaction Information in OXID

6.2Capturing / Cancelling of Orders

Our module allow you to capture payments directly from within Oxid eSales without having to log into giropay / paydirekt.

6.2.1Capturing Orders

In order to capture orders, open the transaction tab (giropay / paydirekt Transactions). By clicking on the button Capture a new window will open up in which you can capture transactions.

You can now capture each item individually if you don't want to ship them all at once. The amount of possible partial captures depends on your contract. For more information on this, please contact giropay / paydirekt directly.

I you do not want to capture all items of an orders, click on 'Close transaction for further captures'.

Figure 6.1: Capturing of Orders in OXID eSales.

6.2.2Cancelling Orders

By clicking Cancel the transaction is cancelled and the amount reserved on the customer's card will be released immediately.

6.3Refunding Orders

In order to refund orders, open the transaction tab (giropay / paydirekt Transactions) and click on Refund. A new window will open up.

You can refund every item individually or any amount of your choice by modifying the total amount to pay or the amount of items.

Figure 6.1: Refunds in OXID eSales for giropay / paydirekt.

Executing a refund will not change the status of the order.

6.4Setup a Cron Job to Activate the Timed Operations

To activate the timed operations of the plugin (e.g. update service, deleting pending orders, etc.) make sure that you set up the OXID Cron engine. Especially the update function allows you to automatically retrive additional information or changes of your order directly via the API of giropay / paydirekt. Please note it could be that in order to use the update feature it may be necessary that giropay / paydirekt activates additional options in your account.

In order to use the timed operations, please schedule a cron job in your server to the following controller:

http://urltoyourstore.com/index.php?cl=paydirektcw_cron

Here we suggest you use a Cron Engine like for example EasyCron. That way you can This allows you to open the file ( URL ) with an external service.

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 giropay / paydirekt 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.

9Compatibility with Third-Party Plugins

The plugins listed below are compatible with our payment modules and allow you to handle certain tasks in an easier way.

9.1Birthday and gender in OXID

For certain payment service providers it is necessary to check the birthday and the gender of a customer. OXID does not check this by default. These checks can be enabled under "Settings > Other Settings > Mandatory fields in User Registration Form".

10Error 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.

10.1Log Levels

You can configure the log level in the giropay / paydirekt settings.

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

10.2Log Location

The log file is stored in the OXID log directory. Please make sure the folder and it is writable by the webserver. (Default Path: {shopRootDirectory}/logs/)

11Advanced 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.

11.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__) . "/bootstrap.php";

require_once 'modules/customweb/paydirektcw/classes/PayDirektCwHelper.php';

$transactionById = PayDirektCwHelper::loadTransaction(transactionId);
$transactionObject = $transactionById->getTransactionObject();