Ecommerce integration
Connect Stripe with Wingspan to link client billing and worker pay. Collect client payments through Stripe Billing. Track the related contractor costs in Wingspan. Your team reviews funds and approves worker pay. Keep one owner for each payment. Client bills and worker pay keep separate controls.
Stripe 
Connect the work to the payment
Stripe
Invoice
Wingspan
Client invoices and payers
Stripe
Customer
Wingspan
Client invoices and payers
Stripe
PaymentIntent
Wingspan
Client invoices and payers
Choose which records sync and when they move. Your team stays in control of work review and payment approval.
Approved client work supplies billable units and line items. The client engagement keeps the billing terms. Wingspan creates a draft invoice in Stripe Billing. Your team reviews and sends the client bill. Contractor payables keep their own amounts and approvals.
Wingspan keeps worker forms and bank details for its own pay path. Stripe Billing gets client billing details and amounts. Stripe Connect has its own identity and bank checks. Share only the fields needed for the selected path. Each tool keeps its own access rules.
A client payment in Stripe updates the Wingspan client invoice. Your team sees which client bills are paid. For pay-when-paid work, finance checks funds before paying contractors. Payment success does not mean cash is ready to use. Payer approval for contractor pay stays separate.
Stripe Billing sends client invoices and collects payments. Wingspan manages worker records, work, and pay. Each worker record is called a payee in the app. It keeps the selected Contractor or W-2 type. Contractors use invoices and payables for amounts owed. W-2 workers use pay statements and payroll with tax withholding.
Client work and billing terms supply Stripe invoice lines. Stripe payment updates sync back to the Wingspan client invoice. For pay-when-paid work, your team reviews the client payment and available funds. A successful client payment does not approve worker pay. Finance gives separate payer approval for contractor payables.
Use Wingspan banking or the selected Stripe Connect pay path for each contractor payment. A Stripe Transfer moves funds to a connected account balance. A Stripe Payout moves funds to the account's bank. Keep one owner for each payment to avoid sending it twice.
Choose which tool holds each record. Set the changes that sync between them. Connect your records to the Wingspan workflows below.
Client invoices and payers
Wingspan to Stripe
Approved client work and billing terms supply Stripe invoice lines. Wingspan creates a draft Invoice in Stripe Billing. Your team reviews and sends it. Contractor invoices and payables track a separate amount owed to the worker. Client collections do not approve contractor pay.
Client invoices and payers
Stripe to Wingspan
Customer records in Stripe sync into Wingspan as client payer records. They give buyer details for client engagements and bills. Your team sees which client funds each job. You do not need to copy client profiles by hand.
Client invoices and payers
Stripe to Wingspan
Stripe marks a successful PaymentIntent as succeeded. Invoice payment updates sync to the Wingspan client invoice. Your team sees the paid client bill. For pay-when-paid work, finance checks funds before worker pay. Payment success alone does not prove cash is available. Contractor pay still needs separate payer approval.
Worker records (Contractor)
In both directions
Contractor worker records link to selected Stripe connected accounts. Wingspan keeps its own worker forms and bank records. Stripe Connect has its own identity, bank, and payment checks. Share only the fields needed for that path. W-2 pay uses employee payroll rather than contractor Connect transfers.
Payables
Wingspan to Stripe
Choose Stripe Connect for an approved contractor payable. Wingspan starts a Stripe Transfer for the selected amount. The transfer moves funds to the connected account balance. It is separate from the payout to a bank. Use one pay path for each payable. W-2 pay stays on the employee payroll path.
Payment status and references
Stripe to Wingspan
A Stripe Payout moves funds to the connected account's bank. Payout status and references sync to Wingspan for tracking. They apply to the selected Stripe pay path. Deposit confirmed means the sending bank or provider finished processing. It does not prove the worker bank posted funds. Payouts can still fail or return.
Client invoices and payers
Stripe to Wingspan
A Stripe Refund updates the client billing record in Wingspan. Your team reviews the change and linked project costs. A client refund does not remove money already owed for contractor work. Keep clear rules for holds, disputes, and corrections. Payer approval for new payments stays separate.
01
Your team approves billable client work.
Your team approves client work for billing. The client engagement sets rates and terms. Wingspan creates a draft invoice in Stripe Billing with the agreed line items. Your team reviews and sends the bill. Stripe returns the invoice ID for matching records. Contractor costs keep their own invoices and payables.
02
A client pays a Stripe invoice.
Stripe sends an invoice payment update to Wingspan. The client invoice shows paid. For pay-when-paid work, finance reviews client funds and linked contractor costs. A successful payment does not prove cash is ready to use. Your team gives separate payer approval for the contractor payable. Worker pay then follows the selected pay path.
03
Finance approves a contractor pay run.
Finance pays approved contractor payables through the chosen path. Use Wingspan banking or selected Stripe Connect payments. A Stripe Transfer moves funds to a connected account balance. The bank payout is a separate step. Each tool keeps payment dates and references. Deposit confirmed means the sending bank or provider finished processing. It does not prove the worker bank posted funds. Keep one owner for each payment.
Choose Wingspan banking or Stripe Connect for each contractor payable. Transfers to a Stripe balance and payouts to a bank are separate steps. Keep one owner for each payment. Do not send a second transfer to copy a payment already sent through Wingspan. W-2 pay uses employee payroll.
Set clear rules for Stripe refunds and project cost reviews. A client refund changes client income. It does not erase valid amounts owed for contractor work. Review the linked records before placing holds or making corrections. Keep worker pay approval separate from client billing updates.
Wingspan keeps worker tax forms and records for its pay path. Contractors use W-9 and 1099 forms. W-2 workers use their own withholding and payroll forms. Stripe Connect runs separate identity and bank checks. Choose one owner for each tax filing. Share only the fields needed for the selected payment path.
Connect worker records from hire to pay. Choose the Contractor or W-2 type and keep the right checks for each.
Ecommerce
Connect Square with Wingspan to link worker records, visits, and tracked hours. Your team reviews completed service work and closed timecards. Contractor work approval creates one amount owed. Finance gives separate approval before pay. W-2 pay keeps its own payroll path. Customer sales stay separate from worker costs.
Explore integration
Ecommerce
BigCommerce runs your store. Wingspan manages worker records and pay. Seller, affiliate, and service fees link store sales to contractor work. Your team checks the amount owed before payment. Orders and buyer profiles add context. They do not become workers or payables on their own.
Explore integration
Ecommerce
PayPal Braintree takes customer card and wallet payments. Wingspan manages worker records and pay. Service fees link sales to contractor bills. Your team reviews each amount owed before payment. Contractor pay and W-2 payroll follow separate paths.
Explore integrationBring worker records, work review, and payments together. We’ll help you set up the flow your team needs.
Discuss your integration