Pre-settlement governance for agent payments

Agent payments, decided before money moves.

Revvyn decides before money moves. Your rail (SEPA, card, stablecoin) executes. Revvyn never holds or moves funds.

Six checks, run in sequence — agent standing, routing, policy, risk, rail hand-off and audit — decide whether an agent's payment is allowed, blocked or escalated. Deterministic, and recorded.Every decision is reasoned and replayable; verdicts from Revvyn's verifiable-verdict API are cryptographically signed and sealed into an append-only, hash-chained record you can re-run chain verification on in the console.

Request access →See a live payment get governed● Invite-only · private preview
·
Payments governed
·
Allowed
·
Blocked by policy
·
Escalated — awaiting review
·
In progress / other
Live cumulative figures from the governance engine (/v1/status). Test and sandbox activity — no production traffic yet. True database counts, never estimates. Allowed, Blocked by policy, Escalated and In progress / other sum to Payments governed. Escalated counts payments awaiting review now; once an escalation is resolved it is counted under its final outcome. Evaluate-only quotes are excluded. "—" means the engine is momentarily unreachable, never a guessed number.
How it works

Six checks, in sequence.

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.

S
Agent standing
O
Orchestrator
G
Governance
C
Control
E
Execution
A
Audit
Agent standing
Checks the agent is registered to this partner and assesses its 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 the standing check 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
Hands the cleared payment to the rail the Control agent selected, and won't hand off without a clean decision behind it.
Audit
Seals the whole sequence — every signal, every verdict — into an append-only, hash-chained record.

This is the part most systems don't have: the checks aren't a mere checklist — each consumes the signals the earlier ones produced, and that is recorded in the append-only, hash-chained audit log, so you can see which earlier signals each check used.

The decision

Three outcomes. Each one explainable.

Every payment intent sent to Revvyn 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 in good standing, policy satisfied, risk within bounds. The payment proceeds to its rail.

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

Stopped before funds move.

A sanctions hit (OFAC crypto-wallet screen or a restricted jurisdiction), 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 payment above the review threshold. It's held for human review; a reviewer approves or rejects (single reviewer today; two-person sign-off is not yet enforced), and the escalation and step-up loop are recorded end to end.

trust borderline · amount ≥ review_threshold · state paused → human 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 checks, stage by stage, in real time.

04

Your API

Integrate directly: submit a payment, get one verdict, pull the append-only, hash-chained audit trail.

Built — and deliberately staged

More is built than is switched on.

A governance layer earns trust with deterministic, explainable decisions first. So some capabilities beyond the decision engine are built to varying degrees — some tested, some still dormant — and are deliberately not live yet. Each is labelled below with exactly where it stands.

Agent-to-agent negotiation

Agents consult on corridor posture today with a one-way, static response; multi-round negotiation is modelled and unit-tested but is not produced by any agent yet.

Dormant — not live; no agent negotiates today.

Contradiction resolution

Inter-agent contradictions are detected automatically and surfaced for human resolution; automated evidence-weighted resolution is built and tested but not yet wired to the payment path.

Detection built and active in code; automated resolution not on the payment path — no production traffic yet.

Cross-event memory

Decisions and events are written to memory and looked up on later events.

Write and recall built and active in code; to date no decision has used a recalled memory to change its outcome; cross-partner recall staged.

Issuer step-up

The escalation contract is built and active in code, with completion tested against a reference (test) issuer in our test suite. Plugging in a real bank's step-up is an integration, not a build.

Contract active in code; no production bank integrated and no step-up completed in production.

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 sent to Revvyn
  • »Six-stage decision pipeline with a replayable, append-only, hash-chained audit trail
  • »The stages consume each other's signals — cross-stage influence recorded in the append-only, hash-chained audit log
  • »Tenant-isolated governance, proven under enforced row-level security
  • »Your dashboard, decision replay, and a live agent walk-through of your payments
  • »OFAC crypto-wallet sanctions screening on the payment path; off the payment path, Revvyn observes USDC/USDT transfers on Ethereum
  • »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 coverage — FATF Travel Rule thresholds enforced in the pipeline; MiCA and DORA mapped as design intent, none independently certified
  • →The staged capabilities (agent negotiation, automated contradiction resolution) 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 governed decision, live.

No slides, no canned demo. Run a governed decision through Revvyn's live pipeline right now — a scripted test scenario; no money moves — and watch each agent decide, with a chain-verified trail.

Live governance · Ready
·Agent standingready——
·Orchestratorready——
·Governanceready——
·Controlready——
·Executionready——
·Auditready——
A real governed decision through the live pipeline · a scripted test scenario, no money moves · every stage hash-chained and chain-verified · not a recording.
Request access →

Revvyn is in invite-only private preview. The site and this live proof are open to view; access is granted by request. Prefer a guided start? Request access →

Try to fool it

Forge a mandate. Watch it get caught.

Signed mandate credentials presented to Revvyn are verified against published keys. 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 published keys and catches the forgery in-line — a live signature check, not a recording.
A real forged credential, verified by Revvyn's live 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 re-run chain verification on in the console.

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

GOVERNED BEFORE SETTLEMENTALLOW · BLOCK · ESCALATEEVERY DECISION REASONED & REPLAYABLEPRE-PRODUCTIONGOVERNED BEFORE SETTLEMENTALLOW · BLOCK · ESCALATEEVERY DECISION REASONED & REPLAYABLEPRE-PRODUCTION
allowed
·
escalated
·