SOURCE-ACCOUNT VERIFICATION

Verify your users’ claims.
Directly from the source.

Send a verification link. Your user connects the relevant account. Reclaim’s AI retrieves the information you need and returns verifiable evidence to your application.

Try a verification Discuss your workflow

YBacked by Y CombinatorBuilt for businesses.
Authorized by your users.

FROM CLAIM TO EVIDENCEILLUSTRATION

participant-verification

YOUR APPLICATION REQUESTS

Verify that this participant uses Shopify.

Information needed

Product · Subscription status · Plan

Sample data. No account connection. Source and field support must be confirmed.

Evidence from source accounts

Flexible claims and sources

User-authorized checks

Structured results

CHOOSE YOUR USE CASE

Different claims.
The same source of confidence.

Research

Verify that participants meet your study criteria.

Product accounts · Orders · Memberships

Learn More

Promotions

Verify qualifying purchases before approving rewards.

Retailer accounts · Order history

Learn More

Status Match

Verify users’ status on other airlines when they apply for status on yours.

Airline loyalty accounts

Learn More

Hiring BGV

Verify the employees you hire, from their source records.

Employment · Education · Identity

Learn More

Other workflows

Tell us what your users need to prove. Start with one claim.

Let’s find the relevant source

Discuss your workflow

Example sources and source categories. Availability depends on the website, account, and requested information.

HOW IT WORKS

You ask. Your user connects.
The source answers.

From a specific question to evidence your application can act on.

01
Specify the claim.
Define what your user needs to prove and the information you need from the relevant source.
“Uses Shopify” → product, status, plan
02
Send a verification link.
Your user opens the link and signs in to the source account to authorize the check.
Your flow → user-authorized connection
03
Receive source-backed results.
Reclaim retrieves the requested information and returns evidence to your application for verification and review.
Returned fields → your business decision

WHAT YOU RECEIVE

A result with a source.
And context to act on it.

The requested fields, where they came from, when they were verified, and an evidence reference where supported.

isVerified: true

Requested evidence is available.

The backend verifies the proof, then your application uses the returned fields to make its decision.

EXAMPLE APPLICATION VIEWVerified

Requested fields: Product: Shopify
Subscription: active
Plan: Basic
Source: Shopify account
Verification time: 13 Oct 2026, 14:32 UTC
Evidence reference: illustrative-proof-01

Illustrative fields, not an API response schema. Proof references are included where supported.

SDK note: an empty onSuccess([]) can mean proofs were delivered to your backend callback. It does not by itself mean information was unavailable. Read the callback docs ↗

FITS YOUR EXISTING WORKFLOW

A verification step.
Inside your product.

Add Reclaim at the point you need more evidence: a difficult eligibility criterion, a receipt exception, or an agent waiting on a user-authorized check.

Choose a source and the information to retrieve.
Let your user authorize the connection.
Verify returned proofs on your backend and apply your rules.

Developer documentation

CREATE A VERIFICATION REQUESTNode.js · server

import { ReclaimProofRequest } from '@reclaimprotocol/js-sdk';

const reclaimProofRequest = await ReclaimProofRequest.init(
    process.env.RECLAIMPROTOCOL_APP_ID,
    process.env.RECLAIMPROTOCOL_APP_SECRET,
    'ff4d7afe-4b78-4795-9429-d20df2deaad7' // Example. Replace with provider ID
)

const exportedProofRequestJsonString = reclaimProofRequest.toJsonString();