ormuz
Home/Integrations/Bridge/Nodes/Retrieve payment request (Bridge)
BridgeConnecteurStable

Retrieve payment request (Bridge)

Rereads a Bridge Payment Request and the transactions it contains.

Vue d’ensemble

Retrieve Bridge payment request rereads a known Payment Request and returns its transactions in their current state.

This read is useful when bank initiation changed after link creation or after an asynchronous event.

Process example

Payment request Bridge
Récupérer une demande de paiement (Bridge)
Payment request Bridge

Exemple simplifié d’utilisation de Récupérer une demande de paiement (Bridge) dans un processus Ormuz.

Data resolution

The node applies the following rules from the supplied objects and filters.

DataSource or rule
Retrieved identifierpayment_request.id.
Transactionstransactions array in the current Bridge Payment Request.
Execution state availableexecution_status_available when supplied by Bridge.

Parameters 2

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.
payment_requestRequisBridge payment request
Bridge Payment Request obtained in an earlier step. The node uses its identifier to retrieve the latest representation.

Outputs 1

Payment

Objects and state resulting from the payment lifecycle.

payment_requestBridge payment request
Bridge Payment Request associated with the payment, including its state and known transactions. It may be absent until Bridge has created the corresponding request.

Behavior

Identify the request

The node uses the identifier from the input payment_request.

Reread its state

Bridge returns the current request and associated transactions.

Exposer l’objet

The refreshed Payment Request is available to subsequent steps.

Limits and responsibilities

  • The node does not choose a specific transaction when a Payment Request contains several.
  • It does not modify the Ormuz payment; synchronization is a separate operation.

Troubleshooting

No transaction available

The request may exist before Bridge creates or exposes the expected transaction. Retry after the journey progresses or handle the corresponding event.