Skip to content
payvol
NETWORK ASKED DevNet needs JavaScript

Verify

checked against v0.162 vectors

Paste a request to check it.

Nothing leaves your browser. The packages that answer are the same ones a wallet would import.

  1. Paste a request

    0 CHARS

    A canton: URI, or the canonical JSON on its own. Nothing leaves your browser — no request is made and nothing is stored.

    Nothing to hand? Load a vector, above, fills this with a committed conformance case.

    WHAT THE PACKAGES SAY

  2. See what is canonical

    INPUT → CANONICAL

    Two implementations must agree on the exact bytes an identifier is taken over. This is what yours would become, and what changes on the way.

    HASH AS PASTED

    —

    HASH WHEN FIXED

    —

  3. See what a wallet would do

    IF IT WERE PAID AS PASTED

    What would leave, what would arrive, and what a signature would authorise. Nothing is signed and nothing is sent.

    Paste a request above and this fills in.

About Verify

Check a request line by line against the profile, with each verdict naming the rule and the committed conformance vector behind it.

No wallet needed. No wallet. Every verdict comes from @payvol/core running in your browser, so the page can never form an opinion the package did not.

Checked against profile 0.1 and 0.2-draft.

What this does not tell you

  • Valid means well formed against the profile. It does not mean payable, funded, or honest.
  • The signature check is structural. A request with `signatureVerified: not-checked` has had no cryptography verified at all.
  • A verdict here is the package's, not the screen's: each one names the reason code and the committed vector behind it so you can run it yourself.
Not built yet
  • Receipts
  • Reconcile

Receipts: not built. Reconcile: reconcile ships in @payvol/core 0.4.0, under @payvol/core/draft02. The app has no screen for it yet.

no endpoint of ours no keys held your wallet signs