Description

Bumps @metamask/transaction-pay-controller from 23.5.0 to 23.6.0 in package.json and refreshes yarn.lock to pull in the corresponding transitive dependency updates. There are no application source changes in this PR.

Why: fiat payments in MMPay were broken on the previous TPC version. Version 23.6.0 lands the upstream fixes and behavior changes required to restore that flow.

What changes in TPC 23.6.0:

• Added: Direct mUSD fiat injection flow for Money Account deposits behind the useFiatMUSDQuoteToInjectForMoneyAccount feature flag. When enabled and a provider supports mUSD on Monad, fiat is used to purchase mUSD directly into the Money Account, skipping the ETH→mUSD bridge. Falls back to the existing flow otherwise. Also moves fiatPayment.caipAssetId assignment into the fiat quote functions so the asset ID always matches the quote that succeeded. (core#9080)
• Added: Fiat order polling interval and timeout are now remotely configurable via confirmations_pay_fiat.orderPollIntervalMs and confirmations_pay_fiat.orderPollTimeoutMs feature flags. (core#9090)
• Fixed: Clear stale fiatPayment.rampsQuote when a fiat quote fetch fails, preventing the "No quotes" alert from being silently suppressed after a prior successful fetch. (core#9073)

Full upstream changelog: @metamask/transaction-pay-controller@23.6.0.

Changelog

CHANGELOG entry: Fixed fiat payments in MMPay by updating @metamask/transaction-pay-controller to 23.6.0.

Related issues

Fixes:

Manual testing steps

Feature: Fiat payment in MMPay

  Scenario: User completes a fiat payment in MMPay
    Given the user has a wallet set up
    And MMPay is enabled
    And the user is on a flow that supports paying with fiat (e.g. Money Account deposit / Perps / Predict)

    When the user selects a fiat payment method
    And the user requests a quote
    And the user proceeds with the payment

    Then a fiat quote is returned successfully
    And the payment is processed end-to-end without error
    And the on-ramp order is polled until it settles
    And the resulting on-chain transaction (or deposit) is reflected in the account

  Scenario: Fiat quote fetch fails after a previous success
    Given the user previously fetched a successful fiat quote
    When a subsequent fiat quote fetch fails
    Then the "No quotes" alert is shown (no longer silently suppressed)

Screenshots/Recordings

Before

N/A — dependency-only bump, no UI changes.

After

N/A — dependency-only bump, no UI changes.

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.