For users, the closing confirmation serves as a basic safety measure if you have unsaved actions, such as forms or drafts, in progress. It does not confirm transaction success or wallet signature validity. Users must independently check wallet approvals or transaction states, as closure warnings do not indicate security of data or funds. Developers should apply this prompt specifically to scenarios where users have incomplete work, and must not use it in place of proper transaction or security confirmations.
How Closing Confirmation Works in Mini Apps
Mini Apps on Telegram can trigger a closing confirmation prompt when users attempt to exit the app’s webview, whether by swiping down or navigating away. Developers use the web_app_setup_closing_behavior event to programmatically control this prompt. Its main function is to prevent users from losing unsaved data—such as incomplete forms, unfinished drafts, or other progress—directly within the Mini App interface.
Critically, the confirmation prompt does not handle or validate payments, wallet signatures, or blockchain transactions. It is wholly separate from wallet approval dialogs or server-side security checks. Users should not interpret a closing warning as evidence that an action was saved or securely processed.
For developers, this function should be used only when genuine unsaved progress is present. It adds a browser-level precaution against accidental data loss, but does not protect funds, tokens, or identities. Payment interactions, wallet signatures, and other sensitive actions always require proper, explicit prompts—never just a closing warning.
What Closing Confirmation Does Not Protect
The closing confirmation mechanism only prevents accidental exit from a Mini App webview and is not a transaction approval, server verification, or wallet signing step. When enabled, users will see a warning before leaving if there are unsaved changes or unfinished actions. This reduces the risk of losing progress, but the prompt does not interact with payment flows or blockchain activity.
Users must not mistake closing confirmation for any kind of payment, wallet, or transaction approval. Telegram's documentation confirms that this event does not cover on-chain activity, payment transmission, or any blockchain-specific approval process. Completing a transaction or signing a wallet action does not generate a closing confirmation automatically.
Builders should not rely on closing confirmation as a security function. All confirmed actions—like sending tokens, connecting wallets, or submitting important data—require clear, direct UX and transparent server or blockchain confirmations, entirely separate from accidental closure warnings.
TON Drop Hub take: Using closing confirmation as a replacement for explicit transaction or wallet approval increases risk for both users and projects. It should be reserved purely for protecting unsaved data from accidental loss within the Mini App webview.
Practical Checks Before Interacting With Mini Apps
Within Telegram, Mini Apps are web-based experiences, and some enable closing-confirmation prompts when you try to exit during unfinished work. The prompt only appears if requested by the developer for actions like filling out a form or composing a draft. This popup is useful to prevent lost progress, but it does not confirm or validate payments, wallet actions, or server-side results.
Do not treat closing confirmation as a sign of security. Its sole purpose is to confirm whether you want to leave with unsaved work—it does not prove that payments were made, forms were sent, or transactions were finalized. Always verify wallet signatures, payment flows, or server acknowledgments at their source outside the closing confirmation popup.
TON Drop Hub take: Closing confirmation protects from accidental browser closures, not financial or cryptographic risk. Always double-check wallet, payment, and permission prompts. Verify a Mini App’s legitimacy and permissions before proceeding with any sensitive action.
Mini App closing confirmation is a user-experience feature for preventing the loss of unsaved progress when closing a webview. It cannot validate payments, process wallet signatures, or guarantee any blockchain transaction is complete. It is a simple “are you sure you want to close this window?”—not approval for sensitive or on-chain actions.
TON Drop Hub take: Recognize that closing confirmation is only a prompt to avoid data loss. For any transaction, payment, or wallet action, always rely on explicit wallet or payment confirmations and never treat the closing confirmation as a guarantee.
For more guides on Telegram, TON Mini Apps, and safety features, see TON guides.
Source reference: original source.