So, when should you go with eventual consistency versus strong consistency?

hey everyone, im wrestling with a design decision for a new feature that involves financial transactions. im trying to decide between eventual consistency and strong consistency for some of the data. on one hand, strong consistency feels safer for money, but it can really hurt performance and availability. eventual consistency is faster and more available, but the thought of stale data during a critical operation is unnerving. what are your experiences? when have you found eventual consistency acceptable, and what patterns do you use to mitigate the risks? or do you always lean towards strong consistency for critical systems, even with the performance hit?