ormuz
Home/Integrations/Bridge/Nodes/Reverse payment from transaction (Bridge)
BridgeConnecteurStable

Reverse payment from transaction (Bridge)

Materializes the reversal of a receipt from a negative Bridge transaction linked to the original payment.

Vue d’ensemble

Reverse Payment from Bridge transaction materializes a reversal when Bridge observes the inverse movement of an existing receipt.

The reversal is derived from the banking evidence and source Payment, not from a status setter.

Process example

Transaction Bridge + Ormuz payment
Contre-passer un paiement depuis une transaction (Bridge)
Transaction Bridge + Ormuz payment

Exemple simplifié d’utilisation de Contre-passer un paiement depuis une transaction (Bridge) dans un processus Ormuz.

Parameters 3

Contexte principal

Objects and configuration that determine the Bridge operation.

extension_config_idRequisref(extension_config:bridge)
Active Bridge configuration used for this operation. It determines the Bridge API credentials and environment; the merchant remains the merchant of the current process.

Other parameters

transactionRequisBridge transaction
Bridge bank transaction used as external evidence of the financial movement to materialize or reconcile with an existing Ormuz object.
paymentRequisPayment
Original Ormuz payment to which the Bridge transaction must be attached in order to create a reversal.

Outputs 4

Session and traceability

Session identifiers, mappings, and creation indicators.

extension_object_mappingextension object mapping
Traceability link between the primary Bridge object produced by the node and the Ormuz object with which it is associated.
createdboolean
Whether the node created a new Bridge object. false means an already-associated object was found and reused.

Other outputs

transactionBridge transaction
Bridge bank transaction used as evidence of the financial movement handled by the node.
payment_reversalPayment
Ormuz reversal created from the inverse bank transaction.

Behavior

Verify the source payment

The node checks that the negative transaction can correspond to the supplied Payment.

Create the reversal

The reversal fact is materialized from the Bridge transaction.

Compensate reconciliation

Allocations of the original payment are compensated according to canonical rules.

Limits and responsibilities

  • The node is not for manually correcting a Payment without Bridge banking evidence.
  • The allocation of compensation is not configurable: it reflects reconciliation of the original payment.
  • A transaction with no coherent relationship to the source Payment is rejected.