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
- In your profile → Portals, create a portal and choose the checks visitors must pass.
- Publish the gate and copy your checkout link or embed snippet.
- Paste the embed in your app, or send users to the hosted link.
- Optionally run
gateCheckon your server before granting access.
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. SetoauthProvider 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-sideverifyFromApp 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.
