Flutterwave Subaccounts: Setting Up Marketplace Split in Lagos (2026)

The verdict in three sentences

Flutterwave Subaccounts does the split at the moment of collection, not after: each vendor receives their share directly, without the platform running a manual payout. It is the simplest way to launch a multi-vendor marketplace in 2026, with a cap of 200 subaccounts per split and 1.4% fees locally. The trade-off: less control over rounding and clawbacks than manual calculation, which matters as soon as partial refunds multiply.

How a subaccount works

A subaccount represents a vendor: it is linked to a settlement bank account or mobile money wallet. On creation, you define the split rate or a fixed amount the platform takes. On a payment, you pass the list of subaccounts and their share; Flutterwave distributes and settles each per its settlement cycle. Configuration steps:

• Create the vendor subaccount (name, settlement account, platform rate).
• Retrieve the returned subaccount_id.
• On payment initiation, attach the subaccounts and the transaction_split_ratio or a fixed amount.
• Receive the confirmation webhook and reconcile each share.

Split by percentage or fixed amount

For a classic 15% commission, you set the platform share to 15% and the rest goes to the vendor subaccount. For a multi-vendor order, you list each subaccount with its share pre-calculated.

Fees and delays: Flutterwave vs Paystack

Fees are 2026 orders of magnitude and vary by channel (card, mobile money, transfer) and country. Flutterwave wins on multi-country coverage and beneficiary cap; Paystack is often slightly faster on settlement in Nigeria.

Limits to know before choosing

The 200-subaccounts-per-split cap covers almost all real orders (baskets with more than 200 vendors are rare). The real friction point is elsewhere: automatic split settles vendors fast, which complicates partial refunds and clawbacks, since the money has already left for the vendor. If your marketplace has a high return rate, a hybrid model — centralized collection then deferred weekly payout — gives more control. For a fast launch with few returns, subaccounts are unbeatable for simplicity.

Mini case study

Moussa launches an electronics marketplace in Lagos with 25 vendors. He configures one subaccount per vendor, platform share 12%. In the first month: 310 orders, average basket 42,000 FCFA, GMV 13,020,000 FCFA. Gross platform commission: 1,562,400 FCFA. Flutterwave fee 1.4% on GMV: 182,280 FCFA absorbed from commission. Net platform margin: about 1,380,000 FCFA, without a single manual payout operation. Only adjustment: on 11 partial refunds, Moussa had to handle clawbacks manually, which convinced him to switch to a deferred model beyond 50 vendors.

FAQ

How many subaccounts per split on Flutterwave in 2026? Up to 200 subaccounts per split transaction, enough for the overwhelming majority of multi-vendor orders. Beyond that, you split or move to separate disbursements.

What are Flutterwave's local fees? Around 1.4% on local card payments in 2026, higher internationally (~3.8%) and variable in mobile money by country. Confirm against your contract.

Does settlement go directly to the vendor? Yes, each subaccount is settled to its settlement account (bank or wallet) per its cycle, generally T+1 to T+2 locally, without a manual platform payout.

Subaccounts or deferred payout: which to choose? Subaccounts for a simple launch with few returns. Deferred payout if your partial refund rate is high, because clawbacks are easier when the money is not already with the vendor.

Flutterwave or Paystack for a split in Africa? Flutterwave covers more countries and handles more beneficiaries per split. Paystack is strong in Nigeria and Ghana. The choice depends mostly on your target markets.

Let's talk about your project. We configure your Flutterwave subaccounts and webhook reconciliation, or a deferred model if your returns require it. WhatsApp +221 77 596 93 33.