Articles
18th Nov 2026

Implement Payee Onboarding for Payouts: Crawl, Walk, Run (Nov 2026)

Generated Excalidraw Graphic 1793546779896

If your team is scoping payee onboarding and the conversation has already turned into a debate between shipping fast and owning the full experience, you’re in the right place. Payee onboarding is part of the broader payout experience, and the right integration depth depends on how fast you need to launch and how much control you need over what payees see. That trade-off has three distinct resolution points, and picking the wrong one for your current engineering bandwidth is what usually delays go-live or creates payee drop-off after launch.

TLDR:

  • Choose your integration tier based on engineering bandwidth and brand control, not a forced progression.
  • Hosted flow (crawl) goes live with no engineering build; Routable absorbs compliance updates.
  • Embedded iFrame/SDK (walk) keeps onboarding inside your screens; compliance ownership stays with Routable.
  • Full API (run) gives full screen control; your team owns error states and new fields.
  • Payees are screened against 6,000+ watchlists at onboarding and before each disbursement.

What Payee Onboarding Actually Covers for Payout Operations

Payee onboarding in a payout context covers three data categories:

  • Contact details
  • Payment method preferences
  • Legal or tax documentation

You need all three before a single payment runs. Miss one, and the disbursement fails or creates a compliance liability. For platforms paying hundreds or thousands of payees, from Drivers to Creators to nonprofit Grantees across dozens of jurisdictions, the collection problem scales fast.

Integration depth is a product decision. It sets what payees experience, how much engineering your team owns, and who absorbs compliance updates as volume grows.

The Three Integration Depths: Crawl, Walk, Run

Routable offers three tiers: hosted flow (crawl), embedded iFrame/SDK (walk), and full API (run). Routable runs compliance checks, validation, and sanctions screening on every tier. On the API tier, your team collects the fields and adds new ones when requirements change.

Pick your tier on current engineering bandwidth, go-live timeline, and desired brand control, not a forced progression.

Crawl: Launch With a Hosted Flow

The hosted flow is the lowest-friction path from zero to live. Routable sends the payee a link to a white-labeled, Routable-hosted flow and runs every step end to end: contact information, payment method selection, and tax documentation. No engineering build required on your side.

Who Owns What

  • Styling customization is limited to your logo and primary color.
  • Event response comes from Routable, which runs the flow end to end.
  • MFA and notifications split between the two parties: Routable owns MFA, and your team owns notifications.
  • Compliance and updates stay with Routable, which owns compliance, validation, error states, and any updates triggered by new regulatory requirements.

The Trade-Off: Payees Leave Your UI

  • Payees finish onboarding in a Routable-hosted browser flow. Routable can email them an invitation, or your platform can link them out to it.
  • If brand control is a hard requirement, that gap matters. If you need to launch fast with a standard experience, it does not.

Where Hosted Flow Fits Best

  • Launching a corridor you have not validated or standing up a beta program before a deeper build is scoped
  • Teams with no available engineering bandwidth in the current sprint cycle
  • Organizations that need a compliant, functional onboarding path running before a hard deadline

Pair the hosted flow with Routable’s CSV upload to run mass payouts on day one with no engineering resources. When your program calls for it, pair it with API-driven automation and webhook-triggered workflows instead.

Walk: Embed Onboarding Inside Your Own Screens

The embedded iFrame/SDK tier sits between hosted and API on both control and engineering lift. Routable components for contact details, payment method, and legal/tax information sit inside your own screens. No Routable branding appears anywhere in the flow.

Who Owns What

  • Styling is customizable, with no Routable branding.
  • You receive an event response on each iFrame submission, so your product layer knows where a payee stands.
  • Your team owns MFA and notifications.
  • Routable owns compliance, validation, error states, and any updates triggered by regulatory changes.

The Trade-Off: Build Time on Both Sides

  • Your team places the components, Routable builds and maintains them, so plan for integration sprints on each end.
  • The embedded iFrame/SDK is generally available in the UK, Canada, and Mexico. Later markets are proven in beta first, so confirm current coverage for your target payee corridors with Routable before scoping the build.

Where Embedded Fits Best

  • This tier fits platforms running creator royalty payouts where the payee experience is a product differentiator.
  • For gig marketplaces and seller networks, a native in-app feel beats a redirect to a third-party screen.
  • Teams that want onboarding inside their own screens without building the forms themselves find a native feel here.

If components still cannot match your design system, or you need to control every field and step, the Run tier gives your team full ownership of the payee experience.

Run: Full API Control Over Every Screen

With the API tier, your team owns every screen, field order, grouping, and flow structure. Routable runs behind the scenes, handling compliance checks, validation, and sanctions screening without surfacing to the payee at any point.

Who Owns What

  • Styling is fully your design, including field order, grouping, and every step.
  • Your platform receives an event response on every API call, so your product layer always knows where a payee stands.
  • Your team owns MFA and notifications.
  • Routable runs the compliance checks and updates the API when requirements change, while your team collects the fields, owns error states, and adds new fields.

The Trade-Off: Most Engineering Work

  • Your team builds every screen and calls the API behind the scenes.
  • On the hosted and embedded tiers, new requirements propagate automatically, while on the API tier, your team adds the fields.

Where API Fits Best

  • Platforms where third-party components cannot match the design system.
  • Teams that need control over field order and grouping.
  • Teams with stable engineering capacity and proven payout volume in the target market.

If you are still validating a payee corridor, start with the hosted flow or embedded iFrame. Move up once volume justifies the build.

Side-by-Side Comparison: Hosted Flow vs. Embedded vs. API

Dimension

Hosted Flow (Crawl)

Embedded iFrame/SDK (Walk)

API (Run)

Experience ownership

Routable

Shared (Routable builds components, you place them)

Your team

Engineering effort

None

Moderate, both sides

Highest

Customization depth

Logo and primary color only

No Routable branding, custom styling

Fully your design

Event response

Routable runs the flow end to end

On each iFrame submission

On every API call

MFA ownership

Routable

Your team

Your team

Notification ownership

Your team

Your team

Your team

Compliance ownership

Routable

Routable

Routable runs checks; your team collects the fields

Error state ownership

Routable

Routable

Your team

New requirements handling

Routable absorbs automatically

Routable absorbs automatically

Routable updates the API; your team adds the fields

Crawl hands the most to Routable, Run puts the most on your team, and Walk splits ownership between both. Start in the column that matches your engineering capacity and payee experience requirements today.

When to Graduate to the Next Phase

Watch for these signals that your current tier no longer fits.

Crawl to Walk

  • Payees notice the redirect and drop off or ask why they left your product.
  • Support tickets pile up around the onboarding flow itself, not downstream payment issues.
  • Your product needs real-time event data during onboarding that the hosted flow cannot provide.

Walk to Run

  • iFrame styling limits keep your onboarding screens from matching your design system.
  • You need control over field order or grouping for a compliance or UX need.
  • Your team can own ongoing field changes, and payout volume supports the build.

Starting at Walk or Run

None of these phases are mandatory steps. Teams with engineering capacity and a hard brand requirement on day one can start at walk or run directly.

What Stays With Routable on Every Tier

Across all three tiers, Routable owns the compliance logic. TIN validation, sanctions screening against 6,000+ watchlists (including OFAC sanctions lists), and pre-payment checks all run on Routable’s infrastructure no matter whether a payee completes onboarding through a hosted link, an embedded component, or a screen your team built entirely. On the API tier, your team builds the screens that collect the fields and present the right W-8/W-9 form, while Routable executes the checks. The same onboarding data then drives 1042-S/1099-NEC filing for your international and domestic payees.

New requirements are changes to what gets collected or checked, driven by regulation or by the payment providers moving the money, for example a new required field, a new country, or an updated tax form. KYC and sanctions screening run as one workflow that has to stay current as rules shift.

What changes across tiers is who absorbs those updates. On a hosted flow or embedded iFrame, Routable absorbs them automatically. On the API tier, Routable updates the API and your team adds the fields. The compliance logic never moves. Owning those updates is also the core cost of building a payout solution in-house. Every new field, country, and form change becomes your team’s job permanently, starting at launch.

Getting Started With Payee Onboarding for Mass Payouts

Start with the hosted flow if you need to launch this sprint, or go straight to walk or run if your design system demands it. Then move up as volume and bandwidth grow. Routable runs the compliance checks on every tier, from W-8/W-9 collection at onboarding to 1042-S/1099-NEC filing at year-end. On the API tier, your team collects the fields. Request a demo to see each tier in a live environment.

FAQ

What’s the difference between Routable’s hosted flow, embedded iFrame, and full API for payee onboarding?

Engineering ownership rises as brand control rises. The hosted flow needs no build: Routable sends payees a link and runs the flow, but payees leave your product. The embedded iFrame places Routable’s components inside your screens with no Routable branding. The full API gives your team every screen while Routable runs compliance checks behind the scenes. Pick based on engineering bandwidth and brand requirements on day one.

How do I implement payee onboarding for payouts without delaying my go-live date?

Start with the hosted flow. It needs no engineering build, and you can collect payee contact details, payment method preferences, and W-8/W-9 forms right away. Once your market is validated and engineering capacity opens up, move to the embedded iFrame or full API. Crawl is a compliant starting point, not a temporary workaround.

Can I build a fully branded payee onboarding experience without owning the compliance layer?

Yes. The embedded iFrame and full API tiers let you own the payee-facing experience with no Routable branding, while Routable keeps running TIN validation, sanctions screening against 6,000+ watchlists, and tax form routing. On the API tier your team collects the fields and Routable executes the checks.

When should a gig platform or creator network move from the embedded iFrame to the full Routable API for payee onboarding?

Move to the full API when any one of these signals applies: iFrame styling cannot match your design system, you need granular control over field order or grouping, or your engineering capacity is stable enough to own ongoing field additions and payout volume justifies the build. If you are still validating a new payee corridor, the embedded iFrame covers the experience requirement without the field-maintenance burden of the API tier.

What happens to a batch if one payee is flagged by sanctions screening?

Only that payee’s payment is held. Routable screens every payee against 6,000+ watchlists (OFAC, EU, FTO) at onboarding and again immediately before each disbursement. A flagged payee’s payment goes on compliance hold for review while the rest of the batch keeps processing. This holds on every integration tier because the screening runs on Routable’s side.