Banking-as-a-Service & Treasury

Our team builds embedded-finance products on Stripe Treasury and the surrounding BaaS surface — balances held on the platform, money moving in and out, and cards issued under the user’s brand. We’ve built this kind of infrastructure for some of the largest companies in the world, serving millions of users, in very high-profile environments. When a user is building real financial infrastructure, we build the application and operational layer around Stripe’s APIs.

What we build

We build Treasury financial accounts attached to connected accounts, programmable inbound and outbound transfers (ACH, wire, and between-account) that respect reserves and velocity controls, and the Issuing flows that keep authorization, settlement, and balance accounting coherent when cards are tied to a Treasury balance. We build the operational tooling a financial product can’t run without: the dashboards, alerts, and reconciliation views the operations team uses every day.

How we approach it

BaaS lives or dies on the operational and regulatory design, so that’s where we focus. We design the reserve and liquidity handling, the authorization controls (velocity limits, dual approval on large transfers, country restrictions, and AML signals), and a ledger an auditor will accept, all on top of Stripe’s Treasury and Issuing APIs. Offering financial accounts comes with program terms, and we account for those from day one.

Working with your Stripe team

We work at enterprise scale, which is most of what BaaS is. We partner closely with the Stripe account executive, Professional Services, and solution architects when they’re involved: Stripe owns the platform and the banking-partner relationship, and we build and operate the application layer on top. Bring us in early, because BaaS rewards getting the structure right before the build.