Virtual Assistant and BPO Merchant Accounts: Billing Guide
A VA client can dispute a monthly retainer as services not rendered, since there is no shippable product or receipt. Here is how the account defends that.
By Gray Merchants Team
- VA and BPO firms sell time and task completion, not a shippable product, so services-not-rendered disputes are decided on documented activity, not a delivery receipt.
- Recurring monthly billing plus offshore or distributed delivery teams push this category into high-risk underwriting even though the actual work is legitimate and low-fraud.
- Proper dunning and retry logic on failed card renewals prevents a chunk of rebill disputes before they happen, since a silently failed card often looks like a surprise charge on the next attempt.
- The global BPO market is worth roughly $358.6 billion in 2026 en route to $695.8 billion by 2033, and the human VA services segment alone is valued at $5.6-6.5 billion in 2026, meaning billing volume in this category keeps outgrowing legacy account limits.
- B2C SaaS and services chargeback rates rose 83% year over year through 2025 and 83% of enterprise merchants report rising friendly fraud, which is why documented time and task activity, not just fraud screening, is the real defense for VA and BPO billing.
A virtual assistant or business-process-outsourcing firm sells time and task completion, not a shippable product. That single fact drives most of the underwriting friction in the category. A client who is unhappy with a month of work has no delivery receipt to point to either way, and a card network cannot independently verify how many hours actually got worked.
Why standard accounts flag VA and BPO billing
Recurring monthly billing brings the usual rebill disputes and involuntary churn from failed card renewals, the same friction any subscription business sees. On top of that, distributed and offshore delivery teams with no domestic storefront read as higher risk to processors built around retail card-present transactions. Larger managed-services and staffing plans concentrate high monthly charges onto a single account, and a cross-border client base adds settlement complexity that a standard account was never underwritten for. This isn't a niche problem, either. Around 37% of small businesses in the US now outsource at least one function to stay competitive, according to DemandSage, which means more of them are running exactly this billing pattern than a standard risk model expects.
How big the VA and BPO billing category actually is
The scale here matters because it explains why this friction shows up so often instead of being an edge case. Grand View Research puts the global BPO market at roughly $358.6 billion in 2026, growing to $695.8 billion by 2033 at a 9.9% compound annual rate. The human virtual assistant services segment specifically is valued between $5.6 billion and $6.5 billion in 2026, per VA Masters. That growth is being pulled by adoption on the buyer side too: solo entrepreneurs and micro businesses are the heaviest users of virtual assistant services, a pattern consistent with how fast small operators are turning task work into recurring monthly spend rather than one-off project fees.
More volume flowing through recurring retainers means more accounts scaling past the limits they were originally underwritten for, often before the firm itself notices. A VA agency that started with a few $500-a-month client retainers looks very different once it's running dozens of accounts, some billing $3,000 or more a month for a dedicated executive assistant. Revisiting account limits as that mix grows, rather than waiting for a processor hold to force the conversation, is the practical lesson behind the market numbers.
Billing models that make underwriters nervous
VA and BPO firms don't bill one consistent way, and that variability is itself part of the risk read. Roughly 72% of virtual assistants charge by the hour, while the rest work on retainer, per-task, or flat monthly packages, according to Project Untethered's original-research survey (published December 2024). Hourly work and project-based work also price differently: project-based VAs average $29.34 an hour against $20.15 for straight hourly billing in that same survey. A firm mixing hourly clients, flat retainers, and larger staffing contracts on one account produces exactly the kind of ticket-size and billing-frequency variability that trips an automated fraud model calibrated for one predictable pattern.
That variability is showing up in the dispute data too. B2C SaaS and services chargeback rates rose 83% year over year through 2025, a jump the Sift Q4 2025 Digital Trust Index ties largely to recurring billing confusion, subscription churn, and first-party disputes rather than actual stolen-card fraud. VA and BPO retainers sit squarely in that category: intangible, recurring, and easy for a client to forget authorizing once a few billing cycles have passed.
Structuring the account around remote, recurring labor
A virtual assistant and BPO merchant account gets underwritten for recurring service billing rather than physical-goods retail, with reserves and limits sized to the plan tiers actually sold, from a handful of monthly hours up to larger managed-operations contracts. Firms with offshore delivery teams or an international client base should also look at international merchant account support for multi-currency settlement, since a single domestic account can be a poor fit once client billing spans multiple countries. That gap matters more in this category than most: Project Untethered's survey put average hourly rates for Philippines-based VAs at $11.33 against $35.61 for US-based VAs, a spread wide enough that a firm blending offshore and domestic staff on one price sheet needs settlement support that can actually handle mixed-currency, mixed-rate billing cleanly.
Recurring billing with proper dunning and retry logic on failed cards reduces involuntary churn before it becomes a dispute at all, and a recurring billing setup built for that from the start is a bigger lever in this category than it looks. A card that fails silently and gets treated as a cancellation, rather than retried, generates a rebill dispute the next time the client is billed unexpectedly.
Defending a services-not-rendered dispute
Because the deliverable is time and task completion, disputes are won on documented activity. Time logs, task-completion records, and deliverable summaries tied to each billing cycle are the core evidence under card network dispute rules when a client claims work was not performed. This documentation does double duty. It also resolves the honest version of the same disagreement, where a client genuinely lost track of what was delivered that month.
That documentation matters more than ever given where dispute volume is trending. Chargebacks911's 2026 Chargeback Field Report found that more than 83% of enterprise merchants have seen friendly fraud, cardholders disputing a legitimate charge instead of contacting the merchant, rise over the past three years. A clean chargeback defense process built around timestamped activity logs is what actually moves a dispute from an unwinnable he-said-she-said into a representment case with real evidence behind it.
For larger managed-operations or staffing contracts settled by bank transfer, ACH processing is worth pairing with card acceptance. It carries a flat fee instead of a percentage, which matters more as contract size grows.
Frequently asked questions
Why does a VA or BPO firm need a specialized merchant account?
Recurring billing for intangible remote labor, plus offshore delivery and no storefront, push VA and BPO firms into high-risk underwriting. A dedicated account is built for retainer billing and the services-not-rendered disputes that come with intangible work.
How do we defend a dispute when a client says work was not done?
With activity records: time logs, task-completion records, and deliverable summaries tied to each charge. That documentation shows the work performed, which is the strongest evidence against an intangible-services dispute.
Can we bill monthly plans and larger managed-services contracts on the same account?
Yes. Blended recurring-plus-high-ticket billing is normal for this category, with limits and reserves sized for both the subscription base and larger staffing or managed-operations contracts.
Does an offshore delivery team change what account we need?
Often, yes. A firm billing across multiple countries or running delivery teams abroad should look at multi-currency settlement support rather than forcing everything through a single domestic account built for one currency and one country's card mix.
Why do VA and BPO firms see more disputes than the billing amount alone would suggest?
Because the category sits inside a broader trend: services and subscription billing chargeback rates rose 83% year over year through 2025, driven mostly by recurring billing confusion and first-party disputes rather than stolen-card fraud. A VA retainer that renews quietly every month is exactly the kind of charge a client can forget authorizing, which is why proactive billing reminders and activity documentation matter as much as fraud screening.
Does mixing hourly, retainer, and per-task billing on one account increase risk?
It can. Roughly seven in ten virtual assistants bill hourly while the rest work on retainer or per-task packages, and blending those models on a single account produces the ticket-size and billing-frequency swings that automated fraud models are built to flag. Structuring the account for that variability up front, rather than after a hold, keeps the mix from looking anomalous.
Ready to structure an account around your actual retainer and managed-services mix? Apply free for a same-week underwriting decision.
Gray Merchants Team
Gray Merchants is a payment ISO that places merchant accounts across every risk level — from low-risk retail and e-commerce to 67+ high-risk verticals. The editorial team writes on high-risk merchant accounts, chargeback defense, MATCH/TMF remediation, and ACH processing — whether you are new, scaling, switching processors, or rebuilding after a decline.