Skip to main content

Introduction to Documentation

This documentation aims to describe and guide the developer in using our REST API.

Introduction

We are the first financial institution to create an exclusive Bank-as-a-Service (BaaS) model in Brazil. Our goal is to help any Fintech/Credit Manager or company have access to fast, agile, and secure financial services, however they want. Learn more at https://qitech.com.br.

Environments (Hosts)

QI Tech has completely separate infrastructures for the SANDBOX and PRODUCTION environments, where the sandbox environment presents entirely fictitious monetary values, and only the Production environment performs valid financial transactions.

The Sandbox environment was created for developers to perform their integrations, and when ready for production, they only need to update the Host and Access Token variables with the parameters from the Production environment.

In addition to the division by environments, we also have the segregation of HOSTs related to financial services, analysis services, and QI Tech certification services as per the table below:

ServiceEnvironmentHost
BaaS and LaaSProductionhttps://api-auth.qitech.app/
BaaS and LaaSSandboxhttps://api-auth.sandbox.qitech.app/
CaaSProductionhttps://api.caas.qitech.app/
CaaSSandboxhttps://api.sandbox.caas.qitech.app/
CertifiQIProductionhttps://api.certifiqi.com.br/
CertifiQISandboxhttps://api.sandbox.certifiqi.com.br/

The environments are always on the same version, so when an update occurs in Production, the same update occurs in the Sandbox environment.

How is this documentation divided?

After completing the initial steps in the "Necessary Steps to Start" section, you can already consume QI Tech's microservices in the sandbox environment.

This documentation is divided by products, which are:

  • Banking as a Service
  • Lending as a Service
  • Know Your Customer
  • Certification Authority

To facilitate communication with the QI Tech support team, we have also separated these sections by numbers.

Error Messages

Attention!

Error messages returned by QI should not be strictly mapped. Additional fields may be included in the error messages of our APIs in the future.