For token launches: how an integration works

Know who is claiming before you pay out.

A Fuzzy integration is 1 request in, 1 link out and 1 status back. Each claimant verifies in a browser, with no app and no account. Every decision stays yours.

From claim to decision, in 5 beats

  1. Claim comes in

    Your claimant submits a claim on your site, as they do today.

    You

  2. You send the request

    Their email and your own claim ID. Fuzzy returns a verification link.

    You

  3. They verify in a browser

    You share the link. They verify in a browser. No app, no account.

    Fuzzy

  4. You get a clear result

    Verified, pending, or did not clear, for each claim. Nothing is denied.

    Fuzzy

  5. Your team decides

    Pay, follow up, or send to your own review. Every call is yours.

    You
  • Your site stays your site. Pass your return page and claimants land back on it when they are done.
  • Nothing is denied automatically. If a claimant can't verify, you choose the fallback.
  • Built for a US ID. Claimants verify with a US government ID and a quick selfie.
Talk to us about your launch

What stays with you

What stays with you. All of it.

  • Who is eligible, and who gets paid.
  • The call on every claim. Fuzzy never denies anyone.
  • An export of every request and its result, with your own claim ID on each row.
  • The relationship with your community. Fuzzy never contacts your claimants.

What Fuzzy does

Runs the ID check, the liveness check and the face match, then tells you the outcome in plain categories: verified, pending, or did not clear.

What you never touch

ID documents, selfies and biometrics stay out of your systems entirely.

Getting started

3 steps from hello to your first launch.

Every step ends in exactly 1 thing to do, so nothing sits waiting on a to-do list.

  1. Kickoff call, 30 minutes

    Agree the rules, leave with a key.

    Your goal
    Understand it, and agree how your team handles each result.
    We remove
    The blank page. We arrive with a default setup: never deny, with your own claim ID already in the request.

    Your next actionSend your first test request.

  2. First test, about 5 minutes

    See it work on a real person.

    Your goal
    Watch a real claimant verify before it touches a real payout.
    We remove
    Setup. A teammate submits a test claim with the key and sample request from the kickoff, verifies in a browser, and you read the result.

    Your next actionRun your first test claim.

  3. First launch cohort

    Protect a real payout.

    Your goal
    Run your launch with a verified person behind every claim you pay.
    We remove
    Anything new to learn. It is the same setup you just tested, and we watch the first cohort alongside you.

    Your next actionReview your first launch results.

For your engineer

What your team actually builds.

A small job for 1 engineer. Fuzzy runs the verification. Your side is 2 API calls and a link you share, using the key and sample request we hand you.

You do not build

  • Document handling
  • Biometrics
  • Claimant accounts
  • A mobile app
  1. 1

    Request in

    Send the claimant's email and your own claim ID when a claim comes in.

  2. 2

    Link out

    Our response includes the verification link. Share it by email, text or in your app. Links expire in minutes, so share it straight away; a status read gives you a fresh one.

  3. 3

    Status back

    Check the status of a claim. You get verified, pending, or did not clear.

The claimant

What your claimant sees.

  1. Taps the link you sent. No app to download.

  2. Scans their ID, front and back.

  3. Takes a quick selfie.

  4. Lands back on your page when done.

Good to know

Does Fuzzy decide who gets paid?
No. You do. Fuzzy verifies and reports.
Does Fuzzy ever deny a claim?
Never. If a claimant can't verify, you choose the fallback.
Does it touch your wallets or token logic?
No. It sits beside your claim flow, not inside it.

Start with a test claim

Fuzzy reports that a check did not clear. Your team decides what happens next.

Tell us your launch date and roughly how many claimants you expect. A person will write back with a setup you can test.

Email the partners team

partners@fuzzyverify.com