Files

T

Antoine Vandevenne (anv) 6858d5ca49 [IMP] payment, *: document technical details in README files

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>

2024-03-04 15:15:54 +00:00

790 B

Raw Blame History

SIPS

Technical details

API: SIPS Paypage

This module integrates SIPS using the generic payment with redirection flow based on form submission provided by the payment module.

Supported features

Payment with redirection flow
Webhook notifications

Module history

15.2
- An HTTP 404 "Forbidden" error is raised instead of a Validation error when the authenticity of the webhook notification cannot be verified. odoo/odoo#81607

Testing instructions

VISA

Card Number: 4100000000000000

MasterCard

Card Number: 5100000000000000

790 B Raw Blame History