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

Materialize payment refund from transaction (Bridge)

Confirms an Ormuz bank-refund intent from a negative Bridge transaction that proves the executed movement.

Vue d’ensemble

Materialize Payment refund from Bridge transaction confirms a bank-refund intent already created in Ormuz when Bridge observes the corresponding outgoing movement.

The banking fact therefore does not create a second intent; it materializes the one the process already reserved.

Process example

Transaction Bridge + Ormuz payment
Matérialiser un remboursement depuis une transaction (Bridge)
Transaction Bridge + Ormuz payment

Exemple simplifié d’utilisation de Matérialiser un remboursement 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.
payment_refundRequisPayment
Ormuz bank-refund intent already created and still awaiting materialization by a corresponding Bridge movement.

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.

Other outputs

transactionBridge transaction
Bridge bank transaction used as evidence of the financial movement handled by the node.
payment_refundPayment
Ormuz bank refund after materialization of the corresponding Bridge movement.
appliedboolean
Whether the banking fact was applied to the supplied intent or disbursement; an idempotent replay may return a value that was already materialized.

Behavior

Valider l’intention

The Ormuz refund must be a compatible intent that can still be materialized.

Compare the banking evidence

The node verifies that the negative Bridge transaction matches the expected refund.

Confirm the refund

The movement is applied to the refund and provider correlation is preserved.

Limits and responsibilities

  • The node does not create a refund intent; use refund_payment or the appropriate credit-note helper first.
  • A bank transaction cannot be arbitrarily assigned to a refund whose amount or context does not match.
  • Selection of the credit notes to refund remains an upstream process decision.