Question about Gambling websites with Curaçao license using incorrect Merchant Category code (sida 1 556)

Im still at stage 4 waiting for senior Ombudsman decision.

About 3 weeks ago. Only 4 transactions they could find on my revolut account which 3 of them were declined. Find it hard to believe none of my 42 merchants on monzo aren't any of walletto.

Yes, i spoke to an agent for a long time and explained everything.

Hi. Mine definitely shows RAVTOR. But if you have any information or contact details for RAVORA, I'd appreciate it as well.

Hi. Yes, Xpate seems to do this quite often. I've also seen cases where the documents they provide don't really correspond to the disputed transactions. It's important to check everything carefully and challenge anything that doesn't match. Hopefully your bank will take this into account and the remaining chargebacks will be resolved in your favour.

Glad to hear you've at least started getting some of the money back. Have you tried contacting the merchant or Walleto again since the chargebacks were raised? Maybe now that they've received the disputes and already lost one of them, they might be more willing to refund some of the remaining transactions directly.

Glad to hear you've already managed to recover some of the money. Have you tried contacting Xpate again since they started receiving and losing some of the chargebacks? Maybe once they see that the disputes are being decided against them, they'll be more willing to refund some of the remaining transactions directly rather than letting every case go through the full chargeback process.

Got another group of merchant names I'm trying to identify:

VELTOR, KREMIX, DARNIQ, FOLVEX, QENTAR, MERVIK, SALDRO, NORTIQ, PELVAN, ZERMON

Has anyone seen any of these before? I'm wondering if some of the transactions might have been processed through Xpate or Walleto.

Glad to hear you've had a better experience with Walleto. Unfortunately, it's been completely different in my case. They haven't refunded my money and communication has got me nowhere, so I've had to rely on chargebacks and complaints to try to recover the funds.

Yes, I've managed to win chargebacks on several of the transactions and got the money back. But it's been a long process. Xpate doesn't seem to be in any hurry to resolve these cases or issue refunds, so I'm still waiting on the rest.

That’s a shame, I can only go off my one experience with them. Sorry to hear you’ve had a difficult time with them

I’ve also got another batch of merchant names I’m looking into:

ZELVOR - KANTIQ - BREMEX - DOLVIK - FARNET - QERMON - TALVOR - NEXRIM - GERVAX - PELTRO

Does anyone recognise any of them? I’m particularly interested in finding out whether Xpate could be processing the payments.

how are people actually raising chargebacks on these transactions? Maybe i shouldn’t have raised 62 at a time but i feel like i can’t try and raise them again now? or can i try and add in the extra merchant contact i have had? barclays and vanquish especially.

Still looking for these ,

deposits done to Atefia8.com casino

transfered with apple pay trough segopay.com (unreachable) or dinotech.power something..

I was in the same situation — transactions from NTBOST London and similar masked descriptors (HALSCORE, NWCNTR, DNCG) on my card statements, all linked to the same unlicensed casino operator.

What worked for me, step by step:

Request the technical transaction data (ARN, Acquirer ID, MCC) from your card issuer. In the EU you can do this via a GDPR Art. 15 request. The descriptor name alone is not enough — you need to know which acquirer (payment processor) actually handled the transactions.

Contact the acquirer directly, not just the merchant. File a formal complaint with them referencing PSD2 Art. 47/73, incorrect MCC usage (gambling transactions must use MCC 7995), and the fact that the operator is unlicensed in your country.Provide complete documentation per transaction: dates, amounts, ARN list, and proof that the merchant never delivered (e.g. rejected withdrawals, unresponsive contact channels).In my case, three different acquirers in this cluster have refunded their transactions in full after formal complaints — so it does work. The key is being precise, documented, and addressing the acquirer rather than only the casino.Hope this helps someone here.

Verifierad Acquirers

Acquirer: Walletto UAB → Deskriptor: Epskshop

Acquirer: Unified Finance Ltd →

Deskriptor: lp payECOMMBX Limited → hydronique.me

Acquirer: DECTA Limited → Deskriptor: DCT*key4ge1

Walletto UAB → Epskshop — They respond well to formal written complaints sent to complaints@walletto.eu with a completed TRI form and a full per-transaction ARN list from your card issuer.

Unified Finance Ltd → lp pay — Fastest responder in my experience. Email info@unifiedfinance.com per their own Complaints Policy: include your full name, contact email, transaction dates, amounts, and your proposed resolution.

ECOMMBX Limited → hydronique.me — File at complaints@ecommbx.com and reference their Complaints Policy, which promises a final response within 1–2 business days when the case is fully documented. Attach everything up front (complaint letter, TRI form, ARN list).

DECTA Limited → DCT*key4ge1 — Use their official complaint addresses uk_complaints@decta.com and cy_complaints@decta.com , with data.protection@decta.com in CC for GDPR requests.

General tip for all of them: request the technical transaction data (ARN, Acquirer ID, MCC) from your card issuer first — via a GDPR Art. 15 request in the EU.

The descriptor name alone is not enough; the acquirer confirmation is what makes the complaint land.

Is it confirmed?

Can bank reject it ? Mean if they need to show you all

ask specifically for "ARN, Acquirer ID/ICA, and MCC per transaction" in writing. If they push back, remind them it's a formal GDPR Art. 15 request and note the date — the clock starts running from your request.

In my own case one issuer handed over the full list (ARN, acquirer ID, MCC per transaction) after a phone follow-up, while another had already provided the same data in writing within days. So it works — just be formal and specific.

One important warning: when you receive the data, make sure you get the registered company name of the acquirer, not just the acquirer ID number. A bare numeric ID is essentially useless to you — you cannot send a complaint or a GDPR request to a number. If the issuer only gives you IDs, go back and ask them to provide the acquirer's legal entity name for each ID. That is exactly what I had to do with one of my issuers.Ask specifically for "ARN, Acquirer name and ID, and MCC per transaction" in writing, and note the date you sent the request — the clock starts running from that date.

Sorry to hear that. In my case the difference was going formal from the start: a written complaint to complaints@walletto.eu with a completed TRI form and the full ARN list per transaction attached already in the first email (obtain the ARNs from your card issuer via a GDPR Art. 15 request).If Walletto doesn't respond within their stated 15 working days, escalate:Bank of Lithuania (Lietuvos bankas) — they supervise Walletto; complaint is free, and Walletto has already been sanctioned by them this year.GDPR/data protection authority if they ignore your data requests.Chargeback through your issuer in parallel — the tracks don't conflict.The key is the complete file up front — no back-and-forth.