Skip to main content
VerifyGate checks eligibility, opens Hosted Verify when a new check is needed, then renders your protected content. The default path is a published gate, not a manual check list.

Quickstart

  1. In your profile → Portals, create a portal and choose the checks visitors must pass.
  2. Publish the gate and copy your checkout link or embed snippet.
  3. Paste the embed in your app, or send users to the hosted link.
  4. Optionally run gateCheck on your server before granting access.
Billing and check policy come from the gate. You do not register an app or pass billingWallet for this path.

Key props

Default create behavior

Create mode opens Hosted Verify. The published gate owns verifier inputs, pricing, and checkout policy.

Hosted OAuth

Social, organization, and human checks use Hosted Verify. Set oauthProvider when the user already picked a provider in your app. Allowed values:
  • Social: x, twitter, github, discord, facebook, linkedin, telegram
  • Org: google, microsoft

Advanced server receipts

For backend-created receipts after a one-time user approval, use the server-side verifyFromApp flow in Integrations. Keep browser checkout on gateId.

Next

Verify Checkout

Server eligibility and paid gate checkout.

Integration

Browser, server, and assistant paths.

SDK verifications

Create and poll receipts from code.
Last modified on July 24, 2026