- No pages viewed yet
This installation guide shows the step-by-step installation of the plugin to your installed shop system on your web server. Please test your online shop and the configuration of the plugin on a test system before installing the plugin on your production system.
Upload the zip file containing the Wirecard Checkout Seamless plugin to the document root of your OXID Shop installation and unzip the file. The zip-archive already contains the directory path allowing the plugin to be stored automatically in the right folder.
If you need to unzip the file on your own computer and then upload the plugin, please maintain the directory structure which already exists in the zip file.
To enable the module navigate to “Extensions” → “Modules”, select “Wirecard Checkout Seamless” and click on “Activate”.
Next select the “Settings” tab on the same page.
For a basic configuration enter your customer ID, shop ID and your secret and set the URL to imprint page. You can additionally go over the settings and configure the plugin according to your requirements. Please refer to the section advanced configuration for a more detailed description about the configuration possibilities.
To enable the payment methods navigate to “Shop Settings” → “Payment Methods”.
Each payment method you want to make available to your consumer needs to be activated by clicking on the payment method, selecting “Active” and clicking on the “Save” button.
“Assign User Groups” in the “Main” tab and “Assign Countries” in the “Country” tab allows you to enable specific payment methods for specific user groups and countries.
Additionally the payment methods need to be assigned to your shipping methods at “Shop Settings” → “Shipping Methods”. Select each shipping method, switch to the tab “Payment” and click “Assign Payment Methods” and assign those you want to make available when your consumer selects the respective shipping method.
As described in Step 2 the plugin allows for some additional customization.
The shop plugin fulfills the requirements for credit card payments set forth in the PCI DSS v3.2.1 which is mandatory for all e-commerce merchants as of January 1st, 2018. Following this standard, a merchant's web site(s) is not allowed to itself handle sensitive credit card specific data.
Please visit PCI DSS SAQ A Compliance for Wirecard Checkout Seamless for more information and details.
To this effect, some new parameters need to be set in “Shop Settings” → “Wirecard Checkout Seamless Settings” → “Plugin Settings”:
“SAQ A compliance” is not selected by default, which means that the rather stringent SAQ A-EP is applicable for your online shop and Wirecard Checkout Seamless will not be integrated with the “PCI DSS SAQ A Compliance” feature.
To customize the iframe input fields when using the “PCI DSS SAQ A Compliance” feature, enter a full URL to a CSS file on your server into the “Iframe CSS URL” field.
Display card holder field if you wish to display the card holder field for “PCI DSS SAQ A Compliance” and correspondingly the other credit card fields.
Automated deposit: To prevent the expiration of uncaptured payments you may select this feature which enables an automated deposit and day-end closing of payments. Please contact our sales teams to enable this feature. If you select this feature without previous enabling you will get an error message.
Fraud Prevention Suite: For a description of this feature please refer to the request parameter description. Please contact our sales teams to enable this feature. If you select this feature without previous enabling you will get an error message.
Your consumer gets an error message regarding a missing CVC after entering the credit card number, even if the option for the corresponding check is not activated?
The CVC has to be used for all types of cards where a CVC is required (like Visa or Mastercard). If you activate that check in the back-end of your shop, only card without CVC can be used by your consumers (like Maestro or UATP).
What about using Zend Guard Loader?
OXID eShop Enterprise and Professional editions run only properly within Zend Guard Loader (former Zend Optimizer) but is not needed for Community edition. You can find more details regaring this at Zend Guard Loader.