Q2 2026 Wingspan Product Updates

This quarter, Wingspan Embed covers the full contractor journey, bulk approvals run in the background, requirement edits keep a full history, and failed payments finally explain themselves.

Kate Shpakouskaya
Kate Shpakouskaya

At Wingspan, we're focused on solving the unique needs of businesses managing a flexible workforce, across the entire lifecycle. This quarter, we shipped updates that make approvals faster at scale, give you more control over your compliance requirements, and bring more clarity to payments. Here's a look at what's new.

Wingspan Embed covers the full contractor journey

Wingspan Embed is now a product partners install in a single line, and it spans the whole contractor journey rather than sign-up alone.

  • Onboarding, assembled to fit. Pick which steps to include: account creation, payroll funding method, payroll settings, tax certification, payout method, payment method, eligibility requirements, and tax withholdings.
  • Changing a payout method. Contractors update how they get paid without leaving your platform.
  • Changing a payment method. Same for the method a client pays with.
  • Changing or previewing a funding source. Set the account payroll draws from, or show which one is on file.

Options set the contractor’s country during onboarding and limit which payout methods appear, so the flow matches what you support. Partners who handle all contractor communication themselves can also switch off Wingspan's transactional emails across their account, with security and compliance messages still going out.

Wingspan Embed covers the full contractor journey

Approve thousands of payables without watching the screen

Start a bulk approval and it keeps going on its own. Close the tab, move to another task, or shut your laptop, and the job still finishes. The list you're working from stays accurate the whole time, so what you see matches what's been approved.

Approve thousands of payables without watching the screen

Edit a requirement, keep the version history

Compliance rules change. A carrier raises a minimum coverage limit. A document template gets a new version. An expiration window moves from 30 days to 130.

You can now edit a requirement definition in place, and decide who the change reaches.

  • Edit what's live. Change the name, description, review strategy, expiration strategy and window, manual renewal setting, or the underlying configuration such as a minimum insurance limit.
  • Pick the scope. Apply the change retroactively to existing requirements, or forward only, so it governs new requirements while completed ones stay as they are.
  • Pick how contractors transition. Move affected requirements straight to incomplete, or open them for renewal with a deadline so contractors keep their eligibility while they resubmit.
  • Keep the record. Every edit creates a version. Each requirement shows its current version and the ones before it, so you can tell which configuration a contractor completed and when.
Edit a requirement, keep the version history

Clear payment failure state for teams that invoice their own clients

These changes apply if you use Wingspan to bill your clients and collect what they owe you, rather than only to pay your contractors.

When a client's payment fails, the error now names the specific reason. An ACH return reads as the return it was, and a card decline names the decline instead of showing a generic card error. Most payment failures are fixable by whoever caused them once the cause is visible, which means fewer stalled invoices and less chasing.

Clear payment failure state for teams that invoice their own clients
Share this post