# Setup & passkey troubleshooting (/docs/swivy/troubleshooting)

## Add passkey does nothing [#add-passkey-does-nothing]

Open the console directly over HTTPS in a WebAuthn-capable browser such as Chrome or Safari. Embedded browsers may not support the native credential prompt. For a YubiKey, open **Account security → Add security key**, insert the key and complete its PIN/touch prompt. Cancelling leaves enrollment incomplete.

If the browser reports that passkeys are unavailable, use the suggested external browser. Do not disable server-side approval requirements to work around a browser limitation.

## Existing passkey is not found [#existing-passkey-is-not-found]

Credentials are tied to the domain where they were enrolled. A passkey from another console domain may not be available here. Sign in by email on the current console, then enroll a passkey or YubiKey there. Console credentials and customer credentials are separate.

## Customer code never arrives [#customer-code-never-arrives]

Confirm that email or SMS login is enabled for the **selected environment** and its delivery provider is configured. Check provider status, delivery logs, the destination and spam folders. Respect retry/rate limits. Console sign-in delivery and customer delivery are separate checks.

## Setup fails or stalls [#setup-fails-or-stalls]

Read the error inside the setup dialog. The retry button is restored after a failure. Before retrying after a lost response, check Overview for the project to avoid duplicate setup. Completing an existing project's protected settings may require your console passkey.

## Wallet creation or signing is refused [#wallet-creation-or-signing-is-refused]

Check the enabled chain/network, RPC route, wallet custody policy and the customer's session. Signing may require a customer step-up even though the console operator is already signed in. Inspect the returned error and intent state in the [API reference](/docs/swivy/api-reference); an unavailable balance is not a zero balance.

## Which URL should I use? [#which-url-should-i-use]

- [Swivy documentation](/docs/swivy): this section of Swop Docs.
- [Console](https://swivy.swopme.co/): project setup and administration.
- [Live API reference](https://swivy.swopme.co/docs#reference): the deployed contract.
- **API base URL:** copy it from your environment's Integrations bundle.

Staging supports testing with test assets and software custody. These checks do not establish production readiness.
