Cryptocurrency payments for an adult directory: what accepting crypto actually solves, and what it doesn't

A merchant account application comes back declined, or an existing one gets closed with a form letter that names no reason, and somewhere in the search for what to do next, someone suggests skipping banks and card networks entirely and taking payment in cryptocurrency instead. It sounds like the clean way out of a problem that has already cost weeks: no acquiring bank to satisfy, no card network category to hide from, no processor who can pull the account on a Tuesday.

That pitch treats crypto as a bypass of the entire card-processing problem, and it is worth sorting out, in order, what part of it is actually true before a payment page gets built around it. Some of it holds. A good deal of it does not, and the parts that do not are the ones nobody selling the integration brings up first.

The two processors most people mean by 'crypto' say no too

When an operator says they will just take crypto, the tool they usually mean is one of the two names with brand recognition and a plugin for every shopping cart: Coinbase's payment product, or BitPay. Those are the two most people find first, because they are the two set up to make accepting crypto feel like flipping on a normal payment method rather than running a server of your own.

Both of them ban this business outright, in their own written terms, independently of anything a card network requires. Coinbase's usage policy excludes sites offering sexually related services, naming escorts specifically. BitPay's terms exclude adult businesses and escort services by name and have done so since 2018, when the company tightened a policy that had been looser before. Neither leaves room for a directory to argue it only lists advertisers rather than selling services itself; both policies are written around what the site is, not around how carefully the payment button is worded.

This is worth stating plainly, because a lot of operator time gets spent on the assumption that crypto sits outside the reach of an 'adult business' exclusion the way it sits outside a card network's rulebook. It does not. Coinbase and BitPay wrote that exclusion into their own policies on their own judgment, for the same reason a bank avoids the category: the business carries reputational and regulatory weight the company decided it does not want to carry, and no card network forced either decision.

What is actually left once those two names are off the table is a narrower set of options: smaller and often offshore payment gateways that serve the category deliberately, processors that advertise no verification of the merchant at all, or software the operator runs themselves, where there is no processor to say no because there is no processor in the middle to begin with. Each of those comes with its own cost, and none of them is the neutral, processor-free payment method the pitch implies.

What settlement without a bank actually removes

The part of the pitch that holds up: once a transaction on a public blockchain is confirmed, there is no bank in the chain that can pull it back the way a card issuer reverses a disputed charge at a cardholder's request. The receiving wallet holds the funds, and the mechanism a chargeback runs on simply is not present in the transfer itself. That is a real, structural difference from a card payment, not a marketing claim.

But settlement on the blockchain is one layer of the transaction, not the whole of it, and two things that sit on top of that layer behave a lot like a dispute in practice, even though neither is a chargeback in the technical sense.

The first is the stablecoin issuer itself. Tether and Circle can both freeze a specific wallet address holding their coins after a transfer has already settled; the transaction on-chain is not undone, but the recipient can no longer move or cash out what landed there. Tether states publicly that it has frozen more than four billion dollars this way, across thousands of addresses, working directly with law enforcement in dozens of countries. The freeze follows an address that risk scoring or an investigation flagged as connected to something else, several transfers removed in some cases, which is how a wallet belonging to someone who did nothing wrong can end up caught in an action aimed at somebody else entirely.

The second is the funding source behind the payment itself. If a customer bought the crypto they used with a credit card minutes before paying, that card charge is still open to an ordinary dispute with the card issuer, exactly as it would be for any other purchase. The blockchain transfer that followed it was final; the card charge that funded it was not, and whichever business ends up holding the crypto absorbs the loss when that dispute lands.

Net effect: fewer disputes than a card-based business sees, not none, and the ones that do happen arrive from a direction nobody budgeted for, an address freeze instead of a bank's notice, with no published timeline and no appeal process built for it the way a card dispute has one.

Volatility is the risk everyone plans for; freezing is the one nobody does

Most operators who get this far already know to ask about volatility, and land on a stablecoin, USDT or USDC, priced to track the dollar one to one so the amount that arrives does not swing with the market between the invoice and the payout. That is a reasonable read of the obvious risk, and it is usually where the due diligence stops.

What gets missed is that a peg is a promise from the company behind the coin, not a guarantee written into the software. USDC lost its peg in March 2023, when the bank holding a large share of its reserves failed; it traded down to roughly eighty-seven cents before recovering over the following two days once the bank's depositors were made whole by regulators. The coin did not fail because of anything a merchant did. It failed because its value depended on one specific bank staying open, and for two days it was not one to one with anything.

USDT carries a different risk that matters more for this business specifically: Tether's own freezing activity, described above, is not a rare event reserved for confirmed criminal wallets. It runs on risk scoring that reaches several hops out from whatever it flagged first, and an operator's payout wallet sitting a few transfers away from a flagged address is a documented way an uninvolved business has ended up frozen out of its own balance.

Neither risk appears on the marketing page of a processor selling the integration, because neither one is something the processor caused or can fix. Both are properties of the coin itself, decided by the company that issues it, which is exactly why the pitch to accept crypto rarely mentions either one.

The identity check doesn't disappear, it moves to the exit

Accepting crypto only answers half of a payment problem. The other half is converting it into money that actually pays a hosting bill or a salary, and that conversion runs through an exchange, which is itself a regulated business with the same instinct to avoid this category that a bank has already shown once by closing an account with no explanation.

Exchanges and payment processors operating under real oversight are required to verify who they are dealing with, and above certain transfer sizes, to pass identifying information about both sides of a payment to each other before it settles. Most jurisdictions implement some version of the Financial Action Task Force's Recommendation 16 to require this; the United States version of that rule applies to transfers over three thousand dollars.

Below that threshold, or when the money moves to a wallet nobody but the customer controls, the rule mostly does not reach, and that gap is exactly what processors advertising no merchant verification are built around. Routing the business through that gap does not remove the compliance step; it removes the bank or processor that would otherwise absorb a bad actor's activity before it becomes the operator's own problem to explain.

On tax, nothing above changes the basic rule: crypto received for a sale is ordinary income on the day it arrives, valued at that day's price, whatever happens to the coin afterward. A separate rule that would extend the existing ten-thousand-dollar cash reporting requirement to cover digital assets was written into law in 2021 and still has not been switched on; the IRS confirmed in early 2024 that digital assets stay out of that specific count until it publishes the implementing regulation. That is a delay in one filing requirement, not an exemption from income tax on what the business actually received.

What to actually do with this

Treat crypto as a second payment rail sitting next to a card or ACH relationship that already works, not as a replacement for one. A method that cannot be the only option on the checkout page is not the fix for a processor rejection; it is a hedge against the next one, and it only works as a hedge if the rest of the payment setup is already standing on its own.

If it gets offered, offer a stablecoin only, and know before the first payment arrives which exchange will convert it to spendable currency and what that exchange requires at onboarding. That conversation belongs on the same timeline as opening the bank account, before launch, not after the first payout request makes it urgent.

Skip any processor whose entire pitch is that it asks the merchant for nothing. The appeal is obvious and the bill for it arrives later, as a frozen balance, a shut-down account, or an exchange that will not explain why a transfer stalled, with nobody upstream who owes the business an answer.

Get the tax treatment settled with an accountant who has actually filed for a business paid in crypto before, in the same week the payment method goes live, not at year end when the amount already received is a number somebody has to explain after the fact.