WebMoney Keeper

Opening the app and the first hurdle

Downloading WebMoney Keeper from the Play Store takes less than a minute. The app size is around 73 MB. Opening it for the first time, the user is greeted with a login screen. No registration option is available directly in the app. The user must already have a WebMoney ID (WMID) and a password. This is a critical friction point. The app is not a standalone wallet. It is a client for an existing WebMoney account. A new user cannot create an account from the app. They must first register on the WebMoney website, obtain a WMID, and set up a password. The app then acts as a mobile interface for that account. The login process requires the WMID, password, and often a verification code sent via SMS or E-num. Multiple users report that the SMS code never arrives. The app provides no alternative for code delivery. The user is stuck. Some users restart their phones or try multiple times. The issue persists across versions. The verification system is the first wall. Behind that wall, the app shows a dashboard of wallet balances. The interface is functional but dated. Menus are labeled in a mix of English and Russian. There is no language toggle. The user is forced to navigate a bilingual interface. This creates confusion for non-Russian speakers. The app assumes familiarity with the WebMoney ecosystem. A new user without prior knowledge will struggle.

The home screen displays all connected purses: WMZ (USD), WMR (RUB), WME (EUR), and others. Each purse shows a balance and a list of recent transactions. Tapping a purse opens a detailed view. From there, the user can send funds, request payment, or view history. The UI is dense. Information is packed into small text fields. Buttons are small. The design feels like a desktop application squeezed onto a phone screen. This is not a mobile-first design. It is a port. The app works, but it does not feel modern. Users who expect a sleek fintech experience will be disappointed. The app prioritizes functionality over aesthetics. Every feature from the desktop version is present. The chat function allows messaging other WebMoney users. The file sharing works. The call feature is available. But the core experience is transaction management. Sending funds is straightforward once the user is logged in. The user enters a WMID or purse number, an amount, and a purpose. The app calculates the fee. The fee is displayed before confirmation. The user can then approve the transaction with a password or biometric authentication. This flow works reliably for users who are already verified.

How verification blocks withdrawals and traps funds

The verification process is the single biggest barrier in WebMoney Keeper. The app allows the user to receive funds and top up their purse easily. Withdrawing funds, however, is a different story. Multiple users report that they cannot withdraw without an international passport. The app asks for extensive personal data: full name, date of birth, address, ID documents, and sometimes a selfie video. The verification is not handled within the app. It redirects the user to the WebMoney Passport service website. The user must upload documents there. The verification can take days or weeks. During this time, the funds are locked in the purse. The user cannot access them. Some users report waiting months for verification. One user reported being defrauded of $94 and only getting a refund after four months. Another user reported a 37.97% commission on withdrawal. The app does not clearly communicate these fees upfront. The Play Store description mentions fees only indirectly. This creates a trap: the user deposits money easily, but withdrawing costs time, effort, and money. The app's value proposition is clear for sending payments and paying bills. For receiving and holding funds, the friction is high. The user who relies on WebMoney as a primary wallet will eventually face the verification wall. The app does not offer an alternative. There is no way to bypass verification for small amounts. The financial restrictions for unverified users are severe. The maximum amount of funds is limited. The user must upgrade to WinPro or WebPro to increase limits. This requires additional fees and verification. The system is designed for serious users, not casual ones.

The original analysis here is that the app's ease of deposit versus difficulty of withdrawal creates a one-way flow. The user can add funds from a bank card or through a transfer in seconds. The funds appear in the purse immediately. The user can then send funds to other WebMoney users with low friction. But converting those funds back to fiat currency or withdrawing to a bank card requires a formal verification process. This process is not integrated into the app. It is external. The user must navigate a separate website, upload documents, and wait for approval. The app does not track the verification status. The user must check the Passport service separately. This disconnect between the app and the verification system is a design flaw. It creates confusion and frustration. The user feels trapped. The app works perfectly for receiving money. It works poorly for getting money out. This is not a scam, but it feels like one to users who are not prepared for the verification requirements. The Play Store page does not emphasize this. It highlights the convenience of payments and transfers. It does not mention the withdrawal restrictions. This gap between marketing and reality is a recurring theme in user complaints.

Real-world performance: permissions, trackers, and updates

The app requests a staggering number of permissions. The Exodus Privacy report for version 5.4.39 lists 48 permissions. These include location access (coarse and fine), network state, Wi-Fi state, Bluetooth, and external storage write. The location permissions are particularly concerning. The app does not need location to send or receive funds. The privacy policy states that location is used for security: if the app is launched from an unknown location, the server may take action to protect the account. This is a weak justification. The user must grant location access to use the app. There is no option to deny it. The app also includes multiple trackers. The Exodus report found 2 trackers in version 5.4.39. Earlier versions had up to 11 trackers. These trackers are for analytics, crash reporting, and identification. The app shares data with third parties. The Play Store data safety section confirms that the app shares app info and performance data with third parties. The user can request data deletion, but the process is unclear. The app collects personal info, location, and 8 other data types. This is a heavy data collection profile for a wallet app. Users who value privacy may find this excessive.

The update cycle is frequent but vague. The changelog for version 5.4.75.R-6575 says "minor bug fixes and general improvements." The previous version 5.4.73.R-6566 added support for WMQ wallets. Version 5.4.40.R-5614 included "improved ways to add correspondents, added processing of paid files in chat, bug fixes and stability improvements." The updates are incremental. They do not address the core complaints about verification and fees. The app is stable. It does not crash frequently. The performance is acceptable on modern devices. Older devices may struggle with the 73 MB size and the resource usage. The app runs in the background. It may use battery and data for push notifications. The user cannot easily control background activity. The app does not have a power-saving mode. The overall performance is adequate for a financial app. The real issues are not technical. They are policy and design. The app works as intended. The intended experience, however, is not what most users expect.

Permission model: what the app actually accesses on your device

The permission list is long. The app requests ACCESS_COARSE_LOCATION and ACCESS_FINE_LOCATION. These allow the app to determine the device's approximate and precise location. The app also requests ACCESS_NETWORK_STATE and ACCESS_WIFI_STATE. These are used to check network connectivity and Wi-Fi status. The app requests BLUETOOTH and BLUETOOTH_ADMIN. These permissions are unusual for a wallet app. They may be used for nearby device discovery or file sharing. The app requests WRITE_EXTERNAL_STORAGE. This allows the app to modify or delete contents of shared storage. This is used for caching and file transfers. The app requests WAKE_LOCK. This prevents the device from sleeping. This could impact battery life. The app requests AUTHENTICATE_ACCOUNTS. This allows the app to use the device's account manager. The permission model is broad. The user must accept all permissions to install the app. There is no granular control. The app does not request permissions at runtime. It requests them at installation. This is a legacy approach. Modern Android apps request permissions when needed. WebMoney Keeper does not follow this pattern. The user who is concerned about privacy may find the permission list alarming. The Exodus report classifies many permissions as "very high risk." The app's data collection is extensive. The user's location, personal info, and device identifiers are collected. This data is shared with third parties. The app's privacy policy is available on the WebMoney website. It is not easily accessible within the app. The user must actively search for it. This lack of transparency is a recurring issue. The app is functional, but it demands a high level of trust. The user must trust the developer with significant personal data. The developer, Digimoney SIA, is based in Latvia. The company is the legal owner of the WebMoney trademark. This provides some legitimacy. But the user complaints about data misuse and high fees undermine that trust.