> ## Documentation Index
> Fetch the complete documentation index at: https://docs.dynamic.xyz/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Go Live Checklist

> [accordion] Review Settings
>
> * Review the [general settings](https://docs.dynamic.xyz/docs/platform/console/general.md) and apply the correct ones for your project.
>
> * If using a web SDK (React, JavaScript), review the [security settings](https://docs.dynamic.xyz/docs/platform/console/security.md) and make sure your CORS is set up correctly for your live deployment. Native SDKs (React Native, Flutter, Swift, Kotlin) do not require CORS configuration.

> [accordion] Use cookie-based auth
>
> > [!TIP]
> >
> > This is our top recommendation before going live. Cookie-based auth is the most secure foundation for your integration.
>
> For web SDKs (React, JavaScript), we recommend [cookie-based authentication](https://docs.dynamic.xyz/docs/auth/dynamic-auth/auth-methods.md#cookie-based-authentication). It avoids many security issues: the JWT is stored in an HttpOnly cookie, so it is not accessible to client scripts—reducing the risk of XSS stealing the token—and it provides a better foundation for device registration and session management. The overview links to SDK-specific setup guides.

> [accordion] Implement step-up authentication & device registration
>
> > [!WARNING]
> >
> > Both of these are required before going live. Without them, users will be blocked during login or sensitive actions.
>
> **Step-up authentication** requires users to re-verify their identity before performing sensitive actions like wallet export, wallet sign, and credential linking. See the [step-up authentication overview](https://docs.dynamic.xyz/docs/auth/step-up-auth.md) for implementation guides per SDK.
>
> **Device registration** protects accounts from takeover by verifying users when they sign in from an unrecognized device. See the [device registration overview](https://docs.dynamic.xyz/docs/get-started/security/device-registration.md) for implementation guides per SDK.
>
> If you have a headless integration, see your SDK's [Authentication screens](https://docs.dynamic.xyz/docs/get-started/migrations/api/2026_04_01.md#implementation-guides) page for implementation details.

> [accordion] Consider Multi-wallet
>
> Multi Wallet allows users to connect and handle multiple wallets at once, and
> is a great UX boost for end users. Consider turning it on after reviewing the
> [multi-wallet support section](https://docs.dynamic.xyz/docs/react/wallets/external-wallets/multi-wallet.md).

> [accordion] Enable Information Capture
>
> Make sure you're capturing all the user information you need via [Information
> capture](https://docs.dynamic.xyz/docs/react/users/information-capture.md).

> [accordion] Choose your plan
>
> Make sure to choose the right Dynamic
> [plan](https://console.dynamic.xyz/dashboard/admin#subscription) for your needs. -
> All features are free on sandbox, but if you're using [any advanced
> features](https://www.dynamic.xyz/pricing) you'll need to upgrade to a paid
> plan.

> [accordion] Switch to live mode
>
> There are two different modes to operate Dynamic in: Sandbox and Live. You can
> learn more about them [here](https://docs.dynamic.xyz/docs/platform/console/sandbox-vs-live.md). To switch
> to live mode, you'll need to do so in the Dynamic Console. Remember that the
> environment ID differs between sandbox and live, so make sure to also update
> that in your own code.

> [accordion] Turn on MFA
>
> If you haven't done so already, before going to production we highly recommend turning on MFA for your account. You can do this in the [security settings](https://console.dynamic.xyz/dashboard/security).

> [accordion] Test all the things
>
> We test all the time, but it's also worth you running through your implementation from a few different angles, here are some common testing cases that might be useful to double check:
>
> * Cross device
>
> * Embedded wallets (if you are using)
>
> * Transactions
>
> * New vs existing user flow
>
> * Step-up authentication
>
> * Device registration

> [accordion] Drop us a line!
>
> Let us know how it's going! Drop a line to [dynamic@fireblocks.com](mailto:dynamic@fireblocks.com) or join
> [Slack](https://dynamiccustomers.slack.com/) - if you like, we can give your
> implementation a test and offer advice. We'll also check that your
> implementation is ready for launch.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.