isomer

How it works

The facility lifecycle as we run it, written for the person at the fund who runs facility operations.

You can follow every step on the demo facility: a synthetic Saudi SME lender with a senior and a mezzanine murabaha tranche, twelve months of history, and every screen marked demo data.

The facility lifecycleTwo steps once at the start: onboarding the agreement and connecting the loan system. Then, every period: daily eligibility, the borrowing base certificate, draw requests, the waterfall run, collections reconciliation, covenant tests and reporting, and back to eligibility.01Onboarding the agreement02Connecting the loan system03Daily eligibility04Borrowing base certificate05Draw request06Waterfall run07Collections reconciliation08Covenant tests09ReportingOnceEvery period
  1. 01

    Onboarding the agreement

    Agent, with both sides

    We go through the facility agreement with the fund and the fintech and write its terms down as data: eligibility criteria, concentration limits, advance rates, reserves, the waterfall, the covenants and the reporting dates.

    Both sides check that record of the terms before anything runs on it. The agreement itself does not change.

  2. 02

    Connecting the loan system

    Fintech

    The fintech sends its loan tape. Today that is a CSV upload. A direct connection to the loan system comes next.

    Every row is checked. A row that cannot be read is reported with its line number and the reason, not dropped quietly.

  3. 03

    Daily eligibility

    Runs on its own

    Each tape runs through the eligibility rules in the order the agreement lists them. Every loan comes out eligible, or with the first rule it failed and why, in words.

    Concentration limits run next. Anything above a limit is cut from the newest loans first, so a loan can count in part.

  4. 04

    Borrowing base certificate

    Runs on its own

    The borrowing base is worked out from the eligible balance, the advance rates, the reserves and the commitment, with every line shown.

    The certificate is that working as a PDF, tied to a version of the record, so the number on it can be checked later.

  5. 05

    Draw request

    Fintech asks, agent approves

    The fintech asks for an amount. It is checked against what is available that day and split across the tranches by commitment.

    If it fits, it goes to the agent to approve. The fund sees the request, the check and the decision.

  6. 06

    Waterfall run

    Agent

    At the end of each period, the cash collected is paid out in the order the agreement sets: fees, then profit or interest by tranche, then principal where it is due, then the rest back to the fintech.

    Murabaha profit and conventional interest are each worked out to the day on the tranche's own day count. The result is a list of payment instructions for the account bank. We do not hold or move the money.

  7. 07

    Collections reconciliation

    Runs on its own; a person takes the exceptions

    Every credit on the collection account is matched to instalments on the tape: by reference first, then by amount and date where the reference is missing. One transfer can clear several instalments.

    What does not match goes to a person, with the reason: paid short, overpaid, unpaid, or money nobody can place.

  8. 08

    Covenant tests

    Runs as data arrives

    Each covenant is tested when the data it needs arrives: the tape, the bank statement, the management accounts.

    Each one shows passing, watch or breach, with the number behind it. A breach shows the date it started and the last day to cure it.

  9. 09

    Reporting

    Both sides

    The fund and the fintech look at the same screens and the same numbers. Each period's state is fixed as a new version of the record, which an auditor or a new lender can check against the chain.

What goes on-chain and what doesn't

Each version of the record is a snapshot of the facility's state: the terms, the eligibility totals, the borrowing base and its working, the covenant results, the waterfall and the collection totals. Both sides keep the snapshot.

Its fingerprint, a keccak-256 hash, goes on-chain on Robinhood Chain, with Arbitrum next, together with a version number and the time. That is all that goes on-chain: commitments and state transitions.

On-chain

  • The fingerprint of each version of the record
  • The version number and when it was published

Never on-chain

  • The loan tape, or any loan in it
  • Any fee. The fee letter is not even in the snapshot
  • Any threshold, rate or limit

Anyone holding a snapshot can recompute its fingerprint and compare it with the chain. That is how a new lender or an auditor checks the history without having to trust us.

There is no token. There is no custody: we never hold the facility's money. You do not need a wallet: you log in with your email. In this first phase isomer publishes the fingerprint on behalf of the parties; a party can later publish from its own address.