# Payvol

> An open payment layer for Canton: one request format, six modules, and a record that ties
> every settlement back to the invoice that started it.

Every documentation URL also serves its Markdown source when `.md` is appended.

## Documentation

- [/docs](https://payvol.xyz/docs): Documentation for building Canton payments against the Payvol profile. No account, no key, and no service of ours between your code and the ledger.
- [/docs/concepts/what-is-established](https://payvol.xyz/docs/concepts/what-is-established): Every measurement behind this site: the DevNet environment it was taken in, the date, the artifact it was read from, and what the evidence does not establish.
- [/docs/quickstart](https://payvol.xyz/docs/quickstart): Build a Canton payment request, derive its identifier, deliver it as a QR code, a link or a tap, and read it back. No account and no key at any step.

## Products

- [/products](https://payvol.xyz/products): Six modules that carry a Canton payment all the way: the ask, the check, the route, the sighting, the match, and the handover to your own ledger.
- [/products/connect](https://payvol.xyz/products/connect): Carry a Canton reconciliation record into the ERP a finance team already runs, in the shape that system expects. This integration is planned, not built.
- [/products/observe](https://payvol.xyz/products/observe): Watch Canton settlements arrive on your own participant and turn them into records you can match. No relay, no public index, and nobody else watching your money.
- [/products/reconcile](https://payvol.xyz/products/reconcile): Weigh what arrived on Canton against what the invoice asked, on five independent axes. Payvol classifies and hands over; your ledger decides what closing means.
- [/products/request](https://payvol.xyz/products/request): Create a Canton payment request once and share it as a QR code, a link or an NFC tap. Any conforming wallet can settle it, with no session and no server in the middle.
- [/products/route](https://payvol.xyz/products/route): Describe how a Canton payment may settle, in a shape every module downstream already understands. Payvol expresses the route. Somebody else runs the engine.
- [/products/verify](https://payvol.xyz/products/verify): Check a Canton payment request against the profile and get seven separate answers, each naming the rule it came from, including the one it cannot reach.

## Solutions

- [/solutions](https://payvol.xyz/solutions): Six situations where somebody has to ask for money on Canton, and which modules carry each one. The same primitive, a different asker, a different system to tell.
- [/solutions/agent-payments](https://payvol.xyz/solutions/agent-payments): When both sides are software, a Canton payment request is a contract a machine can check: bounded options, stated requirements, and an outcome that is not a guess.
- [/solutions/b2b-invoicing](https://payvol.xyz/solutions/b2b-invoicing): Invoice another business on Canton and let the payment find the invoice. The request travels with the bill, and the settlement arrives already tied to it.
- [/solutions/marketplace-payouts](https://payvol.xyz/solutions/marketplace-payouts): Represent thousands of Canton payouts in one format, so every obligation stays attributable and partial, late, duplicate and failed outcomes stay distinct.
- [/solutions/merchant-pos](https://payvol.xyz/solutions/merchant-pos): Put a code on the counter and let any Canton wallet pay it. No terminal to buy, no wallet to mandate, and a result you can match without a public index.
- [/solutions/treasury](https://payvol.xyz/solutions/treasury): Send a controlled internal Canton payment request with the payee, amount rule, instrument, scope and expiry stated up front, then reconcile it from your own view.
- [/solutions/validator-services](https://payvol.xyz/solutions/validator-services): You already read the Canton ledger. Bill from the same place: issue a signed service request, observe each payment, and reconcile it without a second system.

## The application

- [/app](https://payvol.xyz/app)
- [/app/match](https://payvol.xyz/app/match): See payments to your own party matched to the reference each one carried, read live from your own view of the Canton ledger through your connected wallet.
- [/app/pay](https://payvol.xyz/app/pay): Paste a Canton payment request and see exactly what signing it would authorise, computed in your browser before any wallet is asked for anything.
- [/app/request](https://payvol.xyz/app/request): Build a Canton payment request and watch it encode to a canton URI, canonical JSON and a QR code, computed in your browser with nothing sent anywhere.
- [/app/verify](https://payvol.xyz/app/verify): Paste a canton URI and get a verdict line by line against the profile, naming the rule and the conformance vector that each check comes from.

## Other pages

- [/](https://payvol.xyz/): Ask for a payment on Canton and know exactly what arrived. An open request format and six modules that carry a payment from the ask to the ledger.
- [/brand](https://payvol.xyz/brand): The Payvol brand assets: what you may do with the marks without asking, and what to check first. The standard is open; the name and the marks are ours.
- [/how-it-works](https://payvol.xyz/how-it-works): One Canton payment from the moment someone asks for money to the moment the books close, and which half of it Canton already does for you.
- [/licenses](https://payvol.xyz/licenses): Two licenses and why they differ: Apache-2.0 on the code for its patent grant, CC0-1.0 on the specification and vectors so anyone can implement and test.