Product In development
Evidence for what an agent did, payment by payment
Pehtee-Nu turns the logs you already keep into a record of what an agent did on a specific payment, one someone outside your team can check.
What it answers
Not only whether a payment matched its instruction, but whether the instruction was sound
Did execution match the instruction?
Right payee per the instruction, right amount, right date. Card networks have started checking this at the rail.
Should the instruction have been given?
What the agent saw, what it weighed, and why it acted. A payment to a fraudster, made exactly as instructed, passes the first test and fails this one.
How it works In development
After the fact, from records you already have
Pehtee-Nu works from read access to existing logs. It never sits in the payment path or holds up a payment.
For a single payment, it rebuilds the path from instruction to execution, with the underlying records attached so the result can be checked rather than taken on trust.
Capabilities
What we're building
Payment reconstruction In development
The path from instruction to execution for a single payment, rebuilt from the records around it.
Evidence packages In development
A reconstruction prepared for a counterparty, an auditor or an examiner, with its sources attached.
Systems we read from In development
The agent frameworks, payment platforms and log formats Pehtee-Nu reads from.
How we handle your data In development
Security and data-handling practices, published before any customer data is handled.
Help shape what we build
We're choosing what to build first from how teams handle agent-initiated payments today. If that's your work, we'd like to hear from you.