Why did Backpack say transaction failed?

Most failures are insufficient SOL for payment plus network fee, wrong network (Devnet instead of Mainnet Beta), user cancelled the approval, or the transaction expired before validators confirmed it. Less often the site did not detect a successful on-chain payment yet.

I approved in Backpack but the site says failed — did I lose SOL?

If Backpack showed a success screen and you have a transaction signature, the payment likely landed on-chain even if the site UI lagged. Look up the signature on Solscan or the transaction lookup tool. If Backpack rejected before signing, no SOL moved.

What does simulation failed mean in Backpack?

Backpack simulates the transfer before you approve. Simulation failed usually means insufficient balance for amount plus fee, wrong network, or an invalid recipient. Fix balance or network, refresh, and try again.

How long should I wait after paying?

Solana mainnet usually confirms in a few seconds. If the site has detect-and-roll, tap it after approval. If still stuck after 30 seconds, paste the transaction signature from Backpack activity or Solscan.

Troubleshooting

Fix Backpack transaction failed

You tried to pay on a Solana site and Backpack or the page showed transaction failed, simulation failed, or nothing happened after you clicked approve. This guide walks through the most common causes — cancelled approval, balance, wrong network, popups, expired blockhash, and site detection — then lets you retry a 0.001 SOL practice roll below.

Try below Mainnet only From 0.001 SOL Free demo first

Quick diagnosis — match your symptom

What you see	Likely cause	Fix
Cancelled / rejected / denied in Backpack	You closed the approval or clicked reject	Click pay again and approve — nothing was charged
Insufficient funds / simulation failed	Balance less than payment + network fee	Add SOL — keep ~0.002 SOL extra for fees
Payment sent but site stuck	On-chain success; UI not updated yet	Solana Pay detection fixes or verify payment
Balance shows SOL but pay fails	Backpack on Devnet / wrong network	Switch to Mainnet Beta
No Backpack popup at all	Browser blocked popups or wallet disconnected	Allow popups + reconnect
Network busy / blockhash expired	RPC delay or slow confirmation	Refresh page, reconnect wallet, try again in a few seconds
Failed on Solscan	On-chain rejection (rare for simple transfers)	Use transaction lookup for error details

1. You cancelled or rejected in Backpack

If you closed the approval window or tapped Reject, Backpack correctly reports failure — no SOL left your wallet. This is not a bug.

Click Pay and roll (or connect wallet) on the site again.
When Backpack opens, review recipient and amount.
Tap Approve or Confirm to complete the transfer.

On mobile, open the site inside Backpack's in-app browser if the extension popup never appears — see connect Backpack to a dApp.

2. Insufficient SOL or simulation failed

Backpack checks whether your wallet can cover payment amount + network fee before signing. A 0.001 SOL roll still needs a few thousand extra lamports for the base fee.

Fix insufficient SOL — balance table and how much to add.
Send SOL with Backpack — fund your wallet on mainnet.
Transaction fees explained — what the network charges.
Wallet balance checker — confirm mainnet SOL before retrying.

3. Wrong network (Devnet vs mainnet)

Devnet SOL looks real inside Backpack but cannot pay live mainnet apps. If payments fail despite a visible balance, check the network label first.

Switch Backpack to Mainnet Beta

4. Popup blocked or wallet not connected

Wallet connect and payment both need Backpack's approval popup. If the browser blocks it, the site may show a generic error with no transaction ID.

Allow popups for the site (click the blocked-popup icon in the address bar).
Refresh the page and click Connect wallet again.
Disable competing wallet extensions temporarily if Backpack never opens.
Try a private window with only Backpack enabled.

Full walkthrough: connect Backpack to a Solana site.

5. Approved in Backpack but the site did not update

Sometimes the transfer succeeds on-chain while the page UI is still waiting. Do not pay twice until you verify.

Wait 5–10 seconds — mainnet usually confirms quickly.
Tap I've paid — detect and roll if the site offers it.
Copy the transaction signature from Backpack activity or Solscan.
Paste the signature into the detect field or use our transaction lookup tool.

Step-by-step: verify a Solana payment on mainnet.

6. Network busy or expired blockhash

If validators are congested or your connection is slow, the prepared transaction can expire before you approve. The site may show Network busy — please try again.

Refresh the page.
Reconnect Backpack if the session dropped.
Retry the payment — a new blockhash is fetched automatically.

Persistent RPC errors are rare on Garden Dice (same-origin /rpc proxy with fallback). If problems continue, try again on a stable connection or mobile data.

Retry after fixing

Confirm Mainnet Beta, enough SOL, and popups allowed.
Try the free demo above — no wallet needed.
Use the pay panel: connect Backpack or scan the Solana Pay QR.
Approve once; wait for detect-and-roll or paste your signature.

First payment walkthrough Play with Backpack

FAQ

Does failed mean I was charged?

Only if Backpack showed success and you have a transaction signature on mainnet. Cancellations and simulation failures do not move SOL. Look up any signature before paying again.

Why does Garden Dice say failed when Solscan shows success?

Detection can lag a few seconds. Use detect-and-roll or paste the signature. See the verify-payment guide for the full flow.

Should I increase the roll amount if it keeps failing?

No — a higher amount needs more SOL, not less. Fix balance, network, or popups first. Start with 0.001 SOL once basics work.

Backpack locked or asking for password repeatedly

Unlock Backpack, complete any pending update, then refresh the site. If the wallet extension crashed, restart the browser.