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

Create payment from transaction (Bridge)

Materializes a bank receipt observed by Bridge as a canonical `platform.payment` without asking the process to reconstruct the factual fields of the movement.

Vue d’ensemble

Create Payment from Bridge transaction turns a bank receipt actually observed by Bridge into a canonical platform.payment.

The process supplies the provider transaction; it does not reconstruct the amount, currency, or date of the financial fact.

Process example

Transaction Bridge
Créer un paiement depuis une transaction (Bridge)
Transaction Bridge + Ormuz payment

Exemple simplifié d’utilisation de Créer 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.
companyOptionnelCompany
Optional buyer company associated with the received payment when it is already known in the process.

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.
paymentPayment
Ormuz payment created from the observed bank transaction.

Behavior

Validate the movement

The node verifies that the transaction is a usable incoming movement for creating a payment.

Materialize the fact

The payment is created from authoritative Bridge data or reread when a mapping already exists.

Trace provenance

The transaction, Payment, and mapping are returned with created.

Limits and responsibilities

  • The node does not allow free-form input of factual payment fields: Bridge remains their source.
  • It does not automatically reconcile the payment with invoices; use reconciliation nodes afterward.
  • An outgoing or inconsistent transaction is rejected rather than artificially converted to a receipt.