| Payment API |
With these interfaces only payments can be made. Credit card, direct debit, prepayment, invoice and telephone are available as classic XML interfaces. Frontend-based eWallets, such as PayPal, are accessed via a URL.
| Risk API |
All offered risk checks can be used in any combination via this XML interface.
| Postback API |
The Notfication Postback API (Webhook) gives you real-time access to all relevant information about your transactions.
| Service-Order API |
In the service area, there are a large number of interfaces with which smaller functions can be executed. These interfaces are regularly extended.
| Phone & SMS API |
You can initialize automated calls or send SMS via our telecommunication API.
| Stats API |
All transaction data including status changes (e.g. cancellation) can be retrieved and read in with this function.
| Inkasso API |
The interface is used to transfer collection data to our system.
| Flexible-link |
You can theoretically decide anew which preconfigured combination of payments, risk checks and other services they want to use for each call. This allows a level of flexibility that is otherwise only possible when using backend interfaces.
| Easy-link |
The frontend is always called via the same link, i.e. the parameters cannot be changed. The user enters all relevant data, including the amount, on the frontend. The confirmation of a successful payment is made by e-mail or http-push to a defined address.
| CAP-Service |
The CAP service (Conditional Access Proxy) combines the payment window with access control.
The highlight is that all traffic is redirected via the CommDoo proxy. This enables CommDoo to allow the user access to the service or not. The CAP service cannot be used for classic shops.
| Partially Payment |
Partially mode separates the collection of sensitive payment data from the actual payment. In one-page checkouts payment data can be collected seamlessly. In multi-page checkout processes, the payment data can be entered at the beginning and the actual payment will be processed without redirects at the end.
| Payment Widgets |
Widget Payment is a perfect alternative for iframe solutions and offers seamless integration into the layout of your site. The payment form is displayed on your page and can therefore be adapted with your stylesheets.
|
Magento offers the possibility to manage several shops with their own catalogues and customer lists on domains. Magento won the 2008 Best New Open Source Project Award at the SourceForge.net Community Choice Awards.
|
The standard solution for xt:Commerce web shops, the xt:Commerce 3, is one of the world's leading shop software solutions with over 100,000 installations.
|
OXID eSales AG pursues a commercial open source strategy in which products are created at the height of time through close partnership with the online community.
|
osCommerce combines well-known and widely used open source solutions to provide a free and open development platform.
|
Gambio is used by more than 25000 companies and offers an all-in-one solution for your webshop.
|
Woo Commerce is a proven shop system plugin for Wordpress, which is characterized by high flexibility.
|
Shopware is a shop system developed in Germany since 2004 that can be operated in an open source or commercial version.
|
JTL offers professional shop solutions with an integrated merchandise management system.
| Webfrontend |
The CommDoo web frontend www.commpay.net is a full-fledged management tool with which you can not only retrieve statistics and detailed transaction data, but also perform a variety of actions such as bookings, cancellations, incoming payments, report cancellations. In addition, we provide you with professional reports for controlling and accounting.
| Desktop Application |
The CommDoo Desktop applications can be used to carry out direct debit and credit card settlements. In addition, collection orders can also be submitted in this way.
| FTP |
On request we can also provide you with an FTP interface.