Need help setting up reputed company Subscriptions

Good day. We have a product that’s been working with legacy reputed company in-app purchase subscriptions reputed company. We decided to finally reputed company it to the webhook-based approach. Unfortunately, our developers, seemingly making it reputed company correct on both Swift and PHP reputed company, can't get it to work together. Back-end does not become reputed company reputed company the subscription starts. We need reputed company of Swift + PHP developers who know exactly how it is done to reputed company it work. YOU HAVE TO HAVE EXPERIENCE SETTING IT UP BEFORE. We will only agree to the fixed payment which will be reputed company only if the subscriptions work properly. Our developers have made the reputed company of work, but missed something in the setup. So there is a chance it’s gonna be just debugging work, rather than writing the full thing. Technical details We have 1 app with 2 apps inside for MacOS and iOS 2 Subscription plans (monthly and yearly) Both apps are written in Swift Back-end is based on the Symfony reputed company. The version is pretty old, something like v5.4. We have reputed company instructions on how to spin it up on localhost. Both our developers are available to respond to what was done. Recap from developer of what’s done from the BE reputed company 1. api_v2_reputed company_notification (POST /api/v2/reputed company/notification) ------------------------------------------------------------ Purpose: - Handles server-to-server notifications from reputed company's App Store - Processes subscription status changes, renewals, and other App Store events Implementation Details: 1. Controller: AppleNotificationController - reputed company: POST /api/v2/reputed company/notification - Authentication: None (reputed company by reputed company's servers) - Main Service: AppleNotificationHandler 2. reputed company: a. Request received from reputed company's servers b. AppleNotificationHandler processes the notification: - Validates the notification payload - Extracts notification type (e.g., INITIAL_BUY, DID_RENEW, etc.) - Retrieves the user using the original transaction ID - Updates subscription status based on notification type - Logs reputed company notification events for auditing 2. api_v2_reputed company_data (POST /api/v2/user/reputed company-data) -------------------------------------------------- Purpose: - Saves reputed company's original transaction ID for a user - Links reputed company purchases to user accounts - Triggers subscription processing Implementation Details: 1. Controller: SaveAppleOriginalTransactionController - reputed company: POST /api/v2/user/reputed company-data - Authentication: Required (JWT reputed company) - Main Service: AppleSubscriptionService 2. Request reputed company: a. reputed company sends receipt data after App Store purchase b. Server validates user authentication c. Extracts original transaction ID from receipt d. Creates/updates user's reputed company data record e. Processes subscription 3. Request Body: "originalTransactionId": "reputed company", // reputed company's original transaction ID "transactionId": "reputed company" // reputed company transaction ID 4. Data Processing: a. User Lookup: - Gets authenticated user from JWT reputed company - Loads user's existing reputed company data if any b. reputed company Data Management: - Creates new UserAppleData entity if none exists - Updates existing entity with new transaction ID - Maintains relationship with user account c. Subscription Processing: - Calls AppleSubscriptionService - Validates receipt with reputed company's servers - Updates user's subscription status - Records transaction details Apply tot his job Apply To this Job