This project aimed to develop an individual data interface between Shopware and a dedicated platform for digital content. Shopware serves as an administration and ordering platform for digital subscriptions that offer users access to digital content. As there was no suitable plugin for Shopware that met the specific requirements, a customized solution was developed. This solution enables the secure management and flexible customization of subscriptions and user access, including single and multi-user licenses, with a particular focus on ID reference handling and robust error handling for payment processing.
Functionalities in detail
- Automatic trigger on receipt of payment:
- Every time a successful payment is received for a subscription order in Shopware, a trigger is triggered that instructs the digital platform to query Shopware's API.
- The API returns the order and customer data, which is processed for the provision and management of access to the digital platform.
- Data preparation and ID management:
- Each customer receives a unique ID that remains unchanged even if the email address changes, ensuring a stable reference to the digital platform.
- Orders with additional products or extended functions (such as multi-user licenses) automatically set the corresponding options. These options are also transmitted via the API so that the access rights can be configured correctly.
- Multi-user licences and organization management:
- The data interface supports multi-user licenses, which allow customers to create an organization and add team members with their own user IDs. This allows multiple users in an organization to access the platform's content.
- These user IDs remain unchanged even if team members leave the organization and take out their own subscription.
- This maintains the continuity of the stored data and authorizations.
- Subscription pause and resume:
- The data interface allows customers to cancel their subscriptions at any time and resume them within a defined time window without losing stored data.
- This mechanism ensures that relevant user data is retained after a subscription interruption and can be reactivated immediately.
- Fallback mechanisms for incorrect payment retries:
- Fallback solutions have been implemented to catch problems with automated repeat orders, especially with payment service providers such as PayPal, which do not always provide clear feedback immediately.
- These fallbacks ensure that a new query or notification is triggered for failed payments to avoid confusion or interrupted access.