Pre-settlement governance for agent payments

Money doesn't move until it's allowed to.

Six agents decide whether another agent's payment should settle, before a cent moves. Every decision is signed, reasoned, and replayable.

Revvyn sits in front of every autonomous-agent payment and returns one verdict, allow, block, or escalate, from a pipeline of agents that check identity, weigh policy and risk, and seal an immutable record. You can watch each decision happen, and verify it yourself.

Request Access →See a live payment get governed● Invite-only · private preview
·
Payments governed
·
Allowed
·
Blocked by policy
·
Escalated to review
Live cumulative figures from the governance engine (/v1/status), the actual current numbers, not projections. Early-stage and real; we show the true value, however small. "—" means the engine is momentarily unreachable, never a guessed number.
How it works

Six agents. Not six steps.

A payment intent comes in one side; a governed verdict comes out the other. But the six aren't stages in a script, they're agents, each working its own domain, and one agent's finding changes what the next one decides.

K
KYA
O
Orchestrator
G
Governance
C
Control
E
Execution
A
Audit
KYA
Verifies the agent's identity and standing. Its finding is a signal the others consume.
Orchestrator
Routes the decision and carries each agent's signal to the next.
Governance
Weighs policy against what KYA and the others found. A concern upstream can flip its verdict.
Control
Synthesises risk from every signal in play, not from the payment alone.
Execution
Selects the rail, and won't proceed without a clean decision behind it.
Audit
Seals the whole sequence, every signal, every verdict, into a tamper-evident record.

This is the part most systems don't have: the agents aren't a checklist, they influence each other, and the influence is recorded on the chain, so you can trace exactly which signal changed which decision.

The decision

Three outcomes. Each one explainable.

Every payment intent gets one verdict before settlement, and the reasoning behind it is captured in full, so a regulator, a partner, or you can ask why and get a real answer.

● Allow

Cleared to settle.

Agent verified, policy satisfied, risk within bounds. The payment proceeds to its rail.

agent_verified ✓ · policy_check ✓ · risk within_bounds → settle
● Block

Stopped before funds move.

A sanctions hit, an exposure ceiling, or a policy breach, the reason is logged, and no money leaves.

policy_check ✗ · reason ceiling_breach · funds_moved none → blocked
● Escalate

Sent for human review.

Borderline trust, or a dual-approval threshold. Settlement pauses; a human approves, rejects, or amends, and the step-up loop is recorded end to end.

trust borderline · threshold dual_approval · state paused → review
What's live today

See and verify every decision on your payments.

Every decision on your payments, visible and verifiable, running on real engine data. Numbers are early because the network is early; every figure is the genuine current value.

01

Your dashboard

Your payments governed, allowed, blocked, and escalated, with your live decision feed.

02

Replay your decisions

Re-open any of your past decisions and step through the signals and reasoning that produced it.

03

Watch your payment govern, live

See your payment move through the six agents, agent by agent, in real time.

04

Your API

Integrate directly: submit a payment, get one verdict, pull the signed audit trail.

Built — and deliberately staged

The organism is bigger than what's switched on.

A governance layer earns trust with deterministic, explainable decisions first. So the capabilities that make Revvyn more than a decision engine are built and tested, and deliberately not live yet.

Agent-to-agent negotiation

Agents resolving competing terms before a payment proceeds.

Built, tested, staged.

Contradiction resolution

When two signals disagree, a real mechanism reconciles them.

Live in our knowledge layer; staged for the payment path.

Cross-event memory

A decision about an entity today, recalled when that entity transacts tomorrow.

Write path live; recall staged.

Issuer step-up

The escalation contract is live and proven against a reference issuer. Plugging in a real bank's step-up is an integration, not a build.

Contract live; bank integration next.

We turned our most advanced capabilities off for launch on purpose, because determinism and auditability come before autonomy when the thing being governed is money. It's in the codebase. You can review it.

Where we are

Honest about what's live, and what's next.

Revvyn is pre-production: the governance engine is real and usable today. Production rail integrations and formal certifications are in progress, not complete. We won't claim otherwise.

Live today ● running
  • »Deterministic allow / block / escalate decision on every payment
  • »Six-agent decision pipeline with a signed, replayable audit trail
  • »Agents that consume each other's signals, cross-agent influence, recorded on-chain
  • »Tenant-isolated governance, proven under enforced row-level security
  • »Your dashboard, decision replay, and a live agent walk-through of your payments
  • »On-chain screening of observed transfers against policy
  • »Sandbox / test-money flows end-to-end
In progress roadmap
  • Production rail integrations with live settlement partners
  • SOC 2, controls being implemented, not yet certified
  • Regulatory mapping (FATF Travel Rule, MiCA, DORA), design intent, not certified
  • The staged organism capabilities (negotiation, contradiction, cross-event recall) moving to the live path
  • Expanded agent roster & multi-chain coverage
  • Independent security audit
Integration targets — in discussion / planned, not current partners
Card networksNeobanksExchangesSEPA / SWIFT / ACHStablecoin settlement
We name categories, not logos. Revvyn has no settlement partnerships to announce yet, any company named in conversations is a prospective integration, not a live customer. This page will list real partners only once agreements exist.
Watch it work

See a live payment get governed.

No slides, no recording. Fire a real payment through Revvyn's production pipeline right now and watch each agent decide, in order, with a signed and chain-verified trail.

Live governance · Ready
·KYAready
·Orchestratorready
·Governanceready
·Controlready
·Executionready
·Auditready
A real payment through the real production pipeline · every stage signed and chain-verified · no recording, no mock.

Revvyn is in invite-only private preview. The site and this live proof are open to view; access is granted by request.

Try to fool it

Forge a mandate. Watch it get caught.

Payment mandates are cryptographically signed. Sign one yourself with a key that is not Revvyn's, claim to be Revvyn's issuer, and submit it. Revvyn verifies the signature against Revvyn's real published keys, catches the forgery in-line, and escalates it for a human to review. It is never silently approved.

Live verification · Ready
Your browser will sign a payment mandate with a key that is notRevvyn's, claiming to come from Revvyn's issuer. Revvyn verifies it against Revvyn's real published keys and catches the forgery in-line. No mock, no recording.
A real forged credential, verified by the real production verifier · caught and escalated, never silently approved · every field is the genuine result of your run.

Where this goes: every agentic transaction, governed, with a decision that's explainable, recorded, and yours to verify.

Today that's payments through a six-agent pipeline. The direction is the standard the rest of the stack can assume.

GOVERNED BEFORE SETTLEMENTALLOW · BLOCK · ESCALATEEVERY DECISION SIGNED & REPLAYABLEPRE-PRODUCTIONGOVERNED BEFORE SETTLEMENTALLOW · BLOCK · ESCALATEEVERY DECISION SIGNED & REPLAYABLEPRE-PRODUCTION
live.logdecision feed — endpoint pending (public read)
agents.online
settled
·
escalated
·
policy.pass