Treasury requests
An internal ask that carries its own paperwork.
One entity asks another for funds. The approval reference, the destination and the deadline travel inside the request, so the record an auditor reads later is the request itself.
Terms travel with the ask
Internal payments have the same problem as external ones, with better manners.
The ask arrives in an email. The approval is a reply. The transfer happens in a different system, and six months later somebody has to prove the three were connected. Nothing in that chain was designed to be evidence.
The conditions are part of the request
The approval reference, the account it must land in, and the date it stops being valid are inside the signed bytes. Changing any of them produces a visibly different request rather than a quiet edit.
What the auditor reads is the record
Each state is appended rather than overwritten. The question is never which version of the email was final, because no version ever replaced another.
The paying entity checks, then releases
The holding entity reads the same request the requester signed, checks the conditions against what is true now, and settles. No separate approval workflow to keep in step.
It sits beside the systems you have
Your treasury management system stays the system of record. This produces an artifact and a record, and both are inputs to it rather than replacements for it.
How it works
Ask, check, release.
01
Ask
- The requesting entity builds a request
- Approval references are named, not attached
- An expiry makes the ask self limiting
02
Check
- The holding entity verifies the request is intact
- It resolves each condition against current state
- Anything it cannot resolve is surfaced, not skipped
03
Release
- The transfer settles on the network
- The payer, the payee and the instrument registry see it
- The record is appended on both sides
How to start
Move one internal transfer this way.
Then read the record it leaves behind, and decide whether it beats the email thread. This situation uses Request, Verify and Observe.
npm i @payvol/core @payvol/qr version 0.4.0
Payvol Request Payvol Verify Payvol Observe Open the app Next: Agent payments