CASHBACK · SAMPLING · CREATOR REIMBURSEMENTS

Verify the purchase behind the claim.

Retrieve purchase evidence from shoppers’ source accounts to support cashback, sampling, and reimbursement decisions.

Test one purchase-verification flow Explore the workflows ↓

One criterion. A relevant source. Evidence your team can use.

FROM CLAIM TO EVIDENCEILLUSTRATION

purchase-verification

YOUR APPLICATION REQUESTS

Verify the purchase behind this reward claim.

Information needed

Merchant · Item · Purchase date · Amount · Order ID

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

IN YOUR EXISTING PROCESS

Give the difficult claims a clearer next step.

Keep your usual receipt and campaign checks. Add an account connection when its value justifies another user step, particularly for receipt exceptions or higher-value claims.

01Receive a reward claim
02Retrieve purchase evidenceRECLAIM
03Apply your campaign rules

THREE PLACES TO START

Give every decision a source to refer to.

Cashback and rebates

“I made a purchase that qualifies for this offer.”

Candidate source: The shopper’s account on the retailer’s website.
Information returned, where available: MerchantItemPurchase dateAmountOrder ID
In your approval flow: Compare available purchase fields with your campaign’s product, date, and spend requirements before approving cashback.

Creator and tester reimbursements

“I bought the item for this campaign.”

Candidate source: The creator’s or product tester’s retailer order history.
Information returned, where available: MerchantItemAmountOrder ID
In your approval flow: Attach purchase evidence to the reimbursement request. Review content, testing, or other deliverables separately.

Receipt exceptions

“My receipt is missing, damaged, or disputed.”

Candidate source: The retailer’s authenticated order page. Receipt email only where supported; email verification is in development.
Information returned, where available: MerchantPurchase dateAmountOrder IDOrder status, if checked
In your approval flow: Give your review team another source of evidence when the usual receipt flow cannot resolve the claim.

Results can include the source, verification timestamp, and an evidence or proof reference where supported.

YOUR WORKFLOW STAYS YOURS

Your campaign. Your decision.

Reclaim supplies evidence. You apply eligibility rules, duplicate-claim checks, and reward approval logic. Account connection is best placed where the additional evidence earns the extra user step.

KNOW WHAT THE EVIDENCE MEANS

A purchase has limits as evidence

Purchase evidence alone does not prove affiliate attribution, physical possession, completion of a review, or absence of a later return. Current order status is reported only when the source exposes it and the verification checks it.

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();

Building for AI agents?

Use Reclaim when a workflow needs source evidence with a user’s authorization. Explore the verification letters API and MCP instructions.

Agent instructions

BUILT FOR YOUR REVIEW PROCESS

Evidence you can examine.
A team you can evaluate.

YBacked by Y Combinator

AI retrieves the requested information. Cryptographic verification helps your application check the returned evidence.

Explore the Trust Center

SOC 2 Type IIIndependent audit

ISO 27001Information security

GDPRReadiness

A FEW USEFUL ANSWERS

Before your first test.

Discuss your workflow

Does Reclaim decide whether to approve a reward?

No. Reclaim returns the available evidence from the source. Your application applies campaign rules, duplicate checks, and any other requirements before making a reward or reimbursement decision.

Which purchase fields can be returned?

Candidate fields include merchant, item, purchase date, amount, and order ID. Availability depends on the retailer, account, and verification configuration. Test the required fields with your source before deploying.

Can you prove that an item was not returned?

A purchase record does not establish the absence of a later return. A verification can report current order status only if the source exposes it and the configured check retrieves it. Any later change needs a separate check.

Should every shopper connect an account?

Place this step where its value justifies the effort, such as a higher-value reimbursement or a missing, damaged, or disputed receipt. Keep a fallback review path for shoppers who cannot complete verification.

Can you check an emailed receipt?

Received-email verification is in development. Confirm source support before offering it in a campaign. Start with authenticated retailer order history where the required purchase information is available.

What happens when we test a flow?

We discuss your promotions workflow, select a source and purchase fields, and test the evidence against your approval rules. Bring one campaign or receipt exception to begin.

ONE CLAIM. ONE SOURCE. A PLACE TO START.

Which purchase claim needs better evidence?

Bring one real workflow. Let’s find the source, agree on the fields, and test the result together.

Test one purchase-verification flow