Banking-as-a-Service · Use case

Run a marketplace payout flow on Banking-as-a-Service

Short answer

Marketplaces collect from buyers, hold funds and pay sellers — and touching those funds can be a regulated activity. A BaaS provider can hold them under its licence, keep a balance per seller and pay out on schedule, so the regulated perimeter sits with the partner.

What this use case is

A money flow where the platform sits between buyers and sellers: collect, hold, split, pay out, handle refunds.

Who builds this

Goods and services marketplaces
Gig and freelance platforms
Travel and rental platforms
Creator platforms

What your customer sees

  1. 1Seller signs up and verifies
  2. 2Buyer pays
  3. 3Seller sees a pending balance
  4. 4Funds become available after the holding period
  5. 5Seller receives a payout to their bank account

How Banking-as-a-Service solves it

1

Buyer pays by card through a payment processor, or by bank transfer

Buyer pays by card through a payment processor, or by bank transfer

2

Funds land in a safeguarded account under the licence holder

Funds land in a safeguarded account under the licence holder

3

The amount is allocated to the seller's sub-ledger, minus your commission

The amount is allocated to the seller's sub-ledger, minus your commission

4

Funds are held for the delivery or dispute window

Funds are held for the delivery or dispute window

5

Payout to the seller's IBAN on schedule or on demand

Payout to the seller's IBAN on schedule or on demand

6

Reporting per seller, including data you need for platform tax reporting

Reporting per seller, including data you need for platform tax reporting

Want to have

  1. Seller onboarding with KYC or KYB
  2. Per-seller balances
  3. Split payments and commission
  4. Scheduled and on-demand payouts
  5. Holds and releases
  6. Refunds and negative-balance handling
  7. Per-seller reporting

Optional

  1. Multi-currency payouts
  2. Cards for sellers
  3. Data for platform tax reporting such as DAC7

Design decisions

Regulatory route

Licensed partner holds funds
Rely on an exemption

exemptions can be narrow and are interpreted strictly; get legal advice before relying on one. [TO CONFIRM: legal analysis for your markets]

Stack

Payment processor's marketplace product
BaaS plus separate acquiring

one integration versus more control over funds and payouts

Payout timing

Scheduled
On demand
Instant

seller satisfaction versus refund and fraud exposure

What to put in your RFP

Structure

  • who holds funds, under which licence

Sellers

  • onboarding scope, verification, countries

Money flow

  • splits, commission, holds, payout schedules

Exceptions

  • refunds, disputes, negative balances

Data

  • per-seller ledgers, reporting, reconciliation with the payment processor

Commercials

  • per-seller, per-payout and FX pricing
Add these to an RFP

How to evaluate providers for this use case

  1. 1Clarity on who holds funds
  2. 2Seller onboarding completion
  3. 3Handling of refunds after payout
  4. 4Reconciliation between collections and payouts
  5. 5Coverage for sellers' countries

Pitfalls

  • Relying on an exemption without a legal opinion
  • Seller verification friction
  • Reconciliation gaps between the payment processor and the BaaS ledger
  • Negative balances from refunds after payout

What providers will ask you

  1. Seller and buyer countries
  2. Transaction volumes and average basket
  3. Holding periods and refund policy
  4. Current payment processor

Other Finlane categories that cover parts of this

This use case is solved mainly with Banking-as-a-Service. These categories cover specific parts of it and can be tendered alongside it.

Frequently asked questions

Questions for this use case are covered in the category guide.

Solving this with another category instead? See Run marketplace split payments

See the full cross-category stack for this use case

Other Banking-as-a-Service use cases

Scope operate a marketplace payout flow with Banking-as-a-Service providers

Scope this use case