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 and the AI drafts it. The AI never pays: a person approves every payment, and every step is recorded.
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.
From the dashboard, the AI Assistant, Slack or your own systems. Every channel goes through the same checks.
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.
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. The recipient is screened again just before the permit is issued.
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.
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.
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.
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 drafts the payment. You and a second person confirm it. Every step is recorded.
The UK has made Confirmation of Payee permanent and EU Verification of Payee is a year old. Here is how corporate payment teams can use both checks well.
Read the article →The OCC has finalised its US stablecoin rule, effective 18 January 2027. Here is what firms that hold or pay in stablecoins should review now.
Read the article →JPM Coin reached Ethereum and Jack Henry brought tokenized deposits to community banks. What changes for treasury controls when bank money runs 24/7 on many networks.
Read the article →For groups with several companies and accounts: the treasury work, the recurring payments and the approvals, in one place.
Several legal entities and bank accounts under one company, with balances per entity on the Treasury page and in the chat.
Move money between your own companies under a recorded agreement. Each transfer is booked as intercompany and shows in the report.
Set a minimum and maximum for an account. IXFXN proposes the top-up or the sweep, and a second treasury person approves it.
Watch the total cash in each currency. You get one message when it leaves your range, updated when it comes back.
Rent, salaries or grants on a schedule. Every payment in the series is approved and recorded on its own.
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-11-21). Payments run on simulated providers until real ones are connected.
Changed bank details need a second person before any payment uses them.
Match, Close match, No match or Verification not possible. Anything but a Match needs “I've seen the name check” before approving.
What each approver saw and confirmed is kept with the payment.
UK Confirmation of Payee and EU Verification of Payee stay with your bank. IXFXN works alongside them.
Name check results are simulated in the Beta. IXFXN does not perform the bank's check. Read: Payee name checks are here to stay
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.
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): read-only connections, live. Names belong to their owners.
Last updated
IXFXN (pronounced I-X Function) is an operating system for institutional money. It handles payment requests, rule checks, approvals, reconciliation and a tamper-evident ledger, with an AI Assistant that drafts the work for authorised people to confirm. It's live with real read-only connections to CoinPayments, DepiPay and bank statement files. In the Beta, payments themselves are simulated.
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.
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.
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.
Not yet: an MCP server for outside AI tools is in development. Ask us if you need it.
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.
Live with real read-only connections to CoinPayments, DepiPay and bank statement files; payments themselves are simulated in the Beta.
Sending real payments through connected bank and crypto providers.
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-11-21.
A working session with your treasury, operations, risk and technology teams, using your own approval rules.
Request a demo