The engine
One engine, from meaning to message.
An agreed term sheet becomes a deterministic event schedule and the ISO 20022 messages that follow from it. Nothing is lost between the source and the ledger. Define, compute, service.
One common language
Every asset described once, in three layers.
The language is built on ISO 20022, the standard banks already use for payments and securities. Describe a tokenized deposit or a bond once, and it means the same thing on any ledger, in any institution, and it fits the ISO 20022 messages your back office already runs.
- 01
What it is
The instrument and its terms: issuer, currency, notional, dates and rates, the facts that identify it.
- 02
What you can do with it
The actions the asset admits, such as issue, transfer, pledge and redeem, and who may perform each.
- 03
What happens to it over its life
Coupons, resets, corporate actions and maturity: the events that produce cash flows and messages.
How it works
One bond, from term sheet to message.
Meaning is agreed before code exists. The engine computes deterministic cash flows for 30+ standard contract types. Positions move, payouts are computed and ISO 20022 messages are generated from the events.
Before and after
A new instrument becomes a configuration, not a project.
Before: terms re-keyed into three systems, coupon dates maintained by hand, breaks reconciled after the fact. After: one specification drives the schedule, the ledger and the messages; breaks cannot originate in the logic.
Before
- ×Terms re-keyed into three systems
- ×Coupon dates maintained by hand
- ×Breaks reconciled after the fact
- ×Months to onboard an instrument
After
- ✓One source drives schedule, ledger and messages
- ✓Every date computed, never typed
- ✓Breaks cannot originate in the logic
- ✓An instrument is a configuration
What it costs today
The bill already arrives every quarter.
a year in corporate actions processing, rising about 10% a year
average industry cost of a single corporate action event
of corporate action data still published and received manually
Why verification
Tokenization has platforms. It does not have trust.
Every platform re-implements financial logic as custom, unverified code, so the same bond behaves differently on every venue. Testing samples behaviour; it cannot establish it.
Programmable
- ×Sample-based testing
- ×Hidden edge cases
- ×Manual reconciliation
- ×Bespoke logic per venue
Provable
- ✓Verified contract logic
- ✓Complete event coverage
- ✓Deterministic outcomes
- ✓Ready for regulated markets
Determinism first
AI orchestrates. We execute.
Every payout is computed by the verified engine. AI agents extract terms, compose products and monitor events against the explicit specification; they never originate a number.
Where we fit
We do not replace your stack. We make it agree.
Phyntec is not a custodian, an exchange, a broker or an issuer. The engine runs alongside what you already run and supplies the one layer nobody else industrialises: contract behaviour you can prove.
- 01
Your platform
A tokenization network, a ledger repo service, a bank-owned platform or your own ledger. The engine supplies verified contract behaviour beside it.
- 02
Your core systems
Core banking, custody and the CSD keep their place. We generate the events and messages they already consume.
- 03
Market standards
ISO 20022 messaging, common lifecycle event models and industry data models: the interfaces your counterparties already speak.
The paid layers
Free where adoption is won. Paid where institutions already spend.
The core engine ships open source at general availability in 2027. Assurance and connectivity are what institutions pay for.
- 01
Assurance
Formal verification per contract family, conformance certification and the audit evidence regulators accept.
- 02
Rails
ISO 20022 message generation, bank rail connectivity and managed hosting, per institution.
- 03
Risk analytics
Liquidity, rate and counterparty exposure computed from contract event schedules, per portfolio.
Proof status
Published per contract family, as the work lands.
We would rather show a roadmap than claim a finished proof. Each family's status is published with its date, the proof scripts, the checker and a conformance suite you can run yourself.
- 01
Fixed-rate bonds
Specification and implementation complete. Machine-checked proof due end 2026.
- 02
Floating-rate notes and annuities
Specification complete, implementation in build. Target 2027.
- 03
Repo and collateral
Scoped. Target 2027.