User rejected transaction: was anything spent?

If you rejected a transaction request before signing, that request did not authorize a new transaction. You do not owe blockchain execution gas merely for opening and rejecting a normal wallet confirmation.

The Ethereum provider standard defines user rejection as a distinct request error. An application can also show a broad “rejected” message for an unsuccessful interaction, so check what the wallet actually recorded.

Review earlier steps separately

You may have approved the token before rejecting the swap. That approval can already be confirmed, cost gas and leave an active allowance. Rejecting the later prompt does not reverse it.

You may also have accepted another request in a different tab. Check activity when the interface is confusing rather than assuming the most recent rejection cancels everything associated with the trade.

If you did not press Reject

Inspect the detailed error and device screen. A closed prompt, unsupported signing path or lost mobile session may be presented through an application’s simplified wording. Report the actual wallet message, request type and connection method to support.

When retrying, generate a fresh quote if time has passed. Read the new request from the beginning: output, recipient and permission scope can change. If the prompt requests an unrelated approval or an unexplained signature, rejection remains the appropriate way to avoid authorizing that request.

No support agent needs your recovery phrase to investigate a rejected request. Public transaction history and nonsecret error details are enough to establish whether an earlier onchain action occurred.