Was the integration adapter with payment gateways an abstraction over different providers?

Yes, the integration adapter with payment gateways is usually implemented as its own abstraction, which hides the differences between various providers. This allows having a unified interface for working with payments, regardless of the specific gateway.

For example, each provider may have its own APIs, request formats, and error handling. The adapter encapsulates these details, providing common methods such as initiatePayment(), refund(), checkStatus(). This simplifies system maintenance and expansion, as adding a new provider only requires implementing a new adapter that conforms to the common interface.