Explore with your agent
Sign in to your bank locally. Use your browser-capable coding agent to understand an existing payment and its data.
OPEN SOURCE · BUILT IN THE OPEN
Your bank.
Your agent.
Everyone’s
infrastructure.
The world has thousands of banks.
Let’s connect them, together.
An open library of banking integrations, built by people and their coding agents. Turn the knowledge inside your bank account into code everyone can use.
MIT licensedNo extension requiredAgent-ready
MercuryFirst integration
Your bankYour next contribution
openplaidCOMMON KNOWLEDGE
AdaptersReadable. Reusable.
Fixtures & reportsTested in the open
One integration is a beginning.
A community makes it infrastructure.
A community makes it infrastructure.
01 / OPEN BY DEFAULT
Every bank is different.
The knowledge shouldn’t stay siloed.
A SMALL CONTRIBUTION. A SHARED FOUNDATION.
From your bank
to everyone’s toolkit.
You bring access to your own bank. Your agent helps do the work. The community makes it better.
Make the knowledge reusable
Contribute a small adapter, synthetic or sanitized fixtures, and tests for the tricky cases. Keep private data private.
Build on each other’s work
Review an integration. Report what worked or failed. Maintain it as the bank changes. Everyone benefits from the next fix.
THE QUESTION BEHIND EVERY PAYMENT
Did A pay B?
Banks express the answer differently. OpenPlaid makes their payment data understandable: who paid whom, how much, in which currency, and what the bank’s status actually means.
Useful building blocks for payment attestations, reconciliation, and open financial applications.
Understand the evidence model →SYNTHETIC EXAMPLEus/mercury
- FROM
- Synthetic account A
- TO
- Synthetic account B
- AMOUNT
- 123.45 USD
- BANK STATUS
- sent
Supported interpretation
Sender-bank evidence. Recipient credit and source authenticity remain unproven.
THE LIBRARY STARTS HERE
One bank today.
Yours could be next.
M
ExperimentalMercury
United States · USD
Outgoing domestic wires. Sender-bank-reported sent status.
View integration ↗Don’t see your bank?
Open a request. Or let your agent help you build it.
Experimental means community-reviewed code, not production certification. Reports describe specific revisions and may include failures. Reporting handles are not verified unique people.
BUILT FOR THE AGENT ERA
You don’t need
to start from zero.
Give your agent the contribution skill. It covers the folder structure, payment semantics, privacy rules, and tests—so your first contribution has a clear path.
Read the contribution skill ↗YOUR NEXT AGENT PROMPT
Read AGENTS.md and skills/contribute-bank/SKILL.md in https://github.com/0xSachinK/openplaid. Help me contribute my bank’s payment integration. Keep raw captures and credentials local. Start with the evidence needed to determine whether A paid B. Do not initiate payments.
Works with your existing coding agent.REWARD THE WORK THAT LASTS
Good integrations
need good maintainers.
Help build a new adapter, reproduce a failure, or keep an integration working. Contribution requests are open; initial bounties are unfunded.
How incentives work →Open on Merit ↗Is OpenPlaid a bank or a Plaid product?
No. OpenPlaid is an independent open-source project. It is not affiliated with Plaid Inc., Mercury, or other named financial institutions.
Do I have to share my banking data?
No. Bank sessions and raw evidence stay local. Public contributions contain code, synthetic or carefully sanitized fixtures, and minimal test reports. This website has no bank-data upload.
Does an adapter produce a payment proof?
It interprets supplied data. Authenticating its bank origin and generating a signed payment attestation require a separate system. Never release funds based on a parser result alone.
Can anyone contribute?
Yes. Use your own authorized account and coding agent, follow the contribution skill, and submit a pull request. Testing, failure reports, documentation and maintenance all help.
Let’s make banking knowledge
a public good.