C# Interface in OOPS – Complete Guide

What is an Interface in C#?

An Interface in C# is an OOPS concept that defines a contract. It tells a class what methods it must implement but does not define how those methods work.

public interface IShape
{
    void Draw();
    double CalculateArea();
}

Why is Interface Required in C#?

Interfaces are required to solve real software problems that simple classes cannot.

• Abstraction: Hide implementation details
• Multiple Inheritance: One class can implement many interfaces
• Loose Coupling: Reduces dependency between components
• Testability: Enables unit testing using mocks
• Scalability: Easy to extend systems

When Should We Use Interface?

• When multiple unrelated classes share behavior
• When building APIs or microservices
• When dependency injection is required
• When future changes are expected

How Interface Works (With Example)

public class Circle : IShape
{
    public void Draw()
    {
        Console.WriteLine("Drawing Circle");
    }

    public double CalculateArea()
    {
        return 3.14 * 5 * 5;
    }
}

IShape shape = new Circle();
shape.Draw();

Real Project Scenario – Payment System

public interface IPaymentService
{
    void ProcessPayment(decimal amount);
}

public class CreditCardPayment : IPaymentService
{
    public void ProcessPayment(decimal amount)
    {
        Console.WriteLine("Credit Card Payment");
    }
}

public class OrderService
{
    private readonly IPaymentService _payment;

    public OrderService(IPaymentService payment)
    {
        _payment = payment;
    }
}

✔ Easy to switch payment method ✔ No code modification ✔ Enterprise-ready design

Advantages of Interface

• Supports multiple inheritance
• Improves maintainability
• Encourages clean architecture
• Used heavily in ASP.NET Core

Explore related C# OOP concepts- abstract classes: C# Abstract Classes .

Frequently Asked Questions about Interface in C# (Beginner Friendly)