Connect to any financial institution in Latin America with Belvo.

Build fintech innovations on top of any banking, fiscal and gig institutions in Latam.


Get started

You can use Belvo's sandbox environment to mimic any real-world use case during development. Interact with banking, fiscal, and gig institutions loaded with dummy data to test out a wide variety of user flows, including multi-factor authentication.

Accessing the sandbox

To access the sandbox, just make sure to generate your sandbox API keys and use them in your calls.

Demo institutions

In the sandbox environment you can simulate real-world interactions using our demo institutions, which contain dummy data as well as a set of credentials to simulate a variety of users.

List of demo institutions

Display name

Type

Names and countries

Gringotts Bank

Banking (retail)

gringotts_mx_retail
gringotts_co_retail
gringotts_br_retail

Erebor Bank

Banking (retail)

erebor_mx_retail
erebor_co_retail
erebor_br_retail

Gotham Business Bank (MFA)

Banking (business)

gotham_mx_business
gotham_co_business
gotham_br_business

Goonies (Ride Sharing)

Gig Economy

goonies_mx_gig
goonies_co_gig
goonies_br_gig

Planet Express (Delivery)

Gig Economy

planet_mx_gig
planet_co_gig
planet_br_gig

Tatooine Fiscal

Fiscal

tatooine_mx_fiscal

Heimdall Bank (MFA Testing Only)

Banking (retail)

heimdall_mx_retail
heimdall_co_retail
heimdall_br_retail

Iron Bank (Advanced login)

Banking (retail)

ironbank_br_business
ironbank_br_retail

Test credentials

Create your first link in Sandbox, for any institution, by using these credentials:

Username: user_valid
Password: pass_valid

Additional use cases

Belvo provides a complete set of credentials to populate your links when retrieving data (like retrieving owners, accounts, invoices or transactions).

Banking

Use case

Username

Password

Description

Banking with full data (default)

bnk100

full

Complete paginated dataset that will cover our entire data schema (transactions, owners, accounts, loans, credits, income, statements).

Banking with no data

bnk101

nodata

A link that won't generate any kind of data.

Banking low data

bnk102

low

Non-paginated data set.

Banking negative balance

bnk103

negative

Same case than "low data" but with a negative balance.

Gig economy

Use case

Username

Password

Description

Gig with full data (default)

gig100

full

Complete paginated dataset that will cover our entire data schema (transactions, owners, accounts, loans, credits, income, statements).

Gig with no data

gig101

nodata

A link that won't generate any kind of data.

Gig low data

gig102

low

Non-paginated data set.

Gig negative balance

gig103

negative

Same case than low data but with a negative balance.

Fiscal institutions

Use Case

Username

Password

Description

Fiscal with full data (default)

fiscal100

full

Full dataset of fiscal information, that includes paginated invoices (outflow & inflow), tax status and tax returns.

Fiscal with no data

fiscal101

nodata

A link that won't generate any kind of data.

Fiscal low data

fiscal102

low

Non-paginated data set.

Test the link flows

Belvo provides a set of additional demo credentials that will help you test any cases during the link creation process (widget or API).

Test standard flows

Case

Username

Password

Institution

Response

Valid credentials

user_valid

pass_valid

Any

201 Created

Invalid credentials

user_invalid

pass_invalid

Any

400 LoginError

Validation error

1234567890abcdefg

1234567890abcdefg

Any

400 ValidationError

๐Ÿ“˜

Creating valid links and avoiding link duplication

We highlight a list of preset credentials to facilitate your tests. However, during the development process, you may need to create more than one link per institution. Using the same credentials, you'll receive a 400 Duplicated error.

Create multiple links for an institution by providing any combination of random username and password (which is not listed before). It will create a valid link using the default use case according to the institution type (Banking, Gig, Fiscal).

Test advanced link flows

Some real-world institutions require to use advanced parameters to create a link like username_type, username2 or password2 .

To test that flow, you can make use of Iron Bank institution (ironbank_br_business or ironbank_br_retail), which will require all those fields to create a link.

Case

Username

Password

Username type

Username2

Password2

API Response

Valid credentials

adv_valid

pass_valid

003

valid

valid

200 Success

Invalid credentials

adv_invalid

pass_invalid

999

invalid

invalid

400 Login Error

Test Multi Factor Authentication

Some real-world institutions need a second step (2FA Auth) in order to complete the link creation.

Test the MFA flows using the dedicated institution called Heimdall (the gatekeeper). It can be used to test all potential MFA flows.

Use one of the following credentials, with Heimdall institution, to simulate MFA flows:

  • heimdall_mx_retail
  • heimdall_co_retail
  • heimdall_br_retail

Case

Username

Password

Description

MFA Default (inputless)

mfa_default

pass_valid

Simulate the default case, where the user needs to generate the 2FA token using its mobile or dedicated device.

QR Code

mfa_qr

qr_code

Simulate the case where the user needs to scan a QR code in order to generate the 2FA token.

Numeric

mfa_numeric

numeric_code

Simulate the case where the user needs to input a challenge code in order to generate the 2FA token.

Using any of those credentials, you'll receive a corresponding 428 response. You then need to PATCH the link, with a token to complete the link creation.

Use one of the following tokens to simulate different token flows:

Case

Value

API Response

Valid token

111111

200 Ok

Invalid token

999999

428 Token Required

๐Ÿ“˜

Invalid token

Sending an Invalid token, we simulate a scenario where the user enters a wrong token. In that case, you will receive a new 428 response, asking again for a new token.

Additional resources

Updated 15 days ago


Sandbox


Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.