Connect and secure your account

Select Connect account to open Sign in to your account. Available methods depend on the current environment and authentication capabilities.

For Sign in with passkey, enter the username linked to that passkey. It may be your email address. Complete the browser or device prompt yourself. Use the existing identity associated with your trading account.

Where Google is enabled, follow its sign-in flow. A new registration can also require creation of a device-backed passkey. Google sign-in and a passkey approval serve different purposes: access to a session does not approve later funding actions.

Sign-in establishes a scoped session for the selected account. Account access also depends on completed setup, accepted terms and a valid realtime ticket for private updates.

Available sign-in methods. The sign-in screen offers passkey or Google access according to the current environment. Use a method shown as available for your account.

Session restoration. An unexpired session may be restored in the same browser tab after its account binding is checked. Realtime tickets are single-use and are replaced when restoring access; a restored screen must still recover fresh account state.

Scopes and visibility. Authorization controls access to account-specific interfaces and permitted actions. Your positions are private to your account, so reading them requires an authenticated session or a scoped realtime ticket.

Integrators can follow authentication and sessions for the API workflow.

After authentication, the application may ask you to complete secure account setup and review trading terms and risks. Finish the specific steps shown before attempting to trade. The order ticket explains whether setup, account data, permissions, or a fresh preview is still required.

An account can be signed in while its funding setup is still incomplete. Similarly, a working public chart does not prove that private balances and positions are up to date. Check the account connection state and the funding screen separately.

Verification requirements are shown on Account. Verification status is separate from passkey setup.

Account setup connects your trading account to its Canton identity. Complete that setup, approve funding, and wait for the account to be ready before trading. Once ready, ordinary permitted orders use your authenticated trading access without requiring a separate passkey prompt for every submission.

Deposit and withdrawal flows can ask for more than one approval. Read the action and amount in the application before approving. Only approve a prompt for an action you initiated on the expected site. A later payout claim is a separate step from authorizing a withdrawal.

Never share session credentials, API keys, browser storage, passkey assertions, or one-time authorization codes in chat or screenshots. Support does not need these secrets to investigate an error. See security for account protection guidance.

An API or agent connection requires its own permissions. Read agent access before connecting software to the account.

If the screen says your sign-in is saved, use its reconnect action. If registration was interrupted, continue the retained registration or recovery flow presented by the application. Creating another account is not a substitute for recovering the first result.

If no sign-in method is available, refresh the capability check or return later. If a passkey cannot be found, verify the username, site, device, and passkey provider before trying again. Do not assume that a new Google login restores a missing signing passkey.

If the flow cannot recover, contact Support with the environment, action, time, and displayed error. Do not send credential material.

Complete passkey prompts in your browser or device’s secure authentication interface. Keep passkeys, custody signing material and owner session credentials private. An agent receives its own scoped API key; it cannot use that key to approve custody actions.

Registration recovery continues an interrupted registration, while account-linking recovery restores a verified account connection. Neither replaces a lost passkey. If the available recovery flow cannot restore access, contact Support before creating another account.

The terminal can restore an unexpired session in the same browser tab after checking its account binding. It obtains a fresh realtime ticket and restores account updates before treating displayed balances and positions as current.