Product
Capture authority and transaction evidence once, then use the same signed record for operations, disputes, audits, and risk analysis across every payment rail.
One schema across payment providers
Send one canonical envelope whether an agent paid through a card API, bank rail, procurement platform, checkout protocol, internal ledger, or x402.
Tamper-evident by construction
Each artifact is content-addressed and bound into one packet root, preserving what the principal authorized and what every system reported at transaction time.
Evidence before opinion
Investigators can reconstruct a transaction and distinguish merchant representation, agent interpretation, deployer controls, and execution-rail failures without changing the source evidence.
Selective disclosure
Create an expiring proof-only link that verifies packet commitments and signatures without exposing private mandates, prompts, payment instruments, or internal notes.
Decide before the agent pays
Preflight evaluates the active spend policy before execution and answers allow, review, or deny. It reserves budget against the daily and hourly limits, and the SDK commits or releases that reservation around the provider call. With no active policy the check fails closed.
Roadmap · warranty on approved volume
Preflight already decides. Shield adds what the decision is worth: a signed authorization token bound to the packet, a latency budget that fits a checkout, and a warranty on the volume LedgerLens approves. The warranty is in design and is not available today.
Roadmap · payment provider integrations
The Stripe adapter captures evidence today. The next step is the return path: when a provider opens a dispute on a transaction LedgerLens already holds, assemble the packet and file it through the provider API without manual log work. Adyen is the second target.
Built for a production pilot