Marketplaces
Charge the buyer once. Pay each seller their share.
A marketplace collects one payment as the merchant of record and divides it between sellers. Each split lands in the seller's own Flint balance and goes out with the seller's own payouts. Refunds, disputes, and negative balances follow published rules, and every movement is a balance transaction.
3.79% + 35¢ on cards · no monthly fee · free sandbox · no credit card
Test mode now
Create payments with splits, approve sellers, refund, and dispute in a sandbox. Test mode needs no review.
Live needs approval
Live splits are off by default. They're available after Flint approves your platform for splits, under the Flint Platform Agreement.
Sellers are merchants
Each seller has its own Flint balance, ledger, payouts, and dashboard, and approves your terms before it receives a cent.
01One payment, divided
One $100.00 order, two sellers, one payment.
Craftly runs a handmade goods marketplace. A buyer orders a $70.00 mug set from Mugworks and a $30.00 scarf from Loom & Co. Craftly creates one $100.00 payment with two splits and keeps what is left.
| Who | Field | Amount |
|---|---|---|
| The buyer paysOne card payment, created with Craftly's API key | amount_money | $100.00 |
| Flint's processing feeThe published card rate, 3.79% + 35¢ | processing_fee_money | -$4.14 |
| Mugworks, split 1Its own Flint balance | splits[0].amount_money | -$60.00 |
| Loom & Co, split 2Its own Flint balance | splits[1].amount_money | -$25.00 |
| Craftly keepsIts commission, after fees and splits | merchant_net_money | $10.86 |
The captured amount always equals Flint's fees plus every split plus the marketplace's share. Craftly never holds Mugworks' or Loom & Co's money in its own balance, and Flint never fronts a seller's share: a split transfers only after the payment's funds are available.
02Create the payment
Send splits with the payment.
Use your own API key. Each split names a seller's install of your partner app and an amount in the payment's currency. Splits are part of the idempotency fingerprint.
curl -X POST https://api.withflintpay.com/v1/payment-intents \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/json" \
-H "Idempotency-Key: craftly-order-1042" \
-d '{
"amount_money": { "amount": 10000, "currency": "USD" },
"payment_options": ["card"],
"splits": [
{
"partner_app_install_id": "pinst_01KF3A8C2D4E6F8G0H2J4K6M8N",
"amount_money": { "amount": 6000, "currency": "USD" },
"description": "Order 1042: 2 stoneware mugs",
"external_reference_id": "1042-mugworks"
},
{
"partner_app_install_id": "pinst_01KF3A9N4P6Q8R0S2T4V6W8X0Y",
"amount_money": { "amount": 2500, "currency": "USD" },
"external_reference_id": "1042-loom"
}
]
}'1 to 25 splits, one per seller install. description and external_reference_id are yours, and the seller sees both.
{
"payment_split_id": "psplit_01KF4B2C4D6E8F0G2H4J6K8M0N",
"partner_app_install_id": "pinst_01KF3A8C2D4E6F8G0H2J4K6M8N",
"seller_merchant_id": "mer_01KF3A7B1C3D5E7F9G1H3J5K7M",
"status": "pending",
"pending_reason": "awaiting_funds",
"amount_money": { "amount": 6000, "currency": "USD" },
"reversed_money": { "amount": 0, "currency": "USD" },
"shortfall_money": { "amount": 0, "currency": "USD" },
"funds_available_at": "2026-11-11T00:00:00Z",
"reversals": []
}The split stays pending with a reason and a date until its funds are available.
- splits
- PaymentIntent.splits
- merchant_net_money
- pending_reason
- funds_available_at
- reversed_money
- shortfall_money
- Accepted on
POST /v1/payment-intents,POST /v1/orders/{order_id}/paywithaction: pay, and capture, which takes each split's final amount.- Who can send them
- Only the marketplace's own credentials. An install token can't, and a payment with splits can't carry a platform fee.
- Collecting the card
- Initialize Stripe.js with your Flint publishable key alone, without a connected account.
client_confirmation.stripe.account_idisnullon these payments. Buyers enter a new payment method for each split payment. - If the splits don't fit
- Splits must leave room for Flint's largest fee and one minor unit for you. Otherwise the request returns
INVALID_VALUEatsplitswithmaximum_money.
03Sellers
A seller is a Flint merchant that installed your app.
Flint has no lighter recipient type. A seller already has a verified account, a balance, payouts, a ledger, and a dashboard, so none of that is yours to rebuild.
1. Declare your terms
Set payment_splits.seller_terms_url on your partner app. Setting it needs no review, and sellers see the link on the consent screen. In the dashboard, it's the Seller terms panel on the app's Platform tab.
2. The seller approves
A seller installs your app and approves receiving split funds, separately for test and live. The consent screen says you take its share back when you refund a sale, lose a dispute, or a payment fails. Sellers created inside your product approve through the emailed signup code.
3. Check it can receive
Store the seller's partner_app_install_id and read its readiness with its install token. A seller must have payouts ready in the payment's mode, or admission returns seller_not_ready. Sellers see their approval in the dashboard under Settings, Connected apps.
curl -X PATCH https://api.withflintpay.com/v1/partner-apps/PARTNER_APP_ID \
-H "Authorization: Bearer YOUR_LIVE_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"expected_version": 8,
"payment_splits": {
"seller_terms_url": "https://craftly.example/sellers"
}
}'- payment_splits
- seller_terms_url
- approved_at
- partner_app_install_id
Change seller_terms_url and sellers that already approved keep the terms they approved. Remove payment_splits and every approval ends at once. A seller that disconnects stops new splits, but refunds and disputes on earlier sales still take its share back.
04When sellers are paid
Sellers are paid when the payment's funds are.
A split doesn't reach the seller the moment the buyer pays. Flint transfers it after the payment's funds are available on Flint's balance, about two business days for US cards, and after any dispute on the payment closes.
Split status
- pending
- processing
- succeeded
- failed
- canceled
pending waits, processing is transferring, and succeeded means the split is in the seller's balance, available at once. If a seller can't receive it for seven days, the split is failed and the amount returns to you. canceled means it will never transfer, such as when the payment didn't complete or the seller's approval ended before capture. Reversals change amounts, never status.
Why a split is pending
- awaiting_payment
- awaiting_funds
- dispute_open
- reversals_pending
Show sellers pending_reason and funds_available_at so they know when to expect the money. You can't hold a split until delivery or release one early.
05Refunds and disputes
Money going back follows a rule you can read.
You are the merchant of record, so you answer for every refund and dispute in full. Flint takes each seller's share back first, and you fund the rest.
Refunds
By default Flint takes each party's share back in proportion: on a $40.00 refund of Craftly's $100.00 payment, $24.00 from Mugworks, $10.00 from Loom & Co, and $6.00 from Craftly. Send split_reversals to name each seller's amount, or an empty list to fund the whole refund yourself. Flint keeps its processing fee on a refund. Refund a split payment
Disputes
You answer as the collecting merchant, and sellers never see the buyer. While a dispute is open, untransferred splits stay pending. A withdrawal lowers or reverses each split by the same proportional rule, and you fund the rest and the dispute fee. A win reinstates what was taken. Disputes and chargebacks
Negative seller balances
A reversal takes only what the seller's balance covers. If the seller already paid the money out, the shortfall is yours to cover, and you cover it at once. The split's shortfall_money and a seller_shortfall_coverage entry on both ledgers record it.
curl -X POST https://api.withflintpay.com/v1/refunds \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/json" \
-H "Idempotency-Key: refund-1042-mugs" \
-d '{
"refund_type": "amount",
"payment_intent_id": "pi_01KF4B1Z3X5C7V9B1N3M5Q7W9E",
"amount_money": { "amount": 4000, "currency": "USD" },
"split_reversals": [
{
"payment_split_id": "psplit_01KF4B2C4D6E8F0G2H4J6K8M0N",
"amount_money": { "amount": 3000, "currency": "USD" }
}
]
}'- split_reversals
- PaymentRefund.split_reversals
- Dispute.split_reversals
A seller's net from a split is its amount, minus what was reversed, plus any shortfall you covered. Sellers can't refund: only the collecting merchant owns the payment.
06Reconcile
Every movement is a balance transaction.
You and each seller read the same split with your own credentials. Six balance transaction types record the money, each naming the split.
Balance transaction types
- payment_split
- payment_split_reversal
- payment_split_reinstatement
- payment_split_failure
- seller_shortfall_coverage
- seller_shortfall_coverage_reversal
Webhook events to the marketplace
- payment_split.created
- payment_split.updated
- payment_split.succeeded
- payment_split.failed
- payment_split.canceled
Sellers don't get payment_split.* events. They learn of money reaching or leaving their balance from balance_transaction.created. Filter splits by payment, seller, install, your own external reference, status, or time window.
curl "https://api.withflintpay.com/v1/payment-splits?status=succeeded" \
-H "Authorization: Bearer SELLER_API_KEY"Sellers see your description and external reference for each split, never the buyer or the payment.
In the dashboard, any merchant that is a party to a split gets a Splits tab on Balances, with each split's status, what was taken back, and the ledger entries behind it. Reconciliation guide
07Choose the right feature
Splits, split tender, platform fees, and separate checkouts.
Four things in Flint look alike from a distance. Each answers a different question.
- Splits
- One payment's funds divided between the marketplace and its sellers. You are the merchant of record. Marketplace guide
- Split tender
- One order paid with several payment methods, such as a gift card and a card. One merchant, one buyer. Gift cards guide
- Platform fee
- A fixed fee your software platform adds to a payment it creates for an installed merchant, within the cap that merchant approved. The merchant is the merchant of record. Platform fees guide
- Separate checkouts
- Each seller takes its own payment as its own merchant, and the buyer pays each one. Fits marketplaces that don't want to be merchant of record. Build payments into your platform
- Inventory transfers
- Stock moving between a merchant's locations. Not related to money.
Pricing the same marketplace on Stripe Connect? Its account and payout fees are worked out for three platform sizes. Flint’s published pricing has neither.
08Availability and limits
What works today, and what splits don't cover.
Test mode runs the whole flow. Live splits need Flint's approval, and a few funds flows are outside splits.
Availability
Test mode works now. Seller approval, admission, refunds, disputes, and reversals all run in a sandbox without review, and the test card 4000 0000 0000 0077 makes test funds available at once.
Live splits are switched off by default. They're available after Flint approves your platform for splits. The Flint Platform Agreement says Flint doesn't accept splits yet and that it will publish the rules for sending, reversing, and recovering split funds before it does. A live request with splits returns 409 MERCHANT_NOT_READY with reason payment_splits_unavailable.
Not covered by splits
- Checkout sessions, payment links, invoices, and subscriptions.
- Saved payment methods on a split payment, and Affirm.
- Paying a seller's bank account directly, or sending a seller money outside a payment.
- Holding a split until delivery, or releasing it early.
- Splits created with a partner app token, and a platform fee on the same payment.
- Choosing which seller funds a dispute.
- Currencies other than USD.
reviewed 2026-11-13 against the public OpenAPI spec and the marketplace, partner app, refunds, disputes, and reconciliation guides · corrections: Flint Help
Start
Run a split payment in a sandbox.
Node
CLI
Declare payment_splits on a partner app, install it on a test merchant that approves splits, and pay a $100.00 test payment with 4242 4242 4242 4242. Pay with 4000 0000 0000 0077 to make the test funds available at once and watch the split move from pending to succeeded. Sandboxes guide
The build, in reading order
- 01Marketplaces and seller splitsThe whole flow, with the rules.
- 02
- 03
- 04
- 05
- 06
- 07
Or run npm install -g @flintpay/cli && flint signup to create your account and a sandbox key from the terminal. CLI guide
FAQ
Questions marketplace teams ask about splits.
Can I split one buyer payment between several sellers?
Yes, if your platform collects the payment as the merchant of record. You create the payment with your own API key and a splits list, one entry per seller. Each seller is a Flint merchant that installed your partner app and approved receiving split funds, and each split goes to that seller's own Flint balance once the payment's funds are available.
Can I use splits in live mode today?
Test mode works now, with no review. Live splits are switched off by default and are available after Flint approves your platform for splits. Flint's Platform Agreement says Flint doesn't accept splits yet and that it will publish the rules for sending, reversing, and recovering split funds before it does. Until then a live request with splits returns 409 MERCHANT_NOT_READY with reason payment_splits_unavailable.
When do sellers get paid?
Each split waits for the payment's funds to become available on Flint's balance, about two business days for US cards, and for any open dispute on the payment to close. The split shows pending_reason and funds_available_at until then. Once it transfers, it sits in the seller's Flint balance, and the seller's normal payouts carry it to its own bank account.
What happens to a seller's share when I refund?
Flint takes each party's share of the refund back in proportion by default, or the amounts you name with split_reversals. You fund whatever the sellers don't give back, first from your share of that payment and then from your balance. A split that hasn't transferred yet is lowered instead, and the seller's ledger shows nothing. Flint keeps its processing fee on a refund, as on any payment.
What if a seller has already paid out the money that a refund or dispute takes back?
A reversal takes only what the seller's balance covers. The rest is a shortfall, and the marketplace covers it at once as the merchant of record. The split's shortfall_money shows how much, and a seller_shortfall_coverage balance transaction records it on both ledgers.
Who answers a dispute on a split payment?
The marketplace, as the collecting merchant, through the same dispute response sessions as any payment. Sellers can't read the payment or the buyer. While a dispute is open, splits that haven't transferred stay pending. When Stripe withdraws the disputed funds, each seller gives back its share, and the marketplace funds the rest and the dispute fee. A loss changes nothing more. If the dispute is won, every reversed amount goes back to whoever funded it.
Is this the same as split tender or inventory transfers?
No. Splits divide one payment's funds between merchants. Split tender is one order paid with several payment methods, such as a gift card plus a card. Inventory transfers move stock between locations. A payment with splits can be one leg of a split tender order.
Can I take a platform fee on a split payment?
No. A payment with splits can't carry a platform fee, and only the collecting merchant's own credentials send splits. Your commission is what you don't send to sellers: the payment minus Flint's fee and every split.
Can I pay a seller's bank account directly or hold a split until delivery?
No. A split credits the seller's Flint balance and the seller's own payouts carry it to its verified bank account. Flint can't send a seller money outside a payment, and each split transfers when the payment's funds are available rather than on a date you choose.