Open Banking
4 technical briefings from 4 companies building open banking infrastructure.
Clay Allsopp
Plaid introduces Wallet Onboard — a Plaid product for crypto developers that brings the familiar Plaid "connect" experience to self-custody crypto wallets. Where Plaid has always linked bank accounts to fintechs, Wallet Onboard normalizes the fragmentation across hundreds of crypto wallets, multiple connection protocols, and the UX differences between MetaMask, Coinbase Wallet, Rainbow, Ledger, and WalletConnect-compatible wallets. The demo shows auto-detection of installed extensions, per-wallet optimized flows (QR for mobile-only wallets, desktop app handoff for hardware), direct wallet-to-app data flow with no Plaid intermediary on wallet addresses, and a drop-in vanilla JavaScript SDK that takes roughly an hour to integrate — plus auto-updates for new wallets and protocols delivered via cdn.plaid.com. Use cases span token gating, NFT mint, holdings tracking, payouts, and message-signature-based authentication.
Jack Ryan
Jack Ryan of FinGoal demos the FinGoal Switch Kit — a wrapper around Plaid, MX Link Money, Yodlee, and other aggregators that normalizes the account and transaction shape so you can swap aggregators in minutes instead of months. The live demo starts with a Next.js app running a Plaid link against Wells Fargo, then swaps the token endpoint and frontend portal to MX Link Money — which authenticates via open banking directly in the Wells Fargo app. The migration philosophy is not a big-bang swap: FinGoal recommends leaving existing Plaid connections alone and re-linking users through the new aggregator only when a connection breaks, so net-new users and natural re-auths silently migrate without churn. The Switch Kit\'s payoff is that the success page digests the callback event string from Link Money and renders the new accounts and /transactions/get output alongside pre-existing Plaid data — same schema, same categories, same fields — with only three files changed across the entire app. The thesis: developers should not be locked into an aggregator by migration cost.
Lindsay Davis & Jeff Hendren
Lindsay Davis and Jeff Hoffer of Atomic demo Atomic's payroll-connectivity APIs — used by hundreds of thousands of consumers per month across challenger banks, neobanks, and online lenders to switch direct deposits, verify employment, and verify income. Atomic ships a standard SDK across iOS, Android, React Native, Flutter, and Kotlin that partners typically integrate in ~4 hours. The demo walks through launching Transact inside a partner app (passing a unique GUID and the destination account/routing number), distinguishing Deposit (write) flows from Identify/Verify (read) flows, and handling the employer-vs-payroll-provider selection. Atomic's conversion engineering is a differentiator: reverse-engineered in-modal password resets push authentication conversion to ~70%, and two-factor authentication (present in ~28% of logins) is handled inside the flow. Linked accounts enable periodic VOE/VOI refreshes without re-prompting the user. Partial direct-deposit switches power investing apps that want to route a percentage or dollar amount of each paycheck to a new destination without the user changing their primary bank.
Brankas is an open banking platform across Southeast Asia — Philippines, Indonesia, Thailand, Vietnam, Singapore. CPO Mike and Senior PM Luis demo Direct, the Brankas bank-transfer product that aggregates transfers across multiple banks via API with the end-user's explicit consent. Brankas never holds funds (no Stripe-style settlement); it exposes consent, authentication, and routing over open-banking rails. The demo walks through the two-endpoint Direct API (payment initiation, transaction retrieval), a live 100-peso payment from a BPI account in the Philippines through Brankas's IDP (identity provider) consent flow, per-bank authentication (username/password, TFA, OAuth 2 where banks support it), a biometric in-app authorization step on the BPI mobile app, and the final redirect + callback webhook that tell the integrator the payment settled. Production use cases include e-wallet top-up, lender collection, marketplace checkout, and bill payment.