Contiant Update: Benelux “Pay-by-Bank” Focus Sharpens the Yapily Casino Stack

Charlene Lensburg
Mon, 19 Jan 2026 13:29:58 +0000
Compliance, Rail Atlas Cases, Contiant, Igloo Ventures, Open Banking, PIS, PISP Rail, Skyhills, Technical Service Provider, TSP, yapily

In December 2025, FinTelegram flagged Contiant Ltd (Bulgaria) as a “technical” open-banking layer sitting in front of Yapily‘s PSD2 rails, enabling pay-by-bank deposits for offshore casino brands apparently offered into restricted markets. New traffic intelligence now points to a strong Benelux banking footprint—and to SkyHills as a dominant feeder into Contiant’s payment gateway.

Key Points

Contiant (www.contiant.com) is positioned as a technical service provider (TSP) that relies on third-party regulated rails (most notably Yapily) to execute payment initiation.

Updated Similarweb signals (Dec 2025) indicate heavy Netherlands concentration for traffic to paywith.contiant.com and outgoing link destinations dominated by Belgian/Dutch banks, plus Revolut’s open-banking touchpoint (oba.revolut.com).

Referral traffic into paywith.contiant.com appears casino-heavy, with SkyHills the largest observed referrer in the new dataset (Dec 2025).

SkyHills discloses it is operated by Igloo Ventures SRL (Costa Rica) (per its “About us”/policy pages).

Contiant markets “Open Banking” payments with typical “card alternative” positioning (e.g., instant payments / no chargebacks), which can be attractive for high-risk merchants.

Risk Signal

The key risk still isn’t a single casino domain. It’s the stack: casino checkout → paywith.contiant.com → Yapily consent/authorization flow (including “Powered by Yapily” UI, per prior observations) → bank approval. This architecture can create plausible distance between the licensed rail provider and the underlying gambling merchant—while regulated rails still settle the transaction.

Go to the Contiant Compliance Profile on RatEx42.

What changed with the new data: the gateway’s footprint looks less “generic EU open banking” and more “Benelux-banking-centric.”

In the new Similarweb snapshots (Dec 2025), the Netherlands dominates traffic share, and the top outgoing link destinations concentrate around KBC (Belgium) and major Dutch retail banks, with Revolut OBA also among the top destinations. That combination is a meaningful partner-risk and geo-risk escalation trigger: it suggests a repeatable consumer journey tied to specific banking rails rather than a diffuse pan-EU pattern.

Mini Rail Map (Update: Dec 2025, traffic intelligence)

Brand/domains: Contiant — contiant.com, paywith.contiant.com (Observed)

Payment options: Pay-by-Bank / Open Banking (PIS) (Observed)

Named rails: Contiant (TSP layer) → Yapily (licensed PISP rail, per FinTelegram’s prior reporting) → bank authorization flows incl. Revolut OBA touchpoint (Observed/Indicated)

New indicators: Benelux bank destinations + casino-heavy referral profile (Indicated)

What the New Similarweb Signals Imply (and what they don’t)

1. Benelux concentration is operationally informative. If a payment gateway’s top link destinations are concentrated in Belgium/Netherlands banks (plus Revolut’s OBA domain), it often means the checkout is optimized for those banks’ authorization journeys—suggesting a deliberate “where players bank” targeting logic, not incidental traffic.

2. SkyHills as a dominant feeder tightens the merchant attribution problem. The new dataset shows SkyHills driving the majority share of observed referral traffic into paywith.contiant.com. SkyHills publicly discloses Igloo Ventures SRL (Costa Rica) as its operator.

This does not prove illegal activity by any specific bank or rail provider.

But it does sharpen the due-diligence question: what KYB, merchant classification, geo-blocking, and prohibited-use controls exist at the Contiant Yapily boundary for gambling merchants and their traffic sources?

3. Group usage claims require documentary confirmation. The broader claim that the same Contiant gateway supports additional offshore casino brands and entities (e.g., Curaçao/Costa Rica-linked operators) is plausible given the recurring gateway pattern and public operator disclosures in the casino ecosystem, but must be evidenced with primary artifacts (checkout screenshots, redirect logs, merchant IDs, T&Cs naming the contracting party, settlement descriptors).

Read our new compliance report on Yapily here.

Call for Information (Whistle42)

Are you at Contiant, Yapily, Revolut, a Benelux bank, a PSP, or a gambling compliance function? We are looking for primary evidence: partner contracts, KYB files, merchant onboarding communications, consent screens (“Powered by Yapily”), redirect host logs, payee/IBAN mapping, and transaction descriptors (PII redacted). Submit securely via Whistle42.com.