Yaspa Merchant Question: Who Contracted with the Casino Route in September 2026?
Whistleblower report raised which company was Yaspa’s merchant and how the beneficiary was assessed.
Key Takeaways
- A whistleblower reported a failed €50 deposit to luckygans.com on 8 September 2026; Yaspa said the payment was not authorised or completed.
- Yaspa Limited is an FCA-regulated payment institution (FRN 826720) and told the reporter on 9 September that its contractual relationship is with the merchant directly.
- The whistleblower’s supplied flow showed ALEYNA LIMITADA as website operator and Fortunella Entertainment Limited as the displayed beneficiary with a Cyprus IBAN.
- Yaspa classified the submission as a third-party merchant risk report, cited confidentiality and declined to disclose its internal findings on 16 September 2026.
- Similarweb screenshots (August 2026) provided traffic clues but do not identify contractual merchants or completed payments.
Yaspa confirmed on 9 September 2026 that its contractual relationship is with “the merchant directly” after a whistleblower reported a failed €50 casino deposit attempt from the Netherlands on 8 September 2026. The correspondence reviewed by FinTelegram records that Yaspa described itself as an FCA-regulated payment institution and said it does not hold end-user funds while also declining to disclose its internal merchant-review findings.
What the whistleblower reported about the Yaspa merchant route
The whistleblower supplied an account of a deposit journey initiated from the Netherlands on 8 September 2026 at about 18:10 CEST. The source records that no payment was authorised or completed. Details preserved in the supplied correspondence are:
Casino website: luckygans.com/nl/
Stated website operator: ALEYNA LIMITADA, Costa Rica
Payment interface: banks.yaspa.com, displaying “luckygans” and Dutch bank options
Bank handoff: SNS Bank, identifying Yapily Connect
Displayed beneficiary: Fortunella Entertainment Limited, with a Cyprus IBAN
Those items come from the whistleblower’s submission and the email thread; the recording referenced in the correspondence was not included in the eight-page PDF FinTelegram reviewed.
Yaspa’s public profile and regulatory status
Yaspa Limited is incorporated in England and Wales (company number 09902175) and lists James Neville as co-founder and CEO. Companies House lists James Adam Neville as the sole active person with significant control, with more than 25% and no more than 50% of shares and voting rights. Yaspa presents itself as an FCA-regulated payment institution (FCA firm reference number 826720) and markets open-banking payments and verification services to sectors that include iGaming, land-based gambling, lotteries, trading, eCommerce and point-of-sale.
Yaspa’s consumer privacy notice identifies Yapily Connect as the partner supplying European account-information and payment-initiation services. SOFTSWISS, an iGaming software provider, publicly lists Yaspa as a Bank Transfer payment partner and describes its role as integrating providers rather than directly processing payments.
The merchant question and Yaspa’s response
The core question arising from the correspondence is explicit: which legal entity contracted with Yaspa as the merchant, and how was the link between the website operator (ALEYNA LIMITADA) and the displayed beneficiary (Fortunella Entertainment Limited) established and assessed? Yaspa’s most significant recorded statement appears in its 9 September reply: “Yaspa’s contractual and business relationship is with the merchant directly, rather than individual end users.” Yaspa also said it operates as a technical software provider and does not hold end-user funds.
The whistleblower asked Yaspa to investigate the relationships between LuckyGans, ALEYNA LIMITADA and Fortunella, the onboarding classification applied, whether gambling activity and Dutch targeting were disclosed, and whether the payment route should remain available.
Timeline of the correspondence and what Yaspa did publicly
The supplied PDF documents correspondence from 8–16 September 2026. Key points in the thread are:
8 September — Yaspa technical support acknowledges the report.
9 September — Yaspa confirms a direct merchant relationship, invokes confidentiality and recommends contacting the merchant about its operations.
9–10 September — the source escalates concerns and supplies or references a recording.
11 September — Yaspa requests photo identification and recent proof of address to verify the complainant’s identity.
14 September — Yaspa says the requested documents have not been received.
16 September — Yaspa acknowledges information and evidence, describes an internal risk review and issues its final correspondence.
Yaspa’s final response, shown in Dutch in the thread, states no transaction was processed and no account or funds were held for the whistleblower. Yaspa therefore classified the submission as a third-party merchant risk report rather than a consumer complaint and declined to disclose internal findings, merchant-status information or actions on grounds of confidentiality and data protection.
Why the merchant identity matters for payments and compliance
A mismatch between the site operator listed on a gambling website and the beneficiary shown in the bank flow raises typical compliance questions: who is contractually responsible for the payments; which entity was the licensed merchant on file with the payment provider; and what customer- and market-level checks were performed during onboarding? The supplied materials do not identify which company Yaspa meant by “the merchant,” nor do they disclose the outcome of the internal review. The documents also do not show completed settlement or a demonstrable compliance breach.
The whistleblower explicitly asked Yaspa not to treat the submission as an ordinary financial dispute seeking compensation. Reclassifying the file as a risk report therefore aligned with part of the complainant’s request. The final letter’s statement that evidence was recorded and an internal investigation was underway does not disclose the investigator’s findings.
Traffic signals, architecture and the Dutch-authorisation point
FinTelegram reviewed supplied Similarweb screenshots (August 2026, worldwide) showing bet20play.com accounting for 8.87% of displayed referral traffic for yaspa.com; a bet20play.com view listed banks.yaspa.com at 41.94% of outgoing traffic and 20bet.com at 39.07% of incoming referral traffic. Those estimates provide leads for route testing but do not trace individual users, identify contractual merchants or measure completed payments.
The consumer privacy notice and the Yapily Connect link support the architecture the whistleblower described but do not independently verify that particular attempt. SOFTSWISS’s public partner listing suggests the reported LuckyGans journey may have used a SOFTSWISS integration. The Dutch regulator, De Kansspelautoriteit, requires a Dutch KOA licence for relevant online gambling offerings; the presence of a bank payment option does not itself confer local authorisation.
Outstanding questions and call for information
The correspondence leaves three concrete questions unanswered: which legal entity contracted with Yaspa as the merchant; how was Fortunella Entertainment Limited linked to the website operator ALEYNA LIMITADA; and what checks were applied to the casino domain and the Dutch customer market? Yaspa’s statement that an internal review was underway and its refusal to disclose findings on confidentiality grounds are part of the record but do not resolve these questions.
If you hold first-hand documents — merchant contracts, onboarding checklists, internal risk findings or recorded payment journeys — FinTelegram requests confidential submission through Whistle42. Industry readers may find additional context on payments integrations in our payments and regulatory coverage in regulation.
“Yaspa’s contractual and business relationship is with the merchant directly, rather than individual end users.” — Yaspa, 9 September 2026
“No transaction had been processed and no account or funds were held for the source.” — Yaspa final correspondence, 16 September 2026
Frequently Asked Questions
What did Yaspa say about who its contractual partner was?
Yaspa stated on 9 September 2026 that its contractual and business relationship is with the merchant directly. The company also said it operates as a technical software provider and does not hold end-user funds.
Did the reported €50 deposit complete through Yaspa?
No transaction was authorised or completed in the reported attempt on 8 September 2026. Yaspa’s final correspondence on 16 September 2026 notes no transaction had been processed and no account or funds were held for the complainant.
Which entities appeared in the whistleblower’s payment flow?
The whistleblower’s record lists ALEYNA LIMITADA (Costa Rica) as the stated website operator and Fortunella Entertainment Limited with a Cyprus IBAN as the displayed beneficiary, while the payment interface showed banks.yaspa.com and a bank handoff identifying Yapily Connect and SNS Bank.
Did Yaspa disclose the outcome of its internal review?
Yaspa declined to disclose internal findings, merchant-status information or actions on grounds of confidentiality and data protection in its 16 September 2026 reply, while stating evidence had been recorded and an internal investigation was underway.
Does a bank payment option prove Dutch gambling authorisation?
No. The presence of a bank payment option does not itself establish permission to offer gambling in the Netherlands; the Dutch regulator requires the relevant online offering to hold a Dutch KOA licence.
Tags
About the author
Priya Nair
Payments Correspondent
Priya Nair covers payments and fintech in the gambling industry — processor and PSP deals, payment-method launches, crypto rails, and the compliance shifts that decide what players can actually use at the cashier. The stories lead with the deal or launch, name the companies and methods precisely, and translate the jargon into what operators and players gain or lose. From open-banking pilots to stablecoin settlement and chargeback rules, Priya Nair follows the money the industry runs on.
More from Priya Nair
