Skip to content

Control Fabric

The control plane over every payment

Four components hold the rules, the evidence, and the record, in continuous dialogue with execution on every rail.

Four components on one governed surface

Each component is independently auditable. Together they decide what may move, under whose authority, and with what evidence.

01 · The rulebook is data, not prose.

Scheme Rules & Rulebook

Scheme, jurisdiction, rail, network, member: five levels of rules, held as data and applied in cascade to every payment the fabric touches.

Scheme Rules & Rulebook

Versioned rules

Every rule versioned. Every amendment recorded.

02 · Deterministic rules enforced at runtime.

Policy Engine

Limits, thresholds, corridors, currencies, time windows, risk appetite, and jurisdiction rules run deterministically against every payment.

A breach is not flagged. It does not proceed.

Policy Engine

Real-time holds

A status change holds warehoused payments in real time.

03 · A zero-trust vault for the evidence behind every payment.

Trust Vault

Identity, incorporation, source of wealth and funds, and beneficiary documents, classified and verified automatically, with member consent captured at onboarding.

Trust Vault

Expiry monitoring

Expiry and version monitoring, with renewal workflows before documents lapse.

04 · Every decision writes its own record.

Evidence & Audit Ledger

Rule, version, inputs, outcome, timestamp: recorded for every decision the fabric takes, at the moment it happens.

Evidence & Audit Ledger

Tamper-evident

Hash-chained and tamper-evident.

01Scheme Rules & Rulebook

The rulebook is data, not prose.

Scheme, jurisdiction, rail, network, member: five levels of rules, held as data and applied in cascade to every payment the fabric touches.

Versioned rules
Every rule versioned. Every amendment recorded.
Reconstructable history
The rule set in force at any moment can be reconstructed, exactly as it stood.
One cascade
One cascade resolves which rules apply, from scheme down to individual member.
02Policy Engine

Deterministic rules enforced at runtime.

Limits, thresholds, corridors, currencies, time windows, risk appetite, and jurisdiction rules run deterministically against every payment.

A breach is not flagged. It does not proceed.

Real-time holds
A status change holds warehoused payments in real time.
Every rail and every way in
The same rules apply on every rail and through every way in.
Agents bounded
Agents are bounded by delegated authority, enforced at runtime like any other rule.
03Trust Vault

A zero-trust vault for the evidence behind every payment.

Identity, incorporation, source of wealth and funds, and beneficiary documents, classified and verified automatically, with member consent captured at onboarding.

Expiry monitoring
Expiry and version monitoring, with renewal workflows before documents lapse.
Evidence travels
The evidence reference travels with every payment.
Agent mandates
Agent mandates live here: principal, scope, limits, expiry.
04Evidence & Audit Ledger

Every decision writes its own record.

Rule, version, inputs, outcome, timestamp: recorded for every decision the fabric takes, at the moment it happens.

Tamper-evident
Hash-chained and tamper-evident.
Per-access logging
Per-access logging on every evidence retrieval.
Feeds reporting
Feeds audit and regulatory reporting directly.

Know Your Agent

Agents are a new principal class

When software agents initiate, validate, and reconcile payments, the question is not whether they can move money but under whose rules. CPN treats them as principals: identified, mandated by a documented principal, and bounded by the same fabric as every payment.

An agent is only as trusted as its mandate.

Every agent-initiated payment passes the same control surface as a human one: identity, policy, limits, approvals, audit.

01

Agent identity

Every agent is registered, credentialed, and bound to a named operator and principal. No shared credentials, and interoperable with emerging agent identity protocols.

02

Mandate as evidence

Authority is delegated from a KYB'd principal and held in the Trust Vault: principal, scope, limits, expiry. Re-approval workflows keep it current. An agent holds no standing of its own.

03

Runtime enforcement

Standing, mandate, and policy are checked at every stage. A request outside scope does not proceed. Human approval thresholds and four-eyes apply to agent actions unchanged.

04

Attestation and kill switch

Every action is recorded against its mandate, with immutable audit per decision. Revocation is instant and halts in-flight instructions.

01Agent identity

Every agent is registered, credentialed, and bound to a named operator and principal. No shared credentials, and interoperable with emerging agent identity protocols.

02Mandate as evidence

Authority is delegated from a KYB'd principal and held in the Trust Vault: principal, scope, limits, expiry. Re-approval workflows keep it current. An agent holds no standing of its own.

03Runtime enforcement

Standing, mandate, and policy are checked at every stage. A request outside scope does not proceed. Human approval thresholds and four-eyes apply to agent actions unchanged.

04Attestation and kill switch

Every action is recorded against its mandate, with immutable audit per decision. Revocation is instant and halts in-flight instructions.

Checked before, during, and after

Two payments compared side by side.

Without CPN

Checked after it moves

One leaves unchecked and freezes at the bank.

  1. Sent

    The payment leaves on the strength of whoever keyed it.

  2. Screened downstream

    Compliance runs at the bank, after funds are committed.

  3. Frozen

    The payment stops. The investigation starts. The counterparty waits.

Days of investigation to recover a payment that should never have left.

With CPN

Governed before it moves

One clears every check before it moves, then attests at delivery.

  1. Standing at capture

    The principal, human or agent, is verified before the instruction exists.

  2. Evidence at validation

    The Trust Vault confirms the documents behind the payment are current.

  3. Policy at routing

    Limits, corridors, screening, and time windows enforced before a rail is chosen.

  4. Release at approval

    Thresholds and four-eyes approval apply, then the payment releases to the rail.

  5. Attestation at delivery

    The Evidence & Audit Ledger closes the record: rule, version, inputs, outcome, timestamp.

The payment arrives once, clean, with its audit trail already written.

Set your rules once. CPN applies them to every transaction, on every rail.