Retrieve payment transaction (Bridge)
Rereads the parent Payment Request to resolve the current version of a specific Bridge transaction.
Vue d’ensemble
Retrieve Bridge payment transaction refreshes a specific transaction by rereading its parent Payment Request, then returns both coherent objects.
Use this node when you already have a Bridge transaction and its status must be refreshed before synchronization or a decision.
Process example
Exemple simplifié d’utilisation de Récupérer une transaction de paiement (Bridge) dans un processus Ormuz.
Data resolution
The node applies the following rules from the supplied objects and filters.
| Data | Source or rule |
|---|---|
| Payment Request parente | payment_transaction.payment_request_id. |
| Searched transaction | The parent request item whose identifier matches payment_transaction.id. |
| Payment Link | Identifier propagated from the original transaction or Payment Request when available. |
Parameters 2
Contexte principal
Objects and configuration that determine the Bridge operation.
psp_payment.Outputs 2
Payment
Objects and state resulting from the payment lifecycle.
CREA, ACTC, PDNG, ACSC, or RJCT).Behavior
Resolve the parent request
The node requires payment_request_id on the supplied transaction.
Relire Bridge
The current Payment Request is retrieved with its transactions.
Resolve the transaction
The node finds exactly the requested identifier and returns the refreshed transaction with its request.
Limits and responsibilities
- A transaction without
payment_request_idcannot be refreshed by this node. - If the expected transaction no longer exists in the reread Payment Request, the node fails instead of selecting another item.
- The read does not modify the Ormuz
psp_payment.
Troubleshooting
payment_request_id manquant
Use a transaction produced by the Ormuz Bridge flow or by an event exposing this relationship.
Transaction missing from the request
Check that a transaction and Payment Request from two different initiations have not been mixed.