ProxyPay3
The ProxyPay³ SSL Gateway processes the payment using the specific protocol needed for a particular payment method. To process the transaction, the interface with the host is then implemented in the ProxyPay³ module
English
Supported Technologies
Windows XP/2000/NT ,
HP/UX,
Solaris/Sun OS
Web-Based (Browser)
Click on a technology to view similar products within this category.
Pricing
System, Module, Other
sales@element.be
++ 32 51 248742
Additional Product Information
To handle online transactions, Element has built ProxyPay, a complete system, allowing to verify transaction data, handle the transaction and pass all post processing details. , ProxyPay³ is the new generation, JAVA-based implementation of the ProxyPay environment, designed to run on a UNIX platform using an Oracle database. It implements the POS and Gateway functionalities for global secure payment on the Internet., ProxyPay³ has been developed with following targets in mind:, . Easy to implement for the Merchant, using his own shopping system (standard protocol http(s) - no API), . Modular system on the gateway side which permits fast integration of additional features/payment methods, . Link with the Merchant?s ERP system using a confirmation POST scheme., . Proven security when using the validation scheme., . Customisation possibilities for gateway (Back Office / Payment modules) and Merchant (Payment templates)., The Architecture, A Merchant/Shop Builder integrates the online payment with a simple POST to the ProxyPay³ SSL Gateway through certain basic parameters (such as amount, currency, merchant reference for the order, a MerchantID, and other variables that can be used as required). Once ProxyPay³ has received the request, it checks the relevant parameters and sends a payment template to the Customer?s browser. If required, this payment template can be personalised by the Merchant to take the appearance of its own shopping environment., Depending on the chosen payment method (credit card number etc.)the customer has to enter his payment information. Additional payment methods to be supported can also be implemented in ProxyPay³, by installing the modular payment components. Once ProxyPay³ has received the customer payment data, an optional validation check is executed on the Merchant site, before processing the transaction. The optional validation check is executed by posting the received order data (amount, currency and Merchantreference) back to a Merchant URL, which then validates the data. In this script a Merchant/Integrator can verify the received parameters with the data, found in its order database. If the data match, then the script returns an ?OK? to ProxyPay³ and the payment is processed. If the data do not match the values found in the Merchant database, then the customer is redirected to a page on the Merchant site which handles rejected payments. If the payment is successful, a redirection is made at the Customer side to a page handling the successful payments (i.e.: showing the order info and status)., The Merchant is notified by means of the notification service (a daemon). This module posts the data for successful payments to a Merchant URL, which handles successful payments, and eventually executes some customised tasks, such as a link with the ERP system, update of a stock database, send an email to the Customer... In addition, the Merchant receives an email as an order confirmation. This POST and email can be customised to support the parameters needed by the Merchant/Integrator., A Merchant is able to process/view the payments using the ProxyPay³ Back Office. This Back Office is implemented using a scripting language allowing the execution of database statements in combination with standard HTML commands, but with security implemented. This way, no data can be shown if the required level has not been set (the access level is set when logging on to the Back Office system). The Back Office authentication scheme can be implemented as required on ProxyPay³, but is a standard user/password authentication scheme. Since no modules have to be installed on the Merchant side, the implementation can be done for any OS/Web server combination. The notifications (confirmation POST, confirmation email) and the validations can be customised to support the variables needed by the Merchant/Integrator, by using templates. The templates contain static data and placeholders for data, which should be dynamically updated., The ProxyPay³ SSL Gateway processes the payment using the specific protocol needed for a particular payment method. To process the transaction, the interface with the host is then implemented in the ProxyPay³ module (daemon). Payment modules can be integrated as required by the Customer., The modular architecture of ProxyPay³, implemented for UNIX platforms based on an Oracle database, provides a modular and scalable solution for POS and Gateway implementations. Using a modular architecture allows easier integration of new functionalities, and straightforward customization of existing ones. All modules can also function independently of each other, which makes it easier and safer to add new components, without interfering with the existing ones., Proxy Pay³:, ? Supports legacy systems and interchange network for several protocols to Acquirer , ? Supports local variations in credit card data, such as absence of Luhn check digit (ISO 7812), CVC2/CVV2;, ? Provides Payment Front-End and Administrator/Merchant Back-Office;, ? Supports single Merchants and Shopping Malls;, ? Enables Merchant aggregation (Shopping Mall) for administration/reporting purposes;, ? Enables single payments, direct sale payments, recurrent payments and installments;, ? Enables multi-currency support;, ? Ensures easy implementation for the Merchant;, ? Provides simple interface to the Merchant?s shop;, ? Allows customization of the payment pages to bring look and feel of the Merchant?s site;, ? Enables multi-language support;, ? Enables multi-channel support;, ? Enables basic payment security, such as floor limit, card detail validation, local stop list per Merchant/Mall/URL;, ? Provides Web-based interface for Merchant operations and post-processing;, ? Enables future implementation of other credit card payment methods, such as VISA 3D-Secure, Mastercard/Europay UCAF/SPA;, ? Uses the standard protocols (http/s, SSL/TSL, JDBC/ODBC, etc.);, The Merchant?s Back Office allows to, ? View transactions (for some or all payment methods), ? Process transactions (capture, cancel, refund, credit, reauthorisation), ? Create reports and output these reports to a file., ? Filter transactions based on their state, timestamp, reference, ? Block cards or range of cards, The Administrator?s Back Office has all the functionalities, which were implemented, in the Merchant?s Back Office; it also permits activities on transactions for all Merchants and supplementary functionalities such as adding Merchants, configuring the payment methods?. , The Administrator?s Back Office allows you to define multiple levels of administration. This enables you to allocate responsibilities to different types of users., The levels supported are:, ? Helpdesk Level 1: provides the possibility to VIEW a Merchant?s configuration and transactions., ? Helpdesk Level 2: provides the possibility to add, delete and modify a Merchant?s configuration and to view and process transactions., ? Administrator: has all the options of Helpdesk Level 2, as well as the possibility to configure system configuration settings., Some of these functions are obtained by using the scripting language, while others are implemented as commands in the interface itself. , Functions that must be implemented in the interface are, ? All functionalities as in the Merchant?s Back Office, ? Add/Delete/View/Edit Merchants., ? Add/Delete/View/Edit Administrators/Operators, ? Unlock Merchants, ? Unlock Administrators/Operators, ? Add/Delete payment methods for Merchants and configuration of the payment method., ProxyPay³ supports:, ? Payment processing:, ? Authorization, ? Capture (full or partial), ? Direct sale, ? Installments, ? Payment post-processing:, ? Refund, ? Credit, ? Cancel