ormuz
Home/Integrations/Bridge/Nodes/Check bank account (Bridge)
BridgeUser actionStable

Check bank account (Bridge)

Runs a Bridge Account Check and then exposes the holder and account information returned by the provider.

Vue d’ensemble

Bridge Account Check opens a banking interaction dedicated to verifying the account holder for the supplied bridge_user.

After return, Ormuz reads the available Account Check information and exposes it as sensitive data. The node does not itself declare that an account “belongs” to the contact beyond the information actually returned by Bridge.

  • The Bridge session is limited to the account_check capability.
  • verified_account_count counts the accounts present in the returned results; it is not a risk score.
  • No platform.payment or other business object is automatically created from the result.

Typical scenario

A supplier enters bank details during onboarding. The process resolves the supplier's bridge_user, runs Account Check, then compares the returned holder information with business rules before accepting or escalating the case.

Quick start

Use a bridge_user already linked to the contact being verified and the email address of the person performing the interaction.

Before the check

  • Bridge configuration with Account Check enabled
  • bridge_user obtained through bridge.ensure_user
  • Contact email address

After the check

  • Inspecter account_information
  • Apply your own name/account matching rules
  • Explicitly route discrepancies when necessary
Configuration example
ParameterBindingRole
bridge_usernodes.ensure_user.bridge_userBridge user associated with the contact
user_emailcontact.emailPerson performing the verification
Key point Account Check provides information verified by Bridge; the final business decision (accept, reject, request review) remains with your process.

Process example

User Bridge + E-mail de l’utilisateur
Vérifier un compte bancaire (Bridge)
User Bridge + Account information Bridge

Exemple simplifié d’utilisation de Vérifier un compte bancaire (Bridge) dans un processus Ormuz.

Data resolution

The node resolves this data from its inputs and Bridge context.

DataSource or rule
Userbridge_user.uuid.
Emailuser_email supplied to the node.
Bridge capabilityaccount_check only.
ResultsHolder information and accounts exposed by Bridge after the session.
Account countTotal number of accounts present across the account_information entries.

Parameters 7

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.

Action presentation

Text visible to the participant before continuing to Bridge.

titleOptionnelstring
Titre affiché au participant pour présenter l’action Bridge. Utilisez un libellé court qui décrit clairement l’action attendue, par exemple poursuivre vers sa banque ou vérifier son compte. Valeur par défaut : Verify my bank account.
descriptionOptionnelstring
Texte d’accompagnement affiché avec le titre de l’action Bridge. Utilisez-le pour expliquer au participant pourquoi il est redirigé vers Bridge et ce qu’il devra y faire. Valeur par défaut : Continue securely with Bridge to verify bank-account ownership..

Payer or user identity

Information used to identify the person or company interacting with Bridge.

user_emailRequisemail
Email address presented to Bridge for the bank-connection or account-verification experience. Use the email of the contact actually performing the action.

Process resumption

Advanced settings controlling replay of the user action.

allow_replay_from_hereOptionnelboolean
Allows an authorized operator to resume the process later from this user action. Leave this disabled unless your resume policy explicitly permits replaying the Bridge interaction.
replay_boundaryOptionnelboolean
Marks this action as a point of no return for process resumption. Enable it when replaying previous steps could recreate a payment initiation or repeat a sensitive bank connection.

Outputs 4

Banking data

Bank-aggregation or verification objects available to subsequent steps.

bridge_userBridge user
Bridge user representing the Ormuz contact for bank-aggregation and account-verification operations.
account_informationBridge account information[]
Account Check results returned by Bridge, including holder identity and available verified accounts. This information is classified as sensitive.
verified_account_countinteger
Total number of accounts present in the Account Check results returned at the end of the action.

Session and traceability

Session identifiers, mappings, and creation indicators.

account_check_session_idOptionnelstring
Identifier of the Bridge session used for Account Check. It provides traceability for the interaction without exposing the hosted URL or authorization token.

Behavior

Prepare the session

The node temporarily authorizes the bridge_user and then creates a Bridge session dedicated to Account Check.

Have the account verified

The participant follows the Bridge experience and selects or confirms the bank account.

Reread the information

On return, Ormuz retrieves the available account information for the user.

Expose the result

account_information and verified_account_count become available to your rules and subsequent steps.

Limits and responsibilities

  • The node does not automatically turn the result into a “match / mismatch” decision. Define your comparison rules explicitly.
  • verified_account_count = 0 means no account is present in the returned result; it must not automatically be interpreted as fraud or rejection.
  • Account Check availability depends on the capabilities enabled for your Bridge application.
  • Holder information and IBANs are sensitive and should be used only by steps that need them.

Troubleshooting

No Account Check result

Check that the session completed and that the Account Check capability is enabled on the Bridge configuration being used.

The returned name differs from the contact

Do not force an automatic conclusion: apply your business rules for normalization, company/natural-person handling, and manual review.

Multiple accounts are returned

Use account_information to identify the relevant account or accounts; verified_account_count does not choose an account for you.