This manual explains the installation, configuration and usage of the payment module for OXID and PostFinance. It is important that you strictly follow the described steps. Only by doing so, a secure usage in compliance with all security regulations can be guaranteed.

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

  • PSPID & Password. You receive these credentials from PostFinance after conclusion of contract. Our support staff is happy to help you acquiring a PostFinance contract if you do not yet have one.
  • OXID payment module from sellxed.com/shop
  • FTP access to your server
  • Login credentials for your shop

1.1Procedure of the Installation

  1. Configuration of the administration interface of PostFinance.
  2. Upload of the module
  3. Configuration of the basic settings of the payment module
  4. Configuration of the payment methods
  5. Carrying out a test purchase by means of the attached test data at the end of this document
  6. If the test was successful, copy all data from your test account into the PostFinance live account.
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 PostFinance might not get through to the shop.

2Configuration PostFinance - Back-End

For the configuration, log into the PostFinance back-end:

The settings carried out on the following pages are a precondition for the configuration of the main module.

The configuration of the settings is done under Configuration > Technical Information. In the following chapter the chapter titles correspond to the tabs in the back office of PostFinance. For some parts screenshots will be added for a more precise illustration. Should a specific setting not be mentioned then it has no importance for the configuration of the payment module and can be ignored by you as such.

2.1Tab: Global Transaction Parameters

Under the tab Global Transaction Parameters you define the basic settings for the processing of transactions.

2.1.1Default operation code and default data capture procedure

We recommend choosing Sale and "Automatic data capture by our system at the end of the day". All incoming payments will be directly processed and debited. If you are using transaction management and deferred capturing we strongly advise to use these settings. In case you have saved different settings in the module, then the module's settings will overwrite those of the PostFinance.

2.1.2Payment Retry

We recommend entering 10.

2.1.3Processing for Individual Transactions

We recommend the option "Online but switch to offline when the online acquiring system is unavailable"".

2.2Tab: Global Security Parameters

Here you define the security parameters for the interaction between your shop and the gateway of PostFinance.

2.2.1Hashing Method

The sellxed payment modules support all hashing methods. In order for the module to function, it is crucial that the settings saved with PostFinance correspond to those made in the back-end of your shop.

In order to guarantee a smooth processing of payments, we recommend the following hashing methods:

  • Each parameter, followed by the pass phrase. It may be that this parameter is not visible in your shop. In this case it is transmitted automatically.
  • Hash Algorithm = SHA 512
  • Character Encoding = UTF-8
Figure 2.1: Configuration of the SHA-Hash.

These settings must be identical to the settings in the main module (cf. Configuration of the main module). Please note that the character encoding in our modules is set to UTF-8 per default and cannot be changed.

2.3Tab: Payment Page

The checkbox under Cancel Button should be ticked. The field under Back Button Redirection can be left empty.

2.4Tab: Data and Origin Verification

The tab Data and Origin Verification defines security elements concerning the transmission of data and the loading of the payment page.

2.4.1Checks for e-commerce & Alias Gateway

The first box under "URL of the merchant page" can remain empty.

The box "SHA-IN pass phrase" is a security element of the payment verifying its authenticity. Therefore it is important that you use the same pass phrase in the back end and in the shop.

Customweb SHA-String Generator

Please note that only ASCII characters may be used for SHA pass phrases. Please use our SHA pass phrase generator so that you do not enter invalid characters.

2.4.2Checks for PostFinance DirectLink and PostFinance Batch (Automatic)

DirectLink allows you to use the Hidden Authorisation (Alias Gateway) as well as the direct debiting of transactions within your shop. If you have activated DirectLInk in your account and wish to use this feature, enter the same SHA-IN pass phrase in the box "SHA-IN pass phrase" as above.

Further information on the configuration of DirectLink can be found under Configuration Hidden Authorisation.

2.5Tab: Transaction Feedback

In the tab Transaction Feedback the response of PostFinance to the shop is controlled.

2.5.1HTTP Redirection in the Browser

The parameters in the transaction feedback determine the processing in the shop after payment has been completed. However, the four fields for "HTTP Redirection in the Browser" can remain empty because they will be configured through the settings of our module.

Un-tick the option "I would like PostFinance to display a short text to the customer on the secure payment page if a redirection to my website is detected immediately after the payment process."

2.5.2Direct HTTP-Server-to-Server-Request

  • The "Timing of the Request" must be set to Online but switch to a deferred request when the online requests fail. As "Request Method" you must select "POST".
  • In the section General make sure that the Option: "I would like PostFinance to display a "processing" message to the customer during payment processing." is un-ticked too.
  • Copy here the URL that is listed in the module backend under: Extensions > PostFinance > Setup.

URL on which the merchant wishes to receive a deferred HTTP request, should the status of a transaction change offline.

For the Transaction Feedback please enter the URL that is generated in the main module. More information can be found under the section Transaction Feedback

All orders have the status 'Pending'

Should you notice during the tests that orders are not registered in the shop and that no confirmation email is sent, this might be due to a failure of the transaction feedback. Make sure that your firewall is not blocking any request coming from PostFinance.

Figure 2.1: Configuration of the feedback URL for the HTTP-Feedback.
Deferred Requests und Time Out

PostFinance sends the notification requests with a time out of 20 sec. Should your shop not respond to the HTTP Request within this time, a time out error will be sent. If you set the option to Online but switch to a deferred request when the online requests fail the request will be retrieved four times in ten minute intervals.

Please note that, depending on your PostFinance subscription, it is possible that the only option available is Always online (immediately after the payment to allow customization of the response seen by the customer). In this case, always select this option.

2.5.3Dynamic e-Commerce Parameters

With this option you control which parameters are sent in the response from PostFinance. In order for payments to effectively be evaluated in your shop, all necessary parameters must be sent. It is possible that you have other options available to select. Just make sure that you move every parameter from available to selected except for the following:

  • PM
  • CN
Figure 2.1: Configuration of the Dynamic E-Commerce Parameters. Your selection may look differently depending on your subscription with PostFinance.

2.5.4Dynamic Parameters

With this option you control which parameters are sent in the response from PostFinance. In order for payments to effectively be evaluated in your shop, all parameters must be sent. It is possible that you have other options available to select. Just make sure that you move every parameters from available to selected.

Figure 2.1: Configuration of the Dynamic Parameters. Your selection may look differently depending on your subscription with PostFinance.

2.5.5Security for Request Parameters

The box "SHA-OUT pass phrase" is an additional safety mechanism for payments. Here too must the entered pass phrase be identical to the one in your shop. However, please make sure that your SHA-OUT pass phrase differs from the SHA-IN pass phrase. .

Customweb SHA-String Generator

Please note that only ASCII characters may be used for SHA pass phrases. Please use our SHA pass phrase generator so that you do not enter invalid characters.

2.5.6HTTP Request for Status Changes

You have the option to be informed about status changes by PostFinance directly. This feature is especially useful when a payment has an uncertain status because the acquirer system could not be reached. The payment status will be updated automatically. Furthermore this feature allows you to capture payments inside PostFinance and have synchronize them with your shop

In order to use this feature you will have to select the option For each offline status change (payment, cancellation, etc.).. Afterwards just copy the URL into the field that is displayed in the Setup of your Main configuration: Extensions > PostFinance > Setup.

Enter the URL shown there into the field 'URL on which the merchant wishes to receive a deferred HTTP request, should the status of a transaction change offline.'

Figure 2.1: Enter the URL from the Setup of the Main Configuration.

2.5.7Dynamic Parameters

Move all parameters from available to selected.


You can now find the option template via Configuration > Template. The Dynamic Template enables you to design the payment mask for the credit card data so it matches your web shop. Should the field for the dynamic template not be visible, please contact PostFinance. It may be that you have to activate additional options in your account.

For the usage of the dynamic template, please save the following settings:

  • Enable JavaScript on template: 'No'
  • Our modules do not allow "usage of static template". So click 'No'
  • Allow usage of dynamic template: 'Yes'
  • In case you are using the dynamic template, enter the host name, i.e. https://Your-Shop.com in the lower box. The upper one must remain empty.
Figure 2.1: Configuration of the Dynamic Template.
Dynamic Template

Please note that you require an SSL certificate for the usage of the dynamic template. Otherwise the CSS-Resources will not be reloaded in certain browsers which might lead to layout issues.

The activation of the dynamic template in the shop is explained here.

2.7Hidden Authorisation, Ajax Authorization (FlexCheckout - Hosted Tokenization Page), External Checkout & Alias Manager


For the usage of the Hidden Authorization, Ajax Authorization (FlexCheckout), Alias Manager or External Checkout during the payment processing, certain adjustments are necessary in the back-end of PostFinance. Please check first if the options are activated in your account under Account > Your Options.

Figure 2.1: Make sure to activate the OPC and DPR options.

If an option is not available please contact PostFinance.

Options and their Meanings:

  • For the usage of the Hidden Authorization you require the option OnePageCheckout (OPC).
  • For the usage of the Ajax Authorization (FlexCheckout) you require the option OnePageCheckout (OPC) and DirectLink (DPR).
  • If you additionally want to use the Alias Manager, you also need the option Alias Manager (RECX).

In case these options are not be available, please contact PostFinance directly.

2.7.2Setting Up an API-User

If you want to use the features of the transaction management or the hidden authorization (Alias Gateway) you will need to set up an API user as described herafter:

Go to Configuration > User Administration and click on 'New User'. Choose a User ID and insert a user name of your choice and your e-mail address. Select Administrator without user manager as a profile. It is furthermore important that you select the option Special user for API (no access to the administration). If you do not see this option, you will need to let PostFinance activate the option DirectLink for your account.

Password of the API-User

The User ID and the API-user password may only contain letters and numbers as wel as special characters. The following special characters are not allowed: & (Ampersand), " (double quotes), ' (single quotes)

Note down the access data. They will have to be inserted in the respective place in the configuration of the main module.

2.7.3Usage of External Checkouts

For the usage of external checkouts there are additional options required. External checkouts, such as MasterPass are payment methods, which offer the possibility to transfer addresses automatically.

The usage of the external checkouts asks for the option Direct Link and for the activation of payment method in your account.

For the performance of the payment method, you have to make sure that under Technical Information > Transactionfeedback in the section Direct Link all parameters selected are shifted

Figure 2.1: Response Parameter for Direct Link.

3Module Installation and Update in the OXID 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 OXID Shop

The configuration consists of two steps. The first step is the configuration of the main module with all the basic settings (cf. Configuration of the Main Module). During the second step you can then carry out individual configurations for each payment method . This allows for full flexibility and perfect adaptation to your processes.

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

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

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

4.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 PostFinance configuration. The URL to be entered can be found in your OXID Shop under: Extensions > PostFinance > Setup > Setup

4.3Configuration of the Payment Module

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

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

By clicking on PostFinance Configuration, you can save different settings for each payment method and thereby optimally adapt the payment methods to your existing processes

Payment Methods not Displayed in the Checkout

Please check if you have attributed the payment method to the available countries as well as customer groups in case a should payment method not be visible in the checkout.

4.4Shop 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 PostFinance based on the shop ID.

4.5Order Prefix

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

4.6Selecting 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 PostFinance 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 PostFinance for further information or switch to another authorization method.

4.7Direct 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 PostFinance and the module

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

4.8Uncertain Status Status

You can specifically label orders for which for example no 3D-Secure verification nor any other security mechanism was carried out. This allows you to manually control the order before shipment.

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

4.10Multi-Shop Set-Up

The payment module is designed for the usage of one PostFinance 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.

4.10.1Usage of several independent OXID shops

In case you wish to connect several independent shops to one contract with one contract with PostFinance, you require a sellxed payment module for each shop as well as the corresponding multi-shop module which you will find directly by the payment module.

  1. Extract the multi-shop module and open the file "router.php"
  2. Enter a shop ID of your choice in the box "Shop ID" within the main configuration of the module (e.g. shop_a and shop_b)
  3. Enter the following line into the corresponding place within the file router.php of the multi-shop module (for each shop shop_a and shop_b):
    $redirect['shop_a'] = 'http://www.your-shop.com/?cl=postfinancecw_process';
  4. Enter the URL below (instead of the URL mentioned above) under the point "Feedbacks" in the back-end of PostFinance: http[s]://yourshop.com/router.php
  5. Copy the file router.php into the main directory of your shop

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

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.

5.3Usage Hidden Authorisation / Alias Gateway

You have the possibility of processing credit cards without redirection to the payment page of PostFinance.

In order to be able to use this feature, you must first carry out the steps listed under Hidden Authorisation / Alias Gateway and create an API-User.

You can then activate the authorisation method 'Hidden Authorisation' for the payment methods of your choice. This procedure requires you as a merchant to fulfill the PCI-SAQ-A-EP. At no time is any credit card data saved on your server. Contact your Acquirer for more information about the SAQ and the requirements.

5.4Credit Card

For the integration you have the choice between the pre-selection in the shop; i.e. the customer chooses the card type already in the shop; or a generic integration in which case the customer only sees the option 'credit card' as a payment method and then chooses the card type on the payment page PostFinance.

Figure 5.1: No pre-selection of the card type - the type will then be chosen on the payment page.
Pre-Selection of the Payment Method

We recommend choosing the option pre-selection. This allows you to configure individual settings for each payment method and add payment fees to the various methods.


You can process PayPal directly via PostFinance. In order to do so, however, some adjustments to your PayPal account are required. Please carry out the following steps:

  1. Activate the payment module in your shop
  2. Make sure that the payment method is activated in your PostFinance account
  3. The API adjustments must be carried out in your PayPal account. The various steps are explained in the "PayPal Express Checkout Integration Guide". This document can be found in your PSP account under: Support > Integration and User Guides > Technical Guides > PostFinance PayPal Express Checkout Integration Guide .

5.6Usage of the Ajax Authorization (FlexCheckout)

You have the possibility of processing credit cards without redirection to the payment page of PostFinance.

In order to be able to use this feature, you must first carry out the steps listed under Hidden Authorisation, FlexCheckout (Hosted Tokenization Page), External Checkout und Alias Manager and create an API-User.

You can then activate the authorisation method 'Ajax Authorization (FlexCheckout)' for the payment methods of your choice. At no time is any credit card data saved on your server.

6The Module in Action

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

6.1Useful Transaction Information on the Order

In the tab PostFinance Transactions you can find an overview over all the most important information of an order's transactions. Among others, this information allows for the definite attribution of the orders to their corresponding transaction, seen in the back-end of PostFinance.

Figure 6.1: Transaction Information in OXID

6.2Usage of the Alias Managers / Token Solution

With the Alias Manager, your customers can securely save their credit cards with PostFinance 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 6.1: Alias Manager Integration in OXID eSales
Alias Manager Options

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

6.3Dynamic Template

We provide a standard skin for the usage of the dynamic template for all sellxed modules. You can activate the option by setting the option "Dynamic Template" to "Use Shop Template" in the main module. Please make sure that all settings specified under Template have been carried out in the back-end of PostFinance.

The Dynamic Template allows you to load the Payment Page of PostFinance in the layout of your shop. The customer, therefore, does not notice that he or she has been forwarded to the website of PostFinance. The template dynamically adjusts to your shop template. This, furthermore, allows you to easily integrate Mobile Skins (cf. Screenshots).

The Dynamic Template requires an SSL Certificate

In order for the Dynamic Template to work correctly with all browsers, you require an SSL certificate in your shop.

Figure 6.1: Example: The skin adapts to the layout of your shop.
Figure 6.1: Example: Dynamic Template with mobile skin

6.4Capturing / Cancelling of Orders

Teh sellxed modules allow you to capture payments directly from within Oxid eSales without having to log into PostFinance.

6.4.1Capturing Orders

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

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

Capturing of Orders in the Back-End of PostFinance

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

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

Figure 6.1: Capturing of Orders in OXID eSales.
Partial Capturing

Please find out if the capturing of partial amounts is supported by your PostFinance contract. If this is not the case, it might happen that no further captures can be carried out.

6.4.2Cancelling Orders

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

6.5Refunding Orders

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

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

Figure 6.1: Refunds in OXID eSales for PostFinance.
Maximal Refund

With our sellxed modules it is not possible to refund more than 100% of the originally authorised amount.

6.6Set-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 OXID Cron engine. Especially the update function allows you to automatically retrive additional information or changes of your order directly via the API of PostFinance. Please note it could be that in order to use the update feature it may be necessary that PostFinance 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:


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.


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:
Credit Card
Card number
3750 0000 000 0007
Expiry Date
American Express
Card number
5399 9999 9999 9999
Expiry Date
Card number
4111 1111 1111 1111
Expiry Date
VISA (Without 3-D Secure Check)
Card number
4000 0000 0000 0002
Expiry Date
VISA (With 3-D Secure Check)
American Express
Card number
3750 0000 000 0007
Expiry Date
American Express
Card number
5399 9999 9999 9999
Expiry Date
Card number
4000 0000 0000 0002
Expiry Date
VISA (With 3-D Secure Check)
Card number
4111 1111 1111 1111
Expiry Date
VISA (Without 3-D Secure Check)

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 PostFinance 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 OXID

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

10Error Logging

The module will log different unexpected errors or information depending on the configured level. If there is any issue with the module, this log can help identify the cause.

10.1Log Levels

You can configure the log level in the PostFinance settings.

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

10.2Log Location

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

11Advanced Information

This section of the manual is for advanced usage of the module. The content is for advanced users with special requirements. Everything in this section is optional and not required for the daily usage of the module.

11.1Transaction Object

This section describes how to extract information from a transaction, if you need it for further processing. E.g. You require more information of the transaction for further processing an order in your erp system.

The code snippets in this section assume your script resides in the root folder of the shop with the default shop folder structure.

Have OXID initialized in your script, this is required for the database connection.
require_once dirname(__FILE__) . "/bootstrap.php";
Include the module module classes.
require_once 'modules/customweb/postfinancecw/classes/PostFinanceCwHelper.php';
Now you can load the transaction and then extract the transactionObject.
Load the transaction by Id:
$transactionById = PostFinanceCwHelper::loadTransaction(transactionId);
$transactionObject = $transactionById->getTransactionObject();