Plenty of players assume that when they tap a card into a mobile casino, the full 16-digit number ends up sitting somewhere on the handset. On Casushi that is not how it works. The platform uses tokenisation for card payments, which means the actual card number is never stored on your device. The number you type is swapped for a substitute token, and that token is what moves through the payment chain. It is a small technical detail with large practical consequences, and it is worth understanding before you fund an account from a phone.
How tokenisation changes what sits on your phone
Tokenisation replaces sensitive card data with a unique reference that is useless to anyone who intercepts it. When you enter card details at the Casushi app cashier, the raw number is passed through a secure channel to the payment processor and exchanged for a token. That token is tied to your account and to a specific merchant, so it cannot be reused elsewhere. If someone lifted it from your handset, it would not work at another casino, a shop, or an ATM.
The practical effect is that losing your phone is a different kind of problem than losing a wallet. A thief who gets past your lock screen finds a token, not a card number. There is nothing to photograph, nothing to copy down, and nothing to key into a fraudulent transaction. This is the core of the security model, and it is the part most players never hear about because it happens silently in the background.
Apple users download the Casushi app from the App Store, and the tokenisation layer sits underneath the interface rather than in it. You will not see a token, a reference code, or any indication that the swap has happened. The cashier simply confirms the deposit. The same principle applies to withdrawals: payouts route back through the same tokenised link, so the full card details never need to be re-entered on the device.
What this means across iPhone and Android
Face ID, Apple Pay and the iOS side
On iPhone and iPad, the Casushi app supports Face ID logins, which adds a second layer on top of tokenisation. The card number is never stored on the device, and access to the account is gated behind a biometric check that is difficult to spoof. The combination matters: even if someone had your phone unlocked, they would still need your face to reach the cashier. The Casushi iPhone experience is built around this pairing of biometric access and tokenised payments.
The iOS build also works with Apple Pay, which uses its own device account number rather than your real card details. That means two separate tokenisation systems can be in play at once, one from Apple and one from the payment processor. Neither stores your card number on the handset. For players who already use Apple Pay for everyday shopping, the behaviour at the cashier will feel familiar and the security model will be consistent with what they trust elsewhere.
Android users access the Casushi site through a mobile browser rather than a native download. Casushi does not publish a standalone Android APK file, so there is no sideloaded package to verify or trust. That removes one of the classic mobile risks, since third-party APK files are a common route for malware. https://casushi-online.uk/app/ offers additional context worth reviewing. Opening the responsive site in Chrome keeps you inside the browser’s sandbox and its update cycle. The responsive layout detects screen dimensions automatically, so the cashier, lobby and account pages resize to fit whatever handset you are holding.
Some players add a home screen shortcut so the site opens like an app. This is a bookmark, not an installed program, and it does not change the tokenisation model. The card number still never lands in local storage. Push notifications, where enabled, are handled by the browser rather than by a native app, which keeps the permission model transparent.
It is worth being precise about what the Casushi casino app does and does not do. The mobile lobby includes the welcome offer, the cashier manages payments, and the Casushi mobile site offers responsible play tools such as deposit limits and session reminders. None of these features require your card number to be held on the device. The security claim is narrow and specific: the card number is tokenised at the point of entry and never stored locally.
One caveat belongs here. Tokenisation protects the card number, not your account password. If your phone is lost, you should still change your login credentials and contact support. The tokenised payment link is one layer of defence, and the Casushi app cashier manages payments in a way that keeps the sensitive data off the handset, but good account hygiene still matters. Enable biometric login where available, keep your device passcode strong, and review your deposit history if anything looks unfamiliar.
For clarity on who is saying what: this website operates as an information page only. It does not process payments, hold accounts, or store card data. The tokenisation happens inside Casushi’s payment flow, and the App Store listing for the iOS app is the authoritative source for what the software does on Apple hardware. If you want to verify the security model yourself, read the cashier’s payment terms and the processor’s documentation rather than relying on forum posts.
The practical takeaway is simple. Fund your Casushi account from your phone with the same confidence you would use for any tokenised payment, keep biometric login switched on, and treat your device passcode as the real front door. If the phone goes missing, change your password, review recent deposits, and let the tokenisation layer do the job it was designed for. Your card number was never on the handset to begin with.