Skip to main content
Bridge is Banking-as-a-Service. You ship financial features; a partner bank/FSP holds custody and owns compliance. You get one set of developer-first APIs for customers, wallets, lending, and payment collections.
Everything below is built around the flows already running in production. Pick a recipe, copy the code, get a real result.

​
Start in your AI editor

The fastest way in: let Claude Code or Cursor build the integration for you. Connect the docs once:
Then paste this into your agent (swap the use case for KYC, wallets, lending, BNPL, or payment collections):
No keys needed to start — the agent writes the code; you add your key when you’re ready to call the API (Getting started). More on the agent setup: Connect your AI agent.

​
Start with a recipe

Customer onboarding (KYC)

Create a customer, submit KYC, activate. Every other flow starts here.

Wallets

Open a wallet, fund it, place and capture escrow holds.

Lending

Create a loan, preview the schedule, disburse, and record repayments.

BNPL

Down-payment hold + loan + auto-sweep repayments, end to end.

Payment collections

Trigger a USSD push, poll status, record the verified payment.

First call in 5 minutes

Token to first real API response, no detours.

​
How it fits together

  • KYC is the authoritative customer store. A customer must be active before holding wallets or loans.
  • Wallets hold stored value; deposits are gateway-verified; escrow supports hold-and-capture.
  • Lending originates loans, optionally linked to a wallet with an auto-sweep standing instruction for repayments.
  • Collections trigger mobile (USSD) payments; verified payments post to loans or wallets.

Onboarding

How businesses join Bridge, what credentials you get, and sandbox vs production.

​
Before you send money

Tokens expire hourly

Tokens last about an hour. On a 401, re-generate the token and retry once — built into every recipe.