Rail Atlas: Revolut, Open Banking, and the Casino Payment Machine — Mapping the Rails Behind Offshore iGaming
FinTelegram’s Rail Atlas analysis have repeatedly observed Revolut’s Open Banking endpoint inside layered offshore casino payment flows. The pattern appears to combine anonymous gateways, open-banking intermediaries, and Revolut’s own customer-side payment infrastructure. This does not prove knowing facilitation by Revolut — but it raises serious questions about monitoring, merchant transparency, and whether casino-related flows have become a hidden growth vector inside one of Europe’s fastest-growing fintech platforms.
Key Findings
Revolut appears repeatedly in observed casino payment paths. FinTelegram has reviewed multiple offshore casino rails where deposits route toward oba.revolut.com, often through intermediary open-banking layers.
The rail structure is layered by design. Typical pattern: casino site → anonymous gateway → open-banking provider → bank/open-banking API.
Contiant traffic is a red flag. The uploaded SimilarWeb screenshots show Contiant traffic heavily concentrated in the Netherlands, with casino domains among top referrals and oba.revolut.com among top outgoing destinations.
Revolut itself recognises gambling-payment risk. Revolut states that some European countries require it to block payments to and from illegal gambling providers, and that it enforces regulator lists where applicable.
Revolut Business terms prohibit gambling activity. Revolut’s UK Business Terms list “binary options or gambling” among prohibited business activities.
Annual accounts do not disclose iGaming exposure directly. Revolut’s 2025 annual report shows explosive growth in customers, transaction volume, payments revenue, payment acceptance, and Revolut Business — but no specific casino/iGaming segmentation.
Financial-crime risk is acknowledged. Revolut’s 2025 report states that its systems analysed over 10 billion transactions and that more than one-third of its workforce works in Financial Crime Prevention.
Rail Map: The Observed Casino Payment Flow
FinTelegram’s working model is as follows:
Player → Offshore casino → anonymous payment gateway → open-banking intermediary → Revolut Open Banking endpoint → player’s Revolut account
Observed or reported rail elements include:
LayerExamplesCompliance relevanceCasino front-endSkyhills, Epicbet, Wizebets, Spacehills and others shown in traffic referralsUnlicensed/offshore iGaming exposureFirst-hop gatewaysecurepayins.com, urbenics, casino-branded gateway pagesMerchant opacity / transaction laundering riskOpen-banking layerContiant, Yapily Connect, Perspecteev, SaltEdgePayment initiation / routing layerBank/API endpointoba.revolut.comRevolut-side account/payment infrastructure
The key compliance issue is not simply that a Revolut customer may gamble. The issue is whether repeated, structured, high-volume flows through Revolut-linked open-banking infrastructure indicate a recognisable casino payment corridor that should trigger enhanced monitoring, blocking, reporting, or regulatory review.
Revolut’s Role in the Observed Rails
Revolut’s Open Banking API is described by Revolut as the gateway for third-party providers to interact with Revolut customers and products, including account information and payment initiation.
This matters because the observed casino rails do not always appear as simple card payments to a gambling merchant. Instead, the flows appear to use open-banking payment initiation and intermediate gateway domains. That structure can make merchant identification harder and can blur whether the transaction is seen as gambling, generic account-to-account transfer, gateway payment, or customer-authorised payment.
Revolut cannot be accused, on the basis of this evidence alone, of knowingly facilitating illegal gambling. But the repeated appearance of oba.revolut.com in offshore casino rail analysis creates a serious compliance question: does Revolut’s monitoring framework identify the upstream casino context when payments arrive through third-party open-banking layers?
The Open Banking Layer: Contiant, Yapily, Perspecteev, SaltEdge
Similarweb statistics on Contiant
Contiant is a Bulgarian open banking infrastructure provide. Contiant SimilarWeb screenshots show a highly concentrated traffic profile.
In March 2026, Contiant traffic was reportedly 93.21% Netherlands, with Germany, Norway, the UK, and France far behind. The referral screenshot shows casino domains as top referrers, including skyhills.com, epicbet.com, wizebets.com, and spacehills.com. The outgoing-traffic screenshot shows bank destinations including KBC, Rabobank, ING, SNS Bank, and oba.revolut.com.
This is not proof of illegality by Contiant or Revolut. It is, however, a strong traffic-intelligence indicator that Contiant functions as a casino-facing open-banking routing layer, with Revolut among the destination banks offered to players.
Read our Contiant reports here.
Traffic Intelligence: What the SimilarWeb Data Suggests
FinTelegram’s working interpretation:
ObservationInterpretationConfidenceContiant referrals dominated by casino domainsContiant appears materially exposed to casino payment trafficCorroborated by screenshotNetherlands accounts for over 93% of Contiant trafficDutch player market appears central to this railCorroborated by screenshotoba.revolut.com appears among top outgoing linksRevolut Open Banking is part of the downstream railCorroborated by screenshotSimilarWeb reportedly shows over 1.1m visits to oba.revolut.com in March 2026Revolut Open Banking has significant traffic scaleFinTelegram-held traffic dataAnonymous first-hop gateways appear before open-banking providersLayering may obscure merchant contextWorking hypothesis
Traffic analytics should be treated as intelligence, not final evidence. They show directionality, referrals, and routing patterns — not necessarily contractual relationships, settlement flows, or regulatory responsibility.
Financial Statement Angle: Can iGaming Exposure Be Seen in Revolut’s Accounts?
Directly: no. Indirectly: possibly.
Revolut’s 2025 annual report does not disclose gambling, iGaming, casino, MCC 7995, or high-risk merchant exposure as a standalone segment. However, the report contains several data points relevant to the Rail Atlas hypothesis:
Retail customers rose to 68.3 million, and retail transaction volume reached £986 billion in 2025.
Business customers reached 767,000, and business transaction volume reached £277 billion.
Revenue increased to £4.5 billion, with card payments the largest revenue stream at 22.2% of total revenue.
Revolut Business accounted for 16% of total income, while payment acceptance volumes increased 228% year-on-year.
Revolut states that financial crime risk includes the risk that its products and services are used to facilitate illegal activity, and that failures may lead to enforcement action, fines, restrictions, or reputational damage.
The financial statements therefore do not prove iGaming dependence. But they do show a company whose growth is heavily driven by transaction volume, payment acceptance, business accounts, open banking, and high-frequency customer usage. If offshore casino flows are material, they would likely be buried inside broader payment, account-to-account, card, or business-payment categories.
Regulatory Context
Revolut’s own help pages acknowledge that some European countries require it to block transactions to and from illegal gambling providers, and that regulators publish licensed or unlicensed gambling-provider lists which Revolut enforces where applicable.
This is critical. Revolut is not blind to the category. It recognises that illegal gambling payments are a regulated payment-risk domain. The compliance challenge is whether open-banking layering allows casino payments to bypass conventional merchant-category detection.
Norway is especially relevant. Public reporting and legal materials describe Norway’s payment transaction ban as requiring banks and financial institutions to block payments connected with unlicensed gambling operators. FinTelegram has separately reported on the alleged use of Revolut as an “entry wallet” in Norwegian offshore gambling flows.
Compliance Assessment
FinTelegram’s initial assessment is that Revolut should be expected to monitor at least five risk layers:
Known casino domains feeding open-banking intermediaries.
Repeated customer deposits to offshore casino-linked gateways.
Open-banking payment initiation patterns involving high-risk gateway domains.
Geographic concentration in regulated or restricted gambling markets, including the Netherlands and Norway.
Mismatch between apparent merchant/gateway descriptors and underlying gambling activity.
The core issue is not only MCC 7995. Open banking may not always present the same clean merchant-category indicators as card acquiring. That is precisely why layered rails create a compliance blind spot.
Evidence & Confidence Table
Entity / Rail ElementObserved RoleEvidence TypeJurisdictionConfidence GradeRevolut / oba.revolut.comDownstream open-banking endpointTraffic analysis, rail observationsUK / EEACorroboratedContiantOpen-banking intermediarySimilarWeb screenshotsBulgaria / Netherlands-facing trafficCorroboratedYapily ConnectOpen-banking layerFinTelegram rail observationsUK / EEACorroboratedPerspecteev / SaltEdgeOpen-banking / data layerFinTelegram rail observationsFR / EEACorroboratedsecurepayins.comAnonymous gatewayFinTelegram observationsUnknownCorroboratedurbenicsAnonymous gatewayFinTelegram observationsUnknownCorroboratedOffshore casino brandsOriginating merchantsCasino-site payment testing / traffic dataOffshoreCorroborated
Open Questions to Revolut
Does Revolut monitor oba.revolut.com traffic for upstream casino or gambling-originated payment flows?
Does Revolut classify payments initiated through Contiant, Yapily, Perspecteev, or SaltEdge differently from direct card gambling payments?
Does Revolut maintain a list of casino-linked gateway domains such as securepayins.com or urbenics?
How does Revolut determine whether an open-banking payment is connected to an illegal gambling operator?
Has Revolut identified Contiant as a high-risk open-banking traffic source?
How many Revolut customer accounts were restricted or closed in 2025 for gambling-related or casino-payment activity?
Does Revolut report suspicious casino-related payment patterns to FIUs or gambling regulators?
Does Revolut’s financial-crime monitoring include merchant-domain intelligence and referral-chain analysis?
Has Revolut received inquiries from Norwegian, Dutch, UK, Lithuanian, or other EU regulators about offshore gambling payment flows?
Does Revolut consider casino-related open-banking traffic a material compliance risk?
Conclusion
This initial Rail Atlas report does not allege that Revolut knowingly enables illegal gambling. It establishes a more precise and regulator-relevant point: Revolut’s Open Banking infrastructure appears repeatedly in observed offshore casino payment paths, often after multiple layers of anonymous gateways and open-banking intermediaries.
That pattern deserves scrutiny. Revolut’s own public materials show that it recognises gambling-payment restrictions and invests heavily in financial-crime prevention. Yet the observed rails suggest that open-banking structures may create a new form of transaction-laundering risk: not by hiding money entirely, but by hiding the commercial context of the payment.
The next Rail Atlas installments should focus on the individual rail components — Contiant, Yapily Connect, Perspecteev/SaltEdge, securepayins.com, urbenics, and the casino brands feeding those rails.
Whistle42 Call
FinTelegram invites Revolut insiders, open-banking providers, casino payment agents, compliance officers, payment processors, affected players, and whistleblowers to submit confidential information through the Whistle42 platform. We are especially interested in payment descriptors, gateway contracts, merchant onboarding files, compliance alerts, blocked-payment records, and internal risk assessments relating to offshore casino flows.
Share Information via Whistle42
Read More