Insights Contact

Payment Rails

Embedded Payments Runbook: Platforms, Fintechs and Partner Banks

By SP Sankar

Embedded payments put money movement inside products that aren’t banks: software platforms, marketplaces, payroll apps and fintechs with partner banks. The app owns the customer experience, but the bank keeps the license and the risk. This is the short version of how I take an embedded payments product from idea to live, safely.

New here? Start with How a US Payment Works: 15 Steps Inside a Bank, then come back for the detail.

How embedded payments fit together

How embedded payments fit togetherThe platform owns the experience; the bank and provider hold the license and the moneyStep 1End customerPays or gets paidinside the appStep 2PlatformProduct, onboarding,supportStep 3Provider orprocessorRuns the railsand APIsStep 4Sponsor bankHolds funds andregulatory dutyStep 5LedgerEvery balancematched dailyWhat holds it togetherResponsibility matrix · KYC and KYB · monitoring · limits and reserves · daily ledger-to-bank reconciliation
How embedded payments fit together

Read from left to right. Each box is one party in an embedded payments product, from the customer using the app to the ledger that records every balance. The band at the bottom shows what must be shared and proven across all of them. Above all: a daily match between the ledger and the money at the bank.

Four common models

ModelWhat it meansWho holds the main license or bank role
Payments provider integrationThe platform uses a provider’s API (a way for two systems to talk to each other) to take payments for its usersThe provider and its acquiring bank (the bank that accepts card payments for sellers)
Payment facilitator (PayFac)The platform signs up its own sellers (sub-merchants) under its one main seller account with the card networksThe platform, through a sponsor acquirer (the seller’s bank for card payments)
Banking as a service (BaaS)The platform offers accounts, cards or transfers through a partner bankThe partner (sponsor) bank
Marketplace payoutsThe platform collects from buyers and pays sellersThe provider or bank, plus state money transmitter license rules to check

The lesson from Synapse

Customer money often sits together in one shared account at a bank, called a “for benefit of” (FBO) account. Every balance in your ledger must then match real money at the bank, every day. The 2024 collapse of Synapse showed what happens when records and bank balances don’t match.

Agree who does what before you build. A written responsibility table (a RACI) should name the owner of customer checks (KYC), fraud and AML monitoring, disputes, complaints and reconciliation, across the platform, the provider and the sponsor bank. US bank regulators expect banks to oversee their fintech partners closely.

Building it: short cycles, firm checkpoints

  • Draw where the money goes for every use case, and get the provider and the sponsor bank to approve it.
  • Plan partner approvals as fixed dates: program approval, marketing review and compliance testing often take weeks.
  • Prove it live with a small group of friendly customers. Run every money flow, and match the ledger to the bank every day of the pilot.
GateDone when
E2E exitEvery money flow traced end to end, ledger matches the bank to the cent, sign-up checks and limits proven
UAT exitSupport, risk and finance procedures signed; disclosures and marketing approved by the bank
Go-liveSponsor bank and provider approval, pilot checked and matched, monitoring and daily reconciliation running

Open banking note: the CFPB’s Section 1033 data access rule was finalized in October 2024. In October 2025, a federal court paused it while the CFPB reconsiders. Check where it stands before you rely on it.

Running it live

Alert on failed payments and payouts, API and webhook errors, fraud spikes and, above all, any gap between the ledger and the bank. If they don’t match, stop payouts and tell the sponsor bank first.

Download the full runbook (PDF, 11 pages)

Every phase in detail, with the four models, rules, a responsibility matrix approach, exit criteria and sign-off, a pilot plan, controls, alerts, incident runbooks, disaster recovery and audit checklists.

Download the PDF

More payment runbooks

The bottom line

Embedded payments work when every party knows its job and the ledger always matches the bank. Agree responsibilities first, reconcile daily from day one, and treat the sponsor bank as a partner in every launch.

Working on a payments project?

I help banks and fintechs deliver real-time payments, ISO 20022, and AI-driven AML and compliance change, from strategy to go-live.

Connect on LinkedInSee how I can help