Packet valid
The JSON matches its embedded SHA-256 receipt digest.
ProofRail verifier
Check the packet.
Do not guess.
Paste a ProofRail packet to verify its SHA-256 receipt, inspect the non-custody boundaries, and see whether the record is only reported or actually settlement-verified.
Input
Paste packet JSON
This verifier runs locally in your browser. It does not contact a bank, Zelle, Talley IT, a blockchain, or a payment provider.
Boundary: a valid packet hash proves the packet was not changed after its receipt digest was created. It does not prove money moved, delivery occurred, or a dispute is resolved.
Result
Verification result
Awaiting packet
Paste a ProofRail packet to start.
The verifier will recompute the signed-material hash, compare it to the embedded receipt digest, and classify the payment status without treating reported payment as verified.
- Schema
- —
- Intent
- —
- Digest
- —
- Computed
- —
- Payment state
- —
- Final receipt
- —
— No custody claimed
— No transfer initiated by page
— No bank credentials collected
— Customer controls bank action
Status ladder
Reported is not verified.
ProofRail separates packet integrity from payment truth. A valid order-intent packet is useful evidence, but final settlement still requires reconciliation.
Reported sent
The user says they paid. This is a claim, not settlement verification.
Reconciled
Talley IT confirms received funds or marks the record for review.
Final receipt
A final settlement receipt can be issued only after reconciliation.