SID Verify

sid-verify appears when the account creation process did not complete cleanly. It is almost always seen immediately after a first login attempt on a new account. There is no email verification step — if you see this error, the account setup itself needs attention.

When sid-verify occurs

sid-verify is specific to the account creation flow. It appears when a login attempt succeeds at the key-matching level — the access key was recognized — but the account record is in an incomplete or unconfirmed state that prevents the dashboard from opening. This is distinct from sid-session, which is about the session being expired, and from a login failure, which is about the key not matching at all.

The most common cause is an interrupted checkout. If the checkout process was disrupted before it fully completed — a browser crash, a network interruption, a payment processor timeout — the account may have been partially created. The key was issued and shown (or not shown, if the confirmation page was not reached), but the account is flagged as pending rather than active.

A less common cause is a delay in processing on the account creation side. If you are logging in within seconds of completing checkout, the account creation may not have fully propagated yet. Waiting two minutes and trying again resolves this in most cases.

No email verification required

StatelessID does not send email verification messages and does not require you to click a link in an inbox before your account activates. If you are expecting a verification email that never arrived, that email does not exist. The account does not activate through email.

If someone told you to check your email for a verification link, that information is incorrect. The account activates when checkout completes and the access key page is displayed. If you reached that page, the account should be active. If sid-verify persists after a successful checkout, the issue is in the account creation record, not in any email step.

What to do when sid-verify appears

First, wait a few minutes and try logging in again. If the account was in a propagation delay, a short wait resolves it. Log out completely, clear your browser cache for statelessid.com, and attempt login fresh. A clean session attempt after a delay is the first step for any sid-verify that appeared immediately after a successful checkout.

If sid-verify persists beyond a few minutes for an account you just created, check whether you have a payment receipt from the checkout. If a receipt exists, the payment completed and the account should have been created. Contact support with the receipt as proof of purchase — support can verify the account status and correct an incomplete account record.

If you never received a receipt and sid-verify persists, the checkout may not have completed and no account was created. The key shown — if one was shown — may have been issued tentatively before the payment was confirmed. In this case, retry checkout from /pricing to create a complete account with a confirmed payment.

If you reached the access key page but still see sid-verify

Reaching the access key confirmation page is normally a reliable signal that the account was created successfully. If you saved the key from that page, tried to log in, and encountered sid-verify, the gap between the confirmation page display and the account becoming fully active may still be closing. Wait two to three minutes before retrying.

If the error persists beyond that window, there is a mismatch between what the confirmation page showed and the account state on the server. This is uncommon. Contact support with any reference numbers shown on the checkout or confirmation page, along with the access key you were given, so the account state can be reconciled.

Troubleshooting

If you are a returning user who has logged in before and now sees sid-verify unexpectedly, this is unusual — sid-verify is typically only an account-creation-stage error. It may indicate that an account state was reset or corrupted. Contact support with your account details. Do not attempt to create a new account to work around it, as this may complicate the support process.

If sid-verify appears alongside sid-billing, resolve the billing issue first. An account in a billing-lapsed state may also surface verification-related error states in some configurations. See the sid-billing article for how to restore the subscription.