™I-X Function Run a scenarioRequest a demo

The operating system
for institutional money

Ask for a payment in plain words. IXFXN drafts it, checks your rules and collects approvals. Nothing moves until an authorised person confirms.

Demo for business users · company email required
Payments on the globe are illustrative.
how a payment moves

AI reasons. IXFXN authorises. The payment engine executes.

No more rebuilding what happened from four systems and an email thread. Ask the questions an auditor would: follow one payment through seven steps, then try it yourself in the Assistant.

Step 1 of 7 · Requested

A request comes in

From the dashboard, the AI Assistant, Slack or your own systems. Every channel goes through the same checks.

Step 2 of 7 · Policies passed

Checked against your policies

Every request, whether it comes from a person, an AI agent or one of your systems, is checked against the same policies: who may spend how much, who may be paid, and your compliance rules. Here: spending-limit rules version 12, and recipient screening found no match.

Step 3 of 7 · Needs 2nd approval

The approvals your rules require

Usually a second person. Small firms can pre-authorise a limit instead, with an after-the-fact review. The requester can never approve their own payment.

Step 4 of 7 · Permit issued

A permit that works once

The payment engine has its own credentials and cannot use any AI. It receives a permit for this exact payment that works once and expires within 60 seconds. The recipient is screened again just before the permit is issued.

Step 5 of 7 · Sent

Sent through your provider

IXFXN picks the cheapest provider that meets the deadline and fee limit: a bank transfer here. The same payment could go through CoinPayments for custodial crypto or DepiPay for non-custodial, with the same rules.

Step 6 of 7 · Completed

Paid and locked into the ledger

The provider confirms the money arrived. Only now does IXFXN call it paid. The ledger entry is balanced and locked to the one before it, so any later change is detectable.

Step 7 of 7 · Reconciled

Checked against the statement

An AI agent matches it to the bank or wallet statement and explains any difference. A person accepts or rejects the fix. Every step is in the audit trail.

now try it

Ask. Review. Confirm.

The same payment, from the chat. Pick a suggestion, then drag the slider to confirm. Switch to Desktop at any point: it shows the same thing.

Review each step above

IXFXN Assistant

Names and amounts are illustrative.

Perspectives

What we're thinking about.

View all articles

what you can do today

Built and working now.

For groups with several companies and accounts: the treasury work, the recurring payments and the approvals, in one place.

Treasury

Many entities, one view

Several legal entities and bank accounts under one company, with balances per entity on the Treasury page and in the chat.

Treasury

Transfers between your entities

Move money between your own companies under a recorded agreement. Each transfer is booked as intercompany and shows in the report.

Treasury

Accounts kept in range

Set a minimum and maximum for an account. IXFXN proposes the top-up or the sweep, and a second treasury person approves it.

Treasury

Cash alerts

Watch the total cash in each currency. You get one message when it leaves your range, updated when it comes back.

Payments

Recurring payments

Rent, salaries or grants on a schedule. Every payment in the series is approved and recorded on its own.

Assistant and Slack

Everything from the chat

Create recipients, chase approvers and set up recurring payments in the Assistant, and approve with one tap in Slack.

Each card is checked against the IXFXN code on every update (last 2026-10-24). Payments run on simulated providers until real ones are connected.

industries

Built for money held under a duty of care.

IXFXN fits where larger payments go to known recipients and someone outside will check the record. Pick your industry.

01 / 09

Banks and financial institutions

Let AI agents do payment-operations work without ever touching funds.

“Why didn't payment PI-4832 reconcile, and what should we do?”
02 / 09

Fintech and payment companies

Add approvals and an audit trail to payouts, without building them.

“Show payouts over 50,000 USD that are waiting for approval.”
03 / 09

Corporate treasury

Pay suppliers and keep balances on target, with approvals built in.

“Pay Acme Supplies 12,400 USD from operating for invoice 2291.”
04 / 09

Private equity, asset and venture managers

Distributions and fund payments with partner sign-off and a provable record.

“Draft the Fund II distribution of 3,200,000 USD to LPs.”
05 / 09

Family offices

One set of rules across trusts, companies and family accounts.

“Who can approve payments from the family trust over 100,000 USD?”
06 / 09

Law firms: client trust accounts

Client trust payments approved, recorded and reconciled.

“Pay the settlement of 85,000 USD from client trust for matter 2026-114.”
07 / 09

Real estate escrow and title

Closing disbursements with approvals and payee checks.

“Draft the closing disbursements for 14 Harbour Road.”
08 / 09

Property managers

Owner payouts and deposit refunds, approved and on the record.

“Refund the 2,400 USD deposit for unit 4B.”
09 / 09

Non-profits and foundations

Grant payments with board approval and a clear record.

“Pay the second 40,000 USD instalment of the Riverside Literacy grant.”

Not a fit today: consumer wallets, retail and small high-frequency payments, payroll at scale, card spend management.

the economic argument

Less human attention per payment, without less control.

IXFXN records why each payment needed a person, turns repeat exceptions into software, and measures the result: human attention per successfully reconciled payment.

12 minMonth 1
3.4 minMonth 6
38 secMonth 12
6 secMonth 24

Illustrative target from the IXFXN blueprint. Not a measured customer result.

Payments→Exceptions a person handled→Why they needed a person→AI diagnosis→New automated rule→Fewer exceptions

See your savings in a live demo

locked ledger

Every entry is locked to the one before it.

Each ledger entry carries a fingerprint of the previous one. Change any past entry and every fingerprint after it breaks, so tampering shows up in the audit check.

Example entries, fingerprinted (SHA-256) in your browser.
providers

Connect any provider. The rules stay the same.

Banks, tokenized deposits, custodial and non-custodial crypto: each plugs in behind the same limits, approvals and ledger.

CoinPayments (custodial) and DepiPay (non-custodial): integrations planned. Names belong to their owners.

questions

Straight answers.

Last updated

What is IXFXN?

IXFXN (pronounced I-X Function) is a control plane for institutional money. It handles payment requests, rule checks, approvals, sending through connected payment providers, reconciliation and a tamper-evident ledger, with an AI Assistant that drafts the work for authorised people to confirm.

Can the IXFXN AI Assistant move money on its own?

No. The Assistant can draft, explain and investigate, but a person confirms every draft it prepares, and the payment then needs the approvals your rules require: usually a second person, or a limit that a named person pre-authorised in advance, with an after-the-fact review. The part of IXFXN that sends money, the payment engine, cannot use any AI component; that separation is checked automatically on every code change. It only acts on a permit for one exact payment, which works once and expires within 60 seconds.

Is IXFXN a regulated financial institution?

No. IXFXN builds the software. Regulated activity is carried out by IXFXN's customers and the payment providers integrated with IXFXN, under their own licences.

Which payment providers does IXFXN connect to?

IXFXN connects to CoinPayments as the default custodial crypto provider and DepiPay for non-custodial crypto. It also runs against simulated bank transfers, tokenized deposits and USDC. Each provider plugs in behind the same limits, approvals and ledger.

Do I have to use the chat?

No. You can switch between the Desktop view and the Assistant at any step. Both show the same live payment, so nothing is copied and nothing goes stale.

How does IXFXN stop anyone changing past records?

Every ledger entry is balanced and carries a fingerprint of the entry before it. Changing any past entry breaks every fingerprint after it, which the audit check on the dashboard detects.

Can outside AI tools like ChatGPT or Claude use IXFXN?

Yes, through the IXFXN MCP (Model Context Protocol) server. Today it is read-only: outside AI tools can look up payment status and audit trails and run IXFXN's reporting agents. They cannot draft, confirm or send payments.

Which industries is IXFXN built for?

Organisations that move larger payments to known recipients under a duty of care someone can audit: banks and financial institutions, fintech and payment companies, corporate treasury, private equity and asset managers, family offices, law firm client trust accounts, real estate escrow and title, property managers, and non-profits and foundations.

where we are

We'd rather show you the architecture than a logo wall.

IXFXN is early. The honest version of trust at this stage is showing exactly what exists.

Specified

A complete platform blueprint: payments, rules, approvals, compliance, ledger, reconciliation and audit.

Enforced

Automated checks block any change that lets AI, chat or integrations reach the payment engine.

Working

A working control plane today, running against simulated providers.

Next

Real bank and crypto providers, starting with CoinPayments and DepiPay.

Design partners

Become a design partner.

We're working with a small number of institutions to shape IXFXN before general release. Design partners get early access, a say in the roadmap, and preferential pricing.

Apply to be a design partner
How it's built
3,675automated tests across 407 test files
23architecture rules checked on every code change, including that AI can't reach the payment engine
86database changes, each reviewed and versioned

Counted from the IXFXN codebase on 2026-10-24.

Talk to IXFXN.

A working session with your treasury, operations, risk and technology teams, using your own approval rules.

Request a demo