Lead Bank: the FDIC bank under Bridge cards and Visa USDC settlement on Solana

When Visa put US domestic stablecoin settlement on USDC over Solana in December 2025, two US banks were named in the first cohort: Cross River and Lead Bank. That is not a marketing footnote for this site. Lead is also the issuer bank behind Stripe Bridge's stablecoin-linked Visa cards, and its partner docs list solana as a first-class rail on the Blockchain Payments API. Put simply: a regulated US bank is treating Solana as settlement and money-movement infrastructure, not as a side experiment.

This piece sits next to our Visa Stablecoin Platform coverage (the network control plane) and our bank APIs for Solana apps guide (Bridge, Sphere, Squads Grid as app-facing ramps). Lead is the charter underneath several of those flows: system of record, compliance, card issuance, Fed connectivity.

Click to zoom

What Lead actually is

Lead is a Missouri state-chartered, FDIC-insured bank that also runs a national Banking-as-a-Service platform. The current leadership — Jackie Reses (CEO), Ronak Vyas (CTO), Homam Maalouf (product/data), Erica Khalili (legal/risk) — all came out of Square / Block and acquired the bank in 2022 for about $56M. In September 2025 they closed a $70M Series B at a $1.47B post-money valuation, with ICONIQ and Greycroft joining existing backers including a16z, Ribbit, Coatue, and Khosla.

Positioning is deliberate: the bank is the platform. Partners are not renting a thin API that proxies a silent community bank. Lead markets itself as system of record, with direct Fed connectivity for ACH and wires, in-house compliance, and programmable product primitives. It still runs ordinary personal and business banking in Kansas City — the community book that keeps regulators oriented — while the growth story is embedded finance for fintechs and digital-asset companies.

Four pillars: Lend, Issue, Move, Store

The Partner Platform is sold as composable blocks rather than a single mega-product:

• Lend — term loans and lines of credit (consumer and commercial), including BNPL-style structures; origination and disbursement over ACH or wire.
• Issue — debit, prepaid, credit, and charge cards on Visa, Mastercard, and Amex; BIN sponsorship with bring-your-own processor.
• Move — ACH (same-day and next-day), FedWire, SWIFT, internal transfer, checks, FedNow instant payments, payment controls, and stablecoin / blockchain payments. Marketing now explicitly calls out agent-forward / agentic commerce workflows.
• Store — FDIC-insured deposit structures, FBO accounts, multi-currency balances, and virtual account numbers mapped to a single ledger account.

Public customer and partner names that matter for Solana builders: Stripe and Visa (stablecoin-linked cards via Bridge), Ramp and Affirm on core product rails, Branch for workplace payments, and Loop Crypto for stablecoin payment products. Lead is not a crypto exchange; it is the regulated banking layer those programs need.

Where Solana shows up (three concrete places)

Dec 2025  Visa launches US domestic USDC settlement.
          Initial banks: Lead Bank + Cross River.
          Initial chain: Solana.

2025–26   Bridge (Stripe) × Visa stablecoin-linked cards.
          Cards issued by Lead Bank; spend from stablecoin
          balances (incl. self-custody wallets). Multi-country
          live; expansion narrative toward 100+ markets.
          On-chain settlement path ties back to Visa's pilot.

Docs      Lead Blockchain Payments API documents rails:
          solana | base | ethereum  →  USDC or USDB
          plus fiat corridors (ACH/wire, IBAN, CLABE, Pix, FPS…).

The settlement pilot is the regulatory signal. The card program is the consumer product signal. The API docs are the developer signal: Solana is not only a press release chain; it is named in the same table as ACH and wire as a way value leaves or enters a Lead program. Transaction minimums and "wrong address / unsupported asset = permanent loss" warnings are bank-grade, not crypto-Twitter casual.

For context on why settlement keeps landing on Solana (finality, fees, USDC depth), see stablecoins on Solana. For Visa's broader mint/move/manage control plane (Ethereum, Solana, Tempo at launch), see the Visa Stablecoin Platform article.

Developer surface: partner APIs, not a public keypair

Lead's documentation at docs.lead.bank is unusually complete for a sponsor bank: Mintlify-style guides, OpenAPI, sandbox simulation endpoints, and an llms.txt index. Integration is still program-based. You do not self-serve a production key from a marketing page. Onboarding is contracting, due diligence, and a technical program launch with a Technical Account Manager.

Once inside a program, the shape looks like modern fintech ops:

• Auth: OAuth2 client credentials, scoped access tokens, IP allowlists in production.
• Object model: Entity (KYC/OFAC unit) → Account → Account Number (routable address; many virtual numbers per account) → Balance / Transaction.
• Interfaces: REST for real-time actions; SFTP pipe-delimited files for batch reporting and network settlement.
• Rails in API: ACH, Wire (v1/v2), Instant Payments (FedNow), Internal Transfer, Blockchain Payments, Cards (beta), Lending / Funding, Applications (Reg B).

Blockchain payments use the same API posture as other rails: POST /v0/blockchain_payments with a debtor (Lead account or external wallet) and a creditor (wallet or local bank details). Lead converts and settles; partners do not manage chain mempools. Documented chains today: solana, base, ethereum for USDC and USDB, with more available on request through the TAM.

# Conceptual shape (partner-gated; not a public sandbox walkthrough)
POST /v0/blockchain_payments
  debtor:  Lead account_number  OR  { wallet_address, chain }
  creditor: wallet  OR  local rail (ach_wire, clabe, pix_key, …)
  amounts: instructed + settlement currency
  payment_purpose: invoice_payment | …

# Documented blockchain rails (settlement currency)
solana    → USDC | USDB
base      → USDC | USDB
ethereum  → USDC | USDB

Honest developer read, same stance as our Visa piece: most Solana builders will never call Lead directly. They will touch SPL USDC, Bridge wallets, card spend, or a fintech that has Lead under the hood. If you are building a regulated program that needs a charter, card BIN, FBO structure, and chain ramps in one partner, Lead is on the short list with Cross River and a handful of other crypto-willing banks.

Crypto solution page vs API docs

Marketing has a short Crypto solution page: on-ramps (fiat into FBO + virtual account numbers) and off-ramps (fiat out after crypto→fiat conversion). The deeper story is in API docs under Blockchain Payments — cross-border local rails funded by stablecoins, not only US ACH. Treat the marketing page as the use-case summary and the blockchain payments overview as source of truth for rails and constraints.

Developer experience: product bet, not a community yet

Lead is hiring a Developer Experience Lead (senior IC) to own docs.lead.bank, changelogs, upcoming-changes discipline, and partner-facing release communications — with runway to build a team. That is a clear signal that DX is becoming a competitive surface, not an afterthought. There is no public GitHub org of SDKs comparable to Stripe or even Visa's agent toolkit; the open surface is documentation, sandbox (for partners), and the bank's own X account @Lead_Bank.

Directory note: we list the org, the docs resources, and the four co-founders. Jackie Reses is the only co-founder with a verified public X handle in our data (@jackiereses). The DX Lead seat is open as of this writing — when someone fills it, that is the natural DevRel-shaped profile to add.

How to think about Lead if you build on Solana

• Wallet / app builders: Support USDC (and watch USDB / program-specific coins). Card spend from self-custody via Bridge-style products is the UX users feel; Lead is invisible plumbing.
• Fintech / RWA / payments startups: If you need a US bank partner that already ships stablecoin cards and Solana settlement adjacency, evaluate Lead against Cross River and other API-native banks. Budget for compliance onboarding, not just integration tickets.
• Infra / analytics: Visa's onchain settlement and card programs create measurable USDC flows; Lead is one of the named bank endpoints in that graph.
• Do not confuse layers: Bridge and Sphere sell app-facing bank APIs; Lead often sits under those or parallel as sponsor. Your integration contract might never say "Lead" even when Lead is the ledger.

Resources

• lead.bank — product home; BaaS Partner Platform
• docs.lead.bank — API docs, sandbox, OpenAPI; Blockchain Payments overview and supported chains / fiat rails
• Series B announcement ($70M, $1.47B valuation) and ICONIQ partnership note
• @Lead_Bank / @jackiereses
• No public first-party GitHub engineering org for the BaaS APIs — partner access is docs + program credentials, not open SDKs.
• Related on devrels.xyz: Visa Stablecoin Platform, bank APIs for Solana apps, stablecoins on Solana, Credible Finance