Android News

Google Wallet Could Let You See Who Has Your Financial Data [APK Teardown]

An APK teardown reveals Google Wallet Open Finance permission controls in development, with a dashboard for reviewing shared financial data, consent periods, payment limits, and access revocation.

An APK teardown reveals Google Wallet Open Finance permission controls in development, with a dashboard for reviewing shared financial data, consent periods, payment limits, and access revocation.

by Kapill M MalaniKapill M Malani
0 Comments
Kapill M Malani

Kapill M Malani A die-hard Liverpool FC fan, Kapill is a big fan of Batman, Android and street Cricket. In that order, probably. Email: [email protected]

Contents hide

What to know

  • Google Wallet is building a hub for viewing and managing incoming and outgoing Open Finance data permissions.
  • The controls cover shared identity details, balances, payment access, limits, consent periods, status, and revocation.
  • We found the new interface strings in code from the unreleased Google Wallet v26.38.985592722 build.

Google Wallet’s broader Open Finance support for linking bank accounts and initiating Pix payments is already public. The latest build, however, reveals a more extensive permissions interface that gives users a detailed view of the financial and personal data shared between institutions.

We diffed Google Wallet v26.38.985592722 against the previous build and found new strings for incoming and outgoing consent records, sharing periods, permission statuses, transaction limits, and controls for withdrawing access.

About APK teardowns — An APK teardown works by reading the not-yet-shipped code inside a beta build, which lets us preview features a developer is working on before they’re announced. But work-in-progress code can change, stay hidden behind a server-side flag, or be scrapped before it ever reaches your phone.

A new “Manage Open Finance data” entry is designed to show data shared with other financial institutions. Its description explicitly identifies the page as a place to see information exchanged through Open Finance, while another string says users will be able to view, manage, and delete permissions granted to financial institutions.

The interface distinguishes between incoming and outgoing data, including institution and account identifiers. Consent records can display when they were created or granted, alongside statuses such as active, expired, pending, revoked, and temporarily unavailable.

pay_wallet_pix_consent_management_item_title = “Manage Open Finance data”
pay_wallet_pix_consent_management_item_description = “See shared data via Open Finance with other financial institutions”
consent_details_title = “Data sharing permissions via Open Finance”
consent_details_header_title_incoming_with_account = “Incoming data from %1$s •• %2$s”
consent_details_header_title_outgoing_with_account = “Outgoing data from %1$s •• %2$s”
consent_details_granted_date_and_status = “Granted on %1$s • %2$s”
consent_details_sharing_period_title = “Sharing period”
consent_details_sharing_period_indefinite = “indefinitely”
consent_status_active = “Active”
consent_status_expired = “Expired”
consent_status_pending = “Pending”
consent_status_revoked = “Revoked”
consent_status_temporarily_unavailable = “Temporarily not available”

Users can inspect exactly what they are sharing

The permission details extend beyond payment authorization. Google Wallet’s code separates access to balances, limits, and payments from registration and identity data. The latter can include a CPF, legal name, address, date of birth, email, phone number, nationality, marital status, identification documents, passport information, and parents’ names.

Before data is shared, a confirmation screen asks the user to review the details and offers “Not now” and “Share” actions. The flow can redirect the user to a financial institution, while the permission page identifies the receiving institution and explains the purpose of sharing.

consent_details_confirmation_title = “Confirm data sharing with %1$s”
consent_details_confirmation_subtitle = “To continue, please review and confirm the following details:”
consent_details_identity_title = “Your personal identity”
consent_details_balance_and_limits_title = “Balance and Limits”
consent_details_permission_balance_access = “Balance access”
consent_details_permission_payments = “Payments”
consent_details_transaction_limit_title = “Transaction limit amount”
consent_details_dialog_item_residency = “Brazilian residency”
consent_details_cpf_format = “CPF: %1$s”
consent_details_dialog_item_legal_name = “Full legal name”
consent_details_dialog_item_address = “Full address”
consent_details_dialog_item_dob = “Date of birth”
consent_details_button_not_now = “Not now”
consent_details_button_share = “Share”

The most important addition is direct consent management. Google Wallet references both a general “Revoke sharing” action and a more specific option to cancel access to balance and limit information. This turns the proposed hub into more than a history of linked institutions: it is designed to give users control over continuing access to their financial data.

consent_details_action_revoke_sharing = “Revoke sharing”
consent_details_action_cancel_balance_and_limit = “Cancel access to balance and limit”
consent_details_purpose_payments = “To make Pix payments using your bank account”
consent_details_institution_title = “Receiving financial institution”
no_active_outgoing_consents = “No active outgoing consents”

These Open Finance permission controls are not available to users yet, and we’ll watch future Google Wallet builds for their rollout.

Related guides

Keep reading

More from Android

All Android guides →

Leave a Reply

Your email address will not be published. Required fields are marked *