A wearable device that presents context-sensitive financial transaction menus based on the user's current location, dynamically updates them as the user moves, supports user-defined conditional shortcuts for frequent transactions, and surfaces fraud alerts requiring on-device approval.
Financial applications on wearable devices present a static set of transaction options — the same menu whether the user is at their home ATM, at a foreign bank, or at a merchant in another country. The device has location information but doesn't use it to surface contextually relevant options or remove irrelevant ones. Users waste time navigating options that don't apply to where they are.
The device presents a first menu of transactions available at the current location. When the user moves, it detects the new location, obtains a second menu for the updated location, and presents it — automatically adding new options and removing ones that no longer apply. Users can configure pre-defined shortcuts with conditions that automate their most frequent transactions based on location context.
Claim 8 adds a fraud-alert layer: the device receives an alert for an unexpected transaction at an unexpected location, surfaces it on the GUI, collects the user's approve or decline input, and communicates the response back to the server — all on-device, without leaving the wearable interface.
The wearable runs a continuous location-aware menu management loop. Menus are stored in device memory and updated from a server based on user profile and location. When the user moves, the device obtains the new menu — either from cache or server — and presents it with any applicable shortcuts already applied.
Shortcut conditions define when a shortcut triggers: the user can configure a shortcut for "withdraw $40 at this ATM every weekday morning" and the device will apply it automatically when those conditions are met, adding the shortcut options directly to the first menu.
Claim 2 specifies that the second menu removes options associated with transactions no longer available at the updated location. The wearable doesn't just add new options — it actively prunes stale ones. Select a location below to see how the menu adapts.
Claim 1 covers the full shortcut system: users configure pre-defined shortcuts for transactions at specific locations, associating each shortcut with one or more conditions that define when it applies. When those conditions are met, the shortcut's menu options are automatically added to the current menu — turning a multi-step transaction into a single tap.
Claim 3 extends this with server-side personalization: a server delivers customization information based on the user's profile and usage pattern, which shapes the second menu. The device's shortcut system layered on top of this server-personalized menu creates a fully adaptive, learnable wearable financial interface.
Each shortcut is associated with one or more conditions — location, time, transaction type — that determine when it fires automatically.
When a shortcut triggers, its menu options are added directly to the first menu — no navigation required. The shortcut becomes a top-level choice.
The server sends customization data based on user profile and pattern, shaping the second menu before shortcuts are applied — combining machine learning with user-defined rules.
Claim 4: Stored menus are dynamically updated as the user's profile or pattern changes — the wearable's menu set evolves over time without user reconfiguration.
Claim 8 covers the fraud-alert flow: when a server detects an unexpected transaction at an unexpected location, it sends a fraud-alert to the wearable. The device surfaces it on the GUI, presents the approve or decline option, receives the user's input, and communicates the response back to the server — all on the wearable, without switching to a phone.
This integrates real-time fraud response directly into the wearable's primary financial interface — the device that was already showing location-aware transaction menus is now also the decision surface for fraud resolution.
Claim 5 adds a location-aware authentication layer: the wearable determines one or more authentication factors required for the transaction at the updated location, with those factors selected based at least in part on location. A transaction at a home ATM might require a PIN; the same transaction abroad might require biometric data plus device ID.
Claim 7 specifies the transaction amount options: the second menu can present multiple pre-set transaction amounts associated with the transactions available at the updated location — enabling the ATM-style "quick amount" pattern directly on the wearable interface.
Standard authentication factors apply — typically PIN or device identifier. Lower friction for familiar location context.
Elevated authentication factors triggered by location — biometric data, voice pattern, or multi-factor combination. Higher assurance where risk is elevated.
Wearable presents multiple transaction amounts in the second menu — e.g., $20, $40, $60, $100 — matching denominations available at the current ATM or partner processor.
A shortcut for "withdraw $40 here" applies specifically at this location — the same shortcut doesn't fire at other ATMs, preventing unintended automation.
The combination of location-aware menus, conditional shortcuts, server personalization, and on-device fraud resolution creates a wearable financial interface that adapts to context rather than requiring the user to navigate to the right function every time.
Cited by Citibank in a 2024 patent on customizing financial user interfaces based on user function completion — directly validating the location-adaptive UI model as a building block for next-generation wearable financial experiences.