Checkify — Integration Guide

What integration looks like

The same core flow works whether you are using WordPress adapters or building a custom integration.

Connect your site

Link your website or domain to Checkify so requests are bound to the correct relying party.

Get your Checkify Pass

Each site gets one Pass ID automatically. Pick a request type such as human verified or age over 18.

Add it to your flow

Use a plugin adapter or attach it to your own form, button, page, or backend action.

Receive a verified result

Allow or block the action based on a clear proof result instead of collecting raw identity data.

Step-by-step setup

A practical path from zero to a working Checkify-protected flow.

Step 1

Create your site in the app

In the Checkify app, create your website entry and add the domain you want to use. This tells Checkify which site the verification flow belongs to.

Once saved, that site gets a Checkify Pass and the allowed domains that control where the embed can run.

Step 2

Connect to the site in WordPress

Open the Checkify plugin in WordPress and use the connect flow to link that WordPress installation to the site you created in Checkify.

This creates the trusted relationship that allows WordPress to start verification requests securely.

Step 3

Copy your Checkify Pass ID from the app or business dashboard

When you create a digital site, Checkify provisions a Pass with request types such as human verified, age over 18, age over 21, or age over 25.

Copy the Pass ID from the app or your business dashboard — you use the same ID everywhere and only change the request type.

Paste Checkify Pass ID into WordPress settings

Step 4

Paste the Pass ID into your WordPress integration

Open the Checkify connector settings in WordPress and paste your Pass ID. Satellite plugins choose a profile, which maps to a request type on that Pass.

This tells the plugin which verification flow to run for checkout, login, comments, contact forms, or shortcode-based pages.

Step 5

Copy the shortcode into a page in WordPress

For shortcode-based flows, paste the shortcode into the WordPress page where you want verification to appear.

Some adapters do not need a shortcode, but it is still useful for manual page-based integrations and custom flows.

Checkify shown in WordPress integration settings

Step 6

Use QR on desktop and magic link on mobile

On desktop, QR is usually the simplest experience. On mobile, a magic link is often better because the user can tap straight into the Checkify app.

A polished integration can support both automatically depending on the device.

WooCommerce WordPress integration

The fastest route for WooCommerce and WordPress sites is to use the Checkify plugin and adapters.

What the plugin can protect

• WooCommerce checkout

• Login and registration

• Comments

• Contact forms

• Custom forms and custom selectors

How WordPress owners configure it

1. Create your site in the app.

2. Connect to the site in WordPress.

3. Copy your Checkify Pass ID from the app or dashboard.

4. Paste the Pass ID into the Checkify connector settings.

5. Add the shortcode to a page when the flow uses shortcode-based verification.

Generic website or app integration

You can also integrate Checkify into your own stack without using WordPress.

// 1. Create a digital site and copy your Checkify Pass ID
// Example: human verification

// 2. Start a Pass request from your page or backend
GET /v1/qr/pass/{pass_id}/start?request_type=human

// 3. Show the returned QR or magic link to the user

// 4. Poll the request status
GET /v1/qr/status?token={token}

// 5. Allow or block the protected action
if (result.status === "completed") {
  // continue with signup, checkout, comment, form submit, etc.
}

Good fit for

• Custom signup flows

• Checkout flows outside WooCommerce

• Support forms or lead forms

• Review and comment systems

• Kiosk and counter experiences

Why this model is useful

You keep your own product logic and UI, while Checkify handles the proof step. That means you can add strong verification without redesigning your whole system around identity storage.

Use the new SDK form binding

The easiest way to add Checkify to a normal form is to bind it to the form with your Pass ID and request type.

What it does for you

• Renders the Checkify button for you

• Stores the verification token in a hidden field

• Disables submit until verification is complete

• Works well for Flask, Django, Laravel, PHP, and WordPress-style forms

• Keeps your backend simple because you only verify the returned token

Best fit for

• Password reset forms

• Signup and login forms

• Contact forms

• Checkout protection

• Comment and review submission

<form id="reset-form">
  <input type="email" name="email">
  <input type="hidden" id="checkify_token" name="checkify_token">
  <div id="checkify-button-wrap"></div>
  <button id="send" type="button">Send</button>
</form>

<script src="https://checkify.me/sdk/v1/checkify.min.js"></script>
<script>
  Checkify.bindForm('#reset-form', {
    passId: 'YOUR_PASS_ID',
    requestType: 'human',
    buttonTarget: '#checkify-button-wrap',
    submitButton: '#send',
    hiddenInput: '#checkify_token'
  });
</script>

How it works

1. Create a digital site and copy your Checkify Pass ID.

2. Add the Checkify SDK script to your page.

3. Call Checkify.bindForm(...) with your Pass ID and request type.

4. Let Checkify write the token into a hidden field.

5. Send that token to your backend and verify it server-side before allowing the action.

Why this is easier

Instead of wiring up button rendering, token handling, and submit state yourself, the SDK handles the form plumbing for you. Your integration becomes: add a Pass ID, bind the form, then verify the returned token on your backend.

<form data-checkify-pass="YOUR_PASS_ID" data-checkify-request="human">
  ...
</form>

For standard forms, you can also use auto-enhance mode with data-checkify-pass and data-checkify-request.

Server-side reminder

The browser only gives you a token. Your server should always verify that token with Checkify before allowing password reset, signup, checkout, comment submission, or any other protected action.

Common use cases

Start with one protected action, then expand across your product.

Bot and spam reduction

Use human verification instead of traditional CAPTCHA for login, comments, reviews, and contact forms.

Age-gated access

Restrict content, products, or services based on over 13, over 16, over 18, or over 25 checks.

Higher-trust actions

Add stronger proof to account recovery, admin actions, payouts, or approvals.

Reusable trust layer

Once integrated, the same pattern can be reused across plugins, forms, apps, and websites.

How to integrate Checkify into your system