I’m just a customer like you, but I have experience in software development and system architecture…
It looks to me (just a wild guess), that instead of having some generic abstract model of “amount”, which should take care of all currency conversion and value comparison automatically across the system, they are using hard-coded logic in each place, therefore they need to “reinvent” this logic every time. OR someone just hard-coded some numbers instead of using abstract model in some parts of the app.
It also looks like card limits are country specific, so, most likely, they are defined in the system in a local currency. Therefore this problem doesn’t appear there.
If that’s really the case, then fix, indeed, will require significant amount of work.
But, as I said, It’s just a wild guess, there are many other options as well. What we see in the app is just the top of the iceberg and it’s almost impossible to know what is under the hood, so I might be completely wrong about that
But what makes me really sad, is that these bugs are actually sign of poor code review & Q&A processes in a dev team, and I really hope Curve will address that ASAP.
@Hannah , I think this is something Curve management should be paying attention too.