Proof Ledger
A cryptographic proof for every event in your system.
Mint a SHA-256 receipt for a payroll upload, a disbursement, an employment verification, or another significant business event. Receipts are batched hourly into a Merkle root that FinVeil stores in its own database, and can be checked through FinVeil’s verification page and API. Anchoring to a public ledger (such as Stellar) is not live. 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 a proof receipt. Each receipt is hashed with SHA-256 and batched hourly into a Merkle root that FinVeil stores in its own database. Public-ledger anchoring is not live.
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.
Batch into a Merkle root
Receipts are batched hourly into a Merkle root stored in FinVeil’s database. Public-ledger anchoring is not live.
Check it with FinVeil
Anyone with the receipt link can check it on FinVeil’s public verification page or API. Verification relies on FinVeil’s servers.
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 receipts for the payroll upload and each employment verification, batched hourly into a Merkle root held by FinVeil.
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. Checked on FinVeil’s verification page.
Benefits
Why teams choose Proof Ledger.
Proof of payroll
Every payroll upload mints a receipt that records the upload’s file hash and details.
Proof of verification
Employment verifications carry a receipt that a lender can check on FinVeil’s verification page, with the employee’s consent code.
Proof of disbursement
Disbursement events mint a receipt that is included in an hourly Merkle batch.
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 with an OpenAPI reference, and a test mode on the same API. Sign up for test API keys without a sales call. SDKs are available on request.
Read the docscurl -X POST https://api.finveil.money/api/v1/verify/employment \
-H "X-API-Key: fvk_test_..." \
-H "Content-Type: application/json" \
-d '{ "tokenId": "<TOKEN_ID>" }'
# => {
# "employeeName": "...",
# "employerName": "Example Employer (Pty) Ltd",
# "tenure": "...",
# "salaryBand": "...",
# "employmentStatus": "ACTIVE",
# "verifiedAt": "...",
# "expiresAt": "..."
# }Works with