feat(card): disable swaps if selected address is different from priority token owner address

[Brunonascdev]

Description

Implements account address validation for the Card feature's "Add Funds" functionality.
The feature now disables swaps when the priority token owner address doesn't match the user's selected EVM or Solana account address.

Changelog

CHANGELOG entry: Disabled "Add Funds" button when priority token address doesn't match selected account on Card feature

Related issues

Fixes:

Manual testing steps

Feature: Card Add Funds Swap Validation

  Scenario: Add Funds button enabled when accounts match
    Given the priority token address matches the selected account
    
    When the Card Home loads
    Then the "Add Funds" button should be enabled

  Scenario: Add Funds button disabled when accounts don't match
    Given the priority token address doesn't match the selected account
    
    When the Card Home loads
    Then the "Add Funds" button should be disabled

  Scenario: EVM addresses compared case-insensitively
    Given an EVM account with address "0x1234...5678"
    And a priority token with address "0xABCD...5678" (different case)
    
    When comparing addresses
    Then they should match (case-insensitive)

  Scenario: Solana addresses compared case-sensitively
    Given a Solana account with address "SolanaAddress123"
    And a priority token with address "solanaaddress123" (different case)
    
    When comparing addresses
    Then they should NOT match (case-sensitive)

Screenshots/Recordings

Before

After

Simulator.Screen.Recording.-.iPhone.16.-.2025-10-20.at.22.24.52.mov

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.

---

Note

Disables the Card Home Add Funds action based on a new address-matching hook, adds disabled styling/tests, and improves SDK error logging for external wallet fetches.

• Card Home:
  • Integrates useIsSwapEnabledForPriorityToken to gate Add Funds by address match; sets disabled and applies styles.halfWidthButtonDisabled when not allowed.
  • Updates ButtonsSection deps to include isSwapEnabledForPriorityToken.
• New Hook: useIsSwapEnabledForPriorityToken
  • Returns true when not authenticated; otherwise requires priority token owner address to match selected account (EVM case-insensitive, Solana case-sensitive).
• Styles: Adds halfWidthButtonDisabled in CardHome.styles.ts.
• Tests:
  • Adds useIsSwapEnabledForPriorityToken.test.ts covering auth and EVM/Solana comparisons.
  • Extends CardHome.test.tsx to verify Add Funds enabled/disabled behavior and styling; updates snapshots.
• SDK (CardSDK.ts): Enhances error logging by attempting to parse and log JSON bodies when fetching external and priority wallet details fails.

^{Written by Cursor Bugbot for commit 5af32de. This will update automatically on new commits. Configure here.}

[github-actions]

CLA Signature Action: All authors have signed the CLA. You may need to manually re-run the blocking PR check if it doesn't pass in a few minutes.

[sonarqubecloud]

Quality Gate passed

Issues
3 New issues
0 Accepted issues

Measures
0 Security Hotspots
92.3% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud