This commit adds the missing neutralisation necessary for the `payment_xendit` module introduced in [1] The purpose of the standard neutralisation framework is to allow us to create database copies that will not interract with external systems in ways that could impact the production database (or if it is not possible to prevent the interractions, make sure that they are benign or wont result in actual changes), or impact the customers of the operator of the production database. This is mainly useful to allow safe support investigation on database duplicates. [1] odoo#141661 closes odoo/odoo#151511 Signed-off-by: Alexandre Moens (mao) <mao@odoo.com>
Xendit
Implementation details
Supported features
- Payment with redirection flow
- Several payment methods such as credit cards, bank transfers, eWallets, pay later, and others.
- Webhook.
In addition, Xendit also allows to implement tokenization.
API and gateway
We choose to integrate with the
Invoices API as it
is the gateway that covers the best our needs: it is a payment with redirection flow and is
compatible with payment's form-based implementation of that flow.
The Payments API was considered too, but it requires implementing a more complex direct payment flow and linking the customer account.
The version of the API implemented by this module is v2.
Merge details
The first version of the module was specified in task
2946329 and merged with PR
odoo/odoo#141661 in branch 17.0.