Your creators judge you on the payout.
Creator platforms pay earnings, revenue shares, referral bonuses and collaboration splits to thousands of independent creators, on a cycle or on demand, through their own product rather than a finance portal. DiscoFi gives that product one payout API: create the payout, get the status, reconcile the batch.
Payouts are a product surface, and they are the one you get judged on.
A creator does not experience your payout infrastructure as infrastructure. They experience it as a number that appeared or did not, on a day that was promised or was not. When it goes wrong they do not file a ticket about ACH return codes; they post about your platform. Payout reliability is a retention metric wearing an operations costume.
The engineering underneath is unglamorous and unforgiving. Thousands of small payments, each of which can fail for its own reason. A request that times out and has to be safe to retry without paying twice. Status that has to reach your UI before a creator refreshes it. A monthly cycle that has to reconcile exactly, because a cent of drift across 40,000 payouts is a support queue.
One API, and the hard parts already handled.
- Create the payoutOne call with the recipient and the amount. Idempotency keys make a retry after a timeout safe rather than a duplicate payment.
- Track it liveWebhooks carry status changes to your product, so a creator sees the same state you do.
- Pay on cycle or on demandBatch the month or release a single cash-out. Every payout is built for instant delivery.
- Reconcile the cycleEvery payout resolves to a final state against one ledger, so the cycle closes rather than mostly closing.
Every payout is built for instant delivery.* See Instant Pay disclosure Your team decides who gets paid and how much; the payout API handles everything after that.
What a monthly creator cycle looks like.
Monthly cycle, illustrative
- Creator earnings3,412 creators$742,600.00
- Revenue sharePartner tier$96,400.00
- Referral bonuses218 qualifying referrals$21,800.00
- Collaboration splits640 split payouts$38,900.00
- Settlement$899,700.00
4,270 payouts · One cycle · One ledger
Illustrative figures for a hypothetical operation, not a DiscoFi customer or a DiscoFi metric.
Questions this raises.
Can creators cash out on demand rather than waiting for a cycle?
Yes. A payout is a single API call, so an on-demand cash-out and a scheduled batch are the same operation at different times.
What stops a retry from paying someone twice?
Idempotency keys. A retried request with the same key returns the original result rather than creating a second payout, which is what makes a timeout safe to handle in your own code.
How does our product learn that a payout landed?
Webhooks carry status changes as they happen, with a reconciling poll as the backstop. Both are documented, including duplicate delivery and out-of-order events.
Do our creators need a DiscoFi account?
No. They are paid to the bank account they already have. Their relationship stays with your platform.
Run your next settlement on DiscoFi.
Starts at $1,000/month plus 0.28% of successful payout volume.
Banking services provided by FinWise Bank, Member FDIC.