Great question! In core banking transactions, eventual consistency is rarely used due to the need for immediate accuracy, so strong consistency models with ACID properties are preferred to avoid discrepancies like double spending. However, eventual consistency is applied in non-critical areas like customer activity tracking or fraud detection, where slight delays are acceptable. In strongly consistent systems, like those using the Clock-Bound Wait pattern, all nodes see the same committed data once a transaction is finalized, ensuring that no outdated information is displayed across nodes.