> For the complete documentation index, see [llms.txt](https://docs.escade.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.escade.io/the-problem.md). # The Problem Escade Solves Buying a card from a stranger online is a solved problem. Swapping one with a stranger is not. This page explains why, and why the big marketplaces have never fixed it. ## Cards are big business Collecting is mainstream. Aviva estimates two in three Brits consider themselves collectors, rising to 86% of Gen Z. Pokémon has become the headline act: monthly sales of single Pokémon cards on eBay passed $100 million for the first time in early 2026, a Pikachu Illustrator sold for a record $16.5 million in February 2026, and as of October 2026 the graded Pokémon market alone is worth around $15.7 billion. More money means more at stake in every transaction, and more reason for things to go wrong. ## How eBay made buying safe Before eBay, your market was your local shop and whoever turned up at a card show. eBay fixed two hard problems: finding someone to deal with and giving strangers a reason to trust each other. Its first answer, feedback, was weaker than it looked. Research on eBay found that buyers had a bad experience about ten times as often as they left negative feedback. A study using graded baseball cards found that a seller's rating said nothing about the condition of the card that turned up, and that a bad reputation could simply be abandoned for a fresh account. eBay has since fixed most of this. Today it: * **verifies sellers** with ID and a bank account, so walking away from a bad reputation costs something * **tracks unhappy buyers** whether or not they leave feedback, and penalises sellers who rack them up * **guarantees your money back** if an item doesn't arrive or isn't as described, and settles the case itself * **authenticates cards** worth £500 or more through PSA before they reach the buyer ## Why none of that works for a swap Look at what every one of those fixes depends on: **a payment**. eBay checks your identity so it can pay you. It penalises bad sellers through fees and payout holds. It refunds buyers out of a payment and recovers it from the seller. It authenticates a card in the gap between the buyer paying and the card being released. In a card-for-card swap there is no payment. There is nothing to take a fee from, nothing to refund and nothing to hold back. So, eBay, and marketplaces like it, offer no way to swap at all. That isn't a missing feature they could add next quarter. It doesn't fit how they work. ## Swapping is harder than selling Even setting the marketplaces aside, a swap is a harder deal to make safe. * **You need a double match.** You need someone who has the card you want *and* wants the card you have. * **Both sides are taking a risk.** In a sale, only the buyer must wonder what will turn up. In a swap, both of you do. * **Nothing anchors the value.** In a sale, one side of the deal is cash, which everyone can value. In a swap, both sides are cards, and only their owners really know what condition they're in. ## What people do instead Collectors who want to swap arrange it themselves in Facebook groups, Reddit and Discord. There is no escrow, no protection and no recourse. Somebody must post first, and sometimes that person loses their card and gets nothing back. The handful of apps built for swapping tend to fall into one of two camps: * **They step back.** They help you find a trade, then leave the risk with you if it goes wrong. * **They take over.** They hold your cards in their vault or hold the money and judge the dispute themselves. That makes it safer, but now you're trusting the platform instead of the other trader. ## Someone got close once OpenBazaar, a decentralised marketplace that ran from 2016 to 2021, used the kind of escrow that suits this problem. Payment sat in an account that needed two of three signatures to release: buyer, seller and a moderator. The moderator could rule on a dispute but could not take the money alone. The escrow did its job. OpenBazaar shut down anyway, for reasons that had nothing to do with it: it tried to be a marketplace for everything, the software was hard to use, choosing a moderator was confusing, and with no fees it couldn't pay its own bills. ## The gap So, the problem is not that collectors are dishonest. Most trades go fine. The problem is what happens when two people disagree about whether a deal was kept, and today there are only two answers: trust the other person or trust the platform. What is missing is a way to swap where: * the trade is enforced without anyone holding your cards or your money * backing out of a deal costs the person who backs out * a dispute has a clear, understandable route to an answer * the platform pays its way without needing to take custody of anything [How a sale works](/how-it-works.md) explains how Escade sets out to do that. *** *This page summarises the opening of the Escade whitepaper, where you will find the full argument and references.* --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.escade.io/the-problem.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.