03 · How it works

Every donation, verifiable on Polygon

Money never touches the platform. Every donation's hash is permanently anchored on a public ledger that anyone can audit.


The donor flow

What actually happens when someone donates.

  1. Donor visits a campaign on Charity-IQ

  2. Clicks Donate — redirects to the charity's own Zain Cash merchant page

  3. Pays via Zain Cash. Money goes donor → ZC → charity wallet. Charity-IQ never touches the funds.

  4. Donor returns to a receipt page on Charity-IQ

  5. The donation hash is anchored to Polygon mainnet within seconds

  6. Donor can verify the donation on polygonscan.com — no Charity-IQ involvement needed


Why on-chain?

Two models of trust. We picked the one that doesn't ask you to trust us.

Database trust

Trust the operator.

If we wanted to alter or hide a donation, we could. You'd have no way to tell.

On-chain trust

Trust the math.

The Merkle root of every batch is published on Polygon. Tampering with the database would not match the on-chain proof. Anyone can verify.


A real example

This is a real anchor from Polygon mainnet. Click to verify it yourself.

0x5ecb08bcc78f56d52241ce7422a56a5d2689234b28f64be9680e3b6bc098426b

This batch contains real donations from charities on the platform. Click to verify on Polygon.

View on polygonscan.com

Common questions

  • Does Charity-IQ hold my money?

    No. Money flows donor → Zain Cash → charity wallet. We are a directory and trust layer, not a payment aggregator.

  • What if Charity-IQ goes away?

    Charities keep their Zain Cash merchant accounts. On-chain anchor records persist on Polygon forever. Donor receipts remain verifiable.

  • What does anchoring cost?

    A fraction of a cent per donation. We absorb the cost via the subscription model — donors pay nothing extra.

  • Can the platform fake a donation?

    No. The Merkle proof is generated from the actual donation data; tampering would not match the on-chain hash.