📘 Scenario:

Imagine you are developing an e-commerce app. When a user checks out, they can choose from different payment methods:

• 💳 Credit Card
• 💸 PayPal
• 💰 Cryptocurrency

Each method has a different algorithm/logic for processing payments.

Problem:

If you try to handle all payment methods in a single PaymentProcessor class using if-else or switch, your code will:

• Become harder to manage
• Violate the Open/Closed Principle (OCP)

💡 Strategy Pattern Solution:

We define a common interface for all payment methods. Then, we plug in the appropriate payment strategy at runtime.

Output:

Paid Rs. 1500.0 using Credit Card.
Paid Rs. 5000.0 using PayPal.
Paid Rs. 12000.0 using Cryptocurrency.