1Introduction
This manual leads you through the installation, configuration and usage of the payment module for OpenCart and Concardis PayEngine 3.0.
Before beginning with the installation, please make sure that you are in possession of all necessary data:
- Access to your merchant center account of Concardis PayEngine 3.0 (https://merchanttest.payengine.de for test and https://merchant.payengine.de for live) - On this plattform you can download the access information.
- OpenCart payment module from sellxed.com/shop.
- Access to your server.
In case you don't yet have a contract with Concardis PayEngine 3.0, we please ask you to contact their support.
Note that you must use at least PHP version 5.6 for our plugins. PHP 8 or higher is currently not supported.
1.1Process of the Installation
In this document you will find all important information for the installation of the module. It is important that you strictly follow the checklist. Only by doing so, can a secure usage in correspondence with all security regulations be guaranteed.
- Configuration of the basic settings of the payment module
- Configuration of the payment methods
- Carrying out of a test purchase by means of the attached test data at the end of this document
- If your test was successful, do not forget to switch the operating mode to live mode.
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
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 Concardis PayEngine 3.0 might not get through to the shop.
1.2System Requirements
In general, the plugin has the same system requirements as OpenCart. 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.
In case you are using OpenCart version 3.0.3.5 or 3.0.3.6, you must patch your store to fix the twig extension error in order for modified templates to be loaded. The following extension can be used to resolve the issue: https://www.opencart.com/index.php?route=marketplace/extension/info&extension_id=40469.
2Configuration of the Payment Module and the Payment Methods
In order to configure and set up the main module in OpenCart please double check that you possess the following information:
- Merchant ID
- API Private Key
All this informations are provided in your https://merchant.payengine.de merchant center account under My Account.
2.1Configuration Main Module
Follow the instruction in the section main module to install and set the above retrieved credentials directly in your shop. If you want to have additional information regarding how to use the Extranet of Concardis PayEngine 3.0 we ask you kindly to directly call the customer support of Concardis PayEngine 3.0.
2.2Activation Payment Methods
Once the main module is configured navigate to the payment methods and activate the payment methods that you want to process with.
3Module Installation and Update in the OpenCart 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:
- Download the plugin. The download can be found in your sellxed.com account under "My Downloads".
- Unzip the archive you have just downloaded.
- In the unzipped folder navigate to the folder "files"
- 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.
- 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.
- 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:
- Always do a backup for your database and your files in your shop
- Use always a test system to test the update process.
- 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.
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. 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 OpenCart 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.
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.
5OpenCart 3.0 Installation - Additions
In order to guarantee smooth operations and the usage of all features please make sure that you follow the instructions below.
5.1Configuration of the Main Module
You will find the settings for the main module under "Extension > Modules > Concardis PayEngine 3.0 Base Module" . Install the module by clicking Install.
By clicking Edit you can configure the main module. Enter all data in the corresponding fields. Each option is, furthermore, explained in short info texts in the shop.
5.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 Extensions > Payments . Each payment method is listed individually. Install the payment methods you wish to offer to your customers. 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.
By clicking on Install the payment method is activated in your shop. Click Edit in order to modify the configuration of the payment method.
5.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.
It may be that settings saved in the payment modules overwrite settings saved in Concardis PayEngine 3.0.
5.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.
5.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.
5.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 Concardis PayEngine 3.0 during the authorisation process. The payment method is displayed in any case
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 Concardis PayEngine 3.0 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.
Never set the status to Pending Concardis PayEngine 3.0 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 Concardis PayEngine 3.0' 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 Concardis PayEngine 3.0 are being blocked. In this case check the settings of your firewall and ask the Hoster to activate the IPs and User Agents of Concardis PayEngine 3.0.
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 Concardis PayEngine 3.0 module.
7.1Useful Transaction Information on the Order
You can find an overview of the transaction information in within the order detail view. Among others, this information allows for the definite attribution of the orders to their corresponding transaction, seen in the backend of Concardis PayEngine 3.0.
7.2Usage of the Alias Managers / Token Solution
With the Alias Manager, your customers can securely save their credit cards with Concardis PayEngine 3.0 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.
The usage of the Alias Managers requires the activation of the correct option with Concardis PayEngine 3.0. To do so, please contact the support directly.
7.3Capturing / Cancelling of Orders
7.3.1Capturing Orders
In order to capture orders, open the transaction manager under Sales > Concardis PayEngine 3.0 Transactions. Here you will find an overview of all transactions. Search for the order in the field with the order numbers. By clicking "view" you will open the transaction of the order.
7.3.1.1Capturing Complete Orders or Partial Capturing
By clicking the button "Capture Transaction" a new window opens up. You can now capture every item individually in case you do not wish to send all items at once. The amount of possible partial captures depends on your contract. Please contact Concardis PayEngine 3.0 directly in order to clarify questions.
The transaction management between your shop and Concardis PayEngine 3.0 is not synchronised. If you capture payments with Concardis PayEngine 3.0, the status in the shop will not be updated and a second capturing in the shop is not possible.
In case you do not wish to capture all items of an order, you can close the transaction by clicking the box.
Please find out if the capturing of partial amounts is supported by your Concardis PayEngine 3.0 contract. If this is not the case, it might happen that the transaction is closed for further transactions after a partial capture.
7.3.2Cancel Orders
By clicking "Cancel Transaction", the transaction is cancelled and the reserved amount on your customer's card is released automatically.
7.4Refunding Orders
In order to refund orders, open the transaction information (cf. above).
You can refund individual items or any amount of your choice by modifying the total amount or the item quantity.
With our module it is not possible to refund more than 100% of the originally authorised amount.
Executing a refund will not change the status of the order.
7.5Setup 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 OpenCart Cron engine. Especially the update function allows you to automatically retrive additional information or changes of your order directly via the API of Concardis PayEngine 3.0. Please note it could be that in order to use the update feature it may be necessary that Concardis PayEngine 3.0 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:
https://www.your-shop.com/index.php?route=payengine3cw/cron/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.
8Testing
Before switching from test to live mode it is important that you test the module extensively.
Do not forget to switch the operating mode from test to live after having successfully tested the module.
8.1Test Data
In the following section you can find the test data for the various payment methods:Card number 5399 9999 9999 9999 Expiry Date 12/2020 CVC 123 Success Amount 1.00$/€ Failure Amount 1.11$/€ | MasterCard Standard |
Card number 5404 0000 0000 0001 Expiry Date 12/2020 CVC 123 Success Amount 1.00$/€ Failure Amount 1.11$/€ | MasterCard 3D |
Card number 4111 1111 1111 1111 Expiry Date 12/2020 CVC 123 Success Amount 1.00$/€ Failure Amount 1.11$/€ | VISA Standard |
Card number 4000 0000 0000 0002 Expiry Date 12/2020 CVC 123 Success Amount 1.00$/€ Failure Amount 1.11$/€ | VISA 3D |
Card number 3741 1111 1111 111 Expiry Date 12/2020 CVC 1234 Success Amount 1.00$/€ Failure Amount 1.11$/€ | Amex |
Card number 3714 4963 5398 431 Expiry Date 12/2020 CVC 1234 Success Amount 1.00$/€ Failure Amount 1.11$/€ | Amex Safekey |
Card number 6400 0512 3456 7895 Success Amount 1.00$/€ Failure Amount 1.11$/€ | Maestro |
Card number 4462 0300 0000 0000 Expiry Date 12/2020 CVC 123 Success Amount 1.00$/€ Failure Amount 1.11$/€ | VISA Debit |
Failure Amounts 1.00/11.00/111.00$/€ | Simulation Failure Amounts |
Failure Amounts 1.00/11.00/111.00$/€ | Simulation Failure Amounts |
Failure Amounts 1.00/11.00/111.00$/€ | Simulation Failure Amounts |
IBAN DE12500105170648489890 BIC INGDDEFFXXX | Simulation IBAN for test order with settlement |
IBAN DE15111111111111111199 | Simulation IBAN for test order |
City Testhausen Surname Ablehnung | Ratepay Failure |
City Testhausen Surname Ablehnung | Ratepay Failure |
Failure Amounts 1.00/11.00/111.00$/€ | Simulation Failure Amounts |
Failure Amounts 1.00/11.00/111.00$/€ | Simulation Failure Amounts |
Failure Amounts 1.00/11.00/111.00$/€ | Simulation Failure Amounts |
Failure Amounts 1.00/11.00/111.00$/€ | Simulation Failure Amounts |
Failure Amounts 1.00/11.00/111.00$/€ | Simulation Failure Amounts |
Failure Amounts 1.00/11.00/111.00$/€ | Simulation Failure Amounts |
Failure Amounts 1.00/11.00/111.00$/€ | Simulation Failure Amounts |
9Errors 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
9.1The Referrer URL appears in my Analytics Tool
When a customer and the notification are redirected via Header Redirection, the Concardis PayEngine 3.0 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.
10Compatibility 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.
10.1Birthday and gender in OpenCart
For certain payment service providers it is necessary to check the birthday and the gender of a customer. OpenCart does not check this by default.
- Add two new custom fields to your checkout via your shops backend under "Customers > Custom Fields"
-
Modify the order context getters to return the value of your custom checkout field from the order / session (or wherever the previous step saves the data).
Order Context Getters
- AbstractOrderContext
- getBillingDateOfBirth()
- getBillingGender()
These functions can be found in "system/library/cw/PayEngine3/AbstractOrderContext.php".
11Error 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.
11.1Log Levels
You can configure the log level in the Concardis PayEngine 3.0 settings.
- Error: Logs unexpected errors only. (Default)
- Info: Logs extended information.
- Debug: Logs information helpful for debugging.
11.2Log Location
The log file is stored in the default log folder of OpenCart. The path is configured in the config.php of your shop system. (Default Path: {shopRootDirectory}/system/logs or {shopRootDirectory}/system/storage/logs)
12Advanced 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.
12.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('config.php'); require_once(DIR_SYSTEM . 'startup.php'); // Registry $registry = new Registry(); // Config $config = new Config(); $config->load('default'); $config->load('catalog'); $registry->set('config', $config); $loader = new Loader($registry); $registry->set('load', $loader); $registry->set('db', new DB($config->get('db_type'), $config->get('db_hostname'), $config->get('db_username'), $config->get('db_password'), $config->get('db_database'), $config->get('db_port')));
require_once DIR_SYSTEM.'library/cw/init.php'; require_once DIR_SYSTEM.'library/cw/PayEngine3Cw/Util.php'; require_once DIR_SYSTEM.'library/cw/PayEngine3Cw/Entity/Transaction.php'; PayEngine3Cw_Util::setRegistry($registry);
$transactionById = PayEngine3Cw_Entity_Transaction::loadById($transactionId); $transactionObject = $transactionById->getTransactionObject();
$transactionsByOrderId = PayEngine3Cw_Entity_Transaction::getTransactionsByOrderId($orderId); foreach($transactionsByOrderId as $transaction){ $transactionObject = $transaction->getTransactionObject(); //Do something with each object }