Photon Failed Transactions: Every Cause and How to Fix It (2026)

A failed trade on a Solana terminal is almost never mysterious. About nine things go wrong on Photon, they fail in recognizable ways, and most are fixed by a setting you can change in a minute.

One thing first. Photon is a web app, at photon-sol.tinyastro.io. It has no Telegram bot and no bot commands. Advice telling you to message a Photon bot or send it a cancel command is describing a different product.

Disclosure: this site carries referral links to Photon. Using them costs you nothing extra.

Fast diagnostic table

1. Not enough SOL for fees

Symptom. The trade fails right away and your balance does not change. Most often on a sell, right after a buy that used most of the wallet.

Why it happens. A trade on Solana costs more than the trade. Four charges ride along with it:

• The Solana base network fee, charged per signature.
• Your priority fee, paid to validators for faster inclusion, set in Settings.
• Your Jito bribe, paid to Jito validators. Also yours to set.
• Photon's platform fee, a flat 1% of the SOL amount on every buy and sell, per Photon's fee documentation.

All four are paid in SOL by the signing wallet, including on a sell. Selling gives you SOL, but you have to pay for the transaction before it settles. A wallet holding nothing but the token you want to dump, because a maximum-size buy consumed the rest, cannot sell that token.

The fix. Keep a SOL buffer you never trade with, and size buys to leave it intact instead of typing in your full balance. Photon's multi-wallet feature covers up to five of your own wallets and each one needs its own buffer. The fee guides separate what Photon collects from what merely passes through. Only the 1% is Photon's.

2. "Transaction executing" and the retry trap

Symptom. The order neither fails nor fills. It reports that the transaction is executing and stays there.

Why it happens. This is the one item that renders on Photon's SOL FAQ page, and it concerns retries. Your transaction has been submitted and is being resubmitted while it waits to be picked up. A Solana transaction is valid only briefly, so terminals retry inside that window instead of failing on the first miss. It is a normal intermediate state, not an error.

The fix. Wait for it to resolve, then check My Holdings or the wallet on a Solana explorer.

What not to do: press buy again. Every press is a new transaction. If two land, you own twice the position at two different prices and have paid Photon's 1% twice, plus two sets of priority fees and bribes. If the state persists, refresh and check your holdings instead of stacking another attempt.

3. Slippage failures

Symptom. The trade fails with a message about price movement or slippage, usually on new launches or in fast moves.

Why it happens. Slippage tolerance is the maximum gap you will accept between the price you saw and the price you get. Between signing and inclusion the pool moves, and on a thin pool your own order size moves it. When the executed price lands outside your tolerance the transaction reverts, which is the tolerance doing its job.

The fix, and the part most guides get wrong. Raising slippage will get you filled. It also guarantees a worse price when the market is against you and widens the window for a sandwich, where someone buys ahead of you, sells into your fill, and pockets the difference you authorized.

Photon's S1, S2 and S3 presets each carry their own slippage setting alongside their MEV mode, priority fee and bribe. Keep one tight for established pairs and one loose for launches you have decided to chase, instead of pushing a single number up whenever something fails.

The trading guides cover preset configuration; the markets pages show which pairs have real depth.

4. Priority fee and bribe set too low

Symptom. No error, no fill. The transaction is never picked up and eventually goes nowhere.

Why it happens. Solana validators prioritize transactions that pay for priority. When blockspace is in demand, a fee and bribe set on a quiet Tuesday sit behind everyone paying current rates.

How Photon routes it. Smart-MEV Protection does not set the size of your bribe. It decides how the bribe is routed, and the thresholds are documented:

Source: Photon's Smart-MEV Protection and Settings pages.

The fix. If your transactions are being ignored, reach for Auto Speed, since it calibrates from what has actually been confirming rather than a number you picked once and forgot. Manually, raise the priority fee and bribe together and watch whether inclusion improves. Limit and DCA orders carry their own per-order fee and bribe, so a stale number can sit inside an order you placed days ago. Paying up is not always right: on a deep pool where you race nobody, a high priority fee buys nothing.

5. Solana network congestion

Symptom. Everything degrades at once: trades that normally work fail, confirmations drag, and other people are seeing it too.

Why it happens. Not a Photon problem. When Solana is saturated, transactions compete for inclusion and the ones without competitive priority fees get dropped. It clusters around launch frenzies and sharp moves, which is when memecoin traders most want to act.

The fix. Recognize it before you change settings that were fine an hour ago, then either wait the window out or pay a higher priority fee deliberately for its duration. Resubmitting the same underpriced transaction does nothing.

6. Wrong token, illiquid pool, or an impersonator

Symptom. The token page loads but the trade will not route, fills at a nonsense price, or leaves you holding something you did not mean to buy.

Why it happens. Two different problems present the same way.

Illiquidity. A pool with almost nothing in it cannot fill a normal order size. The trade fails or executes at a price that makes your entry unrecoverable.

Impersonation. Anyone can mint a token with any ticker. When a name trends, copies appear within minutes and a ticker search shows several. This is not a Photon bug. The terminal traded the token you told it to trade.

The fix. Verify the mint address, not the ticker. Get it from a source you trust, compare it character by character, and paste it into Photon instead of clicking a search result. Memescope's developer-holding and top-ten-holder filters help you assess a token once you have confirmed it is the right one, but they do not replace checking the address. Security and ecosystem cover the unrelated tokens sharing Photon's name.

7. Missed Pump.fun migration fills

Symptom. You waited for a token to graduate off the bonding curve, tried to catch the first fills on the new pool, and got nothing.

Why it happens. Two reasons worth separating. First, the mechanics changed. On 2025-03-20, Pump.fun began migrating graduated tokens to its own PumpSwap venue instead of to Raydium, reshuffling migration detection across the ecosystem. Tooling built for the old Raydium path stopped seeing the events it watched for. Chainstack's documentation on listening to Pump.fun migrations records the change.

Second, and more directly: Photon does not document a migration sniping feature. No page for it exists in the docs. Memescope surfaces new tokens with bonding-curve progress among its filters, and limit and DCA orders set entries in advance, but none of that is automated migration detection.

The fix. Use limit orders to define an entry you would genuinely be happy with on the migrated pair, and trade it after migration instead of racing for something the platform cannot enter.

8. Deposit not showing, or arriving short

Symptom. You send SOL to your Photon wallet and less shows up than you sent, or nothing shows up.

What is actually reported. A Trustpilot review describes depositing 0.15 SOL and seeing only 0.12 arrive. We report that rather than waving it away, and Photon publishes no official explanation we could locate.

The caveat matters just as much. Some reports of this kind come from people who never used the real platform. Funding a clone looks exactly like this: SOL leaves, the balance does not appear. That is phishing rather than platform accounting, and both land under the same heading.

The fix, in order.

1. Find the signature. Look up your sending wallet on a Solana explorer and compare the transfer against what you meant to send.
2. Confirm the destination against the deposit address in your Photon wallet, in full.
3. Confirm the domain you were on when you copied that address. See the warning above.
4. Allow for confirmation time, and test small on any new wallet before moving size.

If the explorer shows the full amount arriving at the correct deposit address and the balance still reads short, that is a support matter. Read section 10 first.

9. Wallet import problems with Phantom

Symptom. You export your Photon private key, try to import it into Phantom, and Phantom rejects it or shows an empty wallet.

Why it happens. Photon is non-custodial and generates a dedicated Solana wallet per account. The private key is revealed once, at signup, and saving it is on you. That export is also the documented route to mobile: Photon has no native app, and the docs describe it as best experienced through Phantom's in-app browser.

Import failures usually come down to the key rather than either app:

• The key was partially copied, truncated by a selection that missed the last characters.
• The key was transcribed by hand from a screenshot, with the character confusions you would expect.
• The wrong Phantom flow was used. Importing a private key is a different action from restoring a seed phrase, and a key entered into a seed phrase field gets rejected.
• The wallet really is empty, because the funds sit in another Photon wallet. Under multi-wallet, each wallet has its own key.

The fix. Re-copy the entire key in one action, paste it without editing, and use Phantom's import private key option instead of seed phrase recovery. If you never saved the key at signup, that is serious: Photon's Terms of Use state the company has no way of granting you access if you lose control of your wallet. See security and getting started.

10. What to expect from support

Here is the honest version, rather than a resolution path that may not exist. Slow or absent support is a recurring theme in Photon user reviews. Photon publishes no response time commitment and no public ticket system, and the company is pseudonymous with no confirmed legal entity on record. In practice:

• Self-serve first. Almost everything on this page is fixable by you, which is the reliable path.
• Keep your own records. Signatures, timestamps, screenshots. An explorer link is evidence; a description is not.
• Do not send your private key to anyone, including anyone claiming to be Photon support. The request itself is the tell.
• Factor it into your choice of terminal. The comparison cluster covers alternatives, including a detailed Photon vs Axiom comparison.

Before you trade again

• A SOL buffer sits unspent, and buy sizes leave it alone.
• Every wallet you use has its own buffer.
• You know the active preset's slippage, priority fee and bribe.
• Auto Speed is on, or your manual numbers match current conditions.
• Open limit and DCA orders carry current fee settings.
• The address bar reads photon-sol.tinyastro.io before you deposit.
• Your signup private key is saved somewhere you can retrieve it.
• You verify mint addresses instead of clicking tickers.
• You check an explorer before resubmitting an executing transaction.

Photon is a working terminal with real limitations, and this site documents both. If nothing here resolved your issue, try the rest of troubleshooting, the guide library, about and referral.