Bank APIs for Solana apps: Bridge vs Sphere vs Squads Grid

Every serious Solana payments conversation eventually hits the same wall: your app settles beautifully in USDC, and your customer wants to pay by bank transfer. Card on-ramps are expensive and cap out; "send crypto to this address" loses everyone who isn't already on-chain. The fix is a category that barely existed three years ago: bank APIs — services that give your app real bank account details (routing number, IBAN) and auto-convert whatever lands there into stablecoins on Solana, and back.

(This article exists because a reader asked "any bank API?" after our crypto-donations piece — The Giving Block does crypto/stock/card, but not ACH. Here's the ACH half of the story.)

The core pattern: virtual accounts

Every provider in this category sells the same primitive:

1. POST /customers        → KYB/KYC the end user or business
2. POST /virtual_accounts → get real bank details (ACH routing + account,
                            IBAN for SEPA, etc.) tied to that customer
3. Fiat arrives           → provider converts to USDC automatically
4. USDC lands             → in a wallet/account on Solana (or other chains)

...and the reverse: POST a payout, USDC leaves, ACH/SEPA/SWIFT arrives.

Your user sees "wire money to this account number." Your backend sees a webhook and a USDC balance on Solana. Nobody installed a wallet.

Bridge — the Stripe-scale default

Bridge is the category leader — Stripe bought it for $1.1B in October 2024 (Stripe's largest acquisition), and it now powers Stripe's USDC payouts in 70+ countries and its Stablecoin Financial Accounts product.

• Virtual accounts in USD, EUR, GBP, and MXN with local routing details; incoming fiat converts to USDC by default, credited to a Bridge wallet.
• Rails: ACH, SEPA, SWIFT. ACH is near-free; SWIFT wires run $15–30 on the underlying rail.
• Chains: Solana, Ethereum, Base, Polygon, Arbitrum, Tron, Stellar — USDC on Solana is a first-class settlement target.
• Extras: stablecoin-backed card issuing (spend your Solana USDC via Visa), custody, FX, and their own USDB stablecoin.

Pick Bridge when you want the deepest liquidity, the most countries, and the comfort of Stripe compliance machinery — and you're fine with the trade that Solana is one chain among seven, not the center of the product.

Sphere — the Solana-native operator

Sphere grew up in the Solana ecosystem (it's the name behind solana.com/solanaramp) and sells the same shape with a payouts/treasury flavor:

• Rails: ACH, wire, SEPA, and PIX (Brazil) — the LatAm coverage is a real differentiator.
• Currencies: USD, EUR, BRL fiat; USDC, USDT, EURC on Solana, Ethereum, Base, Polygon, Avalanche, Arbitrum, Tron.
• Offloader Wallets API — a wallet whose entire job is "any stablecoin that lands here becomes fiat in this bank account," one API call to configure. The cleanest off-ramp primitive in the category.
• REST APIs + SDKs, plus a no-code dashboard for the ops team.

Pick Sphere when Solana is your home chain, you need LatAm/cross-border payouts, or you want the off-ramp-as-a-wallet primitive instead of building conversion logic.

Squads Grid — the smart-account bank

Squads (the multisig/smart-account protocol securing $15B+ on Solana) packaged its infrastructure as Grid: REST APIs for global USD accounts, payments, yield, tokenized-asset trading, and card issuance, with a unified ledger across stablecoins, ACH, wire, and SEPA.

• Accounts are Squads smart accounts on Solana — programmable, multi-authority, recoverable. Your "bank account" is an on-chain object you actually control, not a row in a provider's custodial database.
• Yield and treasury features are built in rather than bolted on — aimed at neobank-style products, not just ramps.
• Solana-only by design: the pitch is stablecoin banking on Solana, not multichain orchestration.

Pick Grid when you're building a fintech product (neobank, treasury, payroll) where the account itself — custody model, programmability, yield — matters as much as the ramps.

The rest of the map

• Brale — when the product is issuing your own stablecoin with bank rails attached, rather than moving USDC.
• Zoneless — the marketplace angle: Stripe-Connect-style split payments and payouts, Solana-settled.
• Stripe itself — if you're already a Stripe shop, Stablecoin Financial Accounts (101 countries, USDC + ACH / SEPA / wire in one balance) may arrive in your stack before you go looking for it. It's Bridge underneath.

Choosing, honestly

                      Bridge          Sphere            Squads Grid
owner                 Stripe          independent       Squads Labs
Solana's role         1 of 7 chains   home chain        the only chain
fiat rails            ACH/SEPA/SWIFT  ACH/wire/SEPA/PIX ACH/wire/SEPA
virtual accounts      USD/EUR/GBP/MXN USD/EUR/BRL       USD (global)
custody model         Bridge wallets  provider/self mix on-chain smart
                                                        accounts (yours)
distinct strength     scale, cards,   LatAm + Offloader programmability,
                      Stripe distro   off-ramp wallets  yield, multisig
best for              global payouts  Solana payouts,   stablecoin
                      at max reach    cross-border ops  neobanks

Cross-cutting caveats, whoever you pick:

• KYB is the real integration cost. The API calls are trivial; getting your business and your users through compliance onboarding is the schedule risk. Ask about approval times before you architect.
• You're adding a regulated intermediary. The whole point is that they hold the bank relationships — which means account freezes, geographic exclusions, and ToS live in your critical path. Read the prohibited-industries list early; "crypto-adjacent" businesses get surprised.
• Quote in all-in cost, not API price. FX spread + rail fees + conversion fees stack. A "free ACH deposit" that converts at 50bps isn't free at volume.

Resources

• Bridge: apidocs.bridge.xyz — API reference and changelog.
• Sphere: docs.spherepay.co and GitHub at Sphere-Laboratories.
• Squads Grid: developers.squads.so and GitHub at Squads-Protocol (the v4 protocol programs are open source).
• Stripe stablecoin accounts: docs.stripe.com/crypto/stablecoin-financial-accounts.

TL;DR

• Bank APIs = virtual accounts with real routing details that auto-convert fiat ⇄ USDC on Solana. Your app gets a bank account number; your backend gets webhooks and stablecoins.
• Bridge (Stripe) for maximum reach and card issuing; Sphere for Solana-native payouts and LatAm rails (PIX); Squads Grid for neobank-grade products on programmable on-chain accounts.
• Brale (issue your own stablecoin) and Zoneless (marketplace splits) cover the adjacent shapes.
• Budget for KYB and read the prohibited-industries list before writing code — compliance, not the API, is the integration.