docs
Get startedTroubleshootingPaymentsWebhooksAgent paymentsSwop MCPOviIdentity (swop.id)SwivyRPC (preview)API reference

Setup & passkey troubleshooting

Diagnose console enrollment, customer login delivery and project setup failures.

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

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

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

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

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; an unavailable balance is not a zero balance.

Which URL should I use?

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

On this page