composer require wallee/oxid-6.0
If you don’t already have one, create a wallee account.
Download the extension.
Extract the files and upload them to the root directory of your store using FTP/SSH.
Run on the same path via terminal (required on oxid 6.10 upwards) this command to install the plugin:
composer require wallee/oxid-6.0
If the plugin still don’t work you need to run these commands:
./vendor/bin/oe-console oe:module:install source/modules/wle/Wallee ./vendor/bin/oe-console oe:module:install-configuration source/modules/wle/Wallee ./vendor/bin/oe-console oe:module:activate Wallee ./vendor/bin/oe-console oe:module:apply-configuration
Login to the backend of your OXID eSales store.
Navigate to Extensions → Modules and activate the wallee module.
You may wish to install the following extensions to enhance your and your customer’s experience:
FrontendOrderList This extension allows to restrict customer order overview based on transaction status. OrderListStatus This extension allows to restrict & sort admin order overview based on transaction status. The OXID eSales system only references orders with status New, Finished and Problems, while wallee references more states, see State graph.
Under Extensions > Modules > wallee, switch to the settings of the activated module and enter the wallee Space ID, User ID and Authentification Key that you can create an application user.
If you are using EE with multistore, the settings under Global Settings are shared over all stores. You may use different spaces for each store to configure different behaviours.
After saving the configuration, the payment methods are created in the OXID eSales store and the necessary webhooks are set up.
|Payment methods will only be available in your store once you assign them to shipping method(s). see Payment method configuration|
Optionally disable downloading invoice and packing slip. These settings allow customers to download the documents from their order overview in the OXID eSales frontend.
Optionally change the debug level which increases what information is logged in your /logs folder, see Error logging.
The main configuration is now finished. You should see the payment methods in your checkout. To view the payment method configuration in the backend of OXID eSales eSales go to Shop Settings > Payment Methods.
The wallee payment method configurations are synchronized automatically into the OXID eSales store. There are just a few payment method settings in the OXID eSales store under Shop Settings → Payment Methods.
To be available in your store, payment methods must be assigned to shipping method(s). This can be done as follows:
Navigate to Shop Settings → Shipping Methods and select the shipping method where the payment method(s) should be available.
Switch to the
Payment tab, and select
Assign Payment Methods.
Drag the wallee payment methods which should be available into the right column.
If you want to change the payment method description, title, logo, etc you need to do this in the payment method configuration. Changes will be synchronized automatically.
The Payment Process of wallee is completely standardized for every payment method you can process. This gives you the ability to simply add a payment method or processor without changes inside of your Magento configuration. An overview about the states and the payment processes of wallee can be found in the Payment Documentation.
In the following section we provide you an overview about how the wallee states are mapped into the OXID eSales State graph for orders.
OXID eSales only shows by default the order states
The order status
New contains all orders that are in state
The order status
Problems contains all orders that need your manual attention or are not considered to be ready for fulfillment (e.g
The order status
Finished contains all failed orders.
In order to map the states from wallee to the OXID eSales status, you should install the OrderListStatus plugin. You will then get more information about the order state in wallee.
Below you find a diagram that shows the state machine of OXID eSales for orders including additional information for the state transitions.
OXID eSales does not have a separate invoice entity. However, we track the payment state of an order. An order is marked as paid if the following conditions are fulfilled:
A transaction is in the state
The invoice in wallee has the state
You can capture, cancel and refund transactions directly from within the OXID eSales backend. Please note if you refund, void or capture transaction inside wallee the events may not be synchronized into OXID eSales.
You have the possibility for your transactions to have the payment only authorized after the order is placed. Inside the connector configuration you have the option, if the payment method supports it, to define whether the payment should be completed immediately or deferred.
In order to capture a transaction, navigate to Administer Orders → wallee Transactions, open the transaction and click on the
|When the completion is pending in wallee the order will stay in pending state.|
In order to void a transaction, open the transaction and click on the
|You can only void transactions that are not yet completed.|
You have the possibility to refund already completed transactions. In order to do so, open the transaction and click on the
Refund button. In case the payment method does not support refund, you will not see the possibility to issue online refunds.
You can make refunds based on product quantity. In order to do so enter the amount of products you wish to refund to your customer.
You can carry out as many individual refunds as you wish until you have reached the quantity of the original order. The status of the order then automatically switches to complete.
|It can take some time until you see the refund in OXID eSales. Refunds will only be visible once they have been processed successfully.|
As long as the delivery should not be done the state of the order will be in
wallee_Completed. This happens when the transaction in wallee
has not reached the fulfill state.
There are essentially two reasons why this can happen:
The transaction is not completed. In this case you have to complete the transaction as written above.
As long as we are not able to tell you if you should fulfill the order. The delivery decision is done automatically. If this does not happen within the defined time frame, wallee will generate a manual task which you should observe and follow the instructions. When there is a manual task we will also display it in the OXID eSales Backend.
You can find more information about manual tasks in our Manual Task Documentation.
Please note that captures, voids and refunds done in wallee are synchronized. However, there are some limitations. Inside wallee you are able to change the unit price and the quantity at once. This can not be done in the OXID eSales backend. We therefore recommend that you perform the refunds always inside the OXID eSales backend and not inside wallee. If a refund cannot be synchronized it will be sent to the processor but it could be that you do not see it inside your OXID eSales backend.
You can find more information about Refunds in wallee in our Refund Documentation.
In case the payment method supports tokenization you can store the payment details of your customer for future purchases.
In order to use this feature make sure that the One-Click-Payment Mode in your payment method configuration is set to
|Tokenization is not available for guest checkouts.|
The extension will log various unexpected errors or information which can help identify the cause of the error. You can find the logs on the server of your store in the /logs folder. You have the option to change the debug level which increases what information is logged in your /logs folder:
Error (Default): Logs unexpected errors only.
Debug: Logs more information helpful for debugging.
Make sure that you followed the Configuration section by stating your wallee space ID and application user’s access information in the OXID eSales backend. By saving the configuration form the synchronization of the payment methods and the set up of the webhooks are initiated.
If this does not solve the problem, it could be that you use a special fee or coupon module that we do not support. Try to disable this plugin and see if it helps. The payment methods are only displayed if the plugin’s total calculation matches the actual order total.
If you need help, feel free to contact our support.