[redhale]

I also don't understand what your product actually does. What would help me: an example + diagram of a solution before and after the use of Ductape. How does this change things? The more detailed, the better (less marketing language, more example code / diagrams).

[Ifedayo_s]

So say you have multiple services that often need to process payments. For example, you have a billing service, a subscription service, and a checkout service, each responsible for handling different parts of the payment flow. Typically, these services integrate directly with a payment provider such as Adyen, Stripe, or Braintree. You have to duplicate logic across these services.

They all have to handle authentication, retries, error handling, and webhook processing separately. You have to manually configure and update and test across envs.

So if you want to make a change, you'll have to go into each service and rework the integration logic.

With Ductape, instead of embedding provider-specific logic in every service, you write it once and configuration files handle the differences between environments and providers. So you can use same logic across your billing, subscription, and checkout services without duplication.

If you want to switch providers, you don’t touch the logic at all. You just update the configuration.