Horacio Tellez
f7b8f07501
Changing the name of model payment.acquirer to payment.provider and everything that it touches. It is technically incorrect to use the term "acquirer" for systems that only provide a service of payment. After this commit the model payment.acquirer and all related to it will be renamed to payment.provider. Task - 2842088 closes odoo/odoo#90899 Related: odoo/upgrade#3542 Related: odoo/documentation#1981 Related: odoo/enterprise#27131 Signed-off-by: Victor Feyens (vfe) <vfe@odoo.com>
Flutterwave
Implementation details
Supported features
- Payment with redirection flow
- Tokenization
- Several payment methods such as credit cards, M-Pesa, and others.
- Webhook.
In addition, Flutterwave also allows to implement refunds and pre-authorizations.
API and gateway
We choose to integrate with Flutterwave standard as it is the gateway that covers the best our needs, out of the three that Flutterwave offers as of May 2022. See the task's dev notes for the details on the other gateways.
The version of the API implemented by this module is v3.
Merge details
The first version of the module was specified in task
2759117 and merged with PR
odoo/odoo#84820 in saas-15.4.
Testing instructions
https://developer.flutterwave.com/docs/integration-guides/testing-helpers