Description

Card Home only showed the spending limit progress bar for EVM chains (isEvmChain), because the original cap is resolved from on-chain Approval logs in BaanxProvider. Solana funding tokens in Limited status therefore showed nothing, even though the Baanx API already returns the remaining allowance as spendingCap.

This change:

1. Removes the EVM-only gate on showSpendingLimitProgress in CardHome.tsx, while keeping isSpendingLimitSupportedToken so AUSDC / AMUSD stay excluded.
2. Adds hasOriginalAllowance to SpendingLimitProgressBar: when originalSpendingCap is absent (typical for Solana; also possible for EVM if log fetch fails), the component renders a compact row: same divider and “Spending Limit” label, then <remaining> <symbol> <localized “available”> with no progress bar (we cannot show consumed vs total without the original cap).
3. Internationalizes the trailing word via card.card_home.spending_limit_available in locales/languages/en.json.
4. Updates tests: SpendingLimitProgressBar compact-mode coverage; CardHome Solana limited case and the EVM “undefined allowance” case now expect the compact string instead of a misleading 0/0 full-bar display.

Trade-off: Solana (and any asset without originalSpendingCap) does not get a progress bar until a backend field or on-chain read path exists; users still see that spending is limited and how much remains.

Changelog

CHANGELOG entry: Added a compact spending limit indicator on Card Home for limited Solana card funding tokens, showing remaining allowance when the original cap is not available.

Related issues

Fixes: #29550

Manual testing steps

Feature: Card Home spending limit for Solana limited tokens

  Scenario: Authenticated user with Solana primary asset in limited spending
    Given the user is logged into MetaMask Card and authenticated
    And the primary funding asset is on Solana mainnet CAIP chain
    And the asset status is limited spending (not full / not inactive)
    And the token symbol is not in the unsupported list (e.g. not AUSDC / AMUSD)

    When the user opens Card Home

    Then the spending limit section is visible with the label "Spending Limit"
    And the line shows the remaining amount, symbol, and the localized "available" suffix
    And no horizontal progress bar is shown for that compact state

  Scenario: Authenticated user with EVM asset and resolved original cap
    Given the same as above but the primary asset is EVM and `originalSpendingCap` is present from the provider

    When the user opens Card Home

    Then the full progress bar is shown with consumed/total and the progress bar control

Screenshots/Recordings

N/A — change is small UI copy/layout on Card Home; capture before/after on device or simulator when opening the PR for review if reviewers require visual proof.

Before

(Solana limited: no “Spending Limit” block on Card Home.)

After

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.

Performance checks (if applicable)

• I've tested on Android
  • Ideally on a mid-range device; emulator is acceptable
• I've tested with a power user scenario
  • Use these power-user SRPs to import wallets with many accounts and tokens
• I've instrumented key operations with Sentry traces for production performance metrics
  • See trace() for usage and addToken for an example

For performance guidelines and tooling, see the Performance Guide.

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.

Files changed (vs main)