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

Execute supplier payment from transaction (Bridge)

Confirms execution of an Ormuz disbursement only when a corresponding negative Bridge transaction proves that funds left the account.

Vue d’ensemble

Execute supplier payment from Bridge transaction confirms that an Ormuz disbursement was actually executed when a corresponding Bridge bank debit is observed.

The Ormuz instruction and banking fact remain two distinct lifecycle steps.

Process example

Transaction Bridge + Supplier payment
Exécuter un paiement fournisseur depuis une transaction (Bridge)
Transaction Bridge + Supplier payment

Exemple simplifié d’utilisation de Exécuter un paiement fournisseur 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.
supplier_paymentRequisSupplier payment
Ormuz disbursement that the Bridge transaction must match in order to confirm execution or materialize an incoming refund.

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.
supplier_paymentSupplier payment
Ormuz disbursement after its execution is confirmed by the Bridge transaction.
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’instruction

The node verifies the expected supplier payment and its state.

Compare the debit

The Bridge transaction must prove the expected financial movement.

Confirm execution

The disbursement is updated and correlated to the provider transaction.

Limits and responsibilities

  • This node initiates no bank payment; it only confirms an already-observed movement.
  • A process cannot force the status to executed without a corresponding Bridge transaction.
  • Movement discrepancies are surfaced as errors rather than silently adjusted.