Money is now a JSON string everywhere
Every monetary field in the Kordio API (amounts, balances, and report totals) is now serialized as a decimal string of integer minor units matching^-?\d+$, for example "100", "25500000", or "1000000000000000001".This is a breaking correctness fix. The wire format was previously inconsistent: posting amount was a string, but balances and report totals (posted, pending, available, trial-balance and statement totals, and so on) were JSON numbers. A JSON number silently loses precision above 2^53, which is only about 0.009 ETH at 18 decimals, so high-value or 18-decimal token balances could come back wrong. Making every money field a string removes that whole class of corruption. There is no live customer, so this lands directly in v1 with no deprecation window.Before
After
What you need to do
Parse every money field with a big-integer or arbitrary-precision decimal type, notNumber:amount still accepts an integer or a decimal string on the way in. Reads always return a string. The per-currency currency_decimals field (an integer count, not money) is unchanged, so you keep formatting display values the same way.