Ayrte — the trust layer for self-funded healthcare payments

Ayrte is financial infrastructure for the U.S. self-funded employer healthcare market. We are not an insurer, a claims adjudicator, or a payment processor — we are the trust layer between the parties who authorize healthcare payments and the parties who receive them, giving everyone in the chain a shared, independently verifiable record of what was owed, what was paid, and when.

The problem

Self-funded employers pay their employees’ healthcare costs directly rather than through an insurer, and have almost no visibility into where those dollars go once a claim is approved. The Third-Party Administrators (TPAs) and Direct Primary Care (DPC) organizations who administer these plans lack the infrastructure to provide that transparency, and rebuild reporting and reconciliation from scratch with every new client. Meanwhile hospitals and providers are often pushed into fee-heavy payment methods that quietly erode their margins.

What we build

An immutable, permissioned ledger capturing every transaction — claim authorized, payment executed, reconciled — with a verifiable audit trail, where each party sees only their own view. Settlement runs through a real, FDIC-insured banking partner: Ayrte never holds client funds, and keeps a sub-ledger tracking each party’s position against that master account. We ingest claims data as industry-standard EDI (837, 835) downstream of adjudication, and store no clinical content. Contract-rate verification and discrepancy flagging are free to every provider on the network.

Who it’s for

Self-funded employers who need to see where their healthcare dollars go; TPAs and DPCs who need transparency they can offer every client without rebuilding it each time; and hospitals and provider groups who need to know that what they were paid matches what they contracted for.

Security and compliance

Zero custody of client funds by design, role-based permissioned access, encryption, and alignment with the FTC Safeguards Rule alongside progress toward SOC 2. The audit trail is hash-chained, so altering or reordering a record breaks every link that follows and is detectable by anyone holding the chain.

Loading the interactive experience…