chore(runway): cherry-pick fix(ramps): improve external-browser callback redirection cp-7.71.0

[runway-github]

• fix(ramps): improve external-browser callback redirection cp-7.71.0 (fix(ramps): improve external-browser callback redirection cp-7.71.0 #27804)

Description

Fixes the external-browser return flow for unified ramps by moving
callback resolution out of Build Quote and into Order Details.

The bug was that external-browser returns were resolved too early in
BuildQuote. If callback parsing or order lookup failed there, users
could get bounced around or end up on a broken Order Details screen.

This change fixes that by moving callback resolution into Order Details
itself. BuildQuote now only hands off the callback context, and Order
Details fetches the real order itself. That makes the flow more
reliable: bailed callbacks return to Build Quote, and real fetch
failures show a retryable error instead of a broken redirect.

What changed

• Build Quote -> Order Details callback handoff
  After a successful external-browser return, Build Quote now navigates to
  Order Details with the full callbackUrl, providerCode, and
  walletAddress instead of trying to resolve the order immediately.

• Order Details callback bootstrap
  Order Details now supports loading from callback params, fetching the
  real order on first render, and updating route params once the order has
  been resolved.

• Bailed / invalid callback handling
  If the callback resolves to a bailed order state or no usable order, the
  user is sent back to Build Quote instead of landing on a blank or broken
  Order Details screen.

• Retryable callback error state
  If fetching the order from the callback URL fails, Order Details now
  shows a retryable error screen rather than silently resetting away. This
  makes transient backend/network failures recoverable.

• Navigation tests updated
  Tests were updated to reflect the callback-based route shape and the new
  Order Details retry behavior.

What stays untouched
This PR does not change Order Content amount rendering, list display
formatting, or duplicate placeholder cleanup. It is scoped only to
fixing the external-browser redirection and callback-resolution path.

Changelog

CHANGELOG entry: null

Related issues

Fixes:

Manual testing steps

Feature: my feature name

  Scenario: user [verb for user action]
    Given [describe expected initial app state]

    When user [verb for user action]
    Then [describe expected outcome]

Screenshots/Recordings

Before

Paypal Order going to build quote page first:
Uploading Screen Recording 2026-03-23 at 1.00.39 PM.mov…

After

Native Transak Redirection

Screen.Recording.2026-03-23.at.12.46.56.PM.mov

Bailed Paypal order (return to build quote page):

Screen.Recording.2026-03-23.at.12.38.45.PM.mov

Paypal order going to order details page:

Screen.Recording.2026-03-23.at.12.33.26.PM.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

Medium Risk
Changes the unified ramps external-browser return flow and navigation
params, which can impact users reaching the correct order state after
checkout; failures may surface as new retry/error behaviors.

Overview
Fixes unified ramps external-browser return handling by moving
callback URL resolution out of BuildQuote and into OrderDetails.

BuildQuote no longer calls getOrderFromCallback/addOrder on
InAppBrowser success; it now resets navigation to OrderDetails with
callbackUrl, providerCode, and walletAddress. OrderDetails
bootstraps from these callback params, fetches the real order (bailing
back to BuildQuote for invalid/bailed statuses), updates route params
to the resolved orderId, and shows a retryable error state if the
callback fetch fails.

Updates rampsNavigation to support an OrderDetails route shaped
around callback params (and makes orderId optional), and adjusts/adds
tests to cover the new handoff and retry behavior.

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

[4efb704](https://github.com/MetaMask/metamask-mobile/commit/4efb70495c55584929c4271bb3576d35fc5a4681)

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

[github-actions]

🔍 Smart E2E Test Selection

• Selected E2E tags: SmokeRamps
• Selected Performance tags: None (no tests recommended)
• Risk Level: medium
• AI Confidence: 92%

click to see 🤖 AI reasoning details

E2E Test Selection:
The changes are entirely contained within the Ramp feature (app/components/UI/Ramp/). The PR refactors the post-external-browser callback handling in the on-ramp flow:

1. BuildQuote.tsx: Removed the getOrderFromCallback and addOrder calls from the external browser callback handler. Instead of fetching the order and navigating to OrderDetails with an orderId, it now passes callbackUrl, providerCode, and walletAddress directly as navigation params.

2. OrderDetails.tsx: Now owns the callback URL fetching logic. On mount, if callbackUrl/providerCode/walletAddress params are present, it fetches the order, handles loading/error states, and supports retry. This is a meaningful behavioral change in the order details screen.

3. rampsNavigation.ts: Extended the navigation params interface and added a new route variant for the callback-based navigation.

These changes directly affect the on-ramp purchase flow - specifically the critical path where a user returns from an external browser after completing a purchase. The SmokeRamps tag covers on-ramp and off-ramp flows including the amount input screen and navigation flows, making it the most relevant tag.

No other feature areas are impacted - no shared navigation components, no controllers, no Engine changes, no other UI components outside Ramp are touched. The changes don't affect performance-sensitive code paths (no list rendering, no heavy state management, no startup/initialization code).

Performance Test Selection:
The changes are a refactoring of where order-fetching logic lives within the Ramp flow (moved from BuildQuote to OrderDetails). There are no changes to list rendering, account/network selectors, app startup, login flows, or other performance-sensitive areas. No performance tests are warranted.

View GitHub Actions results

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

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

See analysis details on SonarQube Cloud

[github-actions]

✅ E2E Fixture Validation — Schema is up to date
17 value mismatches detected (expected — fixture represents an existing user).
View details

[chloeYue]

LGTM