The Yaspa merchant question: payment route, risk report and undisclosed outcome

Yaspa carried out an internal review after receiving, between 8 and 16 September 2026, a complaint about a deposit attempt from the Netherlands; the complaint referred to a payment journey of €50 reported on 8 September at about 18:10 CEST, and asked to clarify which entity acted as the contractual merchant and how the beneficiary was verified. The email exchange contains Yaspa's 9 September statement: “Yaspa’s contractual and business relationship is with the merchant directly, rather than individual end users.”

Who is Yaspa and what services does it say it provides

Yaspa Limited is registered in England and Wales with company number 09902175 and appears on the register as a payment institution regulated by the Financial Conduct Authority with FRN 826720. The company lists James Neville as co-founder and CEO; the Companies House register of people with significant control lists James Adam Neville as the only active person with significant control: more than 25% and not more than 50% of shares and voting rights. Yaspa markets open-banking payments and verification services, and targets iGaming, retail betting, lotteries and trading, together with e-commerce and point of sale.

Yaspa states in its consumer privacy notice that European account information and payment initiation services are supplied via Yapily Connect. The company also said it closed a $12 million funding round in 2025 led by Discerning Capital, and that in 2026 it ranked seventh in the Sifted 250 for revenue growth. None of those references, however, determine what share of revenue or payment volume comes from the gaming sector.

The complaint: reported route and discrepancies between operator and beneficiary

The documentation FinTelegram reviewed describes the deposit attempt as a journey from the Netherlands with these elements:

• Reported casino site: luckygans.com/nl/

• Operator declared on the website: ALEYNA LIMITADA, Costa Rica

• Payment interface shown: banks.yaspa.com, labelled “luckygans” with Dutch banking options

• Transfer to: Fortunella Entertainment Limited, with an IBAN in Cyprus

• Technical bridge reported: handoff to SNS Bank that identifies Yapily Connect

The document records the claim that no payment was authorised or completed. The correspondence includes screenshots and references to a recording, though the video is not part of the PDF reviewed by FinTelegram. The gap between the operator visible on the website and the bank beneficiary requires explanation: a separate collecting entity can have a legitimate contractual role, but the papers do not identify which company Yaspa considered the “merchant” in this case.

The interaction timeline between the complainant and Yaspa

FinTelegram had access to an eight-page thread dated between 8 and 16 September 2026. The record shows these key actions:

1. 8 September: Yaspa technical support acknowledges receipt of the report.

2. 9 September: Yaspa confirms it maintains a direct contractual relationship with “the merchant”, invokes confidentiality and recommends contacting the merchant for operational clarifications.

3. 9–10 September: the reporter escalates the complaint and supplies the referenced recording.

4. 11 September: Yaspa requests photo ID and a recent proof of address to verify the complainant's identity.

5. 14 September: Yaspa reminds that it has not received the requested documents.

6. 16 September: Yaspa confirms receipt of additional information, describes an internal risk review and issues its final response.

The final letter, shown in Dutch, states that no transaction was processed nor were funds retained from the sender, so Yaspa treated the submission as a risk report about a third-party merchant rather than a consumer claim. Yaspa declined to disclose internal findings, the merchant's contractual status or the actions taken, citing confidentiality and data protection.

“Yaspa’s contractual and business relationship is with the merchant directly, rather than individual end users.” — Yaspa response on 9 September.

What remains unanswered and why the merchant's identity matters

The correspondence confirms the complainant explicitly asked that the communication not be treated as a financial dispute aimed at compensation or mediation; reclassifying it as a risk report is therefore consistent with part of that request. However, the reclassification and closing of the public exchange do not prove that Yaspa did not carry out internal measures. The final letter mentions that evidence was recorded and that an internal investigation was under way, but it provides no results.

The request to identify the complainant raises a procedural question: what additional information would have allowed Yaspa to share more details about the merchant? The thread does not make clear whether the identity verification was completed after the 14 September reminder.

Technical infrastructure and regulatory limits in the reported route

Yaspa's privacy notice naming Yapily Connect supports the technical architecture described by the source, but does not prove that that provider participated in this specific attempt. The iGaming software provider SOFTSWISS lists Yaspa among its partners for the Bank Transfer modality and clarifies that its role is to integrate providers, not to process payments directly. That detail suggests the reported route could have occurred through a SOFTSWISS integration.

Separately, the existence of a bank payment option does not equal permission to operate in a specific market. The Dutch regulator requires that the relevant online gaming offer hold a Dutch Koa licence. The reviewed documentation does not establish Dutch authorisation for the reported domain.

External clues and limits of the technical evidence

Similarweb screenshots supplied for August 2026 show that bet20play.com accounted for 8.87% of traffic referred to yaspa.com in a global view. Another view of bet20play.com lists banks.yaspa.com as 41.94% of outgoing traffic and 20bet.com as 39.07% of incoming traffic. Those percentages are leads for further route testing; they do not trace individual users through Yaspa, do not identify merchant contracts or measure completed payments, and should not be interpreted as Yaspa customer shares or revenues.

Outstanding questions

The documentation signed by the parties raises concrete questions: which entity contracted with Yaspa in that attempt, how was Fortunella Entertainment Limited linked to the visible operator ALEYNA LIMITADA, and what checks did Yaspa apply to the casino domain and the alleged targeting of Dutch customers. Yaspa's public positions on the direct contractual relationship and its invocation of confidentiality are part of the official reply, but they do not resolve the material doubts evident in the file.

If you hold contracts, onboarding requirements, correspondence or first-hand information about beneficiary verification and technical integration of merchants in casino payment routes, share documents confidentially with FinTelegram. You can also consult related pieces on payment solutions and the regulation applicable to European markets in our B2B reports.