Skip to content
payvol
NETWORK ASKED DevNet needs JavaScript

What came in

Payments to your party, matched to the reference each one carried.

Matched

connect to see payments carrying a reference you issued

Needs a look

connect to see arrived without a reference you can match

Your party's own view

Connect a wallet and Payvol reads your own party's view through it. Nothing is watched in the background: one read when the wallet arrives, and one more each time you ask.

Read from your own party's view of the ledger, in 2 calls off the update stream rather than the active contract set. Payvol does not index the network and cannot show a transfer you are not a party to. A payment made outside the standard carries no reference, which is what would leave one unmatched here.

About Match

Match payments that arrived against the requests that asked for them, read from your own view of the ledger.

Wallet required. A wallet is required, because the ledger read happens through it. Without one the page explains what it would do and shows nothing that looks like a result.

Checked against profile 0.1, on the DevNet network the app asks for.

What this does not tell you

  • Payvol does not index the network. It reads your own party's view through your wallet, so a payment your party cannot see is a payment this page cannot see.
  • A match is evidence, not an accounting decision. Duplicates, partials, late arrivals and a wrong receiver are reported as what they are rather than resolved for you.
  • Nothing runs in the background. One read when the wallet arrives, and one more each time you ask.
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