Proof Ledger
A cryptographic proof for every event in your system.
Mint a tamper-evident receipt for a payroll run, an advance disbursement, an employment verification, or any significant business event. Every receipt is hashed into a Merkle tree and anchored to a public ledger for independent verification. Priced per-mint — pay only for the receipts you create. Receipts are cryptographic proofs, not transferable financial instruments. Receipts are NOT transferable between users, NOT redeemable for funds, NOT a store of value, and NOT a financial instrument.
Minting architecture
Every business event. Cryptographic proof.
Business events trigger token minting. Each token is hashed, anchored to a Merkle tree, and written to the Stellar ledger.
Business events
FinVeil Mint Engine
Cryptographic proof layer
Proof outputs
How it works
Three steps.
Mint receipt
One API call. Event type, issuer, payload — hashed and stored canonically in Postgres.
Anchor to ledger
Receipts are batched into Merkle roots and anchored to a public ledger for tamper-evident proofs.
Anyone can verify
Public /verify endpoint — recruiters, landlords, credit bureaus, auditors, employees. Re-derive the Merkle proof independently.
The employment verification flow
One upload. One link. Zero phone calls.
Employer uploads payroll
Payroll file lands in FinVeil — the same CSV or export you already produce every month.
Receipt minted automatically
FinVeil mints tamper-evident receipts for the payroll run and each employment verification, anchored to a Merkle root.
Employee shares link
One tap: finveil.money/verify/employment/<id>. Consent is logged, the link is revocable.
Verifier sees confirmed data
POPIA-safe output: name, employer, tenure, salary band, status — never the exact salary. All verification endpoints are free forever. Receipt proof is independently verifiable.
Benefits
Why teams choose Proof Ledger.
Proof of payroll
Every payroll upload generates a cryptographic receipt with the CSV hash, employee count, and pay period.
Proof of verification
Employment verifications carry tamper-evident receipts that lenders can independently verify.
Proof of disbursement
Every bank transfer gets a receipt anchored to a Merkle tree for audit.
Beyond employment
The same primitive generates receipts for proof of voucher issuance, proof of invoice acceptance, payroll runs, expenses, and more. One API — not cryptocurrency.
Who it's for
Developer-friendly
Drop it into your stack.
REST API, typed SDKs in 9 languages, and a sandbox environment you can explore in 30 seconds. No calls with sales to get keys.
Read the docscurl -X POST https://api.finveil.money/api/v1/verify/employment \
-H "Authorization: Bearer fvk_live_xxx" \
-H "Content-Type: application/json" \
-d '{ "receiptId": "rcpt_ev_9f3a1c..." }'
# => {
# "valid": true,
# "employeeName": "Zandi M.",
# "employerName": "Acme",
# "tenure": "2 years 3 months",
# "salaryBand": "R30,000 - R40,000",
# "employmentStatus": "ACTIVE",
# "verifiedAt": "2026-04-15T09:12:44Z"
# }Works with