Analog bureaucracy in a digital process. Days or weeks of waiting for an authorization that should be immediate.
Each bank delivers a slightly different file. Your team spends hours handling exceptions that should never exist.
Credit card statements remain outside the ERP. Manual reconciliation, fragmented control, and users forced to open bank apps.
Each bank requires a separate integration. Your customer has 3 banks? Three VAN processes, three different layouts.
Exporting statements, saving files, uploading to the system. Manual work that multiplies across every customer account.
When reconciliation fails, customers blame the software. The cost of legacy banking processes hits your bottom line.
Your customer authorizes data sharing directly within your ERP in a few clicks through secure digital authentication.
The API automatically captures checking account statements and credit card invoices from authorized institutions.
Data arrives in a standardized JSON format, ready for automated reconciliation, reporting, and financial management in your software.
{
"data": "2026-03-11",
"tipo": "debito",
"descricao": "Fornecedor XYZ — NF 4821",
"valor": 3840.00,
"saldo": 28970.50,
"banco": "Itaú Unibanco",
"origem": "open_finance"
}
Same JSON standard as the current Statements API, full compatibility with existing implementations. Zero change to your ERP data structure.
Connects your ERP directly to the source to fetch and consolidate multi-bank credit card statements. With a single integration, your system receives transaction data ready for reconciliation, eliminating manual processes and dependency on physical files or reports.
The major banks are already integrated with us: Itaú, Bradesco, Santander, CEF, Banco do Brasil, Nubank, Inter, C6, Sicoob, Sicredi, and much more.
Card invoices and transactions enter the ERP in the same format as account statements. Complete financial reconciliation.
Same data structure as the current Statement API. Full compatibility, zero refactoring in your ERP.
Complete documentation and dev-to-dev support. From the first API call to go-live, straightforward.
Technical team made of developers who understand banking integration. Guided onboarding all the way to go-live.
Hand-exported statements, bank by bank, and no credit card coverage. A fragile, manual process in a flow that should be automated.
One digital authorization, +47 supported banks, checking account and credit card in a single JSON, also ready for AI agents via MCP. TecnoSpeed handles regulation. You integrate.












Everything to run your first query: authentication, Open Finance consent creation, and the initial statement protocol.
Access documentationHow to create bank statement query protocols via Open Finance, parameters, and callbacks.
View documentation ListingHow to list and view created statement protocols. History and status for each query.
View documentationInvoices tied to the customer's CNPJ imported automatically, no manual searching required.
A single API to issue, manage, and reconcile bank slips in all major Brazilian banks.
Integrated Pix charges and payments with automated reconciliation via Open Finance.
Complete automation of the accounts payable lifecycle — DDA + Payments + Statements.
TecnoSpeed's Open Finance Statement API is a solution designed for Software Houses and IT teams that need to integrate bank statements and credit card invoices into their clients' ERPs via Open Finance. With a single integration, your software automatically imports transactions from 47+ supported banks, with no VAN, no manager letter needed, and no Central Bank accreditation required. Data arrives in standardized JSON, ready for automated reconciliation.
Open Finance is the Open Financial System regulated by the Central Bank of Brazil. It allows consumers and businesses to share their financial data with authorized systems upon explicit consent. For Software Houses, Open Finance marks the end of bureaucratic banking integration: no VAN, no OFX, no manual processes. With over 65 million connected accounts and 800+ participating institutions, it is the most modern and scalable way to access banking data within an ERP.
No. TecnoSpeed is already registered and accredited by the Central Bank to operate in the Open Finance ecosystem. You simply integrate with our API and start operating. All regulatory complexity—FAPI certifications, OAuth 2.0, mTLS—stays with TecnoSpeed. As our Product Owner Yago Xavier said: "Our API was built so developers don't need to know what FAPI is to integrate it. We handle the regulatory complexity."
Currently, 47 banks are supported: 44 for Individuals (PF) and 36 for Legal Entities (PJ). Among the main ones: Itaú, Bradesco, Santander, Caixa Econômica Federal, Banco do Brasil, Nubank, Banco Inter, C6 Bank, Sicoob, Sicredi, PicPay, and many others. Central Bank regulation requires the participation of every financial institution with over R$ 1 billion in assets, so coverage continues to grow.
Yes! Importing credit card statements is the API's new feature. Using the same Open Finance consent from the customer, the ERP also imports credit card transactions in the exact same standardized JSON as checking account statements. This completes the financial reconciliation cycle: checking account, Pix, bank slips, and now credit cards—all inside the ERP.
The traditional Statement API works via bank VAN: it requires a signed letter to the bank manager, an approval process that can take days, and delivers OFX or TXT files that vary by bank. The Open Finance Statement API eliminates all this bureaucracy: customers authorize via digital authentication in minutes, data arrives in a standardized JSON for all banks, and one authorization covers all institutions. Additionally, Open Finance includes credit card data, which VAN does not cover.
Most customers go from zero to production in under 30 days, including a fully functional consent flow. Complete documentation, dedicated technical support, and a sandbox environment are available for testing before going live.
Yes. Open Finance was built on the most stringent security standards in the financial market: OAuth 2.0 for authentication and authorization, FAPI (Financial-grade API) for access control in high-risk banking environments, and mTLS for two-way encryption in all communications. No data travels without explicit user consent. Sharing includes full traceability (who accessed what and when) and complete compliance with LGPD (General Data Protection Law).
No. Open Finance does not provide DDA (Authorized Direct Debit) data, as this information is not part of the shared data scope defined by the standard. The API provides checking account and credit card statements, but not bank slips via DDA.
No. Open Finance is a regulatory requirement from the Central Bank that applies only to authorized banks and financial institutions; fintechs like Asaas are not required to participate and are therefore not available in the base. API coverage directly follows institutions accredited in Open Finance.