Description

Reason: Users with a MetaMask Card and a Money Account need clearer paths to link spending to their Money balance, copy that matches design (including mUSD cashback and flexible APY), and less noisy linkage feedback. Card Home previously lacked a dedicated entry point; the link confirmation sheet used generic art and older copy.

Solution:

• Card Home: When useMoneyAccountCardLinkage reports canLink, render a MoneyMetaMaskCard in link mode between dividers, with hideCardImage so the hero card image is not duplicated, apy from useMoneyAccountBalance, and metal vs virtual cashback via CardType. Tapping the header, subtitle row, or Link card calls startLinkFlow({ screen: Routes.CARD.HOME }). CTA stays visible while cardHomeDataStatus is loading (stale-while-revalidate) when other conditions still allow linking.
• MoneyMetaMaskCard (link mode): Support hideCardImage (vertical bullets only), and when apy is undefined, use link_subtitle_no_apy and omit the APY bullet instead of forcing 0%.
• MoneyLinkCardSheet: Replace the mUSD coin with the user’s card art from selectCardHomeData (mm_card_metal for CardType.METAL, else mm_card_regular), Figma-aligned sizing, updated sheet description plus link_card_sheet_description_no_apy when vault APY is not yet available.
• useMoneyAccountCardLinkage: Single-line pending/success toasts, updated error copy, pending spinner color IconDefault, and error icon Error instead of Danger.
• Spending Limit (from feat(card): preselect Money Account and add Spend and Earn CTA on spending limit screen #30320): Money Account preselection, Spend and Earn promo UI (SpendAndEarnPromoCard, ShimmerOverlay), and related useSpendingLimit / view tests.
• Other (same branch vs main): Bridge insufficient-native reserve handling and tests; send confirmation alert modal and fee / percentage amount hook adjustments with tests.

Changelog

CHANGELOG entry: Added a Link Money Account section on Card Home, redesigned the link-card bottom sheet (card art and copy), improved Money Account card-linkage toasts, extended Spending Limit with Spend and Earn / Money preselection, and tightened bridge and send confirmation edge cases.

Related issues

Fixes:

Refs: #30320

Manual testing steps

Feature: Money Account linking and related card flows

  Scenario: Card Home shows link CTA when user can link
    Given I am a cardholder with Money Account requirements met, card home data loaded, and I am not already delegated for card spending
    When I open Card Home
    Then I see the Link MetaMask Card block with dividers and Link card action

  Scenario: Link card opens confirmation sheet with correct art and copy
    Given I tap Link card or the link header from Card Home (or open the link sheet from the Money link flow)
    When the Spend and earn bottom sheet appears
    Then I see the title Spend and earn, description mentioning mUSD back and up to my vault APY when available, and the card image matches my card type (metal vs virtual)

  Scenario: Confirm link still runs linkage after sheet dismiss
    Given the link confirmation sheet is open
    When I tap Link card on the sheet
    Then the sheet closes and the in-app linkage flow continues (pending then success or error toast)

  Scenario: No APY yet uses shorter description
    Given vault APY is not yet available to the client
    When I open the link confirmation sheet
    Then the body copy does not include an APY clause and no raw i18n placeholders appear

  Scenario: Spending Limit Spend and Earn promo (Refs #30320)
    Given I open Spending Limit under conditions where the Spend and Earn promo applies
    When I review the screen
    Then I see the promo treatment and Money Account is preselected where configured

Screenshots/Recordings

Before

N/A

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.