Skip to content
EPP-402

Explorer · receipts

A receipt is a claim. Check it.

A provider signs every receipt over the quote, the payer, the amount, the transaction hash and a hash of the result it delivered. Look one up by id, or paste the JSON from an EPP-RECEIPT header: the checks run in this browser against the schema, the signature and the public RPC.
Lookup

By id.

Receipt ids start with rcpt_ and are 26 characters long after the underscore.

Verify

Paste a receipt.

Seven checks, each with its own result: the text is JSON, it matches the Receipt schema, the signature recovers to the provider address, the registry knows the provider, the transaction exists and succeeded, the transfer matches payer, recipient and amount, and the relay recorded the commerce reference.

  • Nothing you paste is sent to this site.
  • The chain checks read https://testnet-rpc.elysium.kinetiq.xyz directly.
  • A receipt on another network is verified for schema and signature only; this explorer reads eip155:99801.

Nothing leaves your browser except a read of the public RPC and the registry.

  1. Well-formed JSON

     

    not run

  2. Matches the Receipt schema

     

    not run

  3. Signature recovers to the provider address

     

    not run

  4. Provider known to the registry

     

    not run

  5. Transaction found and succeeded on chain

     

    not run

  6. Transfer matches payer, recipient and amount

     

    not run

  7. Settlement relay recorded this commerce reference

     

    not run

Paste a receipt and press Verify. Each line turns into a pass, a fail with its reason, or a skip with why it could not run.

Recent

Recently published receipts.

The newest ten the registry holds, with the flags it recorded on arrival.

Index connected · Elysium Testnet
Receipts
0
  • No receipt has been published yet. Receipts arrive when an agent with a registry URL completes a payment. Agent SDK