Add Checkify to your website with one Pass ID and a request type. No manual launcher setup required.
In the Checkify app or business dashboard, create a digital site and register the domain where your embed will run. Checkify auto-provisions one Pass per site (for example
chk_live_...).
For sandbox testing, use a test Pass (
chk_test_...)
from a test-environment site.
Paste this into your page. Replace
YOUR_PASS_ID
and choose a request type.
<script src="https://checkify.me/sdk/v1/checkify.min.js"></script>
<div
data-checkify-pass="YOUR_PASS_ID"
data-checkify-request="human"
data-checkify-text="Verify with Checkify"
></div>
For login, signup, checkout, or contact forms, let the SDK handle the button, hidden token field, and submit state.
<form id="signup-form">
<input type="email" name="email" required>
<input type="hidden" id="checkify_token" name="checkify_token">
<div id="checkify-button"></div>
<button id="submit" type="button">Create account</button>
</form>
<script src="https://checkify.me/sdk/v1/checkify.min.js"></script>
<script>
Checkify.bindForm('#signup-form', {
passId: 'YOUR_PASS_ID',
requestType: 'human',
buttonTarget: '#checkify-button',
submitButton: '#submit',
hiddenInput: '#checkify_token'
});
</script>
The browser only receives a token. Always verify server-side before allowing the protected action.
Use your site API key and call
POST /v1/qr/results/verify
with the
request_id
from the hidden field (legacy embeds may still submit the poll token).
See the
server verify guide.
For browser events and return URLs, see the
embed API reference for browser events and return-URL handling.
| Request type | Server claim (required_claims) | Typical use |
|---|---|---|
human | human_verified | Bot/spam reduction |
age_over_18 | age_over_18 | 18+ content or checkout |
age_over_21 | age_over_21 | 21+ products (US alcohol, etc.) |
age_over_25 | age_over_25 | Higher age thresholds |
Use these request types in your embed (data-checkify-request or Checkify.bindForm). On your server, verify with the matching claim in required_claims.
The embed only starts from domains registered on your Checkify site. Optional DNS/meta/file verification increases business assurance but is not required for the embed to work on a registered domain.