Start typing to search this publication.
crypto.news logo crypto.news
Open menu
crypto.news logo

Subscribe to crypto.news

Get new posts delivered straight to your inbox.

Matcha Swap Success Does Not Prove Tokens Reached Your Wallet

crypto.news avatar crypto.news
4 min read

Matcha swap success means the identified transaction executed, but it does not alone prove that the token you expected reached your account. The swap receipt shows what happened in that transaction; the recipient’s on-chain holdings show whether the asset is there. A missing entry in your wallet can be a display problem, so start with the transaction hash before judging the outcome.

For a completed swap on one network, the useful questions are: Was this hash for the swap itself? Which token contract sent output, and to which account? Does that account hold the token now? Those answers separate transaction execution, delivery, ownership and wallet display.

Did the Swap Transaction Actually Run?

A swap ran only if the successful hash belongs to the swap transaction, rather than an earlier token approval. An approval gives a contract permission to spend your input token. It can succeed even if you never submit the trade, so an approval receipt cannot establish that you received output.

One attempted trade can therefore leave more than one successful hash in your wallet history. In an illustrative attempt to swap crypto on Matcha, the Matcha swap service may first prompt an approval for the input token and then a separate transaction for the routed trade. Open each hash on an explorer for the network you used and identify what it did. An approval records permission; the later swap transaction is the one whose result matters here.

Once you have the swap hash, its receipt should report success and show the events produced during execution. On an Ethereum-style network, a successful receipt means the transaction completed without reverting. It does not, by that status alone, identify the asset delivered to you. The transaction’s “to” address may be a swap contract, while the output token’s transfer record names the receiving account. Reading the token transfers alongside the receipt is more informative than relying on a completion message in the interface.

Who Received Which Asset?

The intended delivery is established by the recipient account, the network and the exact output asset. Compare the address in the final output transfer with the account you control, then compare the token’s contract address with the asset you selected. A ticker is insufficient: different contracts, and tokens on different networks, can display the same symbol.

For an ERC-20 output, look for the token contract’s Transfer event in the Matcha swap receipt or in the explorer’s decoded token transfers. A routed trade can move tokens between several contracts before its final output reaches a wallet. Follow the transfer whose recipient is your account, rather than treating every transfer in the route as your payout. The amount there is the on-chain amount to compare with your holdings.

The balance query is the next stage, and it needs the right inputs. You must already have the swap hash and know the recipient address, network and token contract; otherwise a zero balance may simply be a query for a different asset or account. View that contract’s balance for the recipient on the same network. If the transfer record and balance agree, you have evidence of delivery even when the wallet’s asset list is empty. If they do not, inspect the account’s later activity before deciding the output never arrived.

Why Is the Asset Absent From My Wallet?

The asset can be absent from the wallet display because the wallet has not detected it, has not indexed the latest activity, or is showing another network or account. In a Matcha crypto swap, an on-chain token balance and a wallet’s visible token list are different things. Once the correct contract shows a balance for your address, adding that token to the wallet’s display can make the existing holding visible; it does not create a transfer or recover a missing one.

Native ETH and wrapped ETH, or WETH, provide a particularly easy mismatch. Native ETH appears in the network’s coin balance, while WETH is an ERC-20 token with its own contract balance. They have related value, but a receipt showing WETH delivered will not make the native ETH balance rise. Conversely, native ETH output will not appear as a WETH token transfer. Use the asset specified by the actual output record when deciding where to look.

Wallet indexing may also lag behind a confirmed transaction. If the explorer shows the right recipient and token balance, refresh the wallet, select the matching network and display the token by its verified contract address. The chain record is the evidence of ownership; the wallet entry is a view of it.

Can a Successful Receipt Coexist With a Zero Balance?

Yes: the output may have reached your account during the swap and then left in a later transaction. A current balance describes what the account holds now, while the swap receipt describes what happened at the time of the trade. Review transfers for that exact token contract and recipient after the swap’s block. A later send, another trade or a contract interaction that spent the token can explain the difference.

If the swap receipt shows no expected output to your account, a zero balance calls for closer examination of the transaction, not another swap. Keep the swap hash, network, expected token contract and intended recipient together when investigating. Those details let you distinguish an unexpected route or recipient from a wallet display issue without putting more funds into a new trade.

Does Cross-Chain Source Success Prove Delivery?

No. For a Matcha cross-chain swap, success on the source network establishes that its transaction executed; delivery on the destination network is a separate event. Use the trade’s cross-chain status and any destination transaction hash to inspect the receiving account and output asset on the destination network. A source receipt alone cannot answer whether the destination transfer completed.

For a completed same-chain trade, the decisive relationship is simpler: the swap receipt identifies the output event, and the correct account’s token balance tells you whether that output is still held.

Subscribe to crypto.news