A request comes in
From the dashboard, the AI Assistant, Slack or your own systems. Every channel goes through the same checks.
Ask for a payment in plain words. IXFXN drafts it, checks your rules and collects approvals. Nothing moves until an authorised person confirms.
Follow one payment through seven steps, then try it yourself in the Assistant.
From the dashboard, the AI Assistant, Slack or your own systems. Every channel goes through the same checks.
People, AI agents and integrations all pass the same check: spending limits, who is being paid, and your compliance rules.
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.
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.
A bank transfer here. The same payment could go through CoinPayments for custodial crypto or DepiPay for non-custodial, with the same rules.
An AI agent matches it to the bank or wallet statement and explains any difference. A person accepts or rejects the fix.
The entry is balanced and locked to the one before it, so any later change is detectable. Every step is in the audit trail.
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.
Preview · verify your company email to try it yourself
Names and amounts are illustrative.
“AI proposes. People confirm. Only the payment engine can move money.”— How IXFXN is built
IXFXN fits where larger payments go to known recipients and someone outside will check the record. Pick your industry.
Let AI agents do payment-operations work without ever touching funds.
Add approvals and an audit trail to payouts, without building them.
Pay suppliers and keep balances on target, with approvals built in.
Distributions and fund payments with partner sign-off and a provable record.
One set of rules across trusts, companies and family accounts.
Client trust payments approved, recorded and reconciled.
Closing disbursements with approvals and payee checks.
Owner payouts and deposit refunds, approved and on the record.
Grant payments with board approval and a clear record.
Not a fit today: consumer wallets, retail and small high-frequency payments, payroll at scale, card spend management.
No more rebuilding what happened from four systems and an email thread. Ask the questions an auditor would.
IXFXN records why each payment needed a person, turns repeat exceptions into software, and measures the result: human attention per successfully reconciled payment.
Illustrative target from the IXFXN blueprint. Not a measured customer result.
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.
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.
Last updated
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.
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.
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.
Today IXFXN runs against simulated bank transfers, tokenized deposits and USDC. Planned: CoinPayments as the default custodial crypto provider and DepiPay for non-custodial crypto. Each provider plugs in behind the same limits, approvals and ledger.
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.
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.
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.
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.
IXFXN is early. The honest version of trust at this stage is showing exactly what exists.
A complete platform blueprint: payments, rules, approvals, compliance, ledger, reconciliation and audit.
Automated checks block any change that lets AI, chat or integrations reach the payment engine.
A working control plane today, running against simulated providers.
Real bank and crypto providers, starting with CoinPayments and DepiPay.
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 partnerCounted from the IXFXN codebase on 2026-10-11.
The case for keeping the power to move money out of every AI model's reach.
Read the article →Protected core, pluggable providers, one doorway in: what the comparison buys you.
Read the article →What a good recommendation looks like, and who signs it off.
Read the article →A working session with your treasury, operations, risk and technology teams, using your own approval rules.
Request a demo