Crypto Payments for Multi-Location Med Spa Chains and Aesthetic Groups in 2026

Five med spa locations, five Stripe accounts, five sets of books, and one chargeback at the Scottsdale clinic that just pushed your group’s blended dispute ratio over Visa’s monitoring threshold for the quarter. Multi-location aesthetic operators inherited a payment stack designed for single retail stores. In 2026 a number of chains are adding a second checkout rail that pools risk differently, settles identically at every location, and reconciles to one set of wallets instead of five merchant accounts.

This guide is for the chain operator, regional CFO, and multi-site ops director. It covers four problems crypto solves at the group level, two wallet architectures, the WordPress setup, reconciliation, refund SOPs, and the limits. None of this is a HIPAA story.

Why multi-location aesthetic groups are looking at crypto in 2026

The med spa industry is consolidating fast. LCG Aesthetics, SkinSpirit, Ideal Image, LaserAway, Ever/Body, and a wave of PE-backed rollups have moved the center of gravity from owner-operator clinics to multi-site groups with regional management layers. The top 20 chains alone operate well over a thousand U.S. locations.

That consolidation creates a payment ops headache that did not exist when each clinic was a single-owner shop. A group running 8 to 60 locations manages dozens of merchant accounts, a federated PCI posture, and location-level chargeback ratios that pool into one parent processor relationship. The executive team is one rough quarter at one location away from a higher reserve, a higher interchange tier, or a TMF placement affecting the entire group.

Crypto does not replace cards at the chain level any more than at the single-clinic level. What it does at scale is three things. It decouples the chain’s payment risk from any single location. It gives the group one consolidated revenue pipe to reconcile. And it adds a cash-pay rail international patients can use uniformly. If you have not read the predecessor, the single-clinic crypto payments guide covers chargeback economics and the four-currency menu; this article extends that up the org chart.

Four problems multi-location chains face that crypto solves

Cross-location chargeback risk pooling

Card networks measure chargebacks at the merchant ID level, but processor relationships are negotiated at the group level. When one location in a 12-clinic group runs a 2.4 percent dispute ratio for two months, the processor’s risk team flags the parent. Reserves rise, interchange tiers shift, and healthier locations subsidize the underperformer through worse blended economics across the network.

Crypto sidesteps this entirely. A confirmed on-chain transaction is final. No dispute to file, no chargeback ratio to track. For the share of group revenue flowing through crypto checkout, the blended risk profile is unaffected by any single location’s outcome. A clinic processing $40,000 a month in USDC has effectively removed that volume from the chargeback denominator.

Centralized vs distributed reconciliation

Most multi-location groups reconcile bottom-up today. Each location’s bookkeeper pulls the daily Stripe report, matches to bookings, posts to the local QuickBooks file, sends a monthly close to corporate. The handoffs introduce errors and timing differences the group CFO chases for the first ten days of every month.

A wallet-based rail flips this. Every crypto payment lands in a wallet the chain controls, tagged at the gateway with the originating location and order ID. The on-chain record is the source of truth, available in real time, exportable as a single CSV broken down by location. Reconciliation moves from bottom-up reconstruction to top-down verification. For the underlying fee math at chain volumes, see the actual fee math.

Cross-border high-net-worth clientele

Aesthetic medical tourism is a meaningful share of high-end group revenue. Patients fly into Miami, Beverly Hills, and Houston for combination procedures, facial work, body contouring. International card payment on a $35,000 procedure routinely runs 3.5 to 4 percent merchant cost once cross-border fees, currency conversion, and elevated chargeback exposure are loaded in. Some issuing banks decline outright because the amount and MCC trigger a fraud rule.

USDT on TRC-20 settles in seconds at near-zero network cost. USDC on Ethereum works for patients with custodial wallets at Coinbase, Kraken, or a regulated EU exchange. Aurpay’s flat 0.8 percent applies regardless of patient origin. For a chain with a 10 percent international pipeline, this changes the close rate.

Discreet billing across franchised locations

Discreet billing applies at the group level with a wrinkle: brand consistency. A patient who picks a chain expects the same experience at every location. A group-wide crypto option, available identically at every clinic, gives privacy-conscious patients the same off-statement path everywhere, instead of one-off cash handling that varies clinic by clinic.

Wallet architecture for chains: master wallet vs per-location wallets

The first real architecture decision is where the crypto actually lands. Two clean models, plus a hybrid. The wrong choice creates governance and tax pain that is hard to unwind once volumes grow.

Master wallet. Every location’s checkout settles into one corporate-controlled wallet per currency, typically a multisig (Gnosis Safe, multisig Bitcoin) with CFO, COO, and a board-designated signer. Each transaction carries a metadata tag for the originating location. This is the right model when locations are wholly-owned subsidiaries. Reconciliation is simplest; the tax position is one entity reporting FMV income on each receipt.

Per-location wallets. Each location has its own wallet, and revenue settles directly to the entity that legally earns it. Right model for franchise structures, JVs, and groups where each location is separately incorporated with its own bank account and profit-sharing. Each location’s signer controls its keys; corporate sees aggregated reporting via the gateway dashboard but does not custody location funds.

Hybrid. Wholly-owned locations settle to the master wallet; franchised or JV locations to their own. Most groups with mixed ownership end up here. Aurpay is non-custodial and never holds funds. Each location specifies its wallet address, and Aurpay routes there directly. The chain sets the policy; the gateway enforces it.

If your group is evaluating self-hosted infrastructure, the self-hosted vs gateway tradeoffs covered here are worth reading first. Running BTCPay Server across 12 locations is a different operational profile.

Setting up Aurpay across 5+ WordPress sites

Most aesthetic chains run separate WordPress sites per location for local SEO. Clinic-city URLs rank independently for “med spa Phoenix” or “laser hair removal Atlanta,” and consolidating to a multi-tenant site usually loses the local rank advantage. There are two viable patterns.

Pattern A: WP Multisite, single Aurpay configuration. Aurpay installs once at the network level and propagates to each subsite.

1. Network-activate WooCommerce and aurpay-for-woocommerce from the network admin.
2. Configure the corporate Aurpay account at the network level: API credentials, supported currencies, and either a master wallet or per-subsite override.
3. For per-location wallets, the regional manager enters addresses in the subsite’s WooCommerce settings.
4. Enable the same currency menu (USDC ERC-20, USDT TRC-20, BTC, Lightning) across all subsites.

Pattern B: Separate WordPress installations per location. Common when the group acquired clinics with existing sites. Install the Aurpay plugin on each site.

1. Install WooCommerce and the Aurpay plugin from the WordPress.org repository.
2. Connect to the corporate Aurpay account with credentials issued by the chain’s IT admin.
3. Enter the wallet address this location settles into: master, location-specific, or hybrid.
4. Mirror currency configuration across all sites so any patient sees identical options.

For locations without a full WooCommerce site (a brochure site with Calendly), Aurpay’s Crypto Invoice sends an emailed payment link with price locked at consultation, and Hosted Checkout creates a no-code page for one-off pre-procedure deposits. Either pattern lands at the same end state: one corporate Aurpay account, configured wallet routing per location, identical patient experience across the network. Our 2026 gateway comparison covers how this stacks against BitPay, Coinbase Commerce, and NOWPayments.

Reconciliation, accounting, and group reporting

Reconciling crypto across 5 to 60 locations is mechanically simpler than reconciling card processors across the same footprint, because the on-chain record is canonical and immediately available. The work shifts from “did the deposits arrive” to “did each transaction tag correctly to the originating location.”

Daily reconciliation. The corporate controller pulls the prior-day deposit list from each wallet via blockchain explorer or gateway export. Every transaction carries an order ID and location tag. Match against the booking system’s daily completed-transaction list. Mismatches are bookkeeping questions, not missing-deposit panics. The funds are already on-chain.

Monthly tagging. Crypto revenue posts as ordinary income at FMV at receipt, classified to the originating location’s revenue account. QuickBooks Online and Xero accept manual journal entries or CSV imports broken down by location and currency. For 20+ locations, middleware (Cryptio, Bitwave, SoftLedger) automates FMV pricing and per-location ledger posts; under 20, a CSV-driven monthly close works.

The CFO’s view. The consolidated P&L gains one or two new revenue lines per currency, reconcilable to per-location detail. The CFO sees crypto revenue as a share of total revenue per location and region, and can hold regional managers accountable to the same metric. Etherscan, Tronscan, and mempool.space provide a public audit trail.

Refunds across locations: a SOP for chains

Single-clinic refunds are simple. Patient raises a concern, owner-operator decides, refund sent. Multi-location chains need an actual SOP because authority is distributed and consistency matters.

Corporate policy. The board sets the refund posture: under what clinical circumstances a refund is authorized, the goodwill threshold, documentation required, and the maximum any single location can refund without escalation. Crypto does not change the policy. It changes the mechanics.

Location authority. Most chains delegate refunds up to $1,000–$5,000 to the location director, escalating above to regional or corporate. For crypto, the director needs the ability to send a refund from the location’s wallet, or request one from corporate in the master-wallet model. Multisig handles this cleanly: director initiates, regional manager or CFO co-signs above threshold.

Workflow. Patient raises concern, location evaluates against policy, decision documented in PMS, if approved the refund is sent from the appropriate wallet to the patient’s wallet, bookkeeping posts the return. Elapsed time is hours, not the 60-day Visa dispute window.

Communication. Train front-desk staff that refunds are a clinic decision, not an automatic chargeback right. Script: “we resolve internally, then send the refund to your wallet within X business days.”

What this does not solve for healthcare chains (be honest)

The biggest mistake a group can make is positioning crypto checkout as a healthcare technology upgrade. It is not. These boundaries apply with more force at the chain level, where compliance officers and PE-side risk teams watch every vendor decision.

• HIPAA compliance. Aurpay does not store, transmit, or process PHI. HIPAA posture flows through the EHR, PMS, intake forms, patient portal, and BAAs the group signs with vendors that do touch PHI. Adding crypto checkout neither strengthens nor weakens HIPAA posture, and Aurpay should never be marketed as a “HIPAA-compliant payment solution.” It operates outside the PHI perimeter.
• EHR and practice management. Crypto checkout settles the financial transaction. It does not push appointment data to the patient chart, sync claims, or update insurance ledgers. ModMed, Nextech, PatientNow, AestheticsPro, and Boulevard remain the systems of record.
• Insurance billing. Aesthetic procedures are cash-pay, which is exactly why crypto fits. It cannot settle a claim against any insurance carrier, Medicare, or Medicaid. Mixed-revenue chains use crypto on the cash-pay side and keep the claims workflow intact on the insured side.
• State medical privacy law. California’s CMIA, New York, Texas, and Washington layer additional obligations onto HIPAA. None are altered by the payment rail. Group counsel should sign off on patient-facing language.
• AML, OFAC, patient KYC. Aurpay does not perform patient identity verification or sanctions screening on the chain’s behalf. The group remains responsible for any AML or OFAC obligations, particularly on high-value international transactions.
• Patient financing. Aurpay does not provide installment loans. Chains offering 12 or 24-month plans on $25,000+ packages still need CareCredit, Alphaeon, Cherry, or similar.

If your compliance officer reads one sentence: Aurpay operates exclusively at the payment layer, identical in compliance footprint to the credit card processor the chain already uses.

Real-world signals

SkinSpirit operates 30+ U.S. locations; Ideal Image runs 150+; LaserAway operates 100+ clinics; Ever/Body, LCG Aesthetics, and Schweiger Dermatology all sit in the multi-site multi-state range. None have publicly committed to crypto checkout at the group level as of mid-2026. But the operating pressures above (chargeback pooling, federated reconciliation, international clientele, brand-consistent discreet billing) exist at every one.

The single-clinic precedents are durable. Spath Dentistry has accepted Bitcoin for cosmetic and restorative procedures since 2017. Memorial Plastic Surgery in Houston added crypto for discreet billing. Peace Love Med Spa added it for wellness packages. PayPal’s January 2026 merchant survey found roughly 4 in 10 U.S. businesses now accept digital asset payment, up from a single-digit percentage three years earlier. The 2026 wave is service businesses with high tickets and high dispute exposure.

Here is what most chain operators miss. The path from single-clinic to chain is natural: one location goes first, the regional manager sees the chargeback rate falling on the crypto-paid share, the CFO sees a new revenue column, and the rollout extends across the network over six to twelve months. This is genuinely harder than the single-clinic version, mostly because of governance and tagging discipline, but the mechanics are not exotic.