luceos I would like to clarify my position on this matter. Andrew and I have been discussing this concept for quite some time. While I am capable of developing an ad management extension, integrating a subscription system is a different challenge that would require a significant budget and resources.
To be clear, the requirement here is not simply moving a user to a specific group upon payment. We need to track recurring monthly payments for individual ad placements, such as a header banner.
If I had access to the source code of the Payments extension, I might be able to hook into certain data or extend its logic; however, I am concerned that it still might not offer the necessary flexibility for this specific use case.
What is being requested goes beyond one-time transactions; it requires a dedicated subscription architecture for each ad unit. While Stripe makes managing these processes relatively easier, I still need to access Stripe API data and have the ability to trigger manual synchronizations when necessary. Furthermore, we need to include additional metadata, such as promotion codes, within the payment API requests.
Although the Payments extension already achieves some of these goals, bridging its functionality with a separate ad management extension appears to be a complex task. What would you suggest for Andrew or me in this situation?
