Accept crypto payments at your staffing agency: the business that pays its workforce weeks before its client pays it

Why a staffing agency's money always goes out before it comes in

Almost every other business collects and then spends. A shop buys stock, sells it, banks the money. A software company charges a card and delivers bits. A restaurant is paid at the table before the supplier invoice falls due.

A staffing agency runs the cycle backwards, and it is not an accident of bad terms — it is the structure of the product. What you sell is hours of a human being's work. Those hours are consumed in real time by the client, and the person who supplied them expects to be paid on the ordinary human calendar: weekly for light industrial and hospitality, biweekly for most contract work, monthly at the latest for a professional bench. Your client, meanwhile, is a company with an accounts payable department, a purchase order, a timesheet approval workflow and standard terms of net-30, net-45, sometimes net-60.

So the agency stands in the middle and funds the difference. Not once, not seasonally — continuously, for as long as the contract runs. Sixty contractors at an average of USD 3,500 a month is USD 210,000 leaving the company every month against invoices that will be paid a month and a half later. The steady-state exposure is one and a half to two full payroll runs, permanently, and it grows the moment you win a bigger client. Growth in staffing consumes cash. Every agency owner learns that in the first year, usually the hard way.

Now add the second structural fact, the one that changed the industry in the last decade: both ends of that sandwich went international at the same time. Nearshore and offshore staffing is no longer a niche. An agency headquartered in Bogotá, Buenos Aires, Medellín, Mexico City, Warsaw or Manila places engineers, designers, accountants, customer-support teams and clinical coders with clients in Austin, London, Toronto and Amsterdam. It invoices in dollars or euros to a company on another continent, and it pays its bench across eight or ten countries — some of which have capital controls, thin correspondent coverage, or an official exchange rate nobody actually uses.

That means the agency now has two payment problems that pull in opposite directions:

• Inbound: a small number of large, dated, cross-border B2B settlements from clients whose finance departments run on their own calendar and whose banks deduct fees nobody quoted.
• Outbound: a large number of small, urgent, multi-country payments to people who will leave for a competitor if the money is late, and who absorb a transfer fee and an FX spread on every single one.

And in between sits the margin. This is the detail that makes staffing different from a digital agency, a construction firm or a production company, all of which also live with slow clients. A staffing agency's gross margin is a spread on the bill rate. On volume contract and light-industrial work it is thin by design; on specialist and executive placement it is fatter but far more episodic. Whatever the number, it is a percentage of a pass-through, which means that any friction inside the payment rail is not measured against revenue — it is measured against the spread. A few hundred dollars lost on a wire is not a rounding error on a USD 60,000 invoice; it is a slice of the actual profit on that invoice.

That is the whole vertical in one sentence: you pay first, you get paid last, and everything the rail takes on either journey comes out of a margin that was already thin.

What the wrong rail costs an agency, run by run

The float you are financing at somebody else's interest rate. The gap between paying the bench and collecting from clients has to be funded from somewhere: retained earnings, a bank line, or invoice factoring. Factoring is the industry's standard answer and it is not cheap — a discount fee charged monthly against the face of the invoice, plus service charges, plus recourse if the client never pays. On a thin-spread contract book, financing costs frequently consume a meaningful share of the gross margin. Anything that shortens the collection cycle by even a week is not a convenience feature; it is a direct margin recovery.

The client invoice that arrives short. An international wire for a monthly invoice passes through correspondent banks that deduct fees the sender never quoted and the receiver cannot predict. The client's ledger says the invoice was paid in full; yours says there is a gap. Someone in your finance team now has to open a polite argument with the account you most want to renew, over a number neither of you controls. Do that twelve times a year, across four clients, and the aggregate is real money — money that came directly off the spread.

The ninety small deductions on the way out. The same tax applies again, in reverse, on a much larger number of transactions. A contractor in Buenos Aires, Caracas, Lagos or Manila receiving an international payment absorbs a transfer fee, an intermediary deduction and an FX spread. The World Bank's own tracking of the average cost of sending money across borders has sat stubbornly high for years, and the smaller the payment the worse the percentage. The agency's position is deceptively comfortable — you paid the agreed amount, the deduction landed on them — but the market corrects that: contractors quietly price the leakage back into their rates, and the ones who get a better net elsewhere leave. The cost comes home either way.

The pay run that slips, and the bench that notices. In staffing, payment reliability is a supply-side feature. Contract talent is not loyal to a logo; it is loyal to whoever pays on time, in full, without a monthly argument. A pay run that lands two days late because a client wire had not cleared is not an accounting incident — it is a churn event, and replacing a placed contractor costs you the recruiting, the client's patience, and often the margin on the rest of the contract.

The card ceiling on a real invoice. Nobody puts a USD 60,000 monthly staffing invoice on a corporate card, and the arithmetic explains why: interchange plus a cross-border assessment plus FX on that size of charge is a contractor's month. So the large money goes back to wires, and wires go back to banking hours, cut-off times and a three-to-five day clearing window that has no relationship whatsoever to your payroll date.

The dispute on a service already delivered. Where cards are used — the smaller client, the first month, the placement fee, the self-serve package — the money stays reversible for months. Card scheme dispute windows, set out in network documentation such as the Visa Core Rules, give a cardholder a long runway to raise a claim. By then the contractor has been paid, the placement has started, and there is nothing to reclaim. It is the same structural asymmetry any merchant defending disputes faces, applied to hours that were genuinely worked and cannot be returned.

The acquirer's read on staffing. B2B services, large tickets, advance and placement fees, delayed delivery of a service, a documented dispute profile, and no consumer-style recurring baseline. Underwriting reads that as risk and answers with lower ceilings, delayed settlement, and sometimes a rolling reserve. A reserve on a staffing agency is uniquely destructive: the month your receipts peak is the month your payroll peaks, so the funds are held back at precisely the moment the bench has to be paid.

Payment-instruction fraud on the onboarding form. Every new contractor sends bank details by email, and every existing one occasionally emails to say they have changed banks. The FBI's Internet Crime Complaint Center has documented for years that business email compromise — impersonating a supplier or employee to redirect a legitimate payment — is among the costliest categories of cyber-enabled crime. A staffing agency processes dozens of payee-detail changes a year and pays hundreds of people it has never met in person. That is exactly the surface this attack is built for, and it is the control that matters most in this vertical regardless of which rail you use.

The corridor where the placement is easy and the payment is impossible. The talent is in a market with FX rationing, a parallel exchange rate, restrictions on receiving foreign currency, or simply no correspondent bank willing to handle small inbound payments. The candidate is excellent, the client is happy, and the constraint is not recruiting — it is that you cannot reliably get money to the person you hired.

The placement fee that has to travel backwards. Permanent placement is invoiced on start date, usually as a percentage of first-year salary, and almost every contract carries a guarantee period: if the hire leaves within thirty, sixty or ninety days, the fee is refunded or credited on a sliding scale. So the money has to move out to you, and sometimes a fraction of it has to move back, quickly, without a dispute process and without souring the relationship. Any rail that takes a week in each direction turns a routine contractual term into a month of friction.

Why wires, cards and payroll files all fail somewhere in staffing

• International wires assume you can wait and can predict the amount. A staffing agency can do neither: the pay date is fixed by the contractor's rent, and the figure that lands is not the figure on the invoice.
• Cards settle in one to three days and stay reversible for months. On a service consumed in real time by a client's own managers, a reversal months later has nothing left to reverse.
• Bank payroll files are built for employees, in one country, on one calendar, at one bank. A modern contract bench is dozens of independent professionals invoicing from eight or ten countries, each with a different currency, a different account structure and a different set of local fees.
• Local instant-payment schemes — Pix, SPEI, Bizum, domestic account-to-account transfers — are resident-only by design. They are excellent for the contractor who lives where your office is, and completely useless for the client in Austin and the developer in Belgrade, who are the two ends of the business.
• Invoice factoring solves the symptom by selling the receivable at a discount. It is a financing product, not a payment rail: it buys you time and charges you for it. If the collection itself were faster, you would need less of it.

The structural fact: an agency has to receive a small number of large, dated, cross-border payments and disburse a very large number of small, urgent, multi-country payments, on a fortnightly clock, permanently, with a thin spread absorbing every fee on both journeys. Traditional rails are decent at one side of that. None is good at both.

How Payzum lets a staffing agency accept crypto payments and pay the bench

Payzum is a non-custodial crypto payment processor. There is no Payzum balance, no settlement batch and no rolling reserve priced against a services risk score. When a client pays, funds move on-chain from their wallet directly into a wallet your agency controls, and settlement is the payment. For a business whose entire problem is a gap between money going out and money coming in, removing three to five days of clearing from every single collection is not a cosmetic improvement — it is the gap getting smaller, every month, without borrowing anything.

On-chain payments are also final. Once confirmed, no issuer reverses them ninety days later because a hiring manager reorganised a team. What happens next is governed by your service agreement and your guarantee terms — a conversation with a client, not an adjudication you find out about in a chargeback notification.

And a stablecoin is the same asset in the client's country and in the contractor's. A payment from Austin, one from Amsterdam and one from Singapore are all the same dollar-denominated instrument, confirming in seconds, at any hour, for cents in network fees — the general mechanics of cross-border collections applied to a business whose deadline is somebody's rent.

The instruments, mapped to how an agency actually moves money

• Invoices with an expiry and overpayment detection for the monthly or fortnightly client bill. Put the purchase order, the cost centre and the week ending in the reference, and set the expiry to the date the money is genuinely needed — your pay date — rather than to a net-45 fiction that nobody in your finance team believes. If it is going to be late, it flags itself while there is still a decision to make. Overpayment detection matters because clients routinely round up for approved overtime, an extra week, or a rate change that was agreed on a call.
• Recurring subscriptions for the part of the book that is genuinely recurring, which in modern staffing is most of it. Staff augmentation is sold as n seats at a monthly rate: five engineers, one designer, a support pod. Managed-service and RPO arrangements are sold as a monthly retainer. Those are subscriptions, and they behave far better as subscriptions than as a card-on-file that dies silently when a client's finance director is issued a new card — the mechanics of subscriptions without chargebacks applied to a monthly seat.
• Payment links — no code, sent by email, WhatsApp or straight from your ATS — for the permanent placement fee on start date, the retained-search engagement fee, the overtime rebill approved on Thursday afternoon, the background-check or assessment pass-through, and the client in a corridor where a wire is genuinely difficult. They pay from any wallet, at face value, without needing a bank account in your country.
• Mass payouts — the instrument that changes the most here. CSV batch payouts plus EVM stablecoin payouts on Polygon, Arbitrum, Optimism, Base, BNB Chain and Avalanche. One file settles the entire bench: contractors by client account, the specialists on a partial month, the recruiter on a commission split, the sourcer in another country, the referral bonus. Each recipient receives the exact agreed amount rather than a figure reduced by a chain of fees they absorb and then price back into next quarter's rate. The mechanics are the same as any recurring contractor payout run and the file format is the same CSV batch you would use anywhere else.
• Hosted checkout — redirect, modal or inline — plus drop-in compatibility with the plugin you already run, so the productised end of the business closes itself: a job-posting package, a single background check, a bundle of assessments, a small client's first month, an employer-branding add-on. A signed digital quote ends in a paid deposit instead of an invoice someone will action next week.
• POS with a fresh QR per sale at branch counters that actually take money over a desk: certification and safety-training courses, PPE and uniform kits, badge replacements, medical checks, and the recruitment stand at a hiring fair in a city where your agency has no local acquiring entity for a three-day event. Any phone is a terminal, and cashier accounts with PIN let branch staff collect without ever touching the company wallet, with per-cashier analytics for the daily count. It is the same in-person flow as any counter. (In many jurisdictions charging jobseekers for placement is restricted or prohibited outright — see the honest-scope section below. This is for goods and services you may lawfully sell, and for corporate clients paying at a desk.)
• REST API and signed webhooks so your ATS, VMS or timesheet platform marks an invoice funded the second it confirms — which is what should trigger the payout run, release the placement record, and stop your operations lead from refreshing a bank portal on a Thursday night.

The payout run: one file instead of ninety transfers

This is where the vertical separates from every other services business. A design studio has a payables problem measured in a handful of freelancers a month. A staffing agency has one measured in dozens or hundreds of people, on a fortnightly clock, forever, across borders, where lateness is a churn event rather than an inconvenience.

A batch payout collapses that into a single operation. The domestic half stops being a queue of individual transfers and becomes a line in a file with a name, an amount, a network and an address. The international half — the developer in Belgrade, the accountant in Manila, the support pod in Bogotá, the recruiter on commission in Madrid — stops being thirty separate international transfers with thirty cut-off times, thirty fee schedules and thirty different arrival dates, and becomes part of the same run as everyone else. Everybody receives the exact number they agreed to, and the record of it exists before anyone asks for it.

The operational saving is real and it is usually underestimated. Agencies that run a distributed bench routinely spend half a day to two days a month on the run itself — assembling files, chasing failed transfers, reconciling short arrivals, answering "did you send mine?" messages. That time is your operations manager's time, and it is spent on plumbing.

The spread is where every fee lands

Worth stating on its own, because it is the argument that actually lands with an agency owner. In a retail business a payment fee is a percentage of a sale with a real markup behind it. In staffing, the fee is a percentage of a pass-through: the bill rate contains the pay rate, and the pay rate is not yours. A three-percent card fee on a bill rate does not take three percent of your income — it takes three percentage points off the difference between the bill rate and the pay rate, which is a far larger share of your actual margin.

Network fees on stablecoin payments are cents, not points, and they do not scale with the size of the invoice. A USD 60,000 client invoice and a USD 600 rebill cost effectively the same to settle. Confirmation is measured in seconds — roughly 0.4 seconds on Solana, around two seconds on Base and Polygon — so a payment approved at four in the afternoon is money in your wallet at four in the afternoon, and can be in a contractor's wallet at five.

Honest scope: what this rail does not do

This is the section most worth reading carefully, because staffing is one of the most heavily regulated activities a small business can operate, and a payment rail touches exactly one layer of it.

Payzum is not an employer of record and not a payroll bureau. This is the single most important sentence in the article. Whether a worker is an employee or an independent contractor is a legal test in every territory — the US position is set out in the IRS guidance on the independent contractor versus employee distinction, and every other country has its own — and it does not change because of how the money moves. Minimum wage and overtime, working-time rules, holiday accrual, equal-treatment rights for agency workers, social security contributions, income tax withholding, workers' compensation cover, statutory sick pay, co-employment exposure and end-of-contract entitlements all remain the agency's responsibility.

And the practical corollary: if someone is your employee, in most territories they must be paid through the statutory payroll mechanism, in local currency, with the legally required deductions. This rail does not satisfy that and does not pretend to. Where it fits cleanly is the independent professional who invoices you — which, for the nearshore and offshore contract bench that most modern agencies run, is the majority of the payout file. Where it does not fit, nothing changes. Be honest with yourself about which of your people are which, and get that answer from an employment lawyer in each country, not from a payments article.

Agency licensing and permitted fees are unchanged. Private employment agencies and temporary work businesses are licensed, registered or otherwise supervised in a great many countries, with conditions attached: financial guarantees, reporting, restrictions on which sectors you may supply, and — very commonly — a prohibition on charging fees to jobseekers. Never use a payment link or a branch QR to collect money from candidates for placement unless you have confirmed it is lawful where you operate. The rail is neutral; the rule is not.

This is not factoring, a credit line or an advance. Payzum does not lend you money and does not buy your receivable. Your float shrinks because the collection settles in seconds instead of days, and because a client in a difficult corridor can actually pay you — not because anyone is financing you. If your gap is structural at net-60, faster settlement narrows it; it does not close it.

It is not escrow. A client's prepayment for a month of seats is an obligation to supply, not funds held by a third party. Finality cuts both ways: a guarantee-period refund on a placement fee is instant because you already hold the money, but there is no scheme to arbitrate it, so your terms of business — guarantee period, sliding scale, replacement versus refund, notice — have to be written down and honoured.

Export-of-services proceeds and FX rules are unchanged. An agency invoicing a foreign client is exporting a service. In countries that require export proceeds to be repatriated and settled through the local foreign-exchange market, that obligation is yours, it is unchanged, and a rail that settles into a wallet you self-custody does not satisfy it by itself. Confirm the position with your own advisers before using this for client collections in such a market. Domestic clients, the payables side and productised services are frequently a separate question.

Everything else stays where it is. Data protection on candidate records, right-to-work and background-check obligations, anti-discrimination rules in selection, contractual non-solicit and temp-to-perm conversion fees, professional indemnity and employer's liability insurance, VAT or sales tax on your fee, and corporate tax. None of it changes because a client paid in USDC.

Volatility is a setting, not a risk

You owe a bench of real people a real number next Friday, so "we cannot hold an asset that moves" is the correct first objection. You do not have to. Payzum accepts crypto and settles in crypto, with optional auto-conversion to a stablecoin such as USDC or USDT. A client invoice received on the 3rd is the same number of dollars when the payout run goes out on the 15th. For a business whose margin is a few points, that is not a preference — it is a requirement, and it should be switched on from day one.

What doesn't change

Payzum is crypto-only and does not settle to a bank account. Converting stablecoins into local currency — to run the statutory payroll for your internal staff, to pay the office lease, to settle a tax liability — remains a separate step you take with your own exchange or off-ramp, on your own schedule and under your own regulatory obligations. What changes is how fast confirmed money arrives, who holds it in the meantime (nobody but you), and whether a contractor in a hard corridor can be paid at all.

How it works, step by step

1. Open the account and connect a wallet you control. Create a Payzum account, complete KYC, and point settlement at the agency's own wallet. There is never a Payzum-held balance — nothing to reserve against a services risk score, nothing released three weeks after the bench needed it.
2. Turn the client book into instruments. Monthly seats and RPO retainers become recurring subscriptions. The variable timesheet bill becomes an invoice with the PO and week-ending in the reference, an expiry set to your pay date, and overpayment detection on. Placement fees, engagement fees and overtime rebills become payment links you can send from a phone.
3. Build the payout file from approved timesheets. One CSV per run: name, amount, network, address. The whole bench, the partial months, the recruiter commissions and the referral bonuses move in a single operation across whichever of the supported networks suits each recipient. Verify every new or changed payout address out of band — a phone call to a known number, not a reply to the email that requested the change. Address-change fraud is the top control in this vertical on any rail.
4. Give branch staff a PIN, not the wallet. Where a branch or a hiring-fair stand collects over a desk, cashier accounts with PIN let staff take payment on a fresh QR per sale with per-cashier reporting, without anyone touching the company wallet. Any phone is the terminal, so a pop-up stand in another city needs no hardware and no local acquiring entity.
5. Wire it into your ATS or VMS. A signed webhook tells your system that a client invoice has confirmed, which is the event that should release the payout run and update the placement record — without anyone refreshing a bank portal at eleven at night.

Use cases at a staffing agency

Six situations where the difference shows up inside the same fortnight, not in a year-end review.

• The nearshore staff-augmentation contract. A client in Austin books six engineers at a monthly seat rate from an agency in Bogotá. The seats are billed as a recurring subscription that confirms on the 1st instead of a card that fails silently on renewal, and the six engineers — two of whom live in different countries — are paid from the same account on the 5th, in the same stablecoin, at the exact agreed amount.
• The fortnightly bench run. Ninety lines: contractors by client account, three specialists on a partial month, two recruiters on commission split, a sourcer in another country and a referral bonus. One CSV batch of stablecoin payouts, exact amounts, with a record that exists before the bookkeeper asks for it — and no afternoon spent chasing failed transfers.
• The placement fee on start date. A candidate starts on Monday. The fee invoice usually sits in a client's AP queue for six weeks; instead a payment link goes out on Monday morning with the candidate reference and the start date, and confirms the same day at face value. If the guarantee clause is triggered in week five, the pro-rata refund is a payment you initiate immediately — not a credit note that hangs over the relationship for a month.
• The contractor in a corridor nobody will bank. An excellent developer lives in a market with FX rationing and a parallel exchange rate, and every attempt to pay them internationally has arrived late, short, or not at all. A stablecoin payout on a low-fee network reaches their wallet in seconds at face value — the same problem getting paid from abroad without a local bank account solves at the other end of the transaction.
• The overtime rebill approved on Thursday. A client authorises a weekend shift for four warehouse workers. Rather than adding it to next month's invoice and paying the workers out of your own account for five weeks, a payment link goes out Thursday evening, confirms Friday morning, and the shift is funded before it is worked.
• The branch counter and the hiring fair. Your branch sells safety certification, PPE kits and medical checks to corporate clients over a desk, and your team runs a three-day stand at a hiring fair in a city where you have no local entity. A fresh QR per sale with PIN cashiers and per-cashier reporting handles both — no terminal, no acquirer, no local bank account for a three-day event.

Payzum vs wires, cards and payroll files for a staffing agency

Common objections, answered

"Our clients are enterprise procurement departments. They will never pay in stablecoins."

Some will not, and you should not design around convincing them. The realistic pattern is a split book. Your enterprise accounts keep paying exactly as they do now. Where this rail earns its place first is the segment that is already painful: the smaller international client whose wire arrives short, the startup that would rather pay from a treasury it already holds in USDC, the client in a corridor where a wire genuinely takes a week, the placement fee you would like paid on start date rather than in six weeks, and the self-serve productised end of the business. Add the payables side, which is entirely within your control, and the rail is already carrying real volume before a single enterprise client is asked to change anything.

"Our contractors want their own currency. They are not going to take USDC."

Some of them already do, and that number is not evenly distributed. Ask your bench where they are and how they are paid today. Contractors in markets with high inflation, currency controls or expensive inbound transfers are frequently the ones who ask for stablecoins first, because the alternative loses them a visible percentage every month. Contractors in stable markets with cheap domestic banking will mostly want what they have. The honest answer is a split run: the people who prefer it move to the batch, everyone else stays exactly where they are, and you stop paying international transfer fees on the half of the bench that was quietly absorbing them.

"If the payment is final, what protects us when a client disputes the work?"

The same thing that protects you today: the contract, the approved timesheets and the delivery record. What changes is that the decision is not made unilaterally by a card issuer months after the fact, when the contractor has long since been paid. Finality is symmetrical — it also means that when you owe a guarantee-period refund on a placement, you can send it the same day from money you already hold, which is a better client experience than a credit note applied to a future invoice.

"We are an eight-person agency. This sounds like an IT project."

It is not. Payment links and hosted checkout are no-code; invoices and subscriptions are configured in a dashboard; the payout run is a CSV with a name, an amount, a network and an address. If you already have a spreadsheet that drives your fortnightly pay run — and every agency does — you already have the input file. The API and signed webhooks are there for when you want your ATS or VMS to react automatically, not as a prerequisite for getting started.