The community's own directory of places that take Zcash lists 261 entries. Its highest-voted item is a Zcash sticker sold by a local meetup group, and the entries below it include a digital library, a hot sauce maker and a boba shop.
That is not a criticism of anybody. It is the honest size and shape of the spending surface, and it is more useful than the four separate directories that rank for this question and never say how big they are.
what follows covers where ZEC goes and what the alternatives are. Our guide to Send and receive Zcash covers the mechanics of actually sending it.
What the directory actually contains
Counting is the first useful thing nobody does with these lists. A single-page capture of the community pay-with directory yields 261 entries with logos, every one of them distinct (source: Pay With Zcash). That is a count of one page on one day rather than a census of the world.
Its own vote counts order the list, and the ordering is the informative part. At the top sits a sticker sold by a city meetup group, followed by a digital library and a clothing shop.
Read further down and a pattern emerges. A hot sauce maker, a boba shop, a pasta restaurant in one city, a bullion dealer marked as serving a single country, a bracelet maker in another. These are small, often local, frequently online-only businesses run by people who chose to accept it, which is a completely different thing from a payment network.
One large retailer does appear on the list, and the directory does not say how acceptance works there, so no claim about it is made here. A name in a directory establishes that a route existed when somebody added it and nothing more.
A second community listing exists separately (source: Free2Z), maintained independently, which is why the lists disagree. Four directories ranking for one question with four different answers is itself a description of the surface.
Worth being precise about what a count like this can support. It establishes an order of magnitude and nothing finer, since a directory records what somebody added rather than what is currently true, and no directory here publishes a last-checked date against its entries.
The rails behind the directories
A directory shows destinations, which is the visible half of this question and by some distance the less interesting one. What sits underneath any of those entries is a small set of payment rails, each with a different shape and a different reach, and no page anywhere enumerates the four of them together.
A payment gateway. At least one general crypto payment processor offers Zcash acceptance to merchants as a supported option (source: NOWPayments). That means any merchant using that processor can switch it on, which is a much larger potential surface than any directory and says nothing about how many have.
Mobile top-ups. The community wiki documents paying for mobile airtime with ZEC as a working route (source: ZecHub), which is one of the few genuinely everyday uses on the list.
Tipping and creator payments. The same wiki maintains a page of tipping and profile platforms, which is a real surface with a specific shape: small amounts, sender-chosen, often between people who already know each other.
Non-custodial swaps. Covered in the next section, and in practice the largest of the four by volume of intent.
Each of those four rails is real, each is documented by somebody with an interest in it working, and not one of them is retail payments at scale. Our explainer on what a blockchain address is covers the mechanism they all share, and our guide to Send and receive Zcash covers the sending procedure itself.
The gateway is the one with the most leverage in it. A merchant already running that processor turns Zcash on with a setting rather than an integration, which means the gap between potential and actual acceptance here is a business decision rather than an engineering one.
Swapping, which is what most holders do instead
Ask what people actually do with ZEC rather than what they could theoretically do with it, and the answer appears to be that they move it a great deal more often than they spend it. The routes for moving it are considerably better documented than the merchant surface is, and that documentation gap is itself the evidence for the claim.
The community wiki carries a step-by-step guide to swapping Solana assets into ZEC through an intents network, using a browser wallet and no centralized venue (source: ZecHub). It is written as a procedure with screenshots, which is a fair indication of where community effort has gone.
Alongside it sit pages on non-custodial exchanges and on a browser-extension integration, all of them about acquiring or moving rather than spending. Counting pages is a crude instrument and the ratio is not close.
That imbalance is the honest headline. The tooling around getting into and out of ZEC is well developed and actively documented. The tooling for handing it to a merchant is a few directories and a payment processor option.
Anyone deciding between routes should note that swapping and spending have different privacy properties, which our crypto privacy basics guide covers, and that custody changes hands differently in each, which our guide to custody for investors sets out.
None of that makes swapping the wrong choice for anybody. It makes it a different transaction with a different set of parties and a different result, and the section below is about what changes when the destination is another chain rather than a merchant who will hand you something.
Wrapped ZEC vs shielded ZEC
This is the part worth carrying away from the whole article, and the reason it is worth carrying is that it is not an empirical claim about any particular bridge, token or service. It follows from how Zcash is built.
Zcash's privacy comes from shielded pools, which are a consensus feature of the Zcash protocol, defined in its specification and enforced by its nodes (source: Zcash protocol specification). Our guide to Zcash shielded pools covers what they are.
Shielded pools exist only on Zcash. No other chain has them, because they are part of Zcash's consensus rules rather than a portable feature.
It follows immediately that a token on another chain which represents ZEC, however it is named and however it is issued, is not in a Zcash shielded pool. It cannot be. Whatever privacy it has is whatever the host chain provides, which for most chains is the transparency our guide to Bitcoin privacy basics describes.
That argument requires no assessment of any bridge's security, no claim about any specific token, and no information that can go stale. It is true by construction and it will stay true. Our guide to Zcash shielded pools covers what a pool is; the point here is only that there is exactly one chain they exist on.
The practical version: if the privacy is why you hold it, the representation on another chain is not the thing you wanted, and a route that ends in native ZEC in a wallet you control is a different outcome from a route that ends in a balance somewhere else.
Limits of the spending surface
It is not broad merchant acceptance and nothing here should be read as suggesting otherwise (source: Pay With Zcash). A few hundred listings across a community directory, weighted heavily toward small and often local sellers, is a real surface and a small one, and both halves of that sentence matter.
It is not growing or shrinking as far as anything here shows. One count, on one day, from one directory. A second reading later would be needed to say anything about direction, and none is offered.
The directory is not a guarantee either. An entry establishes that somebody added a business at some point, and neither this guide nor the directory checks whether a given seller still accepts payment today. Verifying a payment actually arrived is what a block explorer is for on the transparent side.
Nothing here assesses any bridge, wrapper or swap service. The caveat above is structural and deliberately says nothing about whether a particular route is safe to use.
And this is not an argument that ZEC should be spent. Plenty of holders never intend to, the swap and custody tooling is where the ecosystem's effort has visibly gone, and our guide to Buy Zcash covers acquiring it for whatever purpose you had in mind.
One last thing the surface does not tell you is anything about the asset. A payment network's size is a fact about adoption rather than about design, and our guide to how exchange wallets work covers the route most holders take instead of either spending or swapping.
What to check before you send ZEC to any service
Five checks, and the first two account for most of the ways this goes wrong.
Check which address type the service accepts. A directory entry saying a service accepts ZEC does not say which kind of ZEC address it can receive at. Many accept only transparent addresses, which means the payment publishes its amount whatever your own side does.
Check whether the listing is current. Directories are maintained by volunteers and by the projects themselves, and entries outlive the arrangements they describe. A service that stopped accepting the asset two years ago frequently still appears.
Check what the service does with the coin immediately. Many processors convert to fiat or a stablecoin on receipt, which means the merchant never holds ZEC and the arrangement is a payment rail rather than an acceptance of the asset. That is not dishonest, and it changes what your payment actually is.
Check the minimum and the fee. Payment processors set their own floors and margins, and both can be large relative to a small payment. The figure quoted at checkout is the one that matters rather than the network fee.
Check what happens if the payment fails. A payment sent to an address that the recipient can no longer sweep is not recoverable by the network, and the remedy is entirely a matter of the recipient's support process. Knowing whether one exists before you send is the whole precaution.
Why the spending surface stays small
Three structural reasons keep this list short, and none of them is likely to change quickly.
Merchant acceptance follows payment processors rather than demand. A merchant accepts what its processor supports, and processors add assets when integration cost is low and compliance cost is predictable. An asset whose defining feature complicates transaction monitoring scores badly on the second even when the first is easy.
Volatility makes holding awkward for anyone with costs in another currency. That is why so many arrangements convert on receipt, and conversion on receipt removes most of the reason a merchant would list the asset as a differentiator.
And the privacy feature that makes the asset interesting to a holder is the feature that makes it complicated for a business. A merchant that accepts shielded payments has accepted a payment it cannot fully account for in the way its own obligations may require. That tension is real and it does not resolve by anyone trying harder.
The three ways ZEC actually leaves a holder's hands
Directories describe merchant acceptance, which is the smallest of the three routes by a wide margin. The realistic picture looks different.
Selling on a venue is the overwhelming majority. Most ZEC that stops being ZEC does so because somebody sold it for something else on an exchange, and that route has nothing to do with merchant acceptance at all. Our guide to buying and selling ZEC covers the mechanics in both directions.
Swapping is the second, and it is what most holders reach for when they want a different asset without going through a venue account. The tooling here is genuinely good and it is the part of the ecosystem that has developed fastest.
Direct payment is the third and the smallest. It exists, it works, and the number of places it works is not large. Treating it as the main use of the asset misdescribes what almost everyone does with it.
Naming the three in proportion matters because the ecosystem question is usually asked as though acceptance were the measure of whether an asset is useful. On this asset it is not, and the parts that are heavily used are the parts nobody writes directories about.
What a directory entry actually establishes
Four things it does establish, and four it does not, because the gap between the two is where most disappointment lives.
It establishes that somebody submitted a listing at some point. That is a real fact and it is a low bar.
It establishes a claimed capability rather than a tested one. Almost no directory verifies that a listed business still accepts the asset, and entries persist long after arrangements end.
It establishes nothing about which address type is accepted, which is the question that decides whether a payment publishes its amount.
And it establishes nothing about the payment path. A business accepting the asset through a processor that converts on receipt has a very different relationship to it than one that holds the coin, and directories rarely distinguish the two.
The practical consequence is that a directory is a source of candidates rather than a source of answers. Confirming an entry takes one message to the business and saves the failure that comes from assuming.
There is a structural reason directories drift this way, and it is nobody's fault. Adding an entry is a single action taken by someone with an interest in it appearing. Removing one requires somebody to notice that an arrangement has ended and to care enough to say so, and nobody has that interest. So listings accumulate and rarely leave, which means a directory's size grows over time whether or not the underlying acceptance does.
That asymmetry is worth carrying to any list of this kind, on any asset. The count is a measure of how many entries were ever submitted rather than of how many currently work, and the gap between those two widens with the age of the directory.
What would have to change for the surface to grow
Three conditions, and none of them is a matter of anyone trying harder.
Processor support would have to broaden. Merchants accept what their payment provider offers, so acceptance follows integration decisions taken a layer above the merchant. That layer weighs integration cost against compliance cost, and the second is where a privacy asset scores badly.
Settlement would have to become predictable enough for a business with costs in another currency. Most arrangements today convert on receipt precisely because holding is awkward, and conversion on receipt removes most of the reason a merchant would advertize acceptance at all.
And the compliance position would have to settle. A business accepting shielded payments has accepted value it cannot fully account for in the way its own obligations may require. That tension is genuine, it applies to the feature that makes the asset interesting, and no amount of tooling resolves it.
None of those three is close to resolved, which is why the honest description of this surface is small and stable rather than small and growing. Anyone reading a directory's entry count as a trend line is reading the wrong signal.
Frequently asked questions
Where can you actually spend Zcash?
The community's own pay-with directory lists 261 entries in a single-page capture, weighted toward small and often local businesses: the highest-voted item is a Zcash sticker sold by a meetup group, and entries below it include a digital library, a clothing shop, a hot sauce maker and a boba shop. A second community listing exists separately and disagrees, because each is maintained independently. Behind the directories sit a payment gateway option, a mobile top-up route and a tipping surface.
Is wrapped ZEC the same as Zcash?
No, and the reason is structural rather than a comment on any particular token. Shielded pools are a consensus feature of the Zcash protocol and exist only on Zcash, so a token on another chain representing ZEC is by definition not in one. Whatever privacy it has is whatever its host chain provides. If the shielded property is why you hold ZEC, a representation elsewhere is not the thing you wanted.
Can merchants accept Zcash payments easily?
The rail exists. At least one general crypto payment processor lists Zcash as a supported asset, so any merchant already using that processor can enable it. That describes a potential surface rather than an actual one, since nothing here measures how many have done so, and the directories suggest the answer is a few hundred worldwide rather than a few hundred thousand.
What do most Zcash holders do with it?
Move it rather than spend it, on the evidence of where community documentation effort has gone. The community wiki carries step-by-step guides to non-custodial swaps, browser-extension integrations and cross-chain routes into ZEC, alongside a much thinner set of pages about paying anybody. That imbalance is the clearest available signal about actual usage, and it is a signal rather than a measurement.
Researched and written by the BloFin Academy editorial team with AI-assisted drafting. Primary sources are two community pay-with directories, the community wiki's guides to swaps and top-ups, a payment processor's own supported-asset page, and the Zcash protocol specification. All facts independently verified against cited documentation current as of August 2026. The 261 figure is a count of one directory page on that date and no claim is made about direction.