OOP & Design Patterns - Strategy Pattern - Replace Conditionals with Polymorphism
You want to enhance a payment system to allow splitting a single payment across multiple payment strategies simultaneously (e.g., part credit card, part UPI). Which design approach best supports this requirement, given that the naive Strategy Pattern supports only one strategy at a time?
