MetaMask Money Conversion Failed: Can I Retry Missing mUSD?

A MetaMask user described a confusing split: a small USDC-to-mUSD conversion worked, but a larger one showed Failed. The Money Account total seemed to move, yet the amount was absent when they tried to send it. Their question was practical: Can I retry? The post does not give an app version; MetaMask currently lists Money Account for Mobile v8.0+ and Extension v13.51+.

I would pause before converting again. The screen alone does not show whether the first attempt settled, is still being reflected in the balance, or genuinely failed. The safer first check is the Money Account Activity entry, followed by a refresh and a comparison of the Money Account and source-account amounts. MetaMask's Money Account FAQ says a deposit can take about 30 seconds to appear in the balance, and a force-closed app can even show a misleading Failed label. That describes a possible display issue; it does not prove what happened in this particular user's case.

Why the Money total and sendable amount might disagree

Here is an illustrative way to work through the screen; HideFi did not perform the conversion in the post. I would first write down the time and amount of the attempt, then open Money → Activity. If the conversion is present, its entry is a better clue than the large total at the top of the account. MetaMask specifically tells users to check the Activity tab for a deposit before treating a delayed balance as missing. The FAQ allows for a short balance display delay, but it does not say that an ongoing mismatch is harmless. That calls for verification, not another signature.

The product's own conversion illustration shows a Conversion complete confirmation after a successful attempt. That is different from the Failed state in the user's report; the screenshot below is an official example of the successful screen, not evidence that this user's transaction succeeded.

Check the first attempt before deciding whether to retry

1. Look in Money Account Activity. Find the attempted conversion by time and amount. If it appears there, note the exact status. A Failed label can be a display error if the app was force-closed during a pending transaction, according to MetaMask. Do not assume that explanation when you did not force-close the app or the amounts still disagree.
2. Refresh the Money screen. On Mobile, pull down to refresh and allow the short refresh cycle described in the official FAQ. Then compare the mUSD shown in Money Account with the USDC left in the source account. The source balance helps reveal whether the input was actually consumed; the Money balance helps show whether the output became available. Neither number alone explains an inconsistent Activity entry.
3. Stop if the records do not reconcile. If Activity says Failed but the source USDC is gone, or Money shows a changed total while the amount remains unavailable to send after refreshing, avoid repeating the conversion. Save the time, amount, app version and screenshots with private details hidden, then use MetaMask's official support route. The original public report did not include a confirmed resolution.

This sequence is deliberately read-only until the first attempt is understood. A fresh quote or a second signature could create a second transaction; it is not a repair for an unexplained balance difference. Do not reset the wallet to force a balance update; if the records stay inconsistent, use official support.

When is it safe to try again?

Only after you can establish that the earlier conversion truly failed, the source USDC is still available, and no mUSD from that attempt is pending or credited should you consider starting a new conversion in MetaMask's current flow. A displayed Failed word alone does not establish all three. If any part remains uncertain, ask official support to interpret the account's state first. Never give anyone your Secret Recovery Phrase or follow a direct message offering to “fix” the conversion; MetaMask says its support does not initiate help by DM.