This commit adds the possibility to define a maximum payment amount that a given acquirer can process. If the payment amount exceeds the value, the acquirer is filtered out of the available acquirers listed on the payment forms. While we're at it, the field `country_ids` is renamed to `available_country_ids` to better depict that it is not a property of the acquirer, but a configuration option. It will also be coherent with the field `available_currency_ids` that is expected to be added soon. Task - 2162165 closes odoo/odoo#82411 Related: odoo/enterprise#24412 Related: odoo/upgrade#3703 Signed-off-by: Antoine Vandevenne (anv) <anv@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