Connections

This is an enterprise-only feature. Please contact us to enable.

Connections is a hosted wallet-connect page built on the Dynamic SDK. Instead of building a wallet picker yourself, you deploy this page on your own domain and send users to it — as a browser link, an iframe, or a native web view. When a user picks or pastes a wallet, Connections redirects back to a URL you control with the wallet’s public address. It supports external wallets (e.g. MetaMask, Phantom) across 600+ EVM and Solana wallets, plus manual address entry.

Connect-only. Connections never requests a signature or a transaction — it reads only the user’s public wallet address and hands it back to you. This proves the user can present an address, not that they control it. For proof of ownership, add your own sign-in step after the connection.

When to use Connections

Reach for Connections when you want a wallet address without adding the Dynamic SDK to every client:

You want a hosted picker. Link out to one page instead of building and maintaining a wallet list per platform.
You can’t add a third-party SDK. On iOS and Android, a headless mode runs the wallet list and connection logic behind a hidden web view, so your app links no wallet SDK at all.

If you’re already building with the React, React Native, or JavaScript SDK and want full wallet state (balances, signing, embedded wallets), use the SDK directly instead. See Wallets.

How it works

Every platform follows the same contract:

Open the connect page

Open Connections with a redirect_uri you control, and an optional nonce.

https://your-connect-page.example/
  ?redirect_uri=https://your-app.com/wallet/callback
  &nonce=a1b2c3d4e5

Parameter	Required	Description
`redirect_uri`	Yes	Where to send the user back after they connect. Either an `http(s)` URL you control, or your app’s custom scheme (e.g. `myapp://wallet-callback`) for native integrations. Alias: `redirect_url`.
`nonce`	No	An opaque value echoed back unchanged so you can correlate the response to the request. If you don’t send one, none is returned.

The user connects

The user searches Dynamic’s catalog of 600+ EVM and Solana wallets, or pastes an address manually.

Read the result on your redirect

Connections redirects back to your redirect_uri with the result appended as query parameters.

https://your-app.com/wallet/callback
  ?address=0x1a2b3c4d5e6f7a8b9c0d1e2f3a4b5c6d7e8f9a0b
  &chain=evm
  &walletName=MetaMask
  &walletImage=https://.../metamask.svg
  &nonce=a1b2c3d4e5

Parameter	Description
`address`	The connected wallet’s public address.
`chain`	The chain family the address belongs to: `evm` or `solana`.
`walletName`	Display name of the wallet (e.g. `MetaMask`). Empty for a manually-entered address.
`walletImage`	Icon URL for the wallet. Empty for a manually-entered address.
`nonce`	The exact nonce you passed in, present only if you sent one.

Pick your platform to see the full integration:

Web

Link to the hosted page and read the result on your redirect.

iOS

Present it in ASWebAuthenticationSession, or go headless.

Android

Present it in a Chrome Custom Tab, or go headless.

React Native

Present it with expo-web-browser, for Expo or bare React Native.

Flutter

Present it with flutter_web_auth_2, or go headless.

Securing the redirect

redirect_uri is caller-supplied, so an http(s) target is an open-redirect surface. Lock it down before exposing Connections to untrusted callers.

Set VITE_ALLOWED_REDIRECT_HOSTS to the http(s) hosts you accept — bare hostnames, comma-separated, no scheme, no path, no wildcards. Left unset, any host is accepted (with a console warning) so existing integrations keep working.

.env

VITE_ALLOWED_REDIRECT_HOSTS=app.example.com,checkout.example.com

Exact hostname match. example.com does not match sub.example.com. Port is ignored.
Rebuild to apply. Vite inlines VITE_* variables at build time, so changing this needs a rebuild and redeploy — setting it in a hosting dashboard alone does nothing.
Custom app schemes are never host-filtered. Their “host” is a callback name interpreted by your native app, not a network address.

A handful of schemes that can hand off to another app or a browser-internal page are always refused, even in permissive mode: javascript:, data:, intent:, android-app:, market:, content:, chrome:, ftp:, and similar. A refused value falls back to VITE_REDIRECT_BASE_URL and logs a warning — so if your callback never fires, check the browser console first.

Deploying Connections

Connections ships as an open-source app, dynamic-labs-oss/iframe-fb. To run your own instance:

Set your environment ID

Copy .env.example to .env and set your Dynamic environment ID in VITE_DYNAMIC_ENVIRONMENT_ID.

Enable chains and origins

In the Dynamic dashboard, enable the EVM and Solana chains, and add your domain to Allowed Origins.

Serve over HTTPS

Connections mints WalletConnect URIs via WebCrypto, which needs a secure context. Serve the page over HTTPS in production.

Get Started

Integration guides

When to use Connections

How it works

Web

iOS

Android

React Native

Flutter

Securing the redirect

Deploying Connections

​When to use Connections

​How it works

Web

iOS

Android

React Native

Flutter

​Securing the redirect

​Deploying Connections

When to use Connections

How it works

Securing the redirect

Deploying Connections