Skip to content
AuthKit

Domain Verification

How Domain Verification works in Paycux, what it is for, and the smallest setup that gets it running.

Introduction

Domain Verification is part of the Paycux platform. This page explains what it does, when to reach for it, and the smallest working setup you can ship.

Everything below applies to both environments. Build and test in staging, then promote the same configuration to production without changing your code — only the API key and client ID differ.

Self-serve domain verification

Verify the setup end to end before you hand it to a customer. Run the flow from a private browser window so no existing session masks a broken step.

  1. 1Open the connection in the dashboard and confirm its status reads Active.
  2. 2Start the flow from your application, not from the provider, so the redirect URI is exercised.
  3. 3Sign in as a test user and confirm the profile arrives with an email address.
  4. 4Check the connection's event list — a successful sign-in appears within a few seconds.

Manual domain verification

Manual domain verification applies specifically to Domain Verification. It behaves the same in both environments, and the values it depends on are visible in the dashboard for the environment you have selected.

If the behaviour you see does not match this description, check which environment your API key belongs to before anything else — a staging key against production data is the most common cause.