Browser
TrueSiftCheck creates the short-lived verification token and returns it to your form.
With @truesift/next you integrate a clear verification interface in the browser while keeping the authoritative decision where it belongs: on your server.
TrueSiftCheck creates the short-lived verification token and returns it to your form.
Challenge and Verify remain in your Next.js application. The Secret Key stays server-side.
Only verificationToken comes from the client. Action, Path and Origin are defined by your server.
Real SDK demo
This preview renders TrueSiftCheck directly from @truesift/next/client. The scenarios run through the local demo routes from the SDK example and show the actual widget lifecycle.
Successful human verification.
Recommended visual direction for forms.
Default npm-like fallback behaviour.
Legacy / marketing mode, still available when needed.
Checks how the active theme behaves inside a light card.
No verification callbacks yet.
Decisions such as allow, review or block are never accepted from browser data. The protected business route verifies the token server-side against the expected Action, Path and Origin — only then does it execute the action.