Not five companies.One loop.
Your money arrives from somewhere, waits, and leaves for somewhere else. Today each of those three things belongs to a different company, and none of them knows what the others are doing. That is not a law of finance. It is what happens when nobody owns the whole cycle.
You did not choose a stack. You inherited one.
A bank to hold it. A broker or an app to convert it. Something else to send it. A deposit or a fund for whatever is left over. A spreadsheet to remember which is which. Five relationships, and the only thing joining them is you, which is why the reconciling happens at the end of your day rather than inside a system.
The cost of that is charged twice. Once in the obvious place, as a spread on every conversion and a fee on every transfer. And once where nobody itemises it: money that sits at zero because the thing that would pay for it cannot be unwound in time, and decisions that wait because you are the only integration between five systems that will never talk to each other.
One cycle, four positions
Krypton Pay is where value arrives and where it leaves: the same band, both ends, because it comes back. The Yield Engine is what happens to it in between. Clark is in the middle because it is the only one of the three that is not a place money rests: it holds the calendar and acts on it.
A salary, an invoice, a client transfer, money from home. It settles as the pair it actually is, rather than being routed through a third currency that charges on the way in and again on the way out.
INR, AED, EUR, GBP and USD, as netting pools
Out to the people and places it was already committed to, in their own currency, on the date it was due, and back to the top of the same loop next month.
The same balance, both directions
Rent, wages, a supplier, a fee with a due date. Clark knows what is committed and when, so it works backwards from the dates rather than waiting to be told each time.
One instruction instead of one login per obligation
Almost no balance is spent the day it arrives. The gap between landing and leaving is a horizon, and a position sized against that horizon can be unwound on it.
Allocated against a mandate you set, not a product you pick
Nothing in that diagram is a product you buy separately, and the order is not a pipeline — position 04 is the same band as position 01. That is what makes it a loop: the money that leaves this month is the money that arrives next month, and the only question a system has to answer is what it should be doing in between.
The same loop, four journeys
Each of these draws the diagram above with different amounts in it. They are sorted by the only thing that really differs — why the money crosses a border: because you sell, because you work, because someone you are responsible for is on the other side, or because software decided it should.
None of these is exactly you, and that is expected: they are four readings of one mechanism rather than four products. The size changes by three orders of magnitude between the first and the last, and the four positions do not move.
