=== Flitpay Payments for WordPress === Contributors: Flitpay, Wearetech Tags: flitpay, payments, credit card, africa, mobile money, wearetech Requires at least: 3.0.1 Tested up to: 3.4 Stable tag: 4.3 License: GPLv2 or later License URI: http://www.gnu.org/licenses/gpl-2.0.html Add high conversion Mobile Money payment forms to your WordPress site in a few minutes. == Description == In a few simple steps you can start accepting mobile money payments with Flitpay Plugin on your WordPress site. Flitypay continually tests and optimizes their checkout forms to maximize customer conversion. Flitpay is an API developped by wearetech.fr. It only works in a few country in Africa, please check the list on flitpay.com **What is Flitpay?** *" Flitpay is an embeddable mobile money payment form for desktop, tablet, and mobile devices. It works within your site—customers can pay instantly, without being redirected away to complete the transaction."* If accepting mobile money payments quickly and painlessly with little setup time is what you're looking for, this plugin is for you. For the moment, Flitpay is not designed to integrate with more complex like dynamic shopping cart. That's it. **No other plugins required – No PRO VERSION IT’S ALL FREE. ** = VERSION FEATURES = * Unlimited payment forms * Mobile responsive Flitpay Checkout overlay * Display brand or product image in overlay * Custom shorcodes fields * Custom amounts - let customers enter amount to pay * Optionally collect customer shipping address * Email support with a 72-hour response time during business days == Installation == Before installing, be sure that you have created your account on our website flitpay.com or http://flitpay.herokuapp.com (bêta version). The first thing to do is to get your free account. Flitpay is set for two environment : Development and production environment. Your registration completion will give you two access key (one private and one public key) for development environment. You'll generally use your public key for Flitpay's API settings, and your private key to initiate payment from the back of your application. Later you'll need to activate your account to get access to your production keys. Extremely important : This Plugin will not work if you dont have a regular account in our books. [Install a Plugin using WordPress Plugin Search] The easiest way of installing Flitpay is to use the plugin search. First thing you need to do is go to your WordPress admin area and click on Plugins » Add New, search for Flitpay and then install it. [Install a Plugin using the WordPress Admin Plugin Upload] First, you need to download the plugin from the source (a zip file - We will publish the link later). Next, you need to go to WordPress admin area and visit Plugins » Add New then Upload the plugins. == Frequently Asked Questions == = Where's your plugin documentation? = http://flitpay.herokuapp.com/documentation Find our docs at http://flitpay.herokuapp.com/documentation = What are the system requirements? = http://flitpay.herokuapp.com/documentation SSL is required on live checkout pages, and we recommend staying current with both PHP and WP for security reasons and PCI-DSS compliance. = Can I get notified by email of new releases? = hello@flitpay.com [Subscribe here] = How do I contribute to Flitpay ? = hello@flitpay.com [Subscribe here] We'd love your help! Here's a few things you can do: hello@flitpay.com * [Rate our plugin](https:/ * Report bugs (with steps to reproduce) or submit pull requests [techinical.support@flitpay.com] * Help add or update a [plugin translation](techinical.support@flitpay.com) == Privacy == We do not share your Information about a financial transactions (including the amount of assets), positions held in stocks or funds, outstanding debts, and purchases to any third party. == Changelog == = 0.1 = *Uploaded version == Upgrade Notice == hello@flitpay.com == Screenshots == 1. This screen shot description corresponds to screenshot-1.(png|jpg|jpeg|gif). Note that the screenshot is taken from the /assets directory or the directory that contains the stable readme.txt (tags or trunk). Screenshots in the /assets directory take precedence. For example, `/assets/screenshot-1.png` would win over `/tags/4.3/screenshot-1.png` (or jpg, jpeg, gif). 2. This is the second screen shot