Crypto Payroll After the Stripe Bitcoin Fraud Case

On October 23, 2026, the Department of Justice sentenced a man to 51 months in federal prison for a scheme that moved unauthorized card payments through Stripe, into bank accounts, and out via Coinbase as bitcoin sent to co-conspirators. For finance leads who run crypto payroll, the case is a stark operational warning: the same fiat-to-crypto rails that make cross-border wage payments fast and cheap are also the rails prosecutors traced to build a money-laundering conviction. Knowing which controls separate an authorized payroll batch from a criminal wire is now a compliance necessity, not a theoretical checkbox. The incident also sharpens the focus on crypto payroll compliance and the crypto payroll controls that employers must now build.

Table of Contents

• What just happened: a 51-month sentence for card-to-Bitcoin laundering
• Why this changes the crypto payroll conversation
• The background a finance lead needs
• The gaps most crypto payroll guides leave open
• What to do next: controls that reduce the risk
• What to watch next and open questions
• Key Takeaways

What just happened: a 51-month sentence for card-to-Bitcoin laundering

The Department of Justice announced on October 23, 2026, that Timothy Wadsworth, 35, of Rochester, New York, had been sentenced to 51 months in prison and ordered to pay restitution after pleading guilty to conspiracy to commit wire fraud and money laundering. According to court documents, Wadsworth used account numbers supplied by co-conspirators to initiate 310 unauthorized Stripe card payments totaling $1,673,578 between March 10 and May 15, 2020. Of those, 116 payments succeeded, netting $730,728.22 that belonged to victims who never approved the charges (Cryptonews.net, October 26, 2026).

The scheme didn’t rely on sophisticated blockchain obfuscation. Instead, it exploited the very payment infrastructure many companies now use for legitimate fiat-to-crypto payroll: a payment processor, a business bank account, a crypto exchange, and external bitcoin addresses. The DOJ’s press release made clear that “the account holders did not authorize the transactions” — a phrase that should echo through every controller’s reconciliation checklist.

The money trail: Stripe to HSBC and Evolve to Coinbase to bitcoin addresses

Prosecutors reconstructed a clean chain. Unauthorized Stripe charges landed in accounts Wadsworth controlled at HSBC and Evolve Federal Credit Union. From there, he moved money to Coinbase, bought bitcoin, and sent it to external wallet addresses controlled by co-conspirators. No attempt was made to hide the flow; the fraud succeeded because the initial source of funds — those Stripe card payments — lacked any authorization from the true account holders.

The trail is instructive beyond the criminal context. In a legitimate payroll run, an employer authorizes a debit from its own verified business account, converts fiat to crypto through a licensed exchange or processor, and delivers it to an employee’s known, screened wallet. Wadsworth’s path used the same components but with one fatal difference: the source of funds was stolen. That single gap turned an ordinary transaction sequence into a federal case. Put simply, this is a crypto payroll fraud case that every finance lead should study.

Why this changes the crypto payroll conversation

Payroll and money laundering share the same fiat-to-crypto rails

The infrastructure Wadsworth exploited — Stripe, HSBC, Evolve, Coinbase — is the same or analogous to the stack a Web3 startup might use to pay global contributors in USDC or bitcoin. Payment processors, business bank accounts, and exchanges are not themselves the problem. The problem is that too few employers treat source-of-funds verification as a distinct step before every payroll batch. The conviction shows that regulators and investigators now have the forensics to prove exactly whose money moved through which institutions and when. For a CFO, that means the question “Was this batch funded from our own verified account?” has moved from best practice to a documentary burden you could be asked to meet in court.

Authorization and source-of-funds records are the deciding line

The Wadsworth case did not hinge on whether bitcoin is money or whether Coinbase is a money transmitter. It hinged on the absence of authorization. In a corporate payroll context, that translates to: Do you have a dated, signed approval from a person with proper authority for the specific payment amount and recipient list? Can you prove that the fiat funds came from a business account you control, not from a commingled pool or an unknown source? The DOJ’s successful prosecution relied on the victims’ denial of the debit; in a business, the equivalent is an auditable workflow showing that each batch was ordered by an authorized officer and funded from a known, segregated business account.

The background a finance lead needs

How fiat-to-crypto payroll actually works

Fiat-to-crypto payroll typically follows a simple sequence: an employer funds a designated account with fiat currency; a payroll platform or internal process calculates the crypto equivalent at an agreed timestamp; the conversion occurs through an exchange or broker; and the resulting tokens are transferred to recipients’ wallet addresses. When a stablecoin like USDC is used, the employer may hold a balance directly in that token, removing the conversion step at pay time. Either way, the process involves a payment processor, one or more bank accounts, and a destination address on a blockchain. These are the same building blocks that appeared in the Wadsworth indictment.

The legal, tax, and accounting questions readers keep asking

Crypto payroll sits at the intersection of wage-and-hour law, tax reporting, and anti-money-laundering rules. Below are the most persistent questions finance leads face, answered in light of the security and compliance lessons from the Wadsworth case. As Ogletree Deakins notes in their analysis of global employer considerations, the opportunities are real but demand rigorous compliance.

Is it legal to pay wages in crypto?

Yes, in many jurisdictions, provided the employer complies with minimum wage, overtime, and pay-frequency laws. The United States Fair Labor Standards Act (FLSA) requires wages to be paid in cash or negotiable instruments — a standard that does not bar crypto outright, but the U.S. Department of Labor has expressed concern about volatility and delayed settlement. Paying employees in bitcoin or other tokens is permissible under federal law if structured correctly, though several states impose their own rules. Outside the U.S., the landscape is fragmented. The October 2026 conviction doesn’t change the legality of paying in crypto; it changes the evidentiary standard. You need to be able to prove that the payroll funds were legally sourced and that the distribution wasn’t a laundering channel. For a deeper dive into how the process is defined globally, Globalli’s resource glossary provides a clear breakdown of crypto payroll mechanics.

Can US employees receive payroll in crypto?

This is where ranking pages conflict. Some argue it’s a compliant W-2 option; others treat direct crypto wages as legally risky in multiple states. The practical answer is that U.S. employers can pay employees in crypto, but they must handle tax withholding and fair-market-value (FMV) reporting in U.S. dollars, usually by converting a portion of the wage into dollars to remit payroll taxes. Employee consent, clear FMV calculations, and proper classification are essential. The Wadsworth prosecution underscores that the legal exposure isn’t just employment law — it’s the risk that an unauthorized funding source turns a payroll run into a possible financial crime. The distinguishing line is whether the employer can demonstrate that the payroll funds came from a legitimate business account under its control.

How is crypto taxed when used for payroll?

For U.S. employees, the fair market value of the crypto at the time of receipt is taxable as ordinary income and subject to payroll taxes. Employers must withhold income tax and the employee’s portion of FICA, and pay the employer’s portion. If the employee later sells or exchanges the crypto, a capital gain or loss arises. The Internal Revenue Service (IRS) has not issued a standalone payroll-specific crypto ruling, but existing guidance treats crypto as property for tax purposes. Thomson Reuters highlights that the lack of specific IRS rules on stablecoin wages creates compliance challenges around FMV determination, especially for tokens pegged to fiat. Employers should document the exchange rate source and timestamp for every payment.

What happens if the crypto price changes after payroll is processed?

Price fluctuation after the payroll run is borne entirely by the recipient, unless the employer has contractually locked in a rate or offers a stablecoin wage. For volatile assets like bitcoin, a delayed conversion or payment processing time can shift the value significantly. This volatility risk is a major reason many employers use stablecoins for payroll, as discussed below.

Do crypto payroll platforms require KYC and AML checks?

Reputable platforms do, yes. KYC and AML for crypto payroll — Know Your Customer and anti-money laundering checks — are standard for any service that onboards businesses and processes fiat-to-crypto conversions. These checks typically verify the business entity and its beneficial owners. However, the mere presence of KYC on a platform does not guarantee that every payroll batch is sourced from an authorized business account. The Wadsworth case exploited Stripe, a processor with its own KYC requirements, because the criminal opened legitimate merchant accounts under his control and then fed them unauthorized card numbers. For employers, the critical question is not just “does the platform do KYC?” but “can I prove the source of funds for each batch?”

How do companies account for crypto payroll in their books?

Crypto wages are recorded as a compensation expense at the fair value of the cryptocurrency on the payment date, with the corresponding credit to a liability or directly to cash/crypto held, depending on how the transaction is settled. If the company holds crypto and transfers it, the difference between the carrying value and the fair value at payment may create a gain or loss. A detailed guide on the operational side, including tax reporting, is available from Toku’s payroll guide for stablecoin teams. Standard double-entry accounting applies, but the need for a clear audit trail — showing the date, FMV source, wallet addresses, and authorization — is far more pressing after a case like Wadsworth’s.

How do stablecoins reduce risk in crypto payroll?

Stablecoins like USDC or USDT peg to a fiat currency, so their value doesn’t swing between the moment an employer authorizes a payment and the moment the recipient receives it. This removes the volatility headache and simplifies FMV calculations: $1 in USDC equals $1 for payroll purposes, though tax authorities may still want a documented reference rate. Stablecoins don’t eliminate the compliance risk addressed by the Wadsworth case, however. A fraudster could still use a stolen funding source to buy stablecoins and send them to a co-conspirator. The core control — source-of-funds verification — applies regardless of the asset used.

The gaps most crypto payroll guides leave open

Most ranking pages explain how crypto payroll works, list providers, and mention KYC. They don’t operationalize the lesson from a federal money-laundering sentencing. The October 2026 case exposes three concrete gaps that every employer running fiat-to-crypto payroll must close.

Source-of-funds verification before each batch

In the Wadsworth scheme, the payments that hit HSBC and Evolve came from victim card numbers, not from the defendant’s own lawfully held funds. In payroll, the equivalent is running a batch from a commingled operating account without confirming that the specific transfer was authorized by the account signatory and drawn on legitimately earned, business-owned funds. The practical control: before any payout, confirm that the fiat funding originates from a segregated, verified business account you control, and that the debit amount and timing matches a recorded approval.

Destination-address screening and custody separation

Wadsworth sent bitcoin to external addresses controlled by co-conspirators. Employers don’t have co-conspirators, but they may have employees, contractors, or DAO contributors whose wallet addresses haven’t been screened against sanctions lists or known fraud addresses. The Office of Foreign Assets Control (OFAC) requires screening of digital asset addresses, and failure to do so can result in severe penalties. A payroll process must verify each destination address against a current sanctions database and, for high-risk jurisdictions, maintain records of who owns the address and how it was validated.

The evidence trail you must keep

The DOJ’s case file mapped Stripe logs, HSBC and Evolve transaction records, Coinbase purchase history, and blockchain transfers to external addresses. An employer facing an audit or investigation would need to produce a comparable trail: the authorization (who approved the batch, when), the source of funds (what account, what original transaction), the conversion (timestamp, rate, exchange used), and the destination (screened address, employee identity). Without these records, a perfectly legal payroll run can become impossible to distinguish from the laundering pattern in United States v. Wadsworth.

What to do next: controls that reduce the risk

Confirm authorization and the funding source before any payout

The single most important operational change from the Wadsworth case is this: never initiate a crypto payroll batch without documented, dual-layer confirmation of both the funding source and the authorization. This means requiring at least two officers to approve the batch, verifying that the fiat account from which funds are drawn is the company’s own segregated payroll account, and logging the timestamp and identity of each approver. If the funding comes from an exchange or wallet where crypto is held, prove that the crypto was acquired with clean, traceable fiat.

How OneSafe’s KYB, Fireblocks custody, MFA, and automated workflows reduce this exact pattern

A platform that combines business identity verification, secure custody, and enforced multi-factor authentication can close several of the gaps exposed by the case. OneSafe, for example, requires businesses to complete a Know Your Business (KYB) process before they can transact, which verifies the entity and its owners. Digital assets held on the platform are safeguarded through Fireblocks’ institutional custody infrastructure, with segregated accounts that prevent commingling of payroll funds with other pools. Mandatory MFA on every login adds a layer of protection against unauthorized access to the payment initiation interface. Because the platform supports automated payroll and reimbursement workflows, companies can build approval chains that mirror the dual-authorization controls recommended above. While no technology can replace a sound internal compliance program, the combination of KYB, custodial segregation, MFA, and automated payment approvals makes it materially harder to replicate the Wadsworth money trail inside a legitimate business.

A pre-batch checklist for founders and finance leads

The following checklist distills the controls finance leads should run before every fiat-to-crypto payroll batch. It directly addresses the gaps the DOJ used to prove its case.

Running through these steps won’t eliminate every legal risk, but it will create the documentary record that distinguishes a payroll batch from a laundering transaction. As Innovative Human Capital suggests in their piece on the future of payroll, the shift to borderless pay is inevitable, making these controls foundational.

What to watch next and open questions

How processors and exchanges respond to the case

Stripe, HSBC, Evolve, and Coinbase all appeared in a money-laundering conviction not because they were complicit, but because their infrastructure was used. In the coming months, expect payment processors and exchanges to enhance transaction-monitoring rules around fiat-to-crypto flows that originate from business accounts and move quickly to personal wallets. Coinbase’s push into stablecoin payments means the exchange is likely to adopt stronger screening for high-frequency, high-value “payroll-like” disbursements. HSBC’s own foray into tokenized deposits may also lead the bank to impose tighter source-of-funds checks on its commercial accounts.

Whether payroll-specific compliance standards emerge

Currently, there is no single standard that tells a payroll manager, “If you do X, Y, and Z, your payroll batch is presumptively compliant.” The Wadsworth sentencing could become a catalyst for industry or regulatory guidance. Cross-border stablecoin regulation is already accelerating, and the OCC has signaled new expectations for crypto custody and payment services. The GENIUS Act update further refines the U.S. stablecoin framework. None of these directly address payroll, but they all push toward the kind of documented, segregated, and authorized-by-design infrastructure that makes a Wadsworth-style scheme harder to execute. Finance leads should monitor whether payroll-specific standards emerge from FinCEN or the IRS — and in the meantime, adopt the controls that already exist.

For teams keeping pace with these developments, resources that deliver daily briefings can make the difference between reacting late and staying ahead. Joyrise plans, writes and publishes illustrated SEO articles to your Webflow blog every day, offering a way to keep your own stakeholders informed without adding to your team’s workload.

Key Takeaways

• The October 23, 2026, sentencing of Timothy Wadsworth shows that unauthorized source-of-funds alone can turn a fiat-to-crypto transaction into a money-laundering felony, using the same rails as legitimate crypto payroll.
• Payroll compliance now requires documented proof of authorization and a clean funding source for every batch — not just platform-level KYC.
• A pre-batch verification of funding accounts, destination-address screening, dual sign-off, and the full evidence trail is the operational line between a compliant wage payment and the pattern prosecutors proved in the Wadsworth case.
• Platforms that combine KYB, segregated custody, MFA, and automated approval workflows reduce the risk of an employee or external actor replicating this fraud pattern inside a business.
• The industry should watch for new transaction-monitoring rules from processors and possible payroll-specific guidance as regulators absorb the lessons of this conviction.

For businesses running fiat-to-crypto payroll, now is the time to move your financial operations to a platform that builds these controls into its architecture.

Ready to put this into practice? Get started with onesafe.io.