FRENT pauses checkout when your wallet, network, balance or approval needs attention. The message tells you what is missing before you decide whether to continue in MetaMask Mobile.
- No seed phrase—ever
- Exact USDC approval
- Wait before retrying a submitted payment
Read the signal before you act
What FRENT is checking at each pause.
A clear warning is a guardrail. It gives you time to verify the request instead of pushing you through a wallet prompt.
Before approval
Connection and balance checks protect the setup.
These messages appear before FRENT can prepare the correct payment. No payment transaction has been submitted at this point.Wallet not connected
Connect MetaMask Mobile on the payment network to continue.
- Why you see it
- FRENT needs your public wallet address and selected network to check the payment requirements. Connecting reveals the public address; it does not give FRENT your private key or permission to move funds.
- Safe next step
- Open the checkout in MetaMask Mobile, connect the account you intend to pay with and return to the checkout.
No transaction submitted
Wrong network
Switch MetaMask Mobile to Base or Polygon to continue.
- Why you see it
- USDC balances and contracts are network-specific. FRENT stops instead of treating a token on another chain as the requested payment asset.
- Safe next step
- Use the network named in the checkout. Switching networks alone does not send a transaction.
No transaction submitted
Not enough USDC
This wallet does not have enough USDC on the selected network.
- Why you see it
- The wallet balance is lower than the exact payment amount. USDC held on another network or a different token variant cannot satisfy this request.
- Safe next step
- Fund this same wallet with the supported USDC on the selected network, then let FRENT check the balance again.
No payment submitted
Not enough network fee balance
This wallet needs native currency for network fees.
- Why you see it
- The blockchain charges a network fee to record an approval or payment. FRENT checks for ETH on Base or POL on Polygon before asking you to continue.
- Safe next step
- Add enough of the named gas asset to this wallet. Network fees are separate from the merchant’s USDC amount.
No payment submitted
Inside MetaMask
Each approval has one specific purpose.
MetaMask remains the place where you decide. Read the network, token, amount and contract interaction before confirming.USDC approval required
Approve this exact USDC amount to continue.
- Why you see it
- USDC is an ERC-20 token. The merchant’s onchain POS needs an allowance before it can process the requested amount. FRENT requests the checkout amount instead of an unlimited allowance.
- Safe next step
- Confirm only when the token and amount match the checkout. This approval is recorded onchain, but it is not yet the merchant payment.
Permission step—not payment
Payment approval required
Review and approve the payment in MetaMask Mobile.
- Why you see it
- This is the transaction that calls the merchant-specific POS contract. It remains separate from token approval so you can review the final action.
- Safe next step
- Check the merchant, amount, token and network shown by FRENT. Reject the request if anything differs from what you intended to pay.
Funds move only after confirmation
Request rejected
The last MetaMask request was rejected. Try again when ready.
- Why you see it
- Rejecting is a valid safety choice. FRENT does not treat a dismissed wallet prompt as approval.
- Safe next step
- Review the checkout again. Retry only if you recognize the merchant and agree with every payment detail.
No new transaction submitted
After submission
A submitted payment needs verification, not a duplicate.
Once MetaMask has submitted the payment, the network—not a browser animation—decides its outcome. Wait for FRENT to verify the onchain result.Waiting for confirmation
Payment submitted. Waiting for onchain confirmation…
- Why you see it
- The network has received the transaction, but it is not final yet. Confirmation time can vary with network conditions.
- Safe next step
- Keep the page open and check MetaMask activity or the linked block explorer. Do not create a second payment while this one is pending.
Transaction already submitted
Live update delayed
Live update delayed. Retrying automatically…
- Why you see it
- The browser temporarily could not fetch the latest FRENT status. That connection issue does not cancel, confirm or reverse an onchain transaction.
- Safe next step
- Wait for automatic retry. If MetaMask shows a transaction hash, use payment lookup or the network explorer before attempting another payment.
Check status before retrying
Payment expired or failed
This payment can no longer be completed.
- Why you see it
- A checkout can expire before submission, or an onchain attempt can fail. A failed transaction may still consume a network fee even when no USDC reaches the merchant.
- Safe next step
- Check the final FRENT status and transaction explorer. Ask the merchant for a fresh request only after confirming the original was not paid.
Verify the final status first
Before you approve
Five checks. Then pay.
Stop if a wallet prompt is unexpected or does not match the checkout. A legitimate payment never becomes safer because someone asks you to hurry.
- 01
The payment page uses pay.frent.tech, opened from the merchant’s QR code or payment link.
- 02
The merchant, USDC amount and selected Base or Polygon network match what you agreed to pay.
- 03
A USDC approval is limited to the amount required for this checkout—not an unexpected unlimited amount.
- 04
You never share a Secret Recovery Phrase, private key or screen-sharing access with FRENT, the merchant or support.
- 05
After a transaction is submitted, you verify its status before trying again.
Questions, answered plainly
Payment safety FAQ
Does a FRENT warning mean my USDC already moved?
Usually no. Connection, network, balance and approval-required messages appear before the payment is submitted. When the page says submitted or confirming, check MetaMask, FRENT payment lookup or the block explorer before trying again.
Why can MetaMask show two confirmations?
The first transaction may approve the exact USDC amount for the merchant’s POS contract. The second submits the actual payment. FRENT skips the approval step when a sufficient allowance already exists.
Why do I need ETH or POL when I am paying in USDC?
Base and Polygon charge a network fee to process onchain transactions. FRENT currently checks ETH for Base or POL for Polygon separately from the USDC payment amount.
Should I retry when the browser says the live update is delayed?
Not immediately. A browser connection problem does not determine the blockchain result. If MetaMask already submitted a transaction, verify its status before creating or approving another payment.
Will FRENT or a merchant ever need my recovery phrase?
No. Never share a Secret Recovery Phrase or private key. FRENT checkout uses your public wallet address and explicit MetaMask approvals; neither FRENT nor a legitimate merchant needs wallet recovery credentials.
One final rule
Trust matching details—not pressure.
A safe checkout gives you time to compare the merchant, amount, token and network. If MetaMask or FRENT shows something unexpected, reject the prompt and verify the payment before continuing.