
Inside a Marketplace Migration: What Switching Payout Providers Actually Takes
What you'll learn
- A step-by-step look at a payout migration, from discovery through sunsetting your current provider, including where 1099 payouts and wallet options fit into scoping
- What should you ask a payout provider before you switch?
- Which integration model fits your team, and what does testing involve?
- How does launch actually work, and what happens during the grace period?
- When is it safe to turn off your old provider?
About 80% of gig workers say they would choose one gig platform over another if it paid instantly and without fees. For most established marketplaces, that isn't news. The hard part is the switch itself.
Payouts touch worker onboarding, your ledger, your support queue, your fraud controls, and your year-end tax filing. Nobody wants to explain a missed payday to tens of thousands of contractors.
A payout migration is a defined project with a known shape, though. It breaks into four steps. Here’s what each one involves, what to ask your shortlist along the way, and where the work tends to get underestimated.
Step 1: Discovery and scoping
Discovery removes most of the risk, and the questions that matter least are about your tech stack.
Any provider worth shortlisting will ask about your worker classification mix first, since 1099 contractors and W-2 employees carry different compliance requirements and different product paths. Next comes payout timing: job completion, daily batch, weekly cycle, or some mix across markets. Then funding. Many payout setups require a pre-funded account to cover upcoming payouts. For a marketplace paying out $1 million a day, that can mean $1 million tied up in a funding account, plus the work of topping it up, sometimes days in advance. Ask each provider whether they require pre-funding, and if so, how much and how far ahead.
They should also ask how your workers want to get paid. Some contractors want earnings pushed to the debit card they already carry. Others want a wallet of their own. When one Branch marketplace customer let contractors choose, 46% picked a branded wallet, compared to 39% who chose instant debit and 14% who chose ACH. Plan for more than one option.
One question that’s easy to skip: who owns worker support when a payout fails? Settle that in discovery, not during your first incident.
Step 2: Integration and testing
This is the step engineering leaders brace for. Most providers offer some version of two models, and choosing between them is mostly a question of how much of the worker experience you want to own.
A hosted or widget-based path means you embed a component or redirect workers to a browser, and the provider manages the screens for onboarding, payment history, and payment method updates. It’s a lighter build and a lighter maintenance commitment.
An API-built path means your team owns onboarding, terms acceptance, payment history, and payment method changes inside your own product. It’s a heavier build to stand up and maintain, and it earns its keep when payouts are part of how you differentiate.
Either model shares the same moving parts: an endpoint to onboard a worker, an endpoint to post earnings, and webhooks your system listens to so a worker becomes eligible to get paid. Providers that publish their developer documentation openly let your engineers size that work before you sign anything.
Before anything reaches workers, expect thorough testing in two places: a sandbox environment first, then user acceptance testing in production. That testing is what makes a single, confident launch possible in the next step.
Your timeline still depends on your codebase, your security review, and your legal team. Treat any firm go-live date quoted before a technical discovery call as a guess.
Step 3: Launch to every worker
Launch means the new payout option is live for every worker in your app or portal. Payout migrations typically don’t move workers over in waves. Instead, they go live for everyone at once, followed by a defined grace period. During that window, workers set up their new payment method before the old one turns off.
That makes worker communication the most important part of launch day. Give workers real notice, and ask your provider what communication support they bring. When NexRep switched providers, the team sent communications about the change two weeks ahead of the transition, using materials built with Branch. Most of their agents set up their own accounts by following those steps, which kept the support load manageable.
Branch’s co-marketing team works alongside customers on that launch communication, with pre-built resources ready to adapt, so marketplaces don’t have to explain the change to workers on their own.
Communicate in the worker’s own context, too. Workers trust your brand, not a payments company they’ve never heard of, so the announcement should come from you inside the app they already open. Lead with what changes for them, in their terms.
Adoption is how most teams judge whether a launch worked. Nursa saw about 1 in 4 active clinician users make their new payment experience their primary method within a month of full rollout, and those clinicians picked up 15% more shifts than clinicians using other methods.
Step 4: Close the grace period and sunset your old provider
Rollout is complete when the grace period ends and the new provider becomes your only one. Some marketplaces add a new provider alongside their existing payout methods instead, in which case there’s nothing to sunset.
Expect a few issues along the way. What matters most is how quickly they get resolved and whether you can reach someone directly. Onboarding also comes with a lot of detail at once, so knowing who to call keeps small questions from becoming big ones. FlexCrew’s president contrasted Branch with a previous provider where the team had no integrator or account manager, noting that with Branch, they can talk to a real person when they need help.
Before you turn anything off, work through a short checklist:
- Confirm payout destinations. Make sure every active worker has a verified payout method on the new platform, ideally through a query rather than a spreadsheet.
- Reconcile in-flight payouts. Make sure nothing gets stranded between systems on cutover day.
- Keep your records. Export historical payout data, since you’ll need it for disputes and audits long after the contract ends.
- Settle the tax year on purpose. If you’re migrating mid-year, decide in writing which provider files 1099s for the period it covered, and confirm who files going forward.
- Check your notice window. Review your current contract’s termination terms before you flip the switch.
What should you ask any payout provider?
- What are the platform and transaction costs to the business?
- Do you require pre-funding, and if so, how much and how far in advance?
- How are fraud, customer support, compliance, and the banking relationship handled, and by whom?
- For card programs, who holds the network and issuing relationships?
- Who answers the worker when a payout fails, your team or mine?
- What communication and co-marketing support do you provide at launch?
- Will we have a direct contact once we’re live?
The answers will separate your shortlist faster than a feature comparison will.
What the switch can be worth
FlexCrew, a construction staffing marketplace, switched off a provider with 5-6 business day payout delays and a 2.9% transaction fee. After moving to Branch, payments arrive immediately after processing, and FlexCrew no longer pays that fee. Fetch, a last-mile delivery platform, says faster daily pay created a cycle that significantly reduced their need for recruitment.
Migrations are worth the disruption when the destination removes a cost you’re currently carrying, not just when it adds a feature.
Talk through your migration
The fastest way to learn what your switch actually takes is to put your real constraints in front of a team that has done it before. Bring your worker mix, your payout cadence, your funding model, and your deadlines, and you’ll be prepared for a productive chat with a potential partner.
Get a demo to start that conversation.
Branch is not a bank. Banking services are provided by Evolve Bank & Trust, Member FDIC or Lead Bank, Member FDIC ("Sponsor Banks"), as listed on the back of a user's Branch Card. FDIC insurance only applies for eligible accounts should the Sponsor Bank holding the user's funds fail. The Branch Mastercard Debit Card is issued by the Sponsor Bank pursuant to a license from Mastercard and may be used everywhere Mastercard debit cards are accepted.
Continue reading
Unlock a Happier, More Productive Workforce



