Open Finance Playground
The developer's guide to building on Brazil's Open Finance ecosystem.
Open-source documentation that distills hundreds of pages of regulatory specifications into practical, step-by-step implementation guides. Built and maintained by Juspay and Cumbuca.
Explore every API call behind the flow
The largest Open Finance ecosystem in the world
Brazil's Open Finance ecosystem already moves at a scale most markets are still planning for.
The front door has been narrow for a long time.
The official documentation exists, is extensive, and meets its regulatory purpose. But it was written to describe what the system requires, not to teach how to build on it.
Hundreds of pages of specifications, scattered cross-references to external RFCs, and implicit requirements that no single guide ties together.
A fintech arriving today spends weeks on technical archaeology just to answer the most basic question: what's the first API call I need to make?
The documentation the ecosystem was missing.
Turns specs into shippable code The Playground distills hundreds of pages of regulatory specs into practical, step-by-step implementation guides your engineers can actually ship from.
Built from real engineering notes Born inside Juspay and Cumbuca, where teams had to translate the spec into working code first.
Open-sourced when the pain became clear What started as internal documentation is now public, because every fintech in the market hits the same wall.
Maintained for the long run Built and maintained by Juspay and Cumbuca, with contributions open to the entire Open Finance community.
OPEN SOURCE · MAINTAINED BY JUSPAY & CUMBUCA.
The things developers actually need to know when implementing.
The Playground complements the official documentation. It doesn't replace it. The complete regulatory reference stays where it is. The Playground is the "getting started guide" that helps you take your first steps.
-
Step-by-step API flows
End-to-end sequences for the calls you'll make first.
-
Security requirements
FAPI, mTLS, JWS, and DCR explained the way you'll implement them.
-
Bank-specific quirks
The undocumented edges that only show up in production.
-
Consent management
Lifecycle, scopes, renewals, revocations.
-
Payment initiation
From PISP setup to settlement, in the right order.
The Playground complements the official documentation. It doesn't replace it. The complete regulatory reference stays where it is. The Playground is the "getting started guide" that helps you take your first steps.
Built for the people implementing Open Finance, not describing it.
Three ways to get hands-on, today.
Documentation
Step-by-step implementation guides, organized by flow. From consent management to payment initiation.
Explore the docsSimulator
See Open Finance flows in action. Follow each API call behind each step of the user experience.
Try the simulatorSource code
View the code, report issues, contribute. The project is open source and welcomes community contributions.
View on GitHubBuilt and maintained by
Juspay
Juspay's engineering team created the Playground from real-world experience implementing Open Finance end-to-end in Brazil. Juspay is a global payments infrastructure company operating across 30+ countries and serves as the project's primary maintainer and open-source repository owner.
Cumbuca
Cumbuca is the project's co-maintainer, a Payment Institution authorized by Brazil's Central Bank, and co-founder of INIT. Pedro and Nic (Cumbuca) serve as co-owners and maintainers alongside Juspay, contributing regulatory expertise and deep knowledge of the Brazilian ecosystem.
This project grows with the Open Finance community.
The Playground is maintained by Juspay and Cumbuca. If you're implementing Open Finance in Brazil, your experience belongs here.
The Playground is only as good as the community behind it.
If you've implemented Open Finance and learned something in the process, your experience can help hundreds of other developers. Here's where to start:
