A verifiable income credential — not just a document
An invoice or screenshot says what a worker claims. An IncomeProof certificate is a trust layer between the people who create income and the people who need to verify it.
What it proves
A real client issued the income record.
A worker received payment for a specific activity.
The record has not been altered since issuance.
It is not a replacement for:
It sits on top of them as a verification layer between income creators and income verifiers.
Three roles, one trust hand-off
Trust moves in one direction — from the party with authority, to the worker who owns the proof, to the third party who needs it.
Issuer
The paying client
Company · Client · Employer · Platform
Has the strongest authority to confirm the payment happened.
Holder
The worker
Freelancer · Contractor · Independent worker
Needs portable, reusable proof of income they control.
Verifier
A trusted third party
Banks · Lenders · Landlords · Marketplaces
Needs confidence that the income claim is legitimate.
The lifecycle
1 · Client creates the record
A paying client enters who they paid, for what, how much, and when.
2 · IncomeProof generates the credential
A unique certificate ID and a SHA-256 proof hash are created from the record.
3 · Worker receives & shares
The worker holds a verification link they can share with anyone who asks.
4 · Third party verifies
A verifier confirms the issuer, worker, amount, date, and authenticity — no account or original documents needed.
Who can see what
The verification page shows only what's needed to confirm the record:
- Certificate ID
- Verification status
- Issuing organization
- Worker name
- Income source
- Payment date
- Proof hash
A single record reveals one record — nothing more is exposed:
- Additional financial history
- Other income records
- Private company information
For this demo, certificates are intentionally open so anyone can follow the trust flow. In a production product, sharing would be controlled by the worker — they decide which verifier sees the credential.
How the proof gets stronger
Income record → SHA-256 proof → verification
The hash is a fingerprint of the record. Change any detail and the hash no longer matches.
Income record → SHA-256 proof → blockchain anchor → immutable verification
Anchoring proof hashes on a public ledger lets anyone confirm a record's integrity without trusting IncomeProof at all.
Why would someone trust this certificate?
Because the trust comes from the issuer — the paying client who attests to the income. IncomeProof provides the independent verification layer that proves the record hasn't been altered.
The company creates the proof, the worker owns the credential, and any verifier can independently confirm it.
See the trust flow yourself
Create a client-issued income credential and verify it in under a minute.