Receipts

About Receipts

A document that says a payment happened is a claim by whoever wrote it. What makes a Ryntra receipt different is that every link in it can be recomputed by somebody who does not trust Ryntra: the intent, the authorization, the transaction, the effects the ledger recorded, and the receipt hash over all of them.

This page does that recomputation in your browser and then reads the ledger again to see whether it still agrees. A transaction hash works here too, with no receipt at all — the expectation is taken from the envelope the ledger stores, which proves the network did what the transaction announced without proving anybody authorized it.

Testnet · verification

Check a receipt

TESTNET

What is checked

Paste a Ryntra Stellar receipt and every hash in it is recomputed from its own contents, then the ledger is read again and compared with what it claims. Paste a transaction hash instead and the expectation is taken from the envelope the ledger stores, so any Stellar Testnet transaction can be checked here.

Nothing is uploaded. The receipt is read in this browser and the ledger is read straight from the public Horizon endpoint.

Receipt JSON, or a transaction hash

A transaction, compared with what it announced

NOT READ

What this proves, and what it does not

The expectation here comes from the transaction envelope stored on the ledger — the operations the transaction itself declares. Comparing that against the effects proves the network did what the transaction said, which is worth checking and is not the same as proving somebody authorized it.

Only a receipt carries that second fact, because only a receipt records the intent that was fingerprinted before a wallet ever saw it.

No transaction read

Paste any Stellar Testnet transaction hash to see its declared operations compared against the effects the ledger recorded. It does not have to be one this workspace produced.