HELP CENTER

Welcome to BaaSiC! Before you dive into operations, it’s important to understand a few key concepts and the steps to get started on the platform efficiently.

In this section:

  • The 5 Steps to Go Live
  • Key Payment Concepts
  • Key API Concepts
  • Tools for a Smooth Integration

 

The 5 Steps to Go Live with BaaSiC

BaaSiC is an API-first platform, meaning it is designed for seamless communication between your systems and Transfero’s financial infrastructure. 

Here’s the typical roadmap to get you fully operational:

  1. Onboarding & initial testing

First, you’ll complete Transfero’s standard onboarding process, which includes submitting documents, signing the contract, and configuring your initial access. 

While your onboarding is processed, you can request credentials to our Sandbox environment, allowing you to start exploring the platform's features right away. Think of it as a sneak peek!

  1. Integration kick-off

After the contract is signed, we will schedule an integration kick-off session with your dev team. This session is designed to:

  • Explain key integration components and terminology.
  • Demonstrate how to use the dashboard to easily manage your operations.

Our development team will work with yours to integrate our systems via dedicated API endpoints, each built for specific operations like deposits, withdrawals, or swaps.

  1. Implementation in the sandbox

With the integration in place, you can use the Sandbox environment to run end-to-end tests, validate workflows, and train your team—all without any financial risk. Our tech team will be available to provide support and ensure everything works as expected.

  1. Go live: production access

Once all tests are completed and validated in the Sandbox, we’ll grant you access to the Production Environment. From this point on, all operations are live and involve real funds.

  1. Ongoing support & monitoring

After going live, you can monitor all transactions in real-time through the BaaSiC dashboard or your integrated system. For continuous support, we offer several resources:

  • Help center;
  • API documentation;
  • Direct support.

For hands-on assistance, you can always reach our specialists by opening a support ticket through Zendesk or your dashboard.

 

Key Payment Concepts

Pay-in (deposit)

The process of adding funds to your BaaSiC account. Deposits can be made in fiat or crypto by your business or a third party.

Pay-out (withdrawal)

The process of sending funds from your BaaSiC account to an external bank account or crypto wallet.

Pix Key (Brazil)

A 24/7 real-time payment method in Brazil. Transactions are processed using a Pix Key, a simple identifier linked to a bank account. Keys can be:

➡️ Tax identification

CPF (for individuals): e.g., 123.456.789-00

CNPJ (for businesses): e.g., 12.345.678/0001-90

➡️ Email address

e.g., name@email.com

➡️ Phone number

e.g., +55 11 91234-5678

➡️ Random key (EVP): a unique, randomly generated string.

e.g., 123e4567-e89b-12d3-a456-426614174000

CBU/CVU (Argentina)

Account identifiers used for financial operations in Argentina.

➡️ CBU (Clave Bancaria Uniforme): a 22-digit code for transactions involving traditional bank accounts. The first 8 digits represent the bank and branch code, and the last 14 digits represent the bank account number.

E.g.,0110000123456789012345

➡️ CVU (Clave Virtual Uniforme): a 22-digit code that allows seamless transfers between traditional bank accounts and digital wallets (from Payment Service Providers - PSPs). 

The first 8 digits identify the financial institution (Payment Service Provider – PSP) that issued the virtual account, and the remaining 14 digits are the virtual account number assigned to the user.

E.g.,0000000012345678901234

Tax Identification Formats

Brazil 

➡️ CPF: 11 digits (e.g., 123.456.789-00)

➡️ CNPJ: 14 digits (e.g., 12.345.678/0001-90)

Argentina  

➡️ CBU: 22 digits (e.g.,0110000123456789012345)

➡️ CVU: 22 digits (e.g.,0000000012345678901234)

 

Key API Concepts

Parameter

A piece of information required in an API request. 

For example, a withdrawal request would include parameters like amount, currency, bankAccount, and taxIdCountry.

Endpoint

A specific URL that corresponds to a particular API function, such as creating a deposit or requesting a swap.

Callback (via webhook)

An automated notification is sent from our system to yours when a specific event occurs. BaaSiC uses webhooks to implement callbacks. For example, when a deposit is confirmed, a webhook automatically "pushes" a notification to a URL you define, instantly updating your system

Authentication  

The process of verifying identity to grant secure API access. BaaSiC uses OAuth, an industry standard that allows access without exposing your credentials.

  • JWT (JSON web token): BaaSiC uses the JWT format for its authentication tokens. A JWT is a secure, self-contained credential that includes a header, a payload (data), and a signature to verify its integrity.
  • Token: a secure, temporary credential (in JWT format) that authenticates your API requests. The endpoint to generate a token is /token, and it must be included in your request headers in the format: Bearer [your_token].

📌 Tip: you can find more technical information in our API documentation. It will help to ensure a smoother initial setup and operation with greater efficiency.

 

Tools for a Smooth Experience with BaaSiC

To ensure BaaSiC works seamlessly with your system, the integration must be properly configured. 

These tools are essential for efficiently managing your API requests and ensuring proper communication between your system and BaaSiC.

Below are a few tools and resources to guarantee the best experience:

API Documentation

We provide comprehensive technical documentation with detailed guides and examples.

👉 Access the full API guide at: https://baasic.transfero.com 

Postman Repository

Postman is a tool for testing and managing API workflows. We provide a pre-configured Postman Collection and Environment to help you get started faster.

  • Postman collection: ready-to-use set of all BaaSiC API requests, making it easy to test and automate workflows.
  • Postman environment: template to store your specific variables - like API keys, tokens, and account IDs - allowing you to switch between Sandbox and Production environments easily.

👉 For more technical details on setting up Postman, please refer to our full API documentation.