Antoine Vandevenne (anv)
6858d5ca49
Each payment acquirer has its own implementation specificities: some implement a 'payment with redirection' flow and others a 'direct payment flow'; sometimes the 'payment with redirection' flow is even implemented as a 'direct payment' flow through an iframe; one payment acquirer could support webhooks while another does not and relies on another mechanism to fetch payment status updates... It can be tricky to guess where to look in the code to determine how a payment acquirer is implemented. On top of that, the online payments ecosystem evolves at a fast pace due to competition, buyouts, and legislation enforcement. Acquirers are thus frequently migrated to new APIs that might differ in implementation from the previous API. To help figure out the *which*, *why*, *how*, and *when* of payment API implementations, a README.md file is added to the main directory of all payment acquirer modules. They can be browsed in human-readable format on GitHub. task-2374916 closes odoo/odoo#156084 X-original-commit: 4c19f26df3d39394cce2f183d6df15c5b89c7d27 Related: odoo/enterprise#57921 Signed-off-by: Antoine Vandevenne (anv) <anv@odoo.com>
Flutterwave
Technical details
API: Flutterwave standard
version 3
This module integrates Flutterwave using the generic payment with redirection flow based on form
submission provided by the payment module.
Supported features
- Payment with redirection flow
- Webhook notifications
- Tokenization with payment
Not implemented features
- Manual capture
- Refunds
Module history
15.4- The first version of the module is merged. odoo/odoo#85514
Testing instructions
https://developer.flutterwave.com/docs/integration-guides/testing-helpers
MasterCard
Card Number: 5531886652142950
Expiry Date: 09/32
CVC Code: 564
OPT: 12345