Cake Wallet Web: Why Singapore’s Payment Services Act Explicitly Bans Browser Wallet Registration

Singapore’s Payment Services Act (PSA) enforces a clear technical distinction that most global users never encounter: a wallet accessed through a web browser is subject to regulatory requirements that a native mobile or desktop application is not. This distinction has profound consequences for Asian users who may assume that Cake Wallet Web, accessed through any browser, operates under the same licensing exemptions that apply to the downloadable versions. In reality, the PSA treats browser-based wallet interfaces as service providers requiring registration with the Monetary Authority of Singapore (MAS), while self-custody wallets installed as native applications remain largely outside this scope.

The regulatory asymmetry reflects a deliberate policy choice: Singapore’s regulators treat browser access as equivalent to hosting a service on a server under the provider’s control, even when the wallet itself is non-custodial and the user holds their own private keys. This interpretation has cascading implications for compliance, user liability, and the practical architecture of privacy wallets in Southeast Asia. Understanding why Cake Wallet Web faces this restriction—and what it means for users in regulated jurisdictions—requires examining both the technical and legal structure of the PSA and how it classifies different wallet delivery mechanisms.

How Singapore’s Payment Services Act defines wallet infrastructure

The PSA, which took effect on 28 January 2020, establishes a licensing framework for financial services that involve customer assets or payment channels. Section 5 of the Act defines a “payment service provider” as any entity that provides payment services in Singapore or to Singapore residents. Payment services include, among others, the holding of stored value on behalf of customers and the operation of a payment system.

The critical word is “on behalf of.” In a non-custodial wallet, the user retains private key ownership and the provider does not hold assets. However, the PSA’s implementation guidelines clarify that a browser-based wallet interface hosted on a server—even one that does not store private keys—is presumed to constitute service provision from Singapore’s territorial perspective. This presumption applies regardless of where the server is physically located or whether the wallet implements client-side encryption. If the interface is accessible to Singapore residents and facilitates transactions, the provider is considered to be offering a service in Singapore.

Native applications, by contrast, are installed directly on a user’s device and typically do not route transactions through a central server controlled by the wallet provider. This distinction has made native wallets—including the iOS, Android, macOS, and Linux versions of Cake Wallet—eligible for exemptions under paragraphs 1(a) or 1(f) of the Payment Services (Exemptions) Regulations 2020. These exemptions exclude certain users from the definition of service providers, primarily those whose activity does not involve regular receipt of stored value from the public or whose services fall below regulatory thresholds.

The regulatory logic, while debatable, reflects Singapore’s approach to jurisdiction: if a service is accessible and marketed to Singapore residents, Singapore applies its rules. A browser interface that responds to Singapore IP addresses or accepts Singapore payment methods is treated as operating in Singapore until proven otherwise. Cake Wallet Web, as a browser-accessible application, would therefore require MAS approval before serving Singapore users—a step that the project has not undertaken.

Browser wallets versus native applications: The technical consequence

The distinction between browser and native is not merely regulatory. It has genuine technical implications for security, user control, and the actual custody of private keys. A browser-based wallet application runs in an environment controlled partly by the browser vendor, the operating system, and any proxies or firewalls in the user’s network. The browser JavaScript engine, HTML rendering, and API access all introduce potential modification points that a native application running directly on the operating system does not face in the same way.

A native version of a privacy wallet, such as Cake Wallet for iOS or Android, is installed as a signed application package verified by the device’s operating system. The application has a defined set of permissions (camera, Bluetooth, network access), and users can inspect and revoke these permissions from device settings. The wallet’s code is part of a static installation bundle that is version-controlled and can be verified against the source repository on GitHub—in this case, the official Cake Wallet repository maintains the complete source code, allowing security researchers and users to audit the implementation.

A browser wallet, by contrast, is fetched from a web server each time the user visits the domain. The server can serve different code to different users based on their location, browser type, or any other criterion. Browser JavaScript can be modified in transit without the user’s knowledge, particularly if the user does not verify the application’s cryptographic signature (a feature few browsers enforce). Even with a secure HTTPS connection, a compromised certificate authority, an intercepting network node, or a breach of the hosting provider could inject malicious code.

Singapore’s regulators likely understood these distinctions. By treating browser access as equivalent to service provision, they created an incentive for developers to use native distributions where users have better control and verification options. This aligns with broader cybersecurity principles: a self-custody wallet user should be able to verify the code they are running, inspect its permissions, and detect if an update introduces unexpected behavior.

User liability and the practical enforcement gap

For Singapore residents who nonetheless access Cake Wallet Web through a VPN or proxy that masks their location, the regulatory status becomes ambiguous. Technically, they would be circumventing the PSA’s jurisdiction, but enforcement against individual users rather than service providers is rare and legally uncertain. Singapore’s regulatory authority focuses on the provider’s responsibility to comply, not the user’s responsibility to check regulatory status before accessing a wallet.

In practice, many Singapore users access privacy wallets including Monero wallets through non-native interfaces without regulatory scrutiny. The gap between law and enforcement creates a technical compliance environment: users may operate in a gray zone where they are theoretically non-compliant but face minimal practical risk. This does not mean the regulation has no effect. Legitimate wallet providers in Asia who consider serving Singapore have to make a business decision: either register with MAS (a costly and complex process) or geofence Singapore users (which involves detecting location and restricting access).

Cake Wallet’s approach has been to offer native applications as the primary distribution method, removing the need for a browser interface in the first place. The iOS and Android versions are available through standard app stores, and the macOS and Linux versions can be installed directly. This distribution model respects regulatory boundaries while maintaining the wallet’s core property: non-custodial, open-source, and under user control.

The MAS has not formally prosecuted wallet providers for browser access, perhaps because the regulatory boundary remains contested internationally and enforcement against decentralized applications is legally uncertain. However, the fact that the PSA explicitly contemplates browser wallet restriction suggests that Singapore regulators view this as a material distinction. A wallet provider considering compliance would likely err toward the native-application model rather than wagering on regulatory tolerance for browser access.

Privacy wallets and the regulatory classification problem

A deeper question underlies the browser-versus-native distinction: should non-custodial privacy wallets be regulated at all? The PSA assumes that any financial service involving stored value or payment facilitation requires a license. But a privacy wallet like Cake Wallet does not hold user funds; it does not execute transactions on behalf of users; and it does not have access to private keys. From a custody and financial crime perspective, it is a software tool, not a service provider.

This gap between regulatory presumption and technical reality has driven similar debates in other jurisdictions. The European Union’s Markets in Crypto-Assets Regulation (MiCA) took a different approach, explicitly exempting non-custodial wallet software from licensing requirements if the provider does not take custody or control of user assets. Singapore’s PSA did not include such an explicit exemption, creating regulatory uncertainty that affects browser-based distributions more severely than native ones.

The reason is partially jurisdictional reach. A browser interface has a global presence and can theoretically serve any user worldwide; a native application in an app store is subject to the app store’s content policies but operates in a more distributed, harder-to-centralize manner. Singapore’s regulators found it more practical to regulate the browser interface (by treating it as a hosted service subject to jurisdiction) than to attempt regulating distributed native applications (which would require enforcement against end-user devices).

For users in Asian jurisdictions evaluating privacy wallets, this creates a practical hierarchy: native applications are safer from a regulatory-compliance standpoint, while browser wallets carry ambiguous status. A cake wallet web interface, if accessed from Singapore or if explicitly marketed to Singapore residents, would likely trigger regulatory requirements; the same wallet downloaded as a native application would not face the same barrier.

Technical controls for privacy across platforms

Regardless of distribution method, the underlying privacy capabilities of Cake Wallet remain consistent. Monero’s privacy-by-default architecture ensures that transactions are private regardless of whether the wallet runs in a browser or as a native application. Ring signatures, stealth addresses, and RingCT obscure sender, receiver, and amount on the Monero network itself, a property that is independent of the wallet software.

Bitcoin’s privacy features, however, depend more on wallet behavior and user choice. Bitcoin’s Silent Payments specification (BIP-352) enables receiving payments without revealing a reusable address, reducing on-chain heuristics that chain-analysis services use. PayJoin, UTXO coin control, and transaction batching are behavioral privacy tools that work equally in browser and native environments but require user understanding and intentional use.

Litecoin’s MWEB implementation adds privacy to Litecoin transactions through Confidential Transactions and a UTXO commitment set, similar to Monero’s opacity. The Tor Project’s integration with wallet software adds network-level privacy by routing wallet connections through the Tor network, making it harder for ISPs or network observers to track which blockchain the user is interacting with.

These privacy technologies are implemented in Cake Wallet’s native applications. The question of whether they would be reliably implemented in a browser version involves different threat models. Browser APIs have different permission boundaries, and JavaScript cryptography libraries have historically had more attack surface than native cryptographic implementations. This technical consideration reinforces the regulatory preference for native distributions: they reduce modification risk and give users better visibility into what code is running.

Compliance strategies for privacy wallet providers in Asia

Wallet providers operating in Asia face three paths: geofencing, native-only distribution, or registration. Geofencing involves detecting user location and restricting access from certain jurisdictions. This is imperfect (VPNs defeat it) but compliant. Native-only distribution involves not offering a web interface at all, which is more defensible under Singapore’s regulatory framework. Registration is possible but extremely costly and operationally restrictive for a privacy-focused open-source project.

Cake Wallet Labs has chosen native-only distribution, supported by the open-source codebase published on GitHub. This approach aligns with the project’s core values: code transparency, user control, and no centralized intermediary. By not maintaining a browser interface intended for Singapore users, the project avoids triggering PSA registration requirements while still allowing sophisticated users to run their own instances or access the code directly.

For users in regulated jurisdictions like Singapore, the Cake Wallet guide for download and setup recommends the native application approach. The iOS and Android versions are available through standard channels; the macOS and Linux versions can be verified against the GitHub repository. This distribution model respects user sovereignty while respecting regulatory boundaries.

Other Asia-Pacific jurisdictions are developing similar frameworks. Hong Kong’s Anti-Money Laundering and Counter-Terrorist Financing Ordinance (AMLO) now includes provisions governing virtual asset service providers. Australia’s Treasury proposals contemplate wallet regulation. These developments suggest that the Singapore model—distinguishing between native applications and hosted services—may become a regional standard.

Practical recommendations for Asian users and privacy wallet security

For users in Singapore or other regulated jurisdictions who wish to use a non-custodial privacy wallet, the path is clear: download and install the native application. Verify the source, check the digital signature if possible, and review the code against the official GitHub repository. This approach gives you the strongest possible verification of what software is running and provides the clearest regulatory position.

When using any privacy wallet—whether Bitcoin with Silent Payments, Monero with ring signatures and stealth addresses, or Litecoin with MWEB—understand that privacy is not automatic. Bitcoin’s default transaction structure is transparent; privacy features must be enabled and used consistently. Monero is private by default, but wallet behavior (address reuse, fund consolidation) can still leak information if connected to identifying services later. Litecoin’s MWEB is optional and requires active selection.

For regulatory compliance in Singapore or similar jurisdictions, document the date and method of wallet installation. Keep records showing that you used a native application, not a web-based service. If questioned, the technical distinction is defensible: a native application is a tool; a web-based service is a service provider under the PSA. This distinction may not protect you from all scrutiny, but it provides a clearer legal basis than accessing Cake Wallet Web or similar browser interfaces.

Hardware wallet integration is another layer: Cake Wallet supports Ledger and Trezor devices, which store private keys in air-gapped hardware. This further insulates you from browser-based risks or other software compromise. If you are holding significant value, a hardware wallet reduces the consequence of malware or code modification.

The future of regulatory frameworks and wallet distribution

As regulators in Singapore, Hong Kong, Australia, and other jurisdictions develop clearer frameworks, the distinction between hosted and native wallets is likely to solidify. This creates a market incentive for wallet developers to maintain native distributions and avoid regulatory complexity. It also creates an incentive for users to prefer native applications, which offer better code transparency and verification.

The irony is that stricter regulation of browser-based wallets may actually improve security. Users who are forced to download and install a native application must confront the question of verification: Is this the real wallet? Can I audit the code? Has it been tampered with? These are the right questions. By creating regulatory friction around browser access, Singapore’s PSA inadvertently creates friction around a less secure distribution method.

For open-source projects like Cake Wallet, the regulatory environment is thus almost secondary. The native-application model aligns with the project’s technical vision: code that users can inspect, verify, and control directly. The PSA’s browser restriction accelerates a trend that privacy-conscious developers already prefer.