User Manual/Administration Interface/Service list

Services explained
The service panel is dedicated to the delivery and payment options that should be available during the checkout process. A service item in fact configures the delivery or payment provider which are responsible for the further handling of the order resp. the payment.

Delivery
During the checkout process, the customer might be able to choose between several delivery options, e.g. UPS, TNT, etc. and each delivery option can have its own description, picture and price. You can add as many delivery options as you like.

The second part is that every delivery option needs a delivery provider configured with the necessary parameter this delivery provider requires. A delivery provider implements the handling of the order after the payment was successful. This can be either a completely manual handling, a transfer of the order to the logistic partner or an automated process for providing a customized download file to the customer. Everything that can be implemented in an algorithm is possible within a provider.

Payment
Like for the delivery, customers can usually select one of the payment options provided by the shop owner. Similar to the delivery options, payment options can also have their own description, picture and even price.

For each payment option there must also be a payment provider configured that will care about the payment process. You can distinguish two different types of payment processes: Local and remote ones. A local payment process collects the required payment data (if there is any additional data necessary at all) and stores it locally in the shop system. For a remote payment process, the provider redirects the customer to a payment gateway which handles the payment and notifies the shop system about the result of the payment process (usually success or failure).

Extensions implementing payment providers are available, especially those using payment gateways to handle payments of customers.

Note: Please don't use any payment provider that stores credit card details locally in the shop system as long as you aren't certified as PCI-compliant. For more information take a look at the website of the PCI Security Standards Council.

Decorators
A decorator can add additional features on top of an existing delivery or payment provider only by configuration. For example, the shipping costs depend on the weight of the products and have to be calculated dynamically based on this value. As each delivery option can have its own price (resp. shipping cost), the decorator can sum up the weight, calculate the shipping costs for this weight based on some rules and replace the shipping cost value of the order by the new value. This does also work for payments with variable costs per transaction.

For an example how to configure a decorator please have a look at the service details page.

List all service items


The list view provides a paged list of all available delivery and payment options in the system, which can be filtered by various criteria. The most important columns are shown by default but the list of columns can be adapted via the list header. Delivery and payment options can be added, edited or deleted either via using the button in the menu or by using the context menu which is shown if you right-click into the list. A double click also opens the detail view for editing the delivery or payment item.



Manual
Completely manual handling of orders without any notifications. It only sets the status of the order to "in progress". This service requires no configuration.

Default
XML based transfer of orders to a web service understanding the content of the XML.


 * url (required) : URL of the web service where the order XML should be sent to and which understands the sent XML, e.g. "https://localhost:443/order.php".


 * username (optional) : The user name if authentication is required to use the web service.


 * password (optional) : The secret password if authentication is required to use the web service.


 * ssl (optional) : To allow self-signed SSL certificates, this option must be set to "weak".


 * project (optional) : User-defined name that will be added inside the tag of the XML.

DirectDebit
If you want to offer payments via an automatic bank transfer from the bank account of the customer, you should configure this payment service provider. The customer is asked for the necessary details like bank name, bank account, etc. which are stored along with the order. This service doesn't have any options.

PayPalExpress
Payments via PalPal are available by the PayPalExpress payment service provider. It provides all possibilities PayPal is offering. The required configuration options are:


 * paypalexpress.AccountEmail : The e-mail address of the account that will receive the money, usually the one you've used for registration
 * paypalexpress.ApiUsername : User name of the account that should be used for the automatic communication with the shop. This is not the name of your own user account!
 * paypalexpress.ApiPassword : The password you have assigned the the API user name. This is not the password of your own user account!
 * paypalexpress.ApiSignature : The shared secret that is created by PayPal for the API user

PrePay
Used for payments that must be done in advance and before the delivery of the ordered products is started, like a bank transfer in advance. This service doesn't have any options.

PostPay
Useful for all payments where the customer pays after he placed his order e.g. payment by invoice or cash on delivery. This service doesn't have any options.

<< Previous: Plugin details | Next: Delivery and payment details >>