Description

Refactors the Card Spending limit screen and related asset selection so default token choice and list ordering follow wallet fiat value for the currently selected MetaMask account, replaces the multi–quick-select asset row with a settings-style summary card, and moves full vs. restricted limit + amount into a dedicated bottom sheet.

Why: Quick-select assumed fixed symbols (e.g. mUSD-first) and did not consistently reflect real balances or account switches. Asset lists should align with how much the user actually holds per account, and the main screen should read like compact “settings” rows instead of several tappable asset tiles.

What changed:

• constants.ts: Adds CARD_CHAIN_IDS (Linea, Base, Monad hex 0x8f, Solana) using @metamask/transaction-controller chain IDs where applicable; keeps caipChainIdToNetwork derived from cardNetworkInfos.
• useSpendingLimit:
  • Removes quickSelectTokens, handleQuickSelectToken, and isOtherSelected.
  • Uses useTokensWithBalance({ chainIds: CARD_CHAIN_IDS }) so default token candidates are sorted by tokenFiatAmount (highest first); if none have positive fiat, falls back to Linea mUSD when present. Candidates come from NotEnabled allowances when applicable, otherwise buildTokenListFromSettings + sdk.getSupportedTokensByChainId.
  • Resets initialization when the selected internal account changes (setHasInitialized(false), clear selection) so defaults are not stale across account switches.
  • handleAccountSelect opens the account selector; handleOtherSelect opens AssetSelectionBottomSheet with excludedTokens set to the current row token; handleLimitSelect opens the new spending-limit options sheet.
  • Consumes returnedLimitType / returnedCustomLimit from the options sheet via useFocusEffect (same pattern as token return params).
• SpendingLimit.tsx: Setup header copy (setup_title / setup_description); settings card with three rows — Account, Token (label SYMBOL on NETWORK) with chevron → asset picker, Spending limit row → options sheet; footer Cancel / Confirm.
• SpendingLimitOptionsSheet.tsx (new modal route): Full access vs Spending limit (with numeric input), LimitOptionItem styling tweaks (input alignment, maxLength={12}), confirm navigates back with limit params.
• Routes / Card stack: Registers CARD.MODALS.SPENDING_LIMIT_OPTIONS for the options sheet.
• AssetSelectionBottomSheet: Optional excludedTokens in navigation params to hide the token already shown on the spending-limit Token row; NotEnabled tokens are sorted by fiat using rawFiatNumber on enriched rows.
• useAssetBalances: Uses CARD_CHAIN_IDS for useTokensWithBalance (adds Monad, aligns with card networks); exposes rawFiatNumber on AssetBalanceInfo for sorting.
• AssetCard: caipChainId support and optional onPress — token icon and network badge use the token’s real chain, not Linea-only.
• locales/languages/en.json: New/updated card.card_spending_limit strings (setup_title, setup_description, account_label, token_label, copy tweaks; Restricted label renamed to Spending limit where used).
• Tests: useSpendingLimit.test.ts, SpendingLimit.test.tsx, AssetSelectionBottomSheet.test.tsx updated for new hooks, navigation params, and UI structure.

Changelog

CHANGELOG entry: Card spending limit screen uses account-scoped wallet fiat to pick and order default tokens; main view is a settings card (account, token, limit) with asset sheet exclusions and fiat sort for NotEnabled tokens; full vs restricted limit is configured in a dedicated bottom sheet.

Related issues

Fixes:

Manual testing steps

Feature: Card spending limit and asset list reflect wallet value

  Scenario: Default token on spending limit after open
    Given I have multiple Card-supported tokens with different fiat balances on the selected account
    When I open Spending Limit (manage / enable / onboarding as applicable)
    Then the pre-selected token favors the highest fiat balance, or Linea mUSD when no positive fiat

  Scenario: Switch account
    Given I change the active MetaMask account from the Account row
    When I return to or remain on Spending Limit
    Then default token selection reflects the new account’s balances (not a stale selection)

  Scenario: Token row → asset sheet
    When I tap the Token row and pick another asset
    Then the row updates and the previously selected token is not duplicated in the list when excluded

  Scenario: Spending limit row → options sheet
    When I tap the Spending limit row
    Then I can choose full access or enter a restricted amount, confirm, and see the summary row update

  Scenario: Asset selection list ordering
    Given tokens in NotEnabled state appear in the asset sheet
    When I view the list
    Then NotEnabled tokens are ordered by fiat value where implemented

Screenshots/Recordings

Pre-merge author checklist

• I've followed MetaMask Contributor Docs and MetaMask Mobile Coding Standards.
• I've completed the PR template to the best of my ability
• I've included tests if applicable
• I've documented my code using JSDoc format if applicable
• I've applied the right labels on the PR (see labeling guidelines). Not required for external contributors.

Pre-merge reviewer checklist

• I've manually tested the PR (e.g. pull and build branch, run the app, test code being changed).
• I confirm that this PR addresses all acceptance criteria described in the ticket it closes and includes the necessary testing evidence such as recordings and or screenshots.