What The Casino And The Payment Processor See With Revolut Payments
When you pay a casino using Revolut, the casino and its payment processor see the data needed to accept and reconcile the deposit: the amount, currency, time, payment status, and an internal transaction reference. If you pay by card, the casino typically receives card scheme data such as the card type (debit/credit), issuing country, and a masked PAN (for example, only the last 4 digits), plus basic risk signals like 3‑D Secure authentication results. Your full card number and CVV never reach the casino; those stay with the card network and the payment processor. If you pay by bank transfer, the casino generally sees the sender name, IBAN (or local account details), bank identifiers, and the payment reference text.
Revolut, as the payment institution, sees the full funding chain: your verified identity (KYC profile), your Revolut account details, the exact merchant name or descriptor, and the destination account or acquiring setup used by the casino. For privacy, Revolut can reduce what the casino sees compared with a direct bank transfer because the casino does not get your full Revolut profile, your address, or your ID documents from the payment itself. The main privacy leak remains the payment rail: bank transfers usually expose your name and account details to the casino, while card payments expose less personal data but still link the deposit to you through the acquirer’s records and chargeback rights. In practice, Revolut hides some fields from the casino, but it does not make the deposit anonymous because both Revolut and the casino keep transaction logs tied to your identity.