> ## Documentation Index > Fetch the complete documentation index at: https://docs.m1amdocs.com/llms.txt > Use this file to discover all available pages before exploring further. # Reseller Integration Timeline This topic provides the Reseller (Service Provider) integration timeline when partnering with a Merchant that has already onboarded to Partner Ecosystem Management. The following table contains descriptions of RACI codes that are used in this topic (see the **RACI** column in the table under the **Partner Ecosystem Management Reseller Integration Task Timeline** section): | Code | Description | | - | - | | **R** | The person **responsible** for the completion of the tasks that constitute the project. | | **A** | The person **accountable** for the successful completion of the entire project. This accountability consists in reviewing the work that the responsible person provides once the work is finished, and then giving technical sign-off for it. | | **C** | The person **consulted** whose advice on the project is sought because they are a subject matter expert (SME). | | **I** | The person **informed** (kept up-to-date) on the progress of the project. | ## Partner Ecosystem Management Reseller Integration Timeline The following table provides the Reseller (Service Provider) with an integration timeline when partnering with a Merchant that has already onboarded to Partner Ecosystem Management. Some of the tasks in the timeline can be done in parallel to help improve the time to launch. For example: you can do some of the onboarding tasks while getting the commercial agreement signed with the Merchants. The following assumptions are made for the Reseller integration: * The Reseller is onboarded and already integrated with Partner Ecosystem Management. * The Reseller (Service Provider) has reviewed and completed the required configuration with Partner Ecosystem Management. * The commercial agreement between the Merchant and the Reseller (Service Provider) has been signed by both parties. * The Reseller and the Merchant have already agreed upon charging for each product. * There are no major roadblocks for the Reseller to accomplish the necessary integration tasks. The timeline below assumes the approximate time we expect for this integration effort. The majority of our cases add up to about 23 days in total depending on the number of Merchants being launched. Under the **Timeline** column in the following table, 5 days is equal to 1 work week. **Note:** This timeline is only a general guideline. The actual project timeline will be determined with all parties involved. | Milestone | Task | RACI | Timeline | | | | - | - | - | - | - | - | | | | **Reseller (Service Provider)** | **Partner Ecosystem Management** | **Merchant** | | | Step 1: Join Partner Ecosystem Management and Learn More | Our ​Partner Ecosystem Management​ team reaches out to the Reseller (Service Provider) for initial discussions, providing the Reseller with a configuration sheet. | I | R, A | | 2 days | | | The Reseller completes the configuration sheet and gives it to the Partner Ecosystem Management team. | R, A | I | | 2 days | | Step 2: Set Up the Reseller (Service Provider) Organization in the Pre-Production Environment | Sign commercial agreements directly with the Merchants, ensuring your Partner Ecosystem Management representative knows legal approvals are completed. | R, A | I | R, A | 1 day per Merchant | | | Your ​Partner Ecosystem Management​ representative creates the Reseller organization and the first Admin user account in the pre-production environment. Your ​Partner Ecosystem Management​ representative assists you in the process to set up your organization in the pre-production environment. Create a [partnership](discoverPartners) and a [product agreement](r_agreementManage) with the test Merchant in the pre-production environment. | R, A | R, A, C | | 4 days | | | The Partner Ecosystem Management team configures the following for your pre-production environment:- API key ​ - Webhook events - Gateway adapter endpoints - Health check endpoint - SFTP settings **Note:** Other configuration settings are determined on a case-by-case basis with your Partner Ecosystem Management representative during the onboarding project. | R, A | R, A | | 1 day | | | Depending on your agreement, either you or the Partner Ecosystem Management team will conduct end-to-end testing of the test Merchant and product. If you're responsible for acceptance testing, the Partner Ecosystem Management team will be available to provide support as needed. | R, A | R, A, C | | 4 days | | | ​​Create a [partnership](discoverPartners) and a [product agreement](r_agreementManage) with a real Merchant in the pre-production environment. | R, A | C | R, A | 1 day | | | Provide Partner Ecosystem Management​ with account numbers that can be used in integration tests. | R, A | I | | 1 day | | Step 3: Set Up the Reseller (Service Provider) Organization in the Production Environment | Your ​Partner Ecosystem Management​ representative works with you to set up your organization and configuration settings in the production environment. In the production environment, your ​ Partner Ecosystem Management​ representative assists you in replicating the real partnerships and product agreements you set up in the pre-production environment. | R, A | R, A, C | R, A | 3 days | | Step 4: Launch and Validate | Integration testing is conducted between you and the Merchant.**Note:** Partner Ecosystem Management recommends that you validate flows with test accounts in the production environment before enabling live customer purchases from your digital store. | R, A | C, I | R, A | 3 days | | | Download the [Daily Partner Subscription Extract](dailyPartnerSubscriptionExtractAbout) and check to see if it reflects what the validation testing shows for Merchant product activations. | R, A | I | I | 1 day | | | Set up an [external IDP (identity provider)](externalIDPSetup) for user federation if desired (optional). | R, A | R, A, C | | | | Total: | | | | | Maximum 5 calendar weeks. | This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.