feat(ramps): uses api endpoint to determine ramp eligibility

[georgeweiler]

Description

This PR updates the Ramps Smart Routing hook to use the actual API endpoints now that they are available in production and staging environments.

What is the reason for the change?
The smart routing feature was previously using a placeholder endpoint (/endpoint-coming-soon) while waiting for the backend API to be deployed. The API endpoints are now available and ready to be integrated.

What is the improvement/solution?

• Integrated production and staging API endpoints for ramp eligibility checks
• Production URL: https://on-ramp-content.api.cx.metamask.io/regions/countries/{region-code}
• Staging URL: https://on-ramp-content.uat-api.cx.metamask.io/regions/countries/{region-code}
• Environment detection uses process.env.METAMASK_ENVIRONMENT directly to determine which endpoint to use
• Production environments: production, beta, rc
• Staging environments: dev, exp, test, e2e, and all others default to staging

Changelog

CHANGELOG entry: null

Related issues

Fixes: https://consensyssoftware.atlassian.net/browse/TRAM-2807

Manual testing steps

Feature: Ramp Smart Routing API Integration

  Scenario: User in supported region sees appropriate ramp option
    Given the app is running in a production environment
    And the user's detected geolocation is "us-ca"
    When the ramp smart routing hook initializes
    Then the app fetches eligibility from "https://on-ramp-content.api.cx.metamask.io/regions/countries/us-ca"
    And the routing decision is set based on the API response

  Scenario: User in supported region in staging environment
    Given the app is running in a dev/staging environment
    And the user's detected geolocation is "us-ca"
    When the ramp smart routing hook initializes
    Then the app fetches eligibility from "https://on-ramp-content.uat-api.cx.metamask.io/regions/countries/us-ca"
    And the routing decision is set based on the API response

  Scenario: User in unsupported region
    Given the app is running in any environment
    And the user's detected geolocation returns global: false from API
    When the ramp smart routing hook initializes
    Then the routing decision is set to UNSUPPORTED
    And the user cannot access ramp features

  Scenario: API fetch fails
    Given the app is running in any environment
    And the API request fails or times out
    When the ramp smart routing hook initializes
    Then the routing decision is set to ERROR
    And appropriate error logging occurs

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

Hook now fetches ramp eligibility from environment-specific endpoints with error handling; tests expanded and Babel config updated to preserve env vars.

• Ramps Smart Routing (app/components/UI/Ramp/hooks/useRampsSmartRouting.ts)
  • Use real eligibility API with env-based base URLs via process.env.METAMASK_ENVIRONMENT (PRODUCTION vs STAGING).
  • Build fetch URL '/regions/countries/{region}'; validate response.ok and throw on errors; log and route to ERROR on failure.
• Tests (useRampsSmartRouting.test.ts)
  • Add cases verifying production/staging URLs across envs (production, beta, rc, dev, exp, test, e2e).
  • Add error-path tests for failed fetch and non-OK responses (404, 500); persist/restore env; update geolocation to us-ca.
• Build/Config (babel.config.tests.js)
  • Exclude useRampsSmartRouting.ts and its tests from inline env var transform to allow runtime env-based behavior.

^{Written by Cursor Bugbot for commit 77d4425. 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.

[wachunei]

Please use URL object to construct URLs, as it handles bass URLs trailing slashes, encoding, etc...

const url = new URL(`/regions/countries/${rampGeodetectedRegion}`, baseUrl).toString();
await fetch(url);

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

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

See analysis details on SonarQube Cloud