Wix & Authorize.net Integration

# Task Overview 1. Build an integration between [login to view URL] and existing Wix website using API and webhooks. 2. Create a paywall to hide site content behind it. The website contains multiple pages, and they must be hidden behind that paywall. The pages will have small publicly visible previews. As a result: - authenticated users with subscription see pages with full content - non-authenticated users or users without active subscription see preview pages with limited content Note: full pages and preview pages are 2 different pages. It's not like content is dynamically hidden or revealed on one page depending on authorization. Test website: [login to view URL] Full page example: [login to view URL] Preview page example: [login to view URL] The implemented system must scale with any amount of full–preview page pairs. ## Wix Wix will provide: - login and user account management via Wix Members Area app - login with "magic" link via email using "Magic: Password-less & SMS" or developer may suggest an existing app if is not suitable. - Subscriptions via Wix Pricing Plans app - subscription-related emails/automations handled by Wix for relevant subscription status changes reflected in Wix ## [login to view URL] [login to view URL] in this system is the payment processor/gateway and source of truth for billing events on purchased subscriptions. Wix plan definitions and [login to view URL] subscription definitions are maintained independently, and plan names, texts, prices, and configuration are not automatically synced between the two systems. Developer will use the sandbox account during the whole development process. Developer may register their own sandbox account and implement development with a dummy content: [login to view URL] [login to view URL] API reference: [login to view URL] # Core User Flows 1. New Subscriber * User visits the Subscriptions page and selects a plan (monthly or yearly). * User fills out the embedded payment form powered by Authorize.net. * On successful payment, user is registered as a Wix Member and assigned the purchased plan. * User gains immediate access to gated content. 2. Existing Member Login * User logs in via Wix Members Area. * System checks for an active subscription. * If active: full content is accessible. * If inactive/expired: user is redirected to preview pages and prompted to subscribe. 3. Subscription Renewal * [login to view URL] automatically charges the user on the renewal date. * A webhook confirms the successful payment and keeps the Wix plan active. * If payment fails, the Wix plan is flagged/revoked and the user loses access. 4. Subscription Cancellation by User * User requests cancellation via their Wix account. * The cancellation triggers an [login to view URL] API call to stop billing. * Webhook confirms cancellation; Wix revokes plan access. 5. Admin-Managed Subscription Changes * Admin can edit Wix subscription names, texts, prices, and other plan presentation data independently from Authorize.net. * Those Wix plan edits do not update [login to view URL] automatically. * Changes that affect an existing subscriber's billing/access state still go through the integration flow for that subscriber. # Core Data Flows 1. New subscriber - On the Subscriptions page user selects a Wix plan (monthly/yearly). - Checkout/payment is processed by [login to view URL] via embedded custom form at Wix website - On successful payment and subscription creation, [login to view URL] triggers a webhook to Wix. - creates a Wix Member (standard Wix setup flow) - assigns the purchased Wix plan - triggers Wix-native subscription emails/automations where applicable - Result: on next page load user gets immediate access to full page content via Wix’s native member gating for that plan. 2. Admin actions in Wix: - Admin manages members' plan assignment/status in Wix (add/remove/cancel). - Wix plan setup is managed independently from [login to view URL] and is not automatically mirrored to it. - Any admin change that affects an existing subscriber's billing state triggers an [login to view URL] API call: - add subscription: create subscription in [login to view URL], then wait for webhook to confirm and finalize Wix state, - remove/cancel subscription: cancel in [login to view URL], then webhook confirms and Wix revokes access. 3. User deletion - Deleting a user in Wix cancels the [login to view URL] subscription (stops billing). - Customer/payment profile is retained in [login to view URL] (not deleted) # Out of Scope Functionalities - Automatic syncing of subscription plan metadata between Wix and [login to view URL] is out of scope for this phase. --- Detailed functional requirements are attached to the project. # Deliverables 1. Developer will create the working and tested solution (sandbox based) which will be available on the client-provided test site. 2. Developer may use LLMs to write the code — no problem with that. But the result must be a high quality, bugless output, tested by the developer before they say that it's done. 3. Developer will provide a short document explaining how to move the created solution to the production website. 4. Developer will provide technical support during the update of the production website and for a short agreed period after launch to help resolve issues related to this work if they appear. 5. Deadline is in 7 days (not including the technical support period).

ID do Projeto: 40348063