Commit

8c3f949

Storing money as BIGINT in minor units (cents/poisha) works fine until you hit multi-currency FX conversions or fractional unit pricing where you need four decimal places. Using NUMERIC(19, 4) in Postgres paired with brick/money in PHP avoids floating-point rounding bugs…
Just as you don't have multiple time zones in a system, you don't add multiple currencies. That is inviting problems. You use foreign currencies for input and display. Everything else is on your preferred currency alone. Bringing modules and architecture to juggle multiple moving values is inviting problems. Money comes in, you store what foreign currency was the input, what the amount was, and convert. From that point on, it is minor units in the chosen currency all the way.

commit 8c3f949