Stack Wallet

This commit is a user-interface refactor for the Stack Wallet app's 'ShopInBit' car-research ticket screen. It replaces a full-screen loading dialog with a small inline spinner while the app checks the server for an in-progress car-research invoice. There is no security-relevant change: no cryptography, authentication, network trust, permissions, or data handling logic is altered.

This commit changes how the Stack Wallet app resumes a 'car research' purchase when a user taps an in-progress ticket. Instead of relying only on invoice details saved on the phone, it now first asks the ShopInBit server for the current invoice list and uses that to decide whether to continue to payment or start over. The change appears to be a feature/robustness improvement, not a security fix, but it does introduce a new network call and slightly different logic for matching invoices.

This commit refactors how Stack Wallet finalizes a paid car-research request in its ShopInBit feature. It moves most of the post-payment work (creating the real support ticket) from the app to the backend, so the app now just logs the payment and then looks up the ticket the server created. It also makes number parsing safer when price data is missing. There is no direct evidence this fixes an active security bug, but it removes client-side logic that could previously leave orders in inconsistent states if the app crashed or retried at the wrong time.

This commit removes a manual 'Complete Request' button from the car-research ticket screen and replaces it with a simple informational note telling the user that the request is being finalized automatically. The change is a user-experience refactor, not a security fix.

This commit changes a car-research fee invoice screen so that, when requesting an invoice, the app now also sends the customer's car request details (a pseudonym, comment, and delivery country) to the backend. The stated goal is to let the backend create the real research ticket automatically once the fee is paid. There is no direct security bug visible in the diff, but it increases the amount of personal/order data transmitted and stored server-side, which could matter for privacy if the backend does not protect it properly.

This commit adds two new features to the ShopInBit integration in Stack Wallet: it lets users attach a car-research request to a fee invoice, and it lets them retrieve any unpaid car-research invoices so they can finish paying. The code itself is a normal feature addition and does not appear to introduce an obvious security vulnerability. The main thing to watch is that the new API calls send personal/pseudonymous data and payment links over the network, so they rely on the existing HTTPS and authentication plumbing being correct.

This commit hardens the checkout flow for a built-in shopping feature (ShopInBit). Previously, the payment screen could open even if no live invoice with payment addresses had been loaded, and it tried to recover or render empty payment links. Now the app refuses to open the payment screen unless a usable invoice is already in hand, and it disables the 'Pay Now' action when an address is missing. This reduces the chance a user accidentally sends money to an empty/invalid destination or gets stuck in a broken payment state.

This commit simply removes an unused import statement from a single Dart file in the Stack Wallet app. It does not change any app behavior, fix a bug, or alter security in any way. It is a routine code cleanup.

This commit changes how error messages are shown to users when a ShopinBit order submission fails. Previously, a small temporary notification banner (a 'flush bar') appeared at the bottom of the screen. Now, a centered popup dialog appears instead. There is no security change here—only a user-interface improvement to make errors more noticeable.

This commit changes how error messages are shown to the user when a ticket retry request fails in the ShopInBit feature. Previously, a brief floating notification (a 'flush bar') appeared; now, a modal dialog box appears instead. There is no security issue here—this is purely a user-interface improvement.

This commit changes how an error message is shown to the user when saving a customer key in the ShopInBit settings. Instead of a temporary warning banner, it now shows a proper dialog box. It also adds a safety check to avoid a crash if the user navigates away while the dialog is open. There is no direct security vulnerability being fixed here; it is a UI/UX robustness improvement.

This commit changes how an error message is shown to the user when key generation fails in a shopping-related settings screen. Instead of a temporary warning banner, it now shows a popup dialog. It also adds a safety check to avoid updating the screen after the user has navigated away. This is a minor UI/UX fix with no clear security impact.

This commit changes how invoice creation errors are shown to users in a car-research shopping feature. Instead of a brief floating warning bar, the app now displays a proper dialog box with the error message. This is a user-experience improvement, not a security fix, and it does not change how errors are handled or logged.

This commit changes how an error message is shown to the user when a car research payment retry fails. It swaps a temporary floating notification bar for a popup dialog. There is no security issue here—this is purely a user-interface improvement.

This commit changes how error messages are shown to users when a car-research payment fails in the Stack Wallet app. It replaces small floating notification banners with larger popup dialogs so users are more likely to notice the problem. There is no security fix here—only a user-interface improvement.

This commit changes how payment-check errors are shown to the user in the ShopInBit feature. Previously, a brief warning banner (a 'flush bar') appeared. Now, a blocking dialog box appears that the user must acknowledge before continuing. This is a user-experience and reliability improvement, not a fix for a code vulnerability. It makes it harder for a user to miss an important payment failure message, but it does not change how payments are processed or how errors are generated.

This commit is a straightforward user-interface cleanup. It replaces a custom read-only 'Country' field in the ShopInBit shipping screen with a shared 'DetailItem' widget so the locked country is rendered as a disabled text field. There is no security change: the country was already locked and uneditable before, and it remains locked and uneditable after.

This commit is a UI/UX fix for the Stack Wallet app's ShopinBit integration. It makes sure the delivery country shown during shipping matches the country that was used to price the order. It does not appear to be a security fix and does not introduce obvious security risks.

This commit fixes a bug in Stack Wallet's ShopInBit payment screen. Previously, if the user tapped 'PAY NOW' before the payment address had loaded, the app would abruptly close the entire navigation stack (effectively kicking the user out of the checkout). Now it shows a warning message, attempts to recover the missing payment details from the server, and continues polling instead of popping screens.

This commit is a user-interface refactor for the ShopInBit checkout flow. It moves the loading of payment information earlier in the process so the payment screen appears already filled in, rather than showing a spinner after the page opens. There is no direct security fix here, but the change touches code that handles invoice creation, polling, and route arguments for a third-party payment integration.

This commit fixes a timing bug in the Stack Wallet app's ShopInBit payment flow. Previously, the code that launches the in-wallet send screen was called without waiting for it to finish, and the app could continue running logic on a screen that had already been closed. The change makes the navigation awaitable and adds a check to stop further work if the widget is no longer visible. This is a correctness and stability fix that could prevent UI glitches or inconsistent order state, but it is not a clear-cut security vulnerability.