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 send users to a connect page that supports 800+ EVM and Solana external wallets (for example MetaMask or Phantom), plus manual address entry.

Dynamic hosts a ready-to-use instance at https://connect.dynamicauth.com/. You can also deploy your own instance on a custom domain. See the live demo.

There are two ways to integrate:

Redirect (basic)

Open Connections with a redirect_uri. The user connects a wallet (or pastes an address) and Connections redirects back with the public address. Address-only: no signature or transaction.

Headless

iOS, Android, and Flutter. Render your own native wallet list backed by a hidden web view running the Dynamic SDK. After connecting, you can also sign messages and transactions over the same bridge. Your app links no wallet SDK.

Already building with the React, React Native, or JavaScript SDK? Use the SDK directly for full wallet state (balances, embedded wallets, signing APIs). See Wallets.

When to use Connections

Reach for Connections when you want a wallet address (and optionally signing) 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, Android, and Flutter, headless mode runs the wallet list and connection logic behind a hidden web view, so your app links no wallet SDK. After connect, you can also sign messages and transactions through that same bridge.

How it works

Every platform follows the same redirect contract for the basic flow:

Open the connect page

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

"https://connect.dynamicauth.com/" +
 "?redirect_uri=https://your-app.com/wallet/callback" +
 "&nonce=a1b2c3d4e5" +
 "&environmentId=b1e3aca9-0646-411a-b4ab-c31ce49935b3"

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.
`environmentId`	No	Dynamic environment ID to use instead of the page’s build-time default. Must be a UUID. Invalid values are ignored with a console warning, and the page falls back to its build-time default. For headless, set this before `prewarm()` / `connect()`.

The user connects

The user searches Dynamic’s catalog of 800+ 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 for the full integration guide (including copy-paste harness sources):

Web

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

iOS (basic)

Present it in ASWebAuthenticationSession.

iOS (headless)

Native list via a hidden web view. Connect and sign over the bridge.

Android (basic)

Present it in a Chrome Custom Tab.

Android (headless)

Native list via a hidden WebView. Connect and sign over the bridge.

React Native

Present it with expo-web-browser.

Flutter (basic)

Present it with flutter_web_auth_2.

Flutter (headless)

Native list + message sign and EVM send via a hidden WebViewWidget.

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 NEXT_PUBLIC_CONNECT_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

NEXT_PUBLIC_CONNECT_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. Next.js inlines NEXT_PUBLIC_* 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 the same-origin /callback page and logs a warning. If your callback never fires, check the browser console first.

Get Started

Integration guides

Redirect (basic)

Headless

When to use Connections

How it works

Web

iOS (basic)

iOS (headless)

Android (basic)

Android (headless)

React Native

Flutter (basic)

Flutter (headless)

Securing the redirect

Redirect (basic)

Headless

​When to use Connections

​How it works

Web

iOS (basic)

iOS (headless)

Android (basic)

Android (headless)

React Native

Flutter (basic)

Flutter (headless)

​Securing the redirect

When to use Connections

How it works

Securing the redirect