Skip to content
CCPEDIAby Unity Nodes
#760Declined Pull Request1.9M CC requested

Proposal: Payvol, Open Payment Intent, Lifecycle and Reconciliation Infrastructure for Canton

cayvox06-09-2026Last activity today
dapp-integrationfinancial-workflows-composabilityneeds-champion
References:CIP-0056CIP-0103CIP-0112

Development Fund Proposal Submission

Proposal file:
https://github.com/cayvox/canton-dev-fund/blob/proposal/payvol/proposals/2026-09-Cayvox-Payvol.md


Applicant

Organization:
Cayvox Labs, an open-source infrastructure company building on the Canton Network.

Author / Primary Contact:
Anıl Karaçay, Cayvox Labs, anil@cayvox.com

Champion:
Needs Champion. A Development Fund Champion is being sought, and we welcome an introduction from the Payments and DeFi or Wallet Apps SIGs.


Proposal Classification

Proposal Type:

  • RFP-aligned proposal
  • Individual initiative

RFP / Roadmap Area:
RFP 13, Payments and DeFi, under Financial Markets, Standards & Verification. Secondary alignment with RFP 14, Wallet and dApp Integration Tooling, under Developer Experience, Tooling & Education.

Primary SIG:
Financial Workflows & Composability

Secondary SIG Alignment:
dApp Integration
Wallet Apps

Label:
financial-workflows-composability (primary); dapp-integration (secondary)


Funding & Timeline

Total Funding Request:
1,900,000 CC

Project Duration:
23 weeks, split across three milestones of 650,000 CC, 650,000 CC and 600,000 CC.

Maximum Amount:
N/A. RFP 13 does not specify a maximum amount.

Maximum Duration:
N/A. RFP 13 does not specify a maximum duration.


Summary

Payvol is an open, wallet-neutral coordination layer for programmable payments on Canton. It standardizes how a payment intent is expressed, safely presented to a payer, translated into an authorized Canton Token Standard transaction, and reconciled through a private lifecycle after submission, so that an intent can travel through a QR code, URI, NFC record, web link, API, invoice, message, or an application-to-wallet handoff without binding the payee to a specific wallet, custodian, token issuer, or settlement application. The grant turns the existing self-funded prototype into a stable public standard, a production TypeScript implementation, a conformance suite, Canton execution profiles, a lifecycle and reconciliation toolkit, a self-hostable resolver, an ISO 20022 Request-to-Pay reference converter prototype, and a version-pinned x402 representation mapping. Every deliverable is an open-source, reusable component or standard designed to support multiple Canton applications, wallets and issuers rather than one-off, application-specific integration work.


Submission Checklist

  • Full proposal file is included in this PR
  • Organization and primary contact identified
  • Champion identified or Needs Champion selected
  • RFP / roadmap alignment identified, if applicable
  • Total funding request provided
  • Project duration provided
  • Proposal is within any RFP maximum amount
  • Proposal is within any RFP maximum duration
  • Milestones and milestone funding are defined in the proposal
  • Acceptance criteria are based on ecosystem value
  • Architectural alignment is addressed

Notes for Reviewers

Milestone 0 is already delivered and self-funded, before submission: the specification, the four Apache-2.0 packages published on npm at v0.2.0 (@payvol/core, @payvol/qr, @payvol/conformance, @payvol/cli), the conformance vectors, and a public playground at https://payvol.xyz/app. The requested funding covers Milestones 1 to 3 only.

The proposal is scoped as shared ecosystem infrastructure built directly on the Canton Token Standard (CIP-0056) and the dApp and wallet standards (CIP-0103, CIP-0112), not as a wallet, a custodian, or a settlement application. It is deliberately wallet-neutral and issuer-neutral so that the same intent artifact is usable by any Canton wallet or application.

The document contains thirteen figures, stored beside it in /proposals/ with the same filename prefix, following the convention used by the merged Certora proposal. Relative image paths resolve against the repository and branch being viewed, so before this PR is merged the figures render on the branch link above rather than in the rich diff view. The proposal file link at the top of this description is the one to read.

← Back to Proposals