Transaction Proof
Cryptographic proof for every transaction.
Not blockchain. Not a financial instrument. Each settled transaction gets a SHA-256 proof receipt. Receipts are batched hourly into a Merkle root that FinVeil stores in its own database, and can be checked through FinVeil’s public verification page and API. Anchoring to a public ledger is not live.
How it works
Three steps.
Transaction settles
A collection or payout is recorded as settled.
Receipt minted
FinVeil hashes the event (SHA-256), stores the receipt, and includes it in the next hourly Merkle batch.
Check it with FinVeil
GET /api/tokens/{id}/verify, or the /verify/{id} page, returns the receipt and its status. Verification relies on FinVeil’s servers.
Benefits
Why teams choose Transaction Proof.
Minted automatically
Settled payments get a receipt with no extra integration and no extra storage on your side.
Shareable check
A counterparty or auditor can check a receipt on FinVeil’s verification page without a FinVeil account.
Not a financial instrument
Receipts are cryptographic proofs only. NOT transferable, NOT redeemable for funds, NOT a store of value, NOT a token.
Clear about its limits
The Merkle batch covers receipt IDs, so it shows which receipts existed in a batch. It is not yet anchored publicly.
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 docs# Public, no credential required
curl https://api.finveil.money/api/tokens/<TOKEN_ID>/verify
# => {
# "valid": true,
# "tokenId": "<TOKEN_ID>",
# "tokenType": "PAYMENT_RECEIPT",
# "currency": "ZAR",
# "status": "ACTIVE",
# "issuedAt": "...",
# "claims": { ... },
# ...
# }Works with