Everyone is hyping the MiCA scope cut for crypto payments, but NOWPayments’ latest…

Bloody hell, you’re not wrong to choke on that flat white—this isn’t some edgy compliance meme, it’s a straight-up liability landmine. Let me lay the tiers in the order they’ll matter when the chargeback lands. 1. MID contract jurisdiction sits with your acquiring bank, full stop. NOWPayments is the payment facilitator here, not the acquirer, so their licenses—MGA, Curaçao, whatever—only tell you how the fiat leg converts, not who bears the compliance hit. Belgian MID terms still call the shots; if your acquirer flags EURT as unregulated stablecoin, you absorb the chargeback regardless of NOWP’s sales pitch. 2. NOWP’s EURT option shows MGA and Curaçao because they route the crypto settlement through exchanges licensed there, but MiCA explicitly carves out crypto-to-fiat conversion services that sit outside the EU perimeter. EURT is a USD-pegged stablecoin issued by Tether; NOWP converts it to EUR for your acquirer, so the conversion itself is the regulated step—and it falls under MiCA only if the converter holds an EU license. NOWP does not; their conversions happen in offshore entities. 3. Chargeback vector: Belgian player deposits EURT via NOWP’s widget → EUR lands in your merchant account 2-3 days later → next week chargeback hits because the player cried fraud. Acquirer looks at the MID paperwork; finds no EU-licensed entity in the chain for the conversion step; flags it as “unregulated funds.” Liability lands squarely on your settlement agreement with the acquirer, not NOWP’s offshore licenses. Tradeoff you’re staring at: NOWP’s 0.8–1% fee is cheap until a single EURT chargeback costs you 5-15 bps of GGR plus rolling reserve hits. They’ll argue they disclaim everything in their T&C, but courts will look at where the fiat conversion occurs—and that’s not under MiCA coverage. So before you let another Belgian player fund via EURT, check your MID annex that governs stablecoin settlement. If it doesn’t explicitly name an EU-licensed converter, rewrite it or switch acquirers. NOWP’s dashboard isn’t your shield; it’s just marketing.

you ever try to explain to an auditor that the fiat legs of your crypto deposits are "technically" regulated because your payment facilitator cites two offshore licenses while the stablecoin you took is literally a tether issued in the caymans the invoice for that audit still had your name on it, not theirs the math is simple — you got a MID in belgium, the acquirer's office sits in dublin with irish law tucked into the contract, and NOWP's dashboard blinking "MGA approved! curacao approved!" like a casino neon sign in havana after the revolution isn't going to re-wire that reality i've pushed eurt, usdt, usdc through half a dozen "miCA ready" processors over the past 24 months — every single time i got the same song: "trust us, the conversion happens in malta" until the chargeback lands and my compliance guy starts dialing the acquirer's lawyer while my CFO texts the controller to move another 120 bps of ggr into rolling reserve NOWP's ticket #2024-0457 is cute but irrelevant — it's like putting a life vest on the airplane seatback tray and calling it a safety briefing when the pilot forgot to file a flight plan the liability chain is short: your mid contract → acquirer's jurisdiction → your desk. anything that happens between the player and NOWP's offshore crypto desks is noise; the courts care about who signed the settlement agreement with the bank, not whose logo appears next to the big green "EURT" button my advice? rewrite the annex with a line that says "all crypto-to-fiat conversions must be executed by an eu-licensed psp" and price the option of switching acquirers into the model — because one belgian fraud chargeback will eat more than the 80 bps you saved in fees

What do we actually mean by "EU-licensed PSP" here though? Like, does that include a Lithuanian EMI that’s passporting services into Belgium under MiCA, or are we talking about the actual Belgian FSP license with a MID tied to it? And where does NOWP even fit in that chain if they’re routing through Malta but the conversion isn’t happening there?

seen this movie before—when the dust settles it's always about who's got the MID handcuffed to their desk when we say "eu-licensed psp" for crypto-to-fiat in belgium, we're talking about one of three things: 1. the merchant’s own EMI/FSP license in belguim (the full fat one with a psd2 passport into the eea) 2. an intermediary EMI based in lithuania that’s passporting under miCA and whose conversion desk actually touches the fiat rails in belgium 3. your acquiring bank’s own crypto desk if they’ve spun up an miCA compliant outpost—some of the big dublin-based acquirers are quietly launching these in NOWPayments’ case the murk is thicker than curacao rum on a saturday night. the ticket says “malta entity!” but what really happens is a cypriot shell converts the tether invoice to eur offshore, then wires the funds to NOWP’s belguim wallet, then your acquirer sweeps it into your mid. none of those steps are physically inside the eu regulatory perimeter except the last hop—and courts don’t care about the last hop when the conversion that started the chain was executed by a papua-new-guinean sub under a malta trading name. example: last month one of our lithuanian EMIs popped up with a new widget that advertises “eurt mint&burn with miCA passport”. we ran a 50k eur stress through it—deposit lands as tether straight into their lithuanian omnibus, they settle to our belguim mid as eur. chargeback lands? lithuanian emi takes the hit, not us. NOWP can scream MGA, Curacao, Mars, whatever in their dashboard—they’re just the crypto taxi, the taxi doesn’t pay the parking ticket, the driver does ah well, we’ll see

That MiCA carve-out for crypto conversion reads like a fine print footnote when the auditor walks in with a pile of EURT chargebacks—it’s not a lifeline, it’s a liability map you won’t see until the mid-contract gets litigated. Sam_Biz nailed it: the PSP doing the fiat conversion is the one holding the bag, and NOWP’s dashboard “MGA & Curacao” labels mean less than the stamp on your MID annex. In my own books, we had a batch of Belgian deposits routed through EURT via a Malta-licensed converter last summer. Compliance signed off on it because the paperwork said “EU-regulated entity,” but when the first USDT chargeback hit the MID, the acquirer’s lawyer flagged the conversion desk as a Cyprus shell. The rolling reserve clawed 150 bps off that month’s GGR, and NOWP’s support ticket “#2024-0457” did nothing but collect dust. So here’s the caveat: if your annex doesn’t explicitly name the converter entity that touches the fiat rails inside Belgium or an EU-passported EMI, you’re cosigning the fraud file—not them.

Careful, PaymentsProLive—you’re dancing around the one nuance that burns the worst in court: the MID annex doesn’t just need the name of a PSP, it needs the MID tied to that PSP inside Belgium. I’ve sat through two Belgian auditor walk-throughs where the devil lived in Schedule C of the annex, not the body text. First case: annex listed “NOWP Malta OÜ” as converter, but their Belgian MID belonged to a dormant EMI that hadn’t filed PSD2 passports since 2022—auditor treated the schedule as void and parked the liability with the acquirer. Second case: annex named the Lithuanian EMI correctly, but omitted the EMI’s Belgian branch MID because “it’s just a number.” Consequence? Chargeback hit on day 12, courts ruled the branch MID was the “final destination” for settlement, so the conversion footnote in the contract carried zero weight. Lithuanian EMI paid the clawback; Lithuanian EMI wrote the ticket. Rewrite the annex to include the MID numbers of every converting entity, not just legal names—otherwise your lawyer ends up explaining why a “Malta entity” is legally dead in Schedule C while you’re staring at 180 bps of rolling reserve.

So where does that leave a small operator with maybe 200 k EURT volume rolling through NOWP right now? Their dashboard still flashes MGA and Curacao as it did last quarter, but after reading every reply in this thread my gut says the annex in my Belgian MID contract is the only real shield—and I don’t even know the MID numbers for whatever PSP is actually touching the fiat rails.

Last week I sat with our compliance counsel going over every MID annex in our cabinet—four contracts, all different, all Belgian—but when we laid the MID numbers next to the conversion chain, two of the so-called “EU-regulated” entities were dormant shells that hadn’t filed audits since 2023. The lawyer didn’t even blink: “those pages are legally blank.” Small operators? You don’t need a MID annex that screams “liability shield”—you need a clause that bans every offshore hop and forces NOWP to name their actual Belgian MID holder on day one. Otherwise you’re just moving the fraud file from Curacao to your own doorstep.

That Malta-to-Cyprus-to-Belgium hop they're hiding behind NOWP's dashboard is a freaking clown show 😅 been with them a couple years and tbh this is NOT the level we signed up for—our stack just works because it’s CLEAN, no offshore tango. Time to demand that Belgian MID number or switch the taxi