An in-depth review of BetAlice’s deposit infrastructure indicates the use of a multi-layered offshore payment configuration. Although certain BetAlice domains have been subject to Italian blackout measures, alternative domains remain reachable. During testing, no clear operator disclosure was identified.

The payment flow reveals a familiar structure: ChainValley positioned behind cashier-branded options (including Skrill, Rapid, and NETELLER labels), alongside a bank-transfer channel routed through api.payment-gateway.io → checkout.puretransfer.io → pay.clx.acq.mellifera.tech, where Paradis Tech Ltd appears as the payee. The flow references Yapily-labeled methods and Wise Open Banking endpoints.

Executive Summary of Observations

• No transparent operator identity was visible on the reviewed domains (www.betalice.com, betalice-1110.com), despite onboarding users from multiple EU Member States and the UK.
• Italian access restrictions appear partial, as alternative domains remain operational.
• BetAlice offers conventional deposit methods (cards, bank transfers, PaysafeCard, crypto), consistent with offshore retail-facing casino setups.
• ChainValley (Poland) appears linked to cashier options labeled PaysafeCard, Skrill, Rapid, and NTLR.
• In December 2025, UTRG UAB dba utPay (Lithuania) reportedly remained visible in parts of the payment chain, indicating a potential transition phase.
• The bank-transfer route involves layered open-banking orchestration:
• API endpoint (api.payment-gateway.io)
• Checkout layer (checkout.puretransfer.io)
• Acquiring/open-banking interface (mellifera.tech)
• Wise Open Banking infrastructure
• Paradis Tech Ltd is displayed as settlement beneficiary.
• The Mellifera interface references Mellifera Kartiera Limited (Malta) and links to kartiera.eu, where EMI regulation by the MFSA is claimed.
• Yapily appears as a labeled method within the Mellifera flow, though its exact operational role requires verification.

Regulatory and Compliance Considerations

1. Merchant Status as the Primary Risk Factor

Any compliance review must begin with the gambling operator itself.

Testing suggests BetAlice remained accessible to users in regulated European markets without visible operator disclosure. The combination of:

• cross-border onboarding,
• domain rotation,
• partial jurisdictional blocking,
• absence of transparent licensing disclosure,

creates a risk profile that may extend beyond the merchant to the associated payment chain.

Payment intermediaries that facilitate deposits for potentially unlicensed gambling operations may face exposure under:

• AML/CFT requirements,
• gambling regulation enforcement,
• payment scheme rules,
• cross-border consumer protection laws.

During review of the Skrill “Rapid Transfer” channel, Novaforge appeared as the payment recipient, supporting the conclusion that Novaforge is connected to BetAlice’s operational control.

2. ChainValley’s Role and utPay Transition Indicators

The observed presence of ChainValley behind multiple cashier labels aligns with a recurring offshore-casino gateway model.

Consumer-facing labels (e.g., PaysafeCard or Skrill) may suggest direct integration with well-known providers, while actual routing appears handled by an intermediary gateway operator.

Following the suspension context of UTRG UAB dba utPay (Lithuania), ChainValley appears to have assumed a similar deposit-routing function. The continued appearance of utPay in December 2025 supports the possibility of phased migration or temporary dual routing rather than an immediate operational replacement.

3. Open-Banking Structure: Multi-Layer Routing

The documented bank-transfer channel demonstrates structured layering:

Such configurations are not inherently improper. However, when linked to offshore gambling activity targeting regulated jurisdictions, layered routing raises questions about:

• Merchant onboarding procedures,
• Geographical access controls,
• AML monitoring responsibility,
• Merchant-of-record designation,
• Regulatory reporting obligations.

Fragmented service architecture can create divided accountability unless clear compliance controls are in place at each stage.

4. Mellifera Kartiera Limited (Malta)

The Mellifera gateway pop-up identifies Mellifera Kartiera Limited (Malta) and references claimed MFSA EMI authorization effective 20 November 2024 (as disclosed in gateway materials).

If confirmed, this introduces two significant considerations:

1. A regulated EMI-linked interface appearing in a deposit flow associated with cross-border gambling.
2. The presence of regulated entity documentation potentially enhancing user trust, despite ambiguity surrounding the gambling operator’s licensing in target markets.

Clarification is required regarding Mellifera’s operational role:

• Direct regulated service provider to the merchant?
• Technical payment gateway only?
• Outsourced acquiring facilitator?
• White-label integration with legacy Yapily labeling?

5. Yapily, Wise, and Paradis Tech Ltd — Functional Clarification Needed

The flow references a Yapily-labeled payment method and Wise Open Banking API endpoints, while Paradis Tech Ltd is displayed as payee.

Key verification questions include:

• Whether Yapily is actively servicing this merchant chain or appears solely as a method label.
• Whether Wise Open Banking access occurs via a licensed intermediary and under what merchant-category constraints.
• Whether Paradis Tech Ltd acts as:
• Merchant of record,
• Collection agent,
• Settlement intermediary,
• Separate processor.

Public information presents Paradis Tech as a payment-solutions provider offering merchant acceptance and fraud-prevention tools. Although gambling services are not explicitly marketed, the entity’s role as settlement beneficiary in Wise-linked transactions indicates participation in funds collection and routing.

If such routing relates to unlicensed gambling operations, potential concerns include:

• Merchant transparency deficiencies,
• Regulatory perimeter breaches,
• AML/CFT reporting risks,
• Scheme compliance exposure.

Consolidated Compliance Mapping

Overall Assessment

The BetAlice structure illustrates how offshore casino operations can combine:

1. A retail-facing gambling interface,
2. Recognizable cashier branding,
3. Gateway abstraction layers,
4. Regulated-facing open-banking interfaces,
5. Banking API infrastructure,
6. Separate settlement entities.

When merchant transparency is limited and jurisdictional licensing remains unclear, each payment layer becomes a potential regulatory transmission point.

The recurring architectural pattern observed here should be documented for further transaction-level testing, provider clarification, and right-of-reply outreach within the Scam-Or Project monitoring framework.