1Introduction

This manual describes how to install configure and use the payment module for Shopware and PAYONE.

Before you get started, make sure to have all necessary data at hand.

  • You received a user name and a password from PAYONE. Log in to the PAYONE Merchant Interface. ( https://pmi.pay1.de/)
  • Shopware payment module from sellxed.com/shop
  • Login data for your server and shop

2PAYONE Channels

According to the functions of the module which you want to use, you have to request the different channels at PAYONE. With the numbers of channels come various costs on the part of the PAYONE. Here you'll find an overview of the different functions and their corresponding channels.

  • Channel Frontend: Payment page
  • Channel Client-API: Hidden, Alias Manager, Ajax, Moto
  • Server-API: Refund, Capture, Cancel

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

2.1Installation Process

This document contains all information necessary to install the module. Make sure to follow the described steps strictly in order to ensure the safe use of the module in compliance with all security regulations.

  1. Configuration of the PAYONE test administration surface. The test platform can be found under https://pmi.pay1.de/
  2. Configuration of the main settings
  3. Configuration of the payment methods
  4. Conducting a test order by means of the Test Data enclosed at the end of this document
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 information 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 as otherwise the payment feedback of PAYONE might not get through to the shop.

2.2System Requirements

In general, the plugin has the same system requirements as Shopware. Below you can find the most important requirements of the plugin:
  • 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.

3PAYONE - Backend Configuration

First, log on to the PAYONE Merchant Interface (https://pmi.pay1.de/)

3.1Payment Portal Setup

Under Configuration > Payment Portals you can set up the payment portal for your shop. Among other things you define the TransactionStatus URL. This is the URL that the parameters for further processing are sent to after payment has taken place.

3.1.1Shop Portal Administration: Tab General

General settings such as portal name, Shop URL and the sender e-mail can be defined in the tab 'General'. These settings can be defined independently.

Make sure that the Server API, Front-end and Client API are activated in the Channel settings as shown in the screenshot.

Figure 3.1: Tab 'General'

3.1.2Shop Portal Administration: Tab Extended

In this tab you define the TransactionStatus URL. The URL you need to enter can be found directly on the general information site of the module in your shop. More information can be found in the section Transaction-Feedback).The remaining fields can be left empty. They will be filled by the module.

Figure 3.1: Extended configuration of the payment portal

3.1.3Shop Portal Administration: API-Parameter

This tab contains all relevant information to enter in the Main Module .

Figure 3.1: API-Parameter Configuration.

3.2Authorization Methods

PCI 3.1 - SAQ A-EP

Please note that with the changes in PCI new rules apply regarding the applicable self assessment questionnaire. If you host the forms to entering of the credit cards directly in your webshop (Hidden Authorization) or Ajax authroization new rules apply. If you want to continue to work with SAQ-A, you have to use Payment Page or the Widget Authorization.

In the configuration of the payment method you have the possibility to switch between various authorization methods. These regard primarily the depiction of the credit card forms in the shop. You'll find further information about that in chapter authorization methods.

3.3Account Activation

Further information on the payment method configuration and the implementations of the settings can be found here. After the activation and configuration of the payment methods you can conduct a test by means of the Test Data provided in this manual. As soon as the tests As soon as the tests have been successful you can contact PAYONE to demand the activation of your account. You will be able to process payments immediately.

4Module Installation and Update in the Shopware Shop

4.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.

4.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.

4.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.
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.

4.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.

4.2.3Updated Plugin from the PayoneCw to the CwbPayoneCw Version.

We plan to release this plugin in the shopware store in the near future. To make this possible we hda to apply some changes to our code. Most important a prefix for our PHP classes is required and the plugin folder had to be renamed. To update to this new version simply overwriting the existing files is not possible. This sections describes the steps required to update the module in detail.

Do not do updates directly in the live environment

Please test the update procedure first in your development system. So you can ensure the update is working correctly.

Mutliple Plugins

If you are using multiple plugins from us. You need to update all of them to the new version.

  1. Activate the maintenance mode of the shop.
  2. Make a backup for your database and your files in your shop. Without this you will not be able to revert to the old version, if anything goes wrong.
  3. Upload the new plugin files.
  4. Deactivate the existing plugin. Do not deinstall the old plugin yet.
  5. Install and activate the new plugin.
  6. If you have custom css or template files for the plugin, adapt the changes to the new plugin.
  7. If you are using the Shopware API endpoint of this plugin, update the URL to new endpoint.
  8. Verify the main and method settings.
  9. Deinstall the old plugin.
  10. Delete the files of the old plugin. The following files/folders must be removed, if they exist:
    • engine/Shopware/Plugins/Local/Frontend/PayoneCw
    • engine/Library/Customweb
    • engine/Library/Crypt
    • engine/Library/File
    • engine/Library/Math
    • engine/Library/Mobile
    • engine/Library/Net
    • engine/Library/PhoneNumber
    • engine/Library/System
    • engine/Library/loader.php
    • engine/Library/openssl.cnf
  11. Make a test transaction to verify everything is workin correctly.
  12. Deactive the maintenance mode of the shop.

5Module Configuration in the Shopware 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 backups!

Please create a backup 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.

5.1Configuration of the Main Module

In order to install the main module search for PAYONE under Settings > Plugin Manager . Click on the + symbol in order to begin the installation process. Afterwards, click the "edit" symbol and configure the main module.

Enter the individual options which you partly may have already used for the configuration of the administration interface of PAYONE. Should an option not be clear to you, you can click on the question mark and will find further information on the settings.

5.2Defining the URL for the Transaction Feedback

To ensure correct payment processing in your shop, at least one Feedback URL has to be provided in the PAYONE configuration. The URL to be entered can be found in your Shopware Shop under: Configuration > PAYONE > Setup > Setup

5.3Configuration of the Payment Method

After having configured the main module, you will find all payment methods under Settings > Payment Methods. Activate each payment method you wish to offer in your shop. You can save individual settings for each payment method (and for each shop in case of a multi-shop set-up) and thereby optimally adapt the payment methods to your existing processes. The most central options are described in more detail further below.

Figure 5.1: Configuration of the Payment Method

5.4Assigning the Payment Method to the Shipping Costs

In order for the transactions and the shipping costs to be matched correctly to the payment methods you need to assign the payment methods to the shipping methods. Go to settings > shipping costs. Open all the shipping costs and add a payment method.

Figure 5.1: Assigning the Payment Method to the Shipping Method.
Attributing Payment Methods to the Shipping Method

Depending on the amount of delivered payment methods, it may be that certain payment methods can't be attributed to a specific shipping method as not all payment methods can be displayed. This is a known bug of Shopware. Merely the first 30 payment methods are displayed. Please delete all payment methods that you don't need and then all other payments will be displayed.

5.5Direct 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.

Different settings between PAYONE and the module

It may be that settings saved in the payment modules overwrite settings saved in PAYONE.

5.6Uncertain 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.

5.6.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.

5.7Optional: 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 PAYONE during the authorisation process. The payment method is displayed in any case

5.8Defining the URL for the Transaction Feedback

To ensure correct payment processing in your shop, at least one Feedback URL has to be provided in the PAYONE configuration. The URL to be entered can be found in your Shopware Shop under:Configuration > PAYONE > Setup

5.8.1Usage of the Integrated Multishop Functionality of Shopware

The payment module supports the multishop feature of Shopware. No further modifications are necessary. The module automatically recognizes the shop the order belongs to. In order for the multishop functionality to work, it is, however, necessary that the individual sub-shops within Shopware have been configured correctly.

6Settings / Configuration of Payment Methods

6.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 PAYONE 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.

6.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 PAYONE or any similar pending status which is implemented by the module.

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

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

6.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.

7The Module in Action

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

7.1Capturing / Canceling of Orders

7.1.1Capturing Orders

Please note

The transaction management between your shop and PAYONE is not synchronized. If you capture payments with PAYONE, the status in the shop will not be updated and a second capturing in the shop is not possible.

In order to be able to capture orders, you must make sure that you have set 'Capturing' to deferred in the configuration of the payment method.

Open the order you wish to capture and switch to the tab Transactions. Here you will find the tab Captures. Enter the amount you wish to debit from the customer's card. By clicking Capture, a direct capturing of the order occurs with PAYONE.

7.1.2Cancellation

By clicking the button Cancel, you delete the initial authorization on the customer's card. The pre-authorized amount is released from the customer's card.

Figure 7.1: Capturing/Cancellation of orders in Shopware

7.2Useful Transaction Information on the Order

In each order, processed via our module, you can find an overview of the most important information about the transaction as well as a transaction history.

In order to get to the transaction information, open the order and switch to the tab Transactions. Here you will find all authorization attempts and the related information.

Figure 7.1: Transaction Information in Shopware.

7.3Using Invoice Details of a Processor

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

7.3.1Shopware Order Confirmation (E-Mail)

Please add the following code block into your Shopware email template, if you want to send the payment details of the processor in the mail confirmation sent to the customer:

  1. HTML Mailtemplate
  2. {if $paymentInformationHtml}

    {$paymentInformationHtml}
    {/if}

  3. PLAIN Mailtemplate
  4. {if $paymentInformationPlain}

    {$paymentInformationPlain}
    {/if}

7.3.2Shopware Invoice (PDF)

Due to technical limitations, it is currently not possible to display the "payment information" here.

7.3.3Shopware-Backend (Transaction details)

You can view the payment and transaction details in Shopware under Customer > Payments > PAYONE.

Figure 7.1: Transaction details within Shopware.

7.3.4Shopware Success-Page

Figure 7.1: Payment informations on the Shopware "Success-Page".

7.4Refunds

You can refund already captured transactions and automatically transmit them to PAYONE. In order to to so, open the order. Switch to the tab Transactions. A new window will open up in which you must then switch to the tab Refunds in order to refund orders.

To refund a line item you need to enter the quantity you wish to refund. By clicking Refund, the refund is automatically transmitted to PAYONE. It will than be refunded via the payment method the customer chose for the transaction.

Figure 7.1: Refunding Orders in Shopware.

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

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

7.5Usage of the Alias Managers / Token Solution

With the Alias Manager, your customers can securely save their credit cards with PAYONE for later purchases. You can enable this 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 7.1: Alias Manager Usage in Shopware
Please note!

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

8Getting the Credit Card Data via Shopware REST API

When connecting ERP systems to Shopware it may be that further information is required via Shopware API. Our module provides you with a lot of payment information also via Shopware REST API.

Basic Information about the usage of the REST API of Shopware can be found in the Shopware Developers Guide.

The service can be called up under https://www.shop-url.com/api/CwbpayonecwTransactions. The call of the above URL leads to the listing of all transactions. By adding the Transaction ID you can filter by the corresponding Transaction ID. The Transaction ID can be found in the order overview (Customer > Payments > PAYONE )

Additionally, you can also access the transaction via the Payment ID (transmitted through PAYONE). To do so, the parameter 'usePaymentId=1' has to be added as a parameter to the URL.

9Set-up 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 Shopware Cron engine. Especially the update function allows you to automatically retrieve additional information or changes of your order directly via the API of PAYONE. For payment methods which use a delayed authorisation process this is mandatory. Please note it could be that in order to use the update feature it may be necessary that PAYONE activates additional options in your account.

The module uses the standard cron engine of Shopware. More information regarding the set up can be found here: https://community.shopware.com/Cronjobs_detail_1102.html.

10Testing

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

Testing

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

10.1Test Data

In the following section you can find the test data for the various payment methods:
SOFORT
Sofort
IBAN
DE85123456782599100003
BIC
TESTTEST
Bank account
2599100003
Bank code
12345678
giropay
Sofort
IBAN
DE46940594210000012345
BIC
TESTDETT421
ID / PIN
sepatest1 / 12345
NR / TAN
MAS_Test / 123456
Direct Debits
Hidden Mandate
Accept
IBAN
DE00123456782599100004
BIC
TESTTEST
Hidden Mandate
Denied - Invalid BIC
IBAN
DE00123456782599100004
BIC
TESTTESX
Credit / Debit Card
VISA
Verified by Visa
Card number
4012 0010 3714 1112
Expiry Date:
12/2020
Name
Hans Muster
CVC:
123
3-D Secure Password
12345
Visa 3D
VISA
CH
Card number
4111 1111 1111 1111
Expiry Date:
12/2020
Name
Hans Muster
CVC:
123
Visa CH
VISA
DE
Card number
4111 1310 1011 1111
Expiry Date:
12/2020
Name
Hans Muster
CVC:
123
Visa DE
VISA
AT
Card number
4111 1210 1111 1111
Expiry Date:
12/2020
Name
Hans Muster
CVC:
123
Visa AT
MasterCard
MasterCard SecureCode
Card number
5453 0100 0008 0200
Expiry Date:
12/2020
Name
Hans Muster
CVC:
123
3-D Secure Password
12345
Mastercard 3D
Mastercard
Card number
5500 0000 0000 0004
Expiry Date:
12/2020
Name
Hans Muster
CVC:
123
Mastercard
American Express
Card number
340 0000 0000 0009
Expiry Date:
12/2020
Name
Hans Muster
CVC:
1234
American Express
JCB
JCB J/Secure
Card number
3528 4501 3100 3315
Expiry Date:
12/2020
Name
Hans Muster
CVC:
123
3-D Secure Password
12345
JCB 3D
JCB
Card number
3088 0000 0000 0009
Expiry Date:
12/2020
Name
Hans Muster
CVC:
123
JCB
Maestro
Card number
5000 0000 0000 0009
Expiry Date:
12/2020
Name
Hans Muster
CVC:
123
Maestro
Carte Bleue
Card number
4973 0100 0000 0004
Expiry Date:
12/2020
Name
Hans Muster
CVC:
123
Carte Bleue
Diners Club
Card number
30 0000 0000 0004
Expiry Date:
12/2020
Name
Hans Muster
CVC:
123
Diners Club
Discover
Card number
6011 1111 1111 1117
Expiry Date:
12/2020
Name
Hans Muster
CVC:
123
Discover Card
MasterCard
Mastercard
Card number
5500 0000 0000 0004
Expiry Date:
12/2020
Name
Hans Muster
CVC:
123
Mastercard
MasterCard
MasterCard SecureCode
Card number
5453 0100 0008 0200
Expiry Date:
12/2020
Name
Hans Muster
CVC:
123
3-D Secure Password
12345
Mastercard 3D
Visa
VISA
CH
Card number
4111 1111 1111 1111
Expiry Date:
12/2020
Name
Hans Muster
CVC:
123
Visa CH
VISA
DE
Card number
4111 1310 1011 1111
Expiry Date:
12/2020
Name
Hans Muster
CVC:
123
Visa DE
VISA
AT
Card number
4111 1210 1111 1111
Expiry Date:
12/2020
Name
Hans Muster
CVC:
123
Visa AT
VISA
Verified by Visa
Card number
4012 0010 3714 1112
Expiry Date:
12/2020
Name
Hans Muster
CVC:
123
3-D Secure Password
12345
Visa 3D
American Express
American Express
Card number
340 0000 0000 0009
Expiry Date:
12/2020
Name
Hans Muster
CVC:
1234
American Express
Diners Club
Diners Club
Card number
30 0000 0000 0004
Expiry Date:
12/2020
Name
Hans Muster
CVC:
123
Diners Club
Discover Card
Discover
Card number
6011 1111 1111 1117
Expiry Date:
12/2020
Name
Hans Muster
CVC:
123
Discover Card
Carte Bleue
Carte Bleue
Card number
4973 0100 0000 0004
Expiry Date:
12/2020
Name
Hans Muster
CVC:
123
Carte Bleue
JCB
JCB
Card number
3088 0000 0000 0009
Expiry Date:
12/2020
Name
Hans Muster
CVC:
123
JCB
JCB
JCB J/Secure
Card number
3528 4501 3100 3315
Expiry Date:
12/2020
Name
Hans Muster
CVC:
123
3-D Secure Password
12345
JCB 3D
Maestro
Maestro
Card number
5000 0000 0000 0009
Expiry Date:
12/2020
Name
Hans Muster
CVC:
123
Maestro

11Errors 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

11.1The Referrer URL appears in my Analytics Tool

When a customer and the notification are redirected via Header Redirection, the PAYONE 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.

12Compatibility 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.

12.1Birthday and gender in Shopware

For certain payment service providers it is necessary to check the birthday and the gender of a customer. Shopware does not check this by default. To enable these checks go to "Configuration > Basic Settings > Frontend > Login / Registration" and check the following parameters:

  • Show Birthday Field
  • Birthday is required
  • Show "I am" select field

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

13.1Log Levels

You can configure the log level in the PAYONE settings.

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

13.2Log Location

The log file is stored in the Shopware log directory. Please make sure the path exists and it is writable by the webserver. (Default Path: {shopRootDirectory}/logs or {shopRootDirectory}/var/log)

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

14.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 Shopware initialized in your script, this is required for the database connection.
require __DIR__ . '/autoload.php';
use Shopware\Kernel;
$environment = 'production';
$kernel = new Kernel($environment, false);
$kernel->boot();
Register the module module classes.
$pluginPath = 'engine/Shopware/Plugins/Local/Frontend/CwbPayoneCw';
Shopware()->Loader()->registerNamespace('Customweb', 'Customweb/');
Shopware()->Loader()->registerNamespace('CwbPayoneCw_Helpers', $pluginPath . '/Helpers/');
Shopware()->Loader()->registerNamespace('CwbPayoneCw_Entities', $pluginPath . '/Entities/');
Shopware()->Loader()->registerNamespace('CwbPayoneCw_Components', $pluginPath . '/Components/');
Shopware()->Loader()->registerNamespace('Shopware\Components\Api', $pluginPath . '/Components/Api/');

require_once $pluginPath . '/Library/loader.php';
Customweb_Core_Util_Class::registerClassLoader(function ($className){
	return Shopware()->Loader()->loadClass($className);
});	
To load old transactions register a legacy class loader.
	Customweb_Core_Util_Class::registerClassLoader(function($className){
		if(strpos($className, 'PayoneCw') === 0){
			$fileName = substr($className, strrpos($className, '_')+1).".php";
			if(file_exists('engine/Shopware/Plugins/Local/Frontend/CwbPayoneCw/Legacy/'.$fileName)){
				require_once 'engine/Shopware/Plugins/Local/Frontend/CwbPayoneCw/Legacy/'.$fileName;
				return true;
			}
		}
		return false;
	});
	
Now you can load the transaction and then extract the transactionObject.
Load the transaction by Id:
$transactionById =  CwbPayoneCw_Helpers_Util::loadTransaction($transactionId);
$transactionObject = $transactionById->getTransactionObject();