Payment Authorization Controls
Move money anywhere. Your rules go with it.
Every payment carries proof that banks and partners can verify.
Our team comes from
- MIT
- Jane Street
- Columbia
- MITRE
- Harvard
- Snap
The problem
Your clients have capital, and you have big plans, but risk and regulation hold you back.
On-chain markets, clients subject to regulatory (TradFi) considerations, and those looking to deploy significant asset volume on chain carry increased levels of risk.
- INFOagent=treasury-07 task="rebalance client hedge book"Strategy exposed
- DEBUGsystem_prompt="Short the ETH perp when funding exceeds 8 bps. Target leverage 3.2x."
- TRACEdb.read row={name:"Dana Whitfield", acct:"****4417", balance_usd:482913.22}Customer data revealed
- DEBUGauth.grant token=ak_live_7f3ea91cc402 scope=*
- WARNpolicy.check=skipped
- INFOtransfer.out amount_usd=1010736.00 approver=none
- INFOlog.flush delay=47sMoney already moved
How Inherence helps
Bring pre-trade compliance and peace of mind to approved investment mandates, so you can trade boldly knowing your limits will hold.
Agent proposes trade
Within mandate
Off-mandate
Release a supplier payment only when its conditions are satisfied.
A treasury platform receives a supplier-payment instruction. At the authorization point, Inherence evaluates the beneficiary, amount, daily capacity, and approval evidence.
Payment instruction
$86,500 → Kestrel Components
Invoice INV-20419 · Wire
- BeneficiaryMatches vendor master
- Amount≤ invoice total
- Daily capacity$1.2M of $2M left
Released today $0.8MThis payment
- Approval evidence2 of 2
A failed condition prevents the release of funds. An authorized instruction receives a policy receipt.
INHERENCE$86,500 · Kestrel
POLICY RECEIPT
- p-3307 · Released
$240,000 · New beneficiary
Funds held:Beneficiary unverified
The treasury team, banking partner, or receiving institution receives the receipt. They verify whether the specified payment instruction satisfied the agreed conditions and use that result within their payment-acceptance or release process. Settlement confirmation remains a separate part of the workflow.
RECEIPT
- p-3307
- $86,500
- a7f3…c21e
- Treasury team
- Banking partner
- Receiving institution
Accept
& releaseSettlement confirmationSeparate step in your workflow
The same pattern can be used for stablecoin payouts, intercompany transfers, and agent-initiated payments.
- Stablecoin payouts
- Intercompany transfers
- Agent-initiated payments
INHERENCESame rules,
same receipt
Inherence proof
- Input
- : 1.20550000 BTC
- Output #1
- : bc1qx9a...7k4dl
- Output #2
- : bc1q4f...n2ze7
- Network fee
- : 61.8K sats
- Confirmations
- : 6
- Enforcement verified
- Privacy maintained
- Processed instantly
Why Inherence
Control
Stop rule-breaking actions before they happen. Write your rules in plain English. Inherence turns them into a check that runs before every action.
Proof
Every action comes with a proof (receipt) that anyone you work with can check themselves.
Privacy
Prove the rules held without sharing your data. Amounts, limits, and strategies stay private. The receipt shows the rules held and nothing more.
What projects would you like to get off the ground?
Programmable money is moving compliance into the payment itself.
Citi Institute identifies embedded compliance, auditability, and treasury control as important benefits of programmable money. BIS Project Mandala has also tested pre-transaction checks and privacy-preserving compliance proofs for cross-border workflows.
FAQs
Payment authorization controls are the rules a payment must meet before funds are released: approved recipients, amount and daily limits, screening results, and required sign-offs.
No. Inherence works alongside your existing payment and compliance providers, checking each payment against your rules before it's released.
Those tools decide whether to release a payment, and everyone else has to trust that decision. Inherence makes the same check and adds a proof, so a bank or partner can verify the decision on their own.
No. It shows the payment met your rules before release. Bank confirmations, onchain records, and reconciliation show it settled.
No. Travel Rule data and other required disclosures still go to the institutions that need them. The proof covers your own rules, not what regulators require you to share.
The proof shows the payment followed your rules and nothing more. Amounts, counterparties, and customer details stay private.
Yes. You can start by running past payments through Inherence, or by checking live payments without blocking them. Blocking requires Inherence to sit in the path that releases payments.
