This manual explains the installation, configuration and usage of the payment module for JTL and Open Payment Platform.

Before beginning with the installation, please make sure that you are in possession of all necessary data:

  • User name and password for the log-in to the back-end of Open Payment Platform
  • JTL payment module by sellxed.com/shop
  • Access data to your server and shop

In case you don't yet have a contract with Open Payment Platform, you can acquire it directly through us.

1.1Installation Procedure

In this document you will find all information important for the installation of the module. It is important that you strictly follow the check-list. Only by doing so a secure usage in correspondence with all security regulations can be guaranteed.

  1. Configuration of the test environment by means of the integration data from Open Payment Platform. These can be found on the test platform under
  2. Configuration of the basic settings of the payment module
  3. Configuration of the payment methods
  4. Carrying out of a test purchase by means of the attached test data at the end of this document
  5. If the test was successful, you can configure the live data in your shop. Log into the live environment with the obtained access data under:
Installation Service

Our payment plugins should have per default the correct settings for most of our customers' preferences. That means once you have entered the required credentials in the plugin configuration to connect your account to your website, the plugin should be fully operational. Should you be willing to receive detailed informations on a setting you do not know, you may contact our support team who will be able to assist you further.

Our support team is at your disposal during regular business hours at: http://www.sellxed.com/support. Furthermore, you have the option of ordering our installation service. We will make sure the plugin is installed correctly in your shop: http://www.sellxed.com/shop/de/integration-und-installation.html

.htaccess Directory Protection

In order to test the module, any kind of directory protection or IP blocking on your server must be deactivated. This is crucial; otherwise the payment feedback of Open Payment Platform might not get through to the shop.


2.1Basic configuration of the main module

The access data for the test environment () is provided to you by Open Payment Platform.

Navigate to the main module in your Shop and fill in the following access data:

  • Authorization Bearer Token (Access Token)
  • Entity ID (CHANNEL ID )
  • The User ID and Password are depreacted and not required anymore, use the new Authorization Bearer Token instead.
  • You no longer need the parameter Security Sender and Security and Hash Secret for the integration. You can simply ignore this entry.
  • The boxes for "Security Hash" and "Security Hash Secret" can be left empty unless your Payment Service Provider instructs you to do otherwise
Figure 2.1: The Authorization Bearer Token in the Open Payment Platform backend.

You also have more entry options. For example the Custom Parameters. In principle you leave these blank unlessOpen Payment Platform requires you to do otherwise.

2.2Configuration of the Payment Methods

In order to activate the payment methods and to change other payment specific settings, navigate to the settings. (A description as to where to find these settings is listed here hier)

In the configuration of the payment methods you can define which Entity ID (Channel ID) should be used for which amount. This allows you to use a non-3D Secure Channel in case of small figures. In order for you to be able to set up and get the corresponding contract please contactOpen Payment Platform.

Figure 2.1: Configuration of the payment method using the example Magento (icon image, can differ from your version of the image).
PCI: New Authorization Method Widget

Please note that the use of the Hidden Mode comes with additional certification requirements (compare with our blog entry regarding this subject). For this reason we will no longer supply our new versions with the hidden mode. If you still use the hidden mode in you payment methods please solely use Widget. The support of the hidden mode will be terminated shortly.

2.3Configuration Webhook

In some special cases it may happen that the payment notification sent by Open Payment Platform can not be proceed by your JTL shop. We recommend to configure a so called webhook in the Open Payment Platform backen under Administration > Webbhook. Please make sure that you configure the correct URL which you can find in your JTL shop under Plugins > Plugins > Open Payment Platform > Erweiterte Informationen > Setup.

2.3.1Configuration Webhook by Merchant

If you have to configure the the webhook on your own, you can find the webhook URL in your JTL shop at Plugins > Plugins > Open Payment Platform > Erweiterte Informationen > Setup . Make sure you configure it in the Open Payment Platform Backend under Administration> Webbhook. Furthermore you have to define a so called "secret for encryption" key. Make sure that you also save the same values in the corresponding fields, as on the Picture below.

Customweb "secret for encryption" Generator

Please note that only ASCII characters may be used for the generation of this key pass phrases. Please use our "secret for encryption" generator so that you do not enter invalid characters.

Figure 2.1: Open Payment Platform Webhook configuration in the backend under Administration > Webbhook.

2.3.2Configuration Webhook by Open Payment Platform

In some Open Payment Platform accounts you can not configure the webhook by yourself. Therefor you have to provide the webhook URL to Open Payment Platform once they setup it for you, they will provide you a specific "secret for encryption" key, which you have to configure in the main module configuration of the module in your shop.

2.4Activation and Testing

When you have activated and configured the payment methods you can run a test with help from the manual Test data.

If the tests were successful you now switch the operation mode from test mode to "Live Mode" and replace the safety features above with your personal access data for the live platform. You will receive this data directly from your Payment Service Provider. Normally the USER ID etc. should be identical for the Live Mode.

3Module Installation and Update in the JTL Shop


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 download 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 shops 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 thats 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 back up 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.
Do not do updates directly in the live environment

Please test the update procedure first in your test shop. Our support team is able and willing to help you if you experience problems with the update process. However, if you decide to perform the update directly in your live shop there is the possibility of a downtime of the shop of more than two days depending on the availability of our support if you do not want to book our complementary support.

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. They can be found on the plugin page in the shop under the section change log on the lower end of the page. If there are no special remarks, you can proceed by just overwriting the files in your system

4Module Configuration in the JTL 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.

Create back-ups!

Please create a back-up of the main directory of your shop. In case of problems you will then always be able to return your shop to its original state.

We furthermore recommend testing the integration on a test system. Complications may arise with third party modules installed by you. In case of questions, our support is gladly at your disposal.

4.1Configuration of the Main Module

In a first step the plug-in must be installed. The installation of the plug-in is carried out under: Plug-ins > Plug-in administration > Open Payment Platform . By clicking on install, the plug-in is installed in your shop. You can find the settings for the main module under Plug-ins > Open Payment Platform .

In order to configure the main module, go to Plug-ins > Open Payment Platform . Change to the tab Configurations. Enter the data and settings you have already saved in the back-office of Open Payment Platform. In case of questions, you can find further information by moving the cursor to the question mark.

In the tab Information you can find important information on the plug-in such as the version number, release date and callback URL. This data is important when contacting our support.

You have the option of synchronising the order status with the transactions with Open Payment Platform. This means that when an item is sent or cancelled, you have the possibility of automatically also debiting the payment with Open Payment Platform. Further information can be found in the section The Module in Action.

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 Payment Processing > Payment Methods . Each payment method is listed individually. Install the payment methods you wish to offer you customers in your shop. You can carry out individual settings for each payment method and thereby optimally adapt the payment methods to your existing processes. The most central options are described in more detail further below.

In order for the payment method to be displayed in the shop, you must link them with a shipping method. Open the shipping methods under Payment Processing > Shipping Methods. By clicking edit, you can modify the shipping methods. Here you can link the payment methods you wish to offer and also have the option of setting individual payment fees.

4.2.1Configuration of payment methods in the WaWi

In order for the JTL WaWi to map the payment methods from the shop, make sure that you add them inside the WaWi Einstellungen > Zahlungsarten verwalten). Make sure that they are spelled exactly as written in the colum "Anmerkung".

4.3Shop ID

In the case of a multi-store set up (cf. chapter: Multi-Store), the parameter Shop ID identifies the shop's request and, therefore, redirects the feedback of Open Payment Platform based on the shop ID.

4.4Order Prefix

With the option order prefix you can define your own order scheme for the transmission to Open Payment Platform. This option helps you identify to which shop a transaction the back-end of Open Payment Platform is related to. The tag "{id}" will automatically be replaced be the consecutive order number.

4.5Selecting the Authorisation Method

You can choose between two options of authorizing credit card payments. By selecting one of the two under the option 'Authorisation Methods', you define how you want to process the individual payment methods.

Further information on the various authorisation methods can be found on our sellxed website.

Payment Processing

Please pay attention to the fact that you require the activation of further options with Open Payment Platform in order to use some of the authorisation methods.

It may be that certain authorization methods are not available for every payment method.

Alongside the introduction of PCI 3 there are additional certification requirements in case you are using the authorization method Hidden or AJAX. Please contact Open Payment Platform for further information or switch to another authorization method.

4.6Direct 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 the debit the payment at a later point.

Depending on your acquiring contract, a reservation is only guaranteed for a specific amount 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.

Different settings between Open Payment Platform and the module

It may be that settings saved in the payment modules overwrite settings saved in Open Payment Platform.

4.7Uncertain Status 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.7.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.8Optional: 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. 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 he or she 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 Open Payment Platform during the authorisation process. The payment method is displayed in any case

4.9Multi-Shop Set-Up

The payment module is designed for the usage of one Open Payment Platform contract for several shops. It must be differentiated, however, between the case of an integrated multi-shop functionality and independent shops:

Figure 4.1: Multi-shop set-up

In the case of independent shops, you require a payment module license for each shop. For scale prices, please contact us directly.

5Settings / Configuration of Payment Methods

5.1General Information About the Payment Methods

All sellxed payment modules are delivered with 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 Open Payment Platform 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.

Important info regarding Order Status

Never set the status to Pending Open Payment Platform or any similar pending status which is implemented by the module.

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

Orders with the status 'pending Open Payment Platform' 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 Open Payment Platform are being blocked. In this case check the settings of your firewall and ask the Hoster to activate the IPs and User Agents of Open Payment Platform.

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.


You can process Klarna directly viaOpen Payment Platform.In the following we will expand on the characteristics of the Klarna setup.

5.3.1Supported / Unsupported Functions

The module does not support the following functions:

  • You can not create or change any orders in the backend of JTL .
  • Partial activation and refunds can only be performed through the backend of Open Payment Platform () Full activation and full refunds can be performed directly inside JTL. For more information visit the Chapter around transaction management.
Edit Klarna transaction within JTL

Please make sure that you never modify or edit any Klarna transaction in your JTL backend.

The remaining functions are supported by the module. In the following you will find a description of the most important functions.

5.3.2Set Up / Configuration of the Payment Method

Activate the payment method as usual. Please note the following regarding the installation: Name of the Payment Method

You may change the displayed name in the frontend via title. Please use the title Invoice. Furthermore, you can define whether the Klarna logo is visible to your customers in the frontend via Display Logo. of the Payment Method

You may change the description of the payment method in the frontend via description. Please make sure you display the following description in your frontend: "Pay within 14 days". Authorization Method

We recommend to set Server as authorization method. In this case you will not be redirected to the payment page of Open Payment Platform. Merchant ID

In the payment method you can also define the Klarna Merchant ID (EID). You will either find this in your Klarna account or ask for it directly at Open Payment Platform.

5.3.3Canceling the Invoice

How to cancel invoices will be explained below in the chapter Activating / Canceling Orders. For further questions please refer to this section.

5.3.4Full Activating Invoices

For more information visit the Chapter around transaction management.

5.3.5Partial Refund and Partial Activation

Partial refunds and partial activations can only be done through the BIP of Open Payment Platform.

5.3.6On Hold Orders (Pending)

Pending orders are not supported by the module. In order you want those to be handled correctly by the system, please leave the field "Status Check interval" blank in your BIP. Please contact Open Payment Platform to make this setting.


In order for you to test the payment method Klarna you will need specific test data. But first make sure the the operation mode is on test and the test mode is on external.

You will find the official test data for Klarna directly in the developer portal via this link: https://developers.klarna.com/en/de+php/kpm/test-credentials.

5.3.8Payment fees

If you want to charge payment fees for a specific payment method, feel free to use the compatible payment fees modules. Those fees are directly transmitted to Klarna.

Payment Fees

Please make sure to not charge payment fees within the Open Payment Platform BIP Backend. Please use exclusively the compatible modules as described above.

6The Module in Action

Below you will find an overview over the most important features in the daily usage of the Open Payment Platform module.

6.1Useful Transaction Information on the Order

You can find an overview over all the most important information of a transaction in all orders that have been processed with the sellxed module. Among others, this information allows for the definite attribution of the orders to their corresponding transaction, seen in the back-end of Open Payment Platform.

Figure 6.1: Transaction Information in the JTL Back-End

The payment information is also transmitted to your JTL WaWi Client.

Figure 6.1: Transaction Information in JTL WaWi

6.2Usage of the Alias Managers / Token Solution

With the Alias Manager, your customers can securely save their credit cards with Open Payment Platform for later purchases. It is enabled by activating the option "Alias Manager" in the configuration of the Payment Method The customer can then choose from his or her saved credit cards without having to re-enter all the details.

Figure 6.1: Alias Manager Integration in JTL
Alias Manager Options

The usage of the Alias Managers requires the activation of the correct option with Open Payment Platform. To do so, please contact the support directly.

6.3Transaction Management within the JTL Shop

The transaction management can be carried out from within the shop.

6.3.1Capturing of Orders

You can directly debit orders in the back-end of your shop. In order to do so, switch to the tab Transactions. You can now search for the order number and then click on Show in order to find further information about the transaction. If you wish to capture an order, click 'capture'. Here you can modify the amount and the items. By clicking Capture, the action will be transmitted to Open Payment Platform.

In case you do not want to capture all items of the order, you can also close the transaction for further captures.

Figure 6.1: Capturing of Orders in JTL Back-End
Partial Capturing

Please find out if the capturing of partial amounts is supported by your Open Payment Platform contract. If this is not the case, it might happen that the transaction is closed for further transactions after a partial capture.

6.3.2Cancel Orders

In order to cancel an order, open the corresponding transaction. By clicking Cancel , a cancellation of the payment occurs with Open Payment Platform. The reserved amount on the customer's card will be released automatically.

Figure 6.1: Cancelling of Orders in the JTL Back-End


You can also create refunds for already debited transactions and automatically transmit these to Open Payment Platform. In order to do so, open the invoice of the already debited order (as described above). By clicking on Refund a dialog box for refunds will open up. Insert the amount you wish to refund and then click on Refund. The transaction will now be transmitted to Open Payment Platform.

Figure 6.1: Refunds Directly from Within the JTL Back-End

Please note that you can't refund more than 100% of the originally authorised amount.

6.5Setting up Cron Job

In order to activate the time-controlled functions of the plugin (such as update service, deleting pending orders, etc.) set up a time-controlled request in your hosting on the URL, which you will find via Plugins > Plugins >Open Payment Platform in the tab "Extended Information". Invoking it regularly will trigger the actions.

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


Before switching from test to live mode it is important that you test the module extensively. You can find all relevant test credit card data under: http://www.sellxed.com/de/testen.


Do not forget to switch the operating mode from test to live after having successfully tested the module.

7.1Test Data

In the following section you can find the test data for the various payment methods:
American Express
Card number
Expiry Date
No 3D Secure
Card number
Expiry Date
3D Secure
Carte Bleue
Card number
Expiry Date
Card number
Expiry Date
Diners Club
Card number
Expiry Date
Sepa Direct Debits
Austria (AT)
Germany (DE)
Spain (ES)
Discover Card
Card number
Expiry Date
Austria (AT)
Germany (DE)
Spain (ES)
Card number
Expiry Date
Klarna Invoice
Klarna (Approved)
Klarna (Denied)
Klarna (Pending -> Approved)
Klarna (Pending -> Denied)
Card number
Expiry Date
Card number
Expiry Date
No 3D Secure
Card number
Expiry Date
3D Secure
Card number
Expiry Date
No 3D Secure
Card number
Expiry Date
3D Secure
Card number
Expiry Date
3D Secure 2.0
Card number
Expiry Date

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 name of the payment method is not shown correctly in the email.

Depending on the name of the payment method and due to the naming convention, the name of the payment method in the email can be slightly strange. You can avoid this by adapting the email template. Go to Content > Email Templates.

In the order email you can replace the following '{$Bestellung->cZahlungsartName}' with '{$Bestellung->Zahlungsart->caption}'. From then on, the name you set in the payment configuration will be shown.

8.2Releasing Payment Information via Email

Certain payment methods request that the payment information should be sent via email (for example Vorkasse). This always works for the confirmation of the payment. This will be sent if the authorization was successful. If the payment information should be shown in the order email, the module needs to carry out the payment before completing the order. Pay attention to the the settings in the configuration of the payment method.

8.2.1Adjusting the HTML Templates

In order for this to work it will be necessary to make changes to the settings of the email templates. The following steps need to be taken:

{if !empty($Bestellung->cwPaymentInformation)}
{$Bestellung->cwPaymentInformation} {/if}

This needs to be added to each language, text and HTML.

8.2.2Adjusting the Plain Text Email Templates

To display the information in the plain text email please add the following snippet to the desired location:

{if !empty($Bestellung->cwPaymentInformation)} {$Bestellung->cwPaymentInformation|replace:"
":"\n"|strip_tags:false} {/if}

This needs to be added to each language, text and HTML.

8.3The Referrer URL appears in my Analytics Tool

When a customer and the notification are redirected via Header Redirection, the Open Payment Platform 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 a easier way.

9.1Birthday and gender in JTL

For certain payment service providers it is necessary to check the birthday an the gender of a customer. JTL does not check this by default. These checks can be enabled under "Einstellungen > Kunden / Formulare > Anrede abfragen" and "Einstellungen > Kunden / Formulare > Anrede abfragen" respectively.

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 Open Payment Platform settings. The logs are stored according to this setting and are not affected by the shopwide log level settings.

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

10.2Log Location

The log messages are visible in the JTL backend under the menu item Admin > Systemlog.

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.

Have JTL initialized in your script, this is required for the database connection.
Include the module main file and modules Transaction class.
require_once 'includes/plugins/oppcw/version/100/init.php';
require_once 'includes/plugins/oppcw/version/100/classes/OPPCw/Entity/Transaction.php';
Now you can load the transaction and then extract the transactionObject.
Load the transaction by Id:
$transactionById = OPPCw_Entity_Transaction::loadById($transactionId);
$transactionObject = $transactionById->getTransactionObject();