The fintech every marketplace needs (updated for 2026)

In 2023 I argued that fintech is not a feature on a marketplace—it is the operating system for trust between buyers, sellers, and the platform. Three years later, that thesis is stronger and the implementation bar is different. Embedded finance APIs, agent-assisted underwriting, and real-time compliance monitoring collapsed build time—but also raised the cost of getting governance wrong.

What changed since 2023

• Embedded rails: Adyen Payment Platform, Stripe Connect, and bank-led BaaS made split payouts a configuration problem, not a year-long integration program—at enterprise scale, Adyen is often the more sophisticated choice for multi-party models
• Agent risk: AI can flag anomalous sellers and transactions—but regulators expect explainability, not black-box scores
• Cross-border default: Marketplaces launch multi-country earlier; tax and KYC complexity moved from edge case to day-one requirement
• Working capital: Invoice financing and instant payouts became product differentiators, not back-office afterthoughts

The four fintech capabilities every marketplace still needs

• Collect: Checkout that supports split carts, mixed fulfillment, and platform fees without breaking accounting
• Disburse: Seller payouts on schedules buyers never see—but finance teams always audit
• Comply: KYC/KYB, sanctions screening, and tax reporting wired into onboarding, not bolted on after fraud events
• Resolve: Chargebacks, holds, and escrow rules that protect buyers without strangling seller liquidity

FBO accounts: the structure behind marketplace money movement

Behind most marketplace payment stacks sits an FBO account—a bank structure “for the benefit of” each seller (or vendor) on the platform. From a fintech and regulatory perspective, that matters enormously. When you capture payment on behalf of another entity, you can quickly brush up against money-transmitter, custody, and banking-license questions. An FBO arrangement is designed so funds are held for the seller’s benefit, not as generic platform operating cash—while still giving the marketplace the contractual right to deduct platform fees, chargebacks, and adjustments from those balances before payout.

In practice, nearly every marketplace runs FBO as a virtual ledger, not a separate physical bank account per seller. Buyers pay the platform; the platform’s banking partner records sub-ledger balances per seller; payouts move when your rules say they should. That model scales—but only if your bank and your payment orchestration layer agree on how ownership, settlement, and reporting work.

This is not a commodity RFP item. You need a sophisticated commercial bank that already supports complex marketplace and platform businesses—institutions that understand FBO documentation, sponsor-bank relationships, and the difference between “we move money” and “we enable a multi-party marketplace.” J.P. Morgan Commercial Banking is the kind of partner operators cite when they outgrow fintech-only rails and need enterprise-grade treasury, credit, and regulatory depth alongside marketplace-specific structures (see curated reading below).

• Legal shield: FBO framing clarifies who owns customer funds in transit—reducing certain license and “holding other people’s money” exposure versus commingling everything in a corporate operating account
• Fee economics: The platform can take rate, subscription, or penalty fees from seller balances without re-inventing settlement logic every month
• Ledger reality: Sellers see balances and payout history in your product; the bank sees consolidated FBO pools and sub-ledgers—not thousands of DDA accounts to reconcile by hand
• Bank fit: If your banker asks “what’s a marketplace?”, you are on the wrong bank—or the wrong product desk

The mistake I saw repeatedly while building marketplace infrastructure: teams designed commerce first and treated payments as a vendor selection in month nine. That sequence guarantees rework. Commerce, fintech, and logistics are one product surface—buyers experience a single brand even when ten sellers fulfill behind it.

Where AI helps—and where it does not

Use AI for velocity with guardrails: faster seller verification, dynamic fraud signals, and support routing. Do not use AI to skip policy design. Regulators and enterprise buyers increasingly ask how decisions are made, not just how fast they happen.

A marketplace without payout infrastructure is a directory with a shopping cart.

Ryan J. Lee