Description

Token assetIds from the controller use checksummed (mixed-case) addresses (e.g. eip155:1/erc20:0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48), but the on-ramp API and provider supportedCryptoCurrencies keys use lowercase. This case mismatch caused two bugs:

1. "Token Not Available" modal shown incorrectly — BuildQuote checked supportedCryptoCurrencies[assetId] with a checksummed key against lowercase map keys. The lookup returned undefined, so every ERC-20 token appeared unsupported.

2. Payment methods endpoint returned empty — useRampsPaymentMethods passed the checksummed assetId to the API as the crypto query param. The API is case-sensitive and returned no results for the uppercase variant.

Changes:

1. providerSupportsAsset.ts (new utility) — Case-insensitive lookup against supportedCryptoCurrencies. Tries the original key first, falls back to toLowerCase().

2. BuildQuote.tsx — 3 locations replaced supportedCryptoCurrencies?.[assetId] with providerSupportsAsset(): the isTokenUnavailable check, first-time provider selection, and auto-switch on soft selection.

3. ProviderSelectionModal.tsx — displayProviders filter uses providerSupportsAsset() instead of direct bracket lookup.

4. ProviderSelection.tsx — Supported/unsupported provider separation uses providerSupportsAsset().

5. useRampsPaymentMethods.ts — Lowercases assetId before passing to the payment methods API call.

Changelog

CHANGELOG entry: Fixed case-sensitive assetId mismatch that caused false "Token Not Available" modal and empty payment methods for ERC-20 tokens

Related issues

Manual testing steps

Feature: Case-insensitive token support checks

  Scenario: ERC-20 token shows as available when provider supports it
    Given user is in region us-tx with Transak selected
    When user selects USDC on Ethereum
    Then the "Not available" modal does NOT appear
    And payment methods load correctly (e.g. Apple Pay, Debit/Credit)

  Scenario: Provider selection modal shows supporting providers
    Given user is on BuildQuote with USDC selected
    When user taps "Change provider"
    Then all providers that support USDC are listed
    And "No providers available" does NOT appear

  Scenario: Native tokens still work (no hex address)
    Given user selects ETH (native, slip44:60)
    Then token is recognized as supported
    And payment methods load normally

Screenshots/Recordings

Before

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).

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.