BridgeConnecteurStable

List transactions (Bridge)

Lists bank transactions aggregated by Bridge for a user or account, with time filters and pagination.

User Bridge

Lister les transactions bancaires (Bridge)

Transaction Bridge

Vue d’ensemble

List Bridge transactions retrieves aggregated banking movements for the bridge_user, with an optional account filter, business period, and/or synchronization cursor.

Transactions remain extension.bridge.transaction objects. The node does not automatically turn them into Ormuz payments because a banking movement is not necessarily a business payment to reconcile.

since is used for incremental reads of changes; min_date / max_date bound the business date of transactions.
Supply account to avoid mixing movements from multiple accounts when processing is account-specific.
Amounts are normalized to minor units of their currency before being exposed to the process.

Process example

User Bridge

Lister les transactions bancaires (Bridge)

Transaction Bridge

Exemple simplifié d’utilisation de Lister les transactions bancaires (Bridge) dans un processus Ormuz.

Data resolution

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

Data	Source or rule
User	`bridge_user.uuid`.
Compte	`account.id` when an account is supplied; otherwise the Bridge user scope.
Incremental synchronization	`since`: changes since the supplied time cursor.
Business period	`min_date` and `max_date`: bounds on transaction dates.
Pagination	`limit`, `starting_after`, `has_more`, and `next_uri`.
Amount	Bridge value converted to `common.amount` according to `currency_code`.

Parameters 8

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.

bridge_userRequisBridge user

Bridge user representing the person whose bank accounts must be connected, accessed, or verified. Usually obtain it with bridge.ensure_user rather than constructing the object manually.

accountOptionnelBridge account

Bridge bank account to retrieve or use as a transaction filter. Use an object returned by bridge.list_accounts or bridge.retrieve_account.

Filters and pagination

Parameters that bound banking-data lists and synchronizations.

limitRequisinteger

Maximum number of items requested from Bridge for this page. A smaller value reduces the returned volume; use has_more and next_uri to determine whether additional results exist.

starting_afterOptionnelstring

Bridge pagination cursor used to continue a list after an item already received. Use the value from the previous page rather than a locally calculated index.

sinceOptionneldatetime

Bridge time cursor used to retrieve only transactions modified since a previous synchronization. Use it for incremental synchronization rather than to define a business period.

min_dateOptionneldate

Minimum transaction date included in the search. Use with max_date to limit the business period queried, independently from the incremental since cursor.

max_dateOptionneldate

Maximum transaction date included in the search. It bounds the business period queried and may be combined with min_date.

Outputs 3

Banking data

Bank-aggregation or verification objects available to subsequent steps.

transactionsBridge transaction[]

Bridge bank transactions matching the account, period, and requested pagination parameters. Amounts are exposed in minor units of their currency.

Pagination

Indicators used to continue a Bridge list.

has_moreboolean

Whether another page of Bridge results is available.

next_uriOptionnelstring

Pagination URI supplied by Bridge to continue the list. It is null when no additional page is available.

Behavior

Define the read strategy

Choose an account, period, or since cursor depending on whether you are performing a one-off analysis or incremental synchronization.

Retrieve a page

The node sends the documented Bridge filters and retrieves the matching transactions.

Normalize amounts

Each amount is converted to minor units of its currency without exposing floating-point arithmetic to the process.

Continue when needed

Use has_more and next_uri to decide whether another page must be retrieved.

Limits and responsibilities

The node does not create a platform.payment or automatically reconcile any invoice.
A transaction's provider description may contain banking or personal information; the entire output is classified as sensitive.
A paginated read must be continued explicitly when has_more = true.
since and date bounds serve different purposes: do not use since as an approximate substitute for min_date / max_date.

Troubleshooting

Transactions missing for a period

Check min_date, max_date, the supplied account, and pagination before concluding that Bridge does not have the movements.

Duplicates during synchronization

Preserve identifiers or synchronization cursors and treat Bridge transactions as identifiable provider objects rather than new payments on every read.

Unexpected amount

Ormuz values use minor units: 19400 with EUR represents EUR 194.00.

Reference

Filtre	Objectif
`account`	Restrict the read to a Bridge account.
`since`	Retrieve transactions created or modified since a previous synchronization.
`min_date`	Set the minimum included business date.
`max_date`	Set the maximum included business date.
`starting_after`	Continue pagination after the previous page.