- API aggregators
No API products listed for BTGPactual. View the APIs tab for developer resources.
Connect BTGPactual via API Aggregator
BTGPactual is supported by 2 API aggregators. Choose a platform to see the integration guide:
Agentic banking & MCP
→How the Model Context Protocol (MCP) fits next to open banking APIs—and why banks are adding MCP servers for AI assistants.
Institutions are starting to expose permissioned banking actions and data to AI clients via MCP, alongside traditional developer portals and PSD2-style APIs. Open Banking Tracker maps known MCP programs, ecosystem tools, and how consent and governance show up in agentic workflows.
BTGPactual is listed here for open banking and API context. When we have confirmed MCP program details for this institution, they appear in this section automatically.
BTGPactual Open Banking FAQ
BTGPactual's direct API availability may be limited. However, you can often access BTGPactual accounts through Open Banking aggregators like Plaid, Tink, or TrueLayer, which provide standardized connectivity to thousands of banks including BTGPactual.
The easiest way to integrate with BTGPactual is through an Open Banking aggregator. These services provide pre-built connections to BTGPactual and handle authentication, data normalization, and compliance requirements on your behalf.
PSD2 compliance depends on BTGPactual's operating jurisdiction. European banks must comply with PSD2, while banks in other regions follow their local Open Banking regulations. Check the compliance section above for specific certifications.
Through Open Banking APIs, you can typically access account balances, transaction history, account holder information, and in some cases initiate payments. The specific data available depends on BTGPactual's API capabilities and the permissions granted by the account holder. All data access requires explicit customer consent.
