How to Configure Standalone TON Connect Mode in the Omniston Widget

Use the STON.fi swap widget with wallet connectivity built in, without creating or managing a separate TON Connect instance.

Standalone TON Connect mode is the simplest way to give an embedded Omniston Widget its own wallet connection flow. You provide the widget with the URL of your TON Connect manifest, mount the widget on the page, and the widget initializes TON Connect internally. You do not need to install or configure a separate TON Connect package just to make the swap widget work.

That makes standalone mode a good fit for landing pages, lightweight dApps, dashboards, and websites where the Omniston Widget is the main feature that needs wallet access. The important limitation is just as simple: if your application already has its own TON Connect instance, standalone mode is no longer the right choice. In that case, the widget should reuse the existing connection through integrated mode. What standalone mode actually does

The Omniston Widget supports two TON Connect configurations: standalone and integrated.

With standalone mode, the responsibility boundary is clear. Your application provides the TON Connect manifest and a DOM element where the widget should appear. The widget handles its own TON Connect initialization and uses that connection when a user needs to connect a wallet and approve a swap.

The minimal structure is:

You are not passing an existing TonConnect or TonConnectUI instance into the widget. The widget creates the TON Connect layer it needs internally. STON.fi documents this mode specifically for smaller applications or sites that only need the swap flow supplied by the widget.

The practical split looks like this:

Your app hosts the TON Connect manifest. Your app loads and mounts the Omniston Widget. The widget manages its TON Connect instance. The wallet still presents connection and transaction requests to the user. The user remains responsible for approving or rejecting the wallet action.

Standalone does not remove wallet approval. It removes the need for your application to build the wallet connection layer separately. Prepare the TON Connect manifest first

Before initializing the widget, create a tonconnect-manifest.json file for your application.

The manifest tells compatible wallets which application is asking for a connection. TON Connect defines required fields for the application URL, application name, and icon, while terms of use and privacy policy URLs are optional.

A minimal manifest could look like this:

A more complete version might be:

The manifest needs to be publicly reachable. TON Connect documentation says wallets must be able to fetch it without authentication, restrictive CORS rules, or proxy challenges that block automated requests. HTTPS should be used, and the application icon should use a compatible raster format such as PNG or ICO rather than SVG.

STON.fi's widget guide specifically instructs integrators to create and host their own manifest and says the manifest URL should be…