OXID eSales Opayo (formerly SagePay) Payment Extension

Whether credit or debit card, eWallets or web-banking, with this module you can accept all these payment methods in your OXID eSales shop. All sellxed modules are also PSD2 compliant and support the Strong Customer authentication and 3DS 2.0. requirements.

The module links your OXID eSales shop to the payment system of Opayo (formerly SagePay). You receive a license of unlimited duration and are additionally granted 12 months of free e-mail and telephone support as well as access to all our updates and upgrades. For the development and improvement of the modules we are in active contact with Opayo (formerly SagePay). We trust our quality. If the module does not work in your shop, you get your money back!

Screenshots

This module has been discontinued and can no longer be downloaded. Also an existing license can therefore not be extended. Important to know for existing users: You can continue to use your plugin. However, as support and updates will no longer be provided, we recommend that you look for an alternative option as soon as possible. All information on the discontinuation of sellXed and alternatives for this module can be found here: Learn more

Product Description

Give your customers access to numerous new payment possibilities. Besides the known credit cards (Visa, Master Card, etc.) you can also integrate debit cards (Maestro, etc.) and eWallets (PayPal). A detailed list of the supported payment methods can be found further below.

All sellXed modules are based on SagePay V3.

Due to the integration of the Token System the customer's order process is greatly simplified. Once the credit card data has been entered it can be saved for later purchases. The storage occurs with Opayo (formerly SagePay) and is therefore fully PCI-compliant.

Opayo (formerly SagePay) Payment Extension also supports capturing, cancellation and refund. This means that you can process payments directly from the administration interface of the shop and no longer have to log into Opayo (formerly SagePay). This simplifies the payment processing a lot. Further information on the transaction manager can be found under payment processing (see below).

With the Server Integration the customer is redirected to the payment page of Opayo (formerly SagePay) for the completion of the payment process. In combination with the inFrame Integration the payment page can be loaded with the layout of the merchant's shop and the customer therefore does not realise that he has been redirected.

A detailed list of all features can be found under features.

We guarantee the functionality of the payment module. You gain 12 months access to all updates and upgrades released by us. The RSS-Feed informs you about the latest changes and that the new version is ready for download in your customer account. Furthermore, you receive one year free support in case you encounter problems during the integration.

The module includes a detailed installation manual which guides you step by step through the installation process. Optionally you can also order the installation service of customweb Ltd.

customweb is Approved Partner of Opayo (formerly SagePay). This guarantees you comprehensive functionality and smooth operation. The modules were developed in close cooperation with Opayo (formerly SagePay).

Your benefits:

Customweb looks back on long standing experience in the development of shop software. The module is continuously being refined in close co-operation with the Payment Service Provider. This has several advantages for you:

Access to updates and upgrades during the one year support period. You thereby ensure the functionality and compatibility to your shop-system and PSP.
Certified module: the payment modules were developed in close cooperation with the PSP.
Better support. We offer you 12 months support via telephone or e-mail. With the optional installation service we, furthermore, guarantee a fast integration into your system.
Increased security. Due to the integrated support service, possible security holes are eliminated immediately.
Transaction management through the shop: You no longer need to log into your PSP account to process payments. Captures, cancellations and refunds can be carried out in the administration interface of the shop.
Seamless integration. The support of Hidden Authorisation allows for a PCI-compliant processing of transactions in the background; without the customer being redirected to the payment page of the PSP (requires PCI DSS SAQ A-EP).

Software Features

Transaction manager - Process your payments directly from the back-end of your shop (capturing, cancellation, refund)
Unlimited time licence for one shop
Each payment method is integrated as an individual module. This enables specific settings for each payment method (payment zone, order status, etc.). Additional payment methods can easily be added.
The cart is saved during the session. In case of a cancellation or error during payment the shopping cart remains unchanged.
Easy switching between live and test mode
Payment methods are listed individually within the shop and can also be activated individually
Auto-detection of mobile themes
Easy to install. No changes have to be made to the existing code
Alias Manager (SagePay Token System)
SagePay Direct Integration
SagePay Server Integration

Requirements

SagePay contract
Oxid eSales from v6.x CE / PE

Payment Processing

Payment Page (Server)

After having confirmed the order the customer is transferred to the Payment Page of the PSP where he then enters the payment data. Once the payment has been effected, the customer is redirected to the merchant page.

Difference to Dynamic Template: The customer clearly sees that he has left the merchants website.

Difference to Hidden Authorisation: The customer is transferred to the PSP to enter his payment data in comparison to entering it in the shop.
IFrame Authorization (Server with IFrame)
Server Authorization (Direct)
Alias Manager / Token System

The customer's credit card data is saved during the payment process in the PSPs database. The storage occurs with the PSP and is therefore fully PCI compliant. An alias is created for the credit card data which can then be retrieved during the next purchase. Through this, the customer does not have to enter his credit card data again.
Cancellation

Payments can be cancelled directly from the shop. This means that the merchant does not have to log into the payment gateway in order to edit payments but can handle them directly via the shop-system.
Capturing

Payments can be debited directly from the back-end of the shop. This means that the merchant does not have to log into the payment gateway in order to edit payments but can handle them directly via the shop-system.
((SCREENSHOT))
Refunds

Payments can be credited directly from the back-end of the shop. This means that the merchant does not have to log into the payment gateway in order to edit payments but can handle them directly via the shop-system.
Update