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>
1.2 KiB
1.2 KiB
Demo
Technical details
This module does not integrate with an API and, instead, allows for fake payments that can be made to test applications' payment flows without API credentials nor payment method details.
Supported features
- Direct payment flow
- Tokenization with our without payment
- Full and partial manual capture
- Full and partial refunds
- Express checkout
- Select the outcome of the payment
Module history
17.0- The support for express checkout is added. odoo/odoo#113644
- The support for customer fees is removed as it is no longer supported by the
paymentmodule. odoo/odoo#132104
16.3- The support for partial manual capture is added. odoo/odoo#117356
16.0- The module is renamed from
payment_testtopayment_demo. odoo/odoo#99397 - The support for manual capture, full and partial refunds, customer fees, and the selection of the payment outcome are added. odoo/odoo#78083
- The module is renamed from
Testing instructions
The Demo payment provider can only be used in test mode.
No payment method details are required and the outcome of payments can be chosen. If provided, the "Payment Details" are used as display name for the created payment tokens.