There’s a moment in almost every high-risk merchant‘s origin story that they don’t put in the pitch deck. It’s not the moment they got their license, or hit their first thousand users, or closed their marketing budget. It’s a small moment, usually buried in a chat window at eleven at night, where someone on the other end of a sales conversation says something slightly too honest — and the founder, tired and relieved and three months behind schedule, reads right past it.
This is a story about that moment.
The Pitch
Picture the setup: a founder — call him E. — has spent months building a real-money skill-gaming platform. JackPot, but for stakes. The tech is done. The marketing budget is loaded: €200,000, sitting in reserve, ready to fire the moment the lights go green. Projections are the kind that make a payments sales rep sit up straight — a thousand players in month one, seven figures a month within the year. There’s just one problem, the same problem every operator in this category eventually runs into: nobody wants to move his money.
He finds a provider. The first message he sends is really a test, dressed up as a question: are you a direct PSP, or an orchestrator? It’s the right question — the kind of question you ask when you’ve been burned before, or read enough forum threads to know that “orchestrator” is often a polite word for “middleman who disappears when things get complicated.”
The answer comes back clean: direct PSP. Not an orchestrator.
Good. E. relaxes a little. This is the answer he needed.
The Waiting Room
What follows is four months of something that will feel painfully familiar to anyone who has tried to launch a licensed gambling or trading business: waiting. The gaming license is “in the final stages.” Then it’s “a couple of weeks out.” Then, finally — in July, a full four months after the first message — a PDF arrives. Certified. Real. A license number, an Anjouan jurisdiction, the whole thing.
Here’s what’s worth noticing about those four months: the provider never went quiet. Every few weeks, a gentle nudge arrives — any update on the form? No worries, take your time, but let’s get the paperwork moving so we’re ready the second you’re licensed. It reads as helpful. It is, in a narrow sense, helpful. It’s also a technique as old as sales itself: keep the prospect warm, keep them filling out forms, keep them investing time and effort into a relationship before they’ve had a chance to properly interrogate it. By the time the license lands, E. isn’t evaluating a stranger. He’s finishing a relationship that already feels four months deep.
The Contract
The agreement arrives. E. does the thing most founders in his position don’t do — he actually reads it, and he asks questions. Good questions. Twelve of them, numbered, professional, the kind of list you’d expect from someone who’s done this before or hired someone who has. Reserve terms. Settlement caps. Chargeback support. Country coverage. Whether the commercial terms could improve with scale.
Then he asks the one that matters most, almost as an aside, three questions down a numbered list:
Do you provide support with chargeback management or dispute resolution?
The answer arrives, unhurried, almost cheerful:
“Since these will be miscoded MID to save you from hot compliance — we do not fight chargeback — but provide dispute alerts.”
Ten words carrying the entire weight of the sentence: miscoded MID to save you from hot compliance.
What Just Happened
Here’s what that sentence actually means, stripped of the friendly phrasing: the provider intends to process E.’s transactions under a Merchant Category Code that doesn’t describe his actual business. Not an approximation. Not a gray-area judgment call about which of two adjacent codes fits best. A deliberate mismatch, engineered specifically so that card networks and issuing banks looking at the transaction data won’t see “real-money skill gaming” — because if they did, the account would attract exactly the scrutiny it’s supposed to attract.
There’s a name for this in the industry, and it isn’t a flattering one: transaction laundering. It’s explicitly prohibited by Visa and Mastercard’s own operating rules. It’s the reason merchant accounts get frozen without warning, the reason MATCH-listed businesses spend years locked out of card processing entirely, and — in some jurisdictions — a practice that can expose everyone involved, not just the PSP, to genuine legal liability.
And notice the trade being offered: in exchange for the miscoding, the provider won’t fight E.’s chargebacks. Not “we’ll try our best.” Not “our success rate is 60%.” A flat we do not fight chargeback. Because how do you contest a dispute on a transaction that’s already lying about what it is? You can’t defend a story you’ve already agreed not to tell straight.
This is the ten-word moment. This is the sentence that, in a healthier negotiation, ends the deal on the spot. It doesn’t. E. keeps negotiating — not because he missed it, exactly, but because by the time it arrives, he’s asking about settlement caps and fee structures in the very same message. It’s one bullet point in a list of twelve. The conversation simply… continues.
The Slow Reveal
What happens next is a masterclass in how these relationships actually unravel — not with a bang, but with a long series of small clarifications that each individually sound reasonable.
The 6% rate quoted early on turns out to have a silent plus-one: a 2% “settlement fee,” stacked on top, not included — a fact E. has to ask about twice before getting a straight yes. The contract mentions a “Gateway Settlement,” language that sits oddly next to the earlier, confident we are a direct PSP, not an orchestrator. When E. asks — again — whether the provider works with acquiring banks directly or through a partner, the answer this time is softer around the edges: “we directly work with acquiring bank and direct banking partner.” Two nouns where there used to be one clean claim.
The country list, once “all major markets,” turns out to have exceptions that only surface when E. names specific countries by name: one blocked for cards but open for crypto, another the reverse. A $10,000 settlement cap sits in the pricing schedule with no explanation of whether it’s a floor or a ceiling — E. has to ask three times, across three separate messages, before getting confirmation it’s a minimum, not a maximum, with no cap stated on the upside.
None of these, alone, would end a deal. Together, they describe a pattern: every hard number in this relationship is slightly softer than it first appeared, and every soft promise (“we can revisit the reserve after 45 days,” “no such thing as extra fees,” “there’s no max cap here”) exists only in a chat window, never in the signed agreement sitting on E.’s desk.
The Question Nobody Asks Out Loud
Here’s the uncomfortable part of this story, and the reason it’s worth telling at all: E. isn’t naive. He asks better questions than most merchants in his position ever do. He catches the fee discrepancy. He catches the terminology shift. He pushes, twice, on the settlement cap. By any reasonable standard, he’s doing his diligence.
And he still doesn’t walk away from the sentence that mattered most.
That’s not a personal failing. It’s a structural one. By the time “miscoded MID” appears in the conversation, E. has spent four months waiting, built a marketing campaign around a launch date, and finally has a license in hand. The cost of walking away at that exact moment doesn’t feel like “protecting my business.” It feels like starting the entire four-month waiting room over again, from zero, with no guarantee the next provider will say yes either. That asymmetry — a small, easy-to-miss sentence on one side, four months of sunk cost on the other — is exactly what makes this kind of red flag so effective at surviving contact with an otherwise careful founder.
What This Actually Costs
The arithmetic of a miscoded MID is brutally simple, and it’s worth spelling out plainly, because the sales conversation never will: the risk doesn’t sit with the provider. It sits entirely with the merchant. If a card network’s compliance team ever looks closely at the transaction data — and elevated dispute rates are exactly the kind of thing that triggers that closer look — the account gets frozen, the funds get held, and the merchant, not the PSP, ends up explaining to an acquiring bank why their MCC doesn’t match their actual business. The PSP, meanwhile, has a dispute-alert tool and a contract that never mentions miscoding by name, because why would it be written down.
A provider offering to disguise your business isn’t offering you a workaround. It’s offering you a countdown timer with no display.
The Checklist E. Should Have Had on Day One
- Treat any mention of “miscoding,” “recoding,” or an MCC that doesn’t match your actual business as an immediate dealbreaker — not a negotiating point, not a compliance shortcut. It’s the one item on this entire list that isn’t a matter of degree.
- Ask for the total effective rate as a single number, confirmed in writing to include every fee on the schedule — before you’re four months and one license deep into the relationship.
- Re-ask your structural questions after the contract arrives, not just before. “Direct PSP or orchestrator” deserves a second answer once you’re looking at real paperwork with real language in it.
- Get country and payment-method restrictions in writing, by name, rather than accepting “all major markets” as an answer.
- Notice when a provider stays warm during your waiting period. It’s not necessarily bad — but recognize what it’s doing to your objectivity by the time the deal is actually in front of you.
- Separate the emotional relief of finally getting a “yes” from the technical merits of the yes you got. They are not the same signal, and the sales process is not designed to help you tell them apart.
E.’s story isn’t unusual. That’s what makes it worth telling. Somewhere tonight, another founder is reading a message very similar to the one he got, feeling the same relief he felt, and getting ready to keep scrolling past the sentence that mattered.
This piece is based on an anonymized real conversation, reconstructed for narrative clarity. No specific company is named or identified. It is offered as educational content for merchants evaluating payment providers and is not legal or financial advice — anyone with concerns about a specific contract or practice should consult a payments attorney.


Comments
No comments yet. Be the first to share your thoughts.
Leave a comment