After Declining a Wallet Prompt: Check What Was Rejected

Declining a wallet prompt is a valid decision. Diagnose the request you declined before interpreting an application error or considering another attempt. A rejection message alone is not a transaction receipt.

Identify the prompt category

Write down whether the prompt asked to expose an account, change a network, sign a message or send a transaction. EIP-1193 assigns code 4001 to a user rejection; code 4100 instead concerns missing authorization. Interfaces may display different wording or wrap these errors. Preserve the numerical code if available, but do not assume every message containing “rejected” has the same origin. The request category tells you what evidence to look for next.

Reconstruct the sequence

Consider a hypothetical two-step workflow: one permission was accepted, then a later transaction was declined. Rejecting the later step does not undo the earlier permission. Make a short timeline with one line per prompt and your response. If a transaction hash already exists from an earlier step, inspect that transaction independently. Avoid summarizing the whole sequence as “nothing happened” solely because the final dialog was closed.

Retry only a request you understand

If you intentionally declined, keep the action stopped. If the dismissal was accidental, first revisit the domain, account, network and requested action. Open only one deliberate request at a time so an older prompt cannot be mistaken for a new one. Never accept a broader permission simply to clear an error. If the interface keeps reopening a prompt, close that interaction and investigate before continuing.

Apply the distinction to this website

RunixCoin’s public Base estimate form cannot execute a swap. Its quote errors therefore do not establish that an onchain trade was declined or reverted. A browser-wallet connection prompt, if used in another interface path, is a separate event from a completed swap. For a useful report, describe the visible control, prompt category and sanitized error code. Do not attach a signed message, wallet backup or unredacted provider response to prove what you saw.

References and verification

Reviewed . Product limits reflect inspected public interface code. These are educational checklists, not reports of tested mainnet transactions; browser behavior and execution were not verified.