FinTelegram’s latest compliance analysis flags Contiant Ltd (Bulgaria) as a technical service provider sitting in front of Yapily Connect UAB’s PSD2 rails, enabling pay-by-bank deposits for offshore casino brands apparently offered into restricted/unauthorized markets—notably the Netherlands (based on traffic signals).
Read the Contiant Compliance Report here.
Risk Signal
The key risk isn’t a single casino domain. It’s the stack: casino checkout → paywith.contiant.com → Yapily consent/authorization flow (including “Powered by Yapily” UI) → bank approval (e.g., Revolut user journeys referenced in the report). This structure can create plausible distance between the licensed rail provider and the gambling merchant—while the regulated rails still settle the underlying transaction.
FinTelegram also notes traffic intelligence suggesting casino-only referral traffic into Contiant’s payment subdomain and a strong NL concentration, which—if sustained—should trigger enhanced partner due diligence and transaction-monitoring escalations at multiple points in the chain.
Mini Rail Map (Observed Dec 16, UTC)
- Brand/domains: Contiant —
www.contiant.com,paywith.contiant.com(Confirmed) - Payment options: Pay-by-bank / Open Banking (PIS); bank authorization flows incl. Revolut journeys (Confirmed/Indicated)
- Named rails: Contiant (TSP) (Confirmed); Yapily Connect UAB (PISP) (Confirmed); Revolut open-banking touchpoint (Indicated)
- Risk signals: licensing/market mismatch; proxy layering; casino-only traffic profile; NL targeting signal (Indicated)
Monitoring cues:” [redirect host patterns / ‘Powered by Yapily’ consent screen / paywith.contiant.com referrals / descriptor samples requested]
Call for Information
Are you at Contiant, Yapily, Revolut, or an affected bank/PSP? Share due-diligence files, partner contracts, consent-screen evidence, and descriptor samples via Whistle42.
We publish evidence-led compliance intelligence on the payment rails behind illegal gambling.
