5bb97c3fcb
Previously, /payment/status would render a template on the server-side, and a JS widget would render subtemplates on the client-side and insert them in the server-side rendered template.
However, mixing server-side and client-side templates causes issues because the context is not properly communicated between client and server. It also makes the code more complex.
This change assumes that no new information returned by /payment/status is worth re-rendering part of the template. If the transaction moves from a pending ('draft', 'pending') state to a final state, the customer should be redirected to the final route that will display the updated information on the transaction.
task-3340354
closes odoo/documentation#8198
Related: odoo/upgrade#5829
Related: odoo/odoo#149821
Related: odoo/enterprise#58822
Signed-off-by: Antoine Vandevenne (anv) <anv@odoo.com>
26 lines
854 B
ReStructuredText
26 lines
854 B
ReStructuredText
:hide-page-toc:
|
|
|
|
===================
|
|
Payment Transaction
|
|
===================
|
|
|
|
.. autoclass:: odoo.addons.payment.models.payment_transaction::PaymentTransaction()
|
|
|
|
.. automethod:: _compute_reference
|
|
.. automethod:: _compute_reference_prefix
|
|
.. automethod:: _get_specific_create_values
|
|
.. automethod:: _get_specific_processing_values
|
|
.. automethod:: _get_specific_rendering_values
|
|
.. automethod:: _get_tx_from_notification_data
|
|
.. automethod:: _handle_notification_data
|
|
.. automethod:: _process_notification_data
|
|
.. automethod:: _send_capture_request
|
|
.. automethod:: _send_payment_request
|
|
.. automethod:: _send_refund_request
|
|
.. automethod:: _send_void_request
|
|
.. automethod:: _set_authorized
|
|
.. automethod:: _set_canceled
|
|
.. automethod:: _set_done
|
|
.. automethod:: _set_error
|
|
.. automethod:: _set_pending
|