Skip to the operations

Banking

Belvo in a decision flow.

6 Belvo operations a decision flow can call directly, with the credentials your own contract issued. The response is data the rest of the flow reads, branches on, and keeps in the trace.

Category
Banking
Type
Integration
Authentication
HTTP basic auth
Test environment
Separate sandbox host

Who they are

Open Finance data across Latin America.

Belvo connects to banks and financial institutions in Brazil, Mexico and Colombia and returns accounts, transactions, identity and income through one interface. Lenders and personal-finance products use it where a credit bureau file is thin or missing, which describes a large share of applicants in the region. It also derives income and recurring payments from the raw transaction history.

What a flow can call

6 operations, each one a step you can place on the canvas.

  1. GET/api/links/

    List bank connections

    Every link the account holds. A link is one person's connection to one institution and it is what every read below is scoped to, so this is the first call when working out what a flow can actually see.

  2. GET/api/accounts/?link=$data.belvo_link_id

    List accounts

    Accounts behind one link, with balances and account type.

  3. GET/api/transactions/?link=$data.belvo_link_id

    List transactions

    Transaction history for a link. This is the affordability input — what arrives, how regularly, and what leaves again.

  4. GET/api/owners/?link=$data.belvo_link_id

    Read the identity the bank holds

    Name, document, address and contact details as the institution has them.

  5. GET/api/incomes/?link=$data.belvo_link_id

    Read derived income

    Belvo's own income analysis over the link's transactions — recurring streams, their regularity and their confidence.

  6. GET/api/institutions/

    List institutions

    Every institution Belvo can reach, per country, with the credentials each one asks for.

Where it sits in the decision

Banking calls have a natural place in a flow.

Bank data answers the question a stated income cannot: what actually arrives, how regularly, and what leaves again. It is usually pulled once per application and then read by several nodes — affordability, income verification, any rule about balance volatility — so it is worth fetching early and deriving from, rather than calling repeatedly.

Whatever Belvo returns is part of the run, so it is part of the record. When someone asks months later why an applicant was declined, the answer cites what came back at the time rather than re-fetching from a service whose answer has since changed.

  • 01Add Belvo as a connection authenticating with HTTP basic auth.
  • 02Belvo runs a separate sandbox host, so a Sandbox flow can exercise the real call without touching production.
  • 03Place a Connection node and pick an operation — “List bank connections” is usually the first one a flow needs.
  • 04Map the response into the fields your rules read, then test the whole path before it carries live traffic.

Common questions

Using Belvo in a flow.

How do I connect Belvo to a decision flow?

Add Belvo as a connection in your workspace authenticating with HTTP basic auth, with the credentials your own contract issued — ArboRule calls the provider as you, and never holds a contract on your behalf. Once the connection exists, any flow in the workspace can place a Connection node and choose one of its operations. The credentials live on the connection, not in the flow, so a policy owner can use Belvo in a decision without ever seeing the secret.

Can I test Belvo without touching production?

Yes. Belvo runs a separate sandbox host, so a flow executing in Sandbox can make the real call against test credentials and you can read the actual response shape in the trace before anything reaches a customer. The flow does not change when it graduates — only which credentials answer.

What can a flow call on Belvo?

6 operations, including “List bank connections”, “List accounts”, “List transactions”. Each one is a step you place on the canvas and map into the fields your rules read, and most flows start with “List bank connections”. The list comes from the same manifest the engine uses to make the call, so this page cannot describe an operation the product does not have.

Where in a decision should Belvo be called?

Bank data answers the question a stated income cannot: what actually arrives, how regularly, and what leaves again. It is usually pulled once per application and then read by several nodes — affordability, income verification, any rule about balance volatility — so it is worth fetching early and deriving from, rather than calling repeatedly.

Also in Banking

Ready when you are

Wire Belvo into a real decision.

Build the flow in Sandbox, connect your account, and watch the decision pull what it needs before it answers.

Read the docs