1Introduction
This manual leads you through the installation, configuration and usage of the payment module for xt:Commerce and EMS eCommerce Gateway.
Before you can begin with the installation, please make sure that you are in possession of all the necessary data:
- You should have received a Store ID from EMS eCommerce Gateway(Usually an eleven digit combination of numbers )
- Shared Secret for the usage of Connect (Shared Secret Connect Interface)
- If you are working with the professional version of the module and have requested the API Interface with EMS eCommerce Gateway, you should furthermore have received an API User ID, a client certificate as well as the corresponding passwords
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 the information necessary for the installation of the module. It is important that you follow the checklist strictly. Only if you comply with each step we can ensure a secure usage in correspondence with all security regulations.
- Configuration of the basic settings of the payment module
- Configuration of the payment methods
- Carrying out a test purchase by means of the attached test data at the end of this document
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 EMS eCommerce Gateway might not get through to the shop.
1.2System Requirements
In general, the plugin has the same system requirements as xt:Commerce. 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.
2Configuration EMS eCommerce Gateway
If you have merely bought the Standard Version of the module you only need to comply with the part Configuration of the Module
2.1Test Environment and Live Platform for Administration
You can find the administration and the transaction overview if you click on this link (A client certificate is needed to access):
Please note that you can only access the testing platform with a corresponding client certificate which you receive fromEMS eCommerce Gateway.
2.2Mandatory: Configuration of the Module
Navigate to the main module in your shop. Please fill in the following data in to the appropriate location:
- Store ID (you will receive this directly from EMS eCommerce Gateway)
- Shared Secret (you will receive this directly from EMS eCommerce Gateway)
The remaining settings in the main module regard specific fraud settings to identify transactions without 3D secure. The default settings are set correctly for most of them.
Please note that momentarily there is a problem at EMS eCommerce Gateway with certain certificate types. In case no order confirmation mails are being sent out and the status of the order is still set to Pending EMS eCommerce Gateway and the status then changes to Cancelled you have to switch to Yes at Force Non SSL Notification.
2.3Optional: Professional Version - Creating a Certificate File
By working with the Professional Version of the module you can operate the transaction management directly from your shop. This way you don't need to install the certificates to access the backend. To be able to use these functions you must already have bought the Professional Version of the Module at www.sellxed.com/shop. Otherwise you will not have access to these features. In order to change to the Professional Version contact us at contact.
You will receive a ZIP from EMS eCommerce Gateway containing a key (file extension .key) as well as the certificate (file extension .pem) in order to use the backend and the transaction management. Extract these files into a directory of your choice and carry out the following steps:
- Open the certificate (file with the extension .pem)
- Open the key simultaneously (file with the extension .key)
- Insert the content of the key underneath the certificate file
- Save the certificate file and copy it into: files_4.0.x/plugins/emsecommercecw/lib/Customweb/EMSeCommerce/Certificates/Default/
- You can now proceed to the instructions for the installation.
2.4Activating the Payment Methods and Testing
Further information regarding the configuration of the payment methods and the meaning of the specific settings can be found here. When you have activated and configured the payment methods you can run a test by means of the published Test data in the manual. If all tests were successful, switch the operating mode in the main module to Live.
3Module Installation and Update in the xt:Commerce Shop
3.1Installation
At this time you should already be in possession of the module. Should this not be the case, you can download the necessary files in your customer account in the sellxed shop (Menu "My Downloads Downloads"). In order to install the module in your shop, please carry out the following steps:
- 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 xt:Commerce Shop
The configuration consists of two steps. The first step is the configuration of the main module with all the basic settings (cf. Configuration of the Main Module). During the second step you can then carry out individual configurations for each payment method . This allows for full flexibility and perfect adaptation to your processes.
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.
4.1Base Module Configuration
The settings for the Base Module can be found in "Content > Plugin > deinstalled plugins > EMS eCommerce Gateway Base Module" . To install the module, click 'install'. A new window should open now. Next, cklick F5 in your browser in order to reload all Java Script data of the modules and then return to the location of the installed plugins.
The settings of the module can be opened by clicking on the pen. Enter the options that you set in the administration surface of EMS eCommerce Gateway. If an option is unclear, a click on the question mark will show more information. The central settings will be explained.
4.1.1Sending e-Mails for status updates
Mark every status that you want to trigger an e-Mail to the customer if his order was set to this status.
4.2Payment Method Configuration
After the Basic Module was configured successfully, the payment method settings for your shop can be found under Settings >. Every method is listed seperately. Activate the desired payment methods by selecting them and clicking Activate Selection.
With a click on the pen, a new window for the settings will open. Most settings are self-explanatory. A click on the question mark shows additional information.
4.2.1Choosing the Authorization Method
You can choose between several display options for the authorization of card payments. The option Authorization Method determines, which payment methods you would like to process.
For further information on the differen authorization methods, visit our sellxed Website.
4.2.2Payment Form Position
If you have the corresponding package of EMS eCommerce Gateway, the payment information can be entered directly in your shop. The setting Page for Payment Form adjusts the position of the payment form
Please bear in mind that additional options with EMS eCommerce Gateway have to be enabled in order to use some of the payment processing methods.
Some authorization methods might not be available for every payment method.
4.2.3Capturing Orders Directly
The option "Capturing" determines wether payments should be captured directly or if they should be authorized before. If you only want to authorize as a first step, ensure that the payments are issued later.
Depending on your Acquiring Contract, a reservation is guaranteed for a limited time only. If you are not capturing within this time, the authorization might not be guaranteed. Further information on the process of capturing is provided below.
The settings in the payment method module might overwrite your settings in the EMS eCommerce Gateway backend.
4.2.4Uncertain Status
You can mark orders without a 3D Secure Verification or other security mechanism failures. This allows you to examine the order manually before the shipment.
4.2.5Setting the Order Status
You can determine which status the order should have for every payment method. This refers to the initial order status.
By choosing the authorization method Hidden Authorization, the insertion of the credit card data occurs in your shop. This requires additoinal PCI Certification though.
However, if you prefer that the customer inserts the credit card data on the payment page of EMS eCommerce Gateway, you have the possibility of placing your logo on said Payment Page. In order to do so, please contact EMS eCommerce Gateway directly.
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.
It may be that settings saved in the payment modules overwrite settings saved in EMS eCommerce Gateway.
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.5Stock Management in xt:Commerce 4 / 5
Since the 19.05.2017 we changed the way we handle the stock implementation in xt:Commerce 4 / 5. Products will now automatically be restocked when the status of the order is changed to failed. The status of the order is automatically changed to failed if the customer does click on the cancel button on the payment page. However if he uses the back button in the browser we can not determine the status of the order. In this case you have to manually cancel the order to restock the items.
Please note the stock will automatically be increased if you switch an order into the failed state.
4.6Optional: 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 EMS eCommerce Gateway 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 EMS eCommerce Gateway 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.
Never set the status to Pending EMS eCommerce Gateway 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 EMS eCommerce Gateway' 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 EMS eCommerce Gateway are being blocked. In this case check the settings of your firewall and ask the Hoster to activate the IPs and User Agents of EMS eCommerce Gateway.
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 EMS eCommerce Gateway module.
6.1Order Transaction Information
In each order processed by our module, you can view all important information on the transaction. For instance, this feature allows you to match the orders to the transactions visible in the EMS eCommerce Gateway backend.
To view this information, open the orders. At the bottom of the order you will find the paragraph EMS eCommerce Gateway Transactions. This shows all details on all former actions related to this order. Click on the key in the column "Action" to see the transaction information (c.f. image "Transaction Information").
6.2Transaction Table
In addition to information on the order, the transaction table shows information on the transactions in your shop. Among other things, it allows you to match the EMS eCommerce Gateway transaction number to the order in your shop.
6.3Initiating payments in the xt:Commerce backend
The xt:Commerce payment module allows you to initiate a payment directly from the shop, the so called Mail Order / Telephone Order (MOTO). This feature requires an additional module. After installing the plugin, you can set up four orders in the EMS eCommerce Gateway administration surface. When opening the order now, you can add a transaction to this order by clicking on Add Moto Transaction on the bottom right. The transaction will be forwarded to EMS eCommerce Gateway directly.
6.3.1Refunding Orders
In order to issue a refund, open the transaction information (c.f. above). This shows all information on the transaction. With a click on "Refund", an input mask for credit notes will open. By clicking Refund , the refund request is transmitted to EMS eCommerce Gateway.
Executing a refund will not change the status of the order.
6.4Capturing / Cancelling Orders
The transaction management between EMS eCommerce Gateway and your shop is not synchronised. When you register payments with EMS eCommerce Gateway, the status in the shop is not adjusted and the order cannot be captured in the shop again.
6.4.1Capturing / Cancelling Orders
To capture orders, open the transaction information (c.f. above). This will show you all information on the transaction. With a click on "Capture" (top right), the order is forwarded to EMS eCommerce Gateway. You do not have to log in to the EMS eCommerce Gateway backend. You can enter the products you would like to capture in the input mask.
By clicking "Cancel" the transaction is cancelled and the reserved amount is cleared on the customer's card immediately.
6.5Using the Alias Manager / Token Solution
The Alias Manager feature allows you to securely save your customers' credit card data at EMS eCommerce Gateway for future orders. You can enable this by activating the option "Alias Manager" in the configuration of the Payment Method. Now the customer can choose between already saved credit cards when ordering again, without having to enter all card information.
It is necessary to enable the respective option with EMS eCommerce Gateway to use the Alias Manager. To do this, please contact the support team.
6.6Setting up Cron Job
To activate the time-controlled plug-in functions (e.g. Update Service, deleting pendant orders, etc.), follow the EMS eCommerce Gateway instructions for the set up of Cron Job.
7Testing
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.
7.1Test Data
In the following section you can find the test data for the various payment methods:Card number 5404 1070 0002 0010 Expiry Date 12/2020 CVC 123 |
Card number 4921 8180 8989 8988 Expiry Date 12/2020 CVC 123 |
Card number 4921 8180 8989 8988 Expiry Date 12/2020 CVC 123 | |
Card number 5404 1070 0002 0010 Expiry Date 12/2020 CVC 123 |
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 EMS eCommerce Gateway Referrer URL might appear in your Analytics Tool thus hiding the original traffic source. However, most Analytic Tools are able to minimize this problem.
In case you are using Google Analytics as reporting tool, this step by step guide may help you to exclude the URLs: under bullet point 4.
9Error Logging
The module will log different unexpected errors or information depending on the configured level. If there is any issue with the module, this log can help identify the cause.
9.1Log Levels
You can configure the log level in the EMS eCommerce Gateway settings.
- Error: Logs unexpected errors only. (Default)
- Info: Logs extended information.
- Debug: Logs information helpful for debugging.
9.2Log Location
The log file is stored in the xt:Commerce log directory. Please make sure the path exists and it is writable by the webserver. (Default Path: {shopRootDirectory}/xtLogs/)
10Advanced Information
This section of the manual is for advanced usage of the module. The content is for advanced users with special requirements. Everything in this section is optional and not required for the daily usage of the module.
10.1Transaction Object
This section describes how to extract information from a transaction, if you need it for further processing. E.g. you require more information of the transaction for further processing an order in your ERP system.
The code snippets in this section assume your script resides in the root folder of the shop with the default shop folder structure.
$root_dir = dirname(__FILE__).'/'; define('_VALID_CALL','true'); define('_SRV_WEBROOT',$root_dir); include _SRV_WEBROOT.'conf/debug.php'; include _SRV_WEBROOT.'conf/config.php'; include _SRV_WEBROOT.'conf/database.php'; include _SRV_WEBROOT.'conf/paths.php'; include _SRV_WEBROOT._SRV_WEB_FRAMEWORK.'function_handler.php'; include _SRV_WEBROOT._SRV_WEB_FRAMEWORK.'database_handler.php';
require_once 'plugins/emsecommercecw/init.php'; require_once 'plugins/emsecommercecw/lib/EMSeCommerceCw/Util.php';
$transactionById = EMSeCommerceCw_Entity_Util::loadTransaction($transactionId); $transactionObject = $transactionById->getTransactionObject();