- Responsible: The person responsible for the completion of the tasks that constitute the project.
- Accountable: 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.
- Consulted: The person consulted whose advice on the project is sought because they are a subject matter expert (SME).
- Informed: The person informed (kept up-to-date) on the progress of the project.
Integration with the Mock Reseller in Partner Ecosystem Management
This section contains timeline information for a Merchant fully integrating with Partner Ecosystem Management using a test Reseller (Service Provider). The majority of our cases add up to approximately 4 weeks in total. Consider the following assumptions for this mock Reseller and Merchant integration timeline:- The Merchant has signed the commercial agreement
- The Merchant has the required resources for the integration
- The Merchant is committed to the timeline
- There are no major roadblocks to the integration
- Task 1: The Partner Ecosystem Management product and developer documentation and the Onboarding Checklist are shared with the Merchant.
- Responsible and Accountable: Partner Ecosystem Management
- Informed (Via Email): The Merchant
- Time estimate: 1 day
- Task 2: The Merchant reviews the Partner Ecosystem Management documentation, and completes and returns the checklist.
- Responsible and Accountable: The Merchant
- Time estimate: 5 days
- Task 3: The Partner Ecosystem Management team conducts a Q&A session with the Merchant. Partner Ecosystem Management presents out-of-the-box (OOB) use cases to the Merchant. The Merchant reviews the terms and conditions, and the use cases are finalized.
- Responsible: Partner Ecosystem Management and the Merchant
- Accountable: The Merchant
- Time estimate: 5 days
- Task 1: The Partner Ecosystem Management team prepares and hands over the Partner Ecosystem Management sandbox environment (PDT). The Partner Ecosystem Management team sets up a Merchant Admin and a Merchant organization.
- Responsible and Accountable: Partner Ecosystem Management
- Informed: The Merchant
- Time estimate: 1.5 days
- Task 2: Merchant performs the required configuration tasks in the Partner Ecosystem Management sandbox environment (PDT).
- Responsible and Accountable: The Merchant
- Informed: Partner Ecosystem Management
- Time estimate: 1.5 days
- Task 3: The Merchant explores the sandbox (PDT) environment and experiments with the MarketONE APIs. The Merchant can reach out to their Partner Ecosystem Management representative if they have any questions.
- Responsible and Accountable: The Merchant
- Consulted: Partner Ecosystem Management
- Time estimate: 5 days
- Task 1: If requested, the Merchant creates a solution design document which contains test cases for the Partner Ecosystem Management team to review. The Merchant submits the document for approval via email.
- Responsible and Accountable: The Merchant
- Time estimate: 5 days
- Task 2: After the Merchant submits the design document, the Partner Ecosystem Management team reviews and approves the document and the test cases.
- Responsible and Accountable: Partner Ecosystem Management
- Informed: The Merchant
- Time estimate: 5 days
-
Task 1: The Merchant developer completes the development and configuration of the flow (Platform-managed or Merchant-managed).
- Responsible and Accountable: The Merchant
- Time estimate: 5 days
-
Task 2: Flow development is completed. The Merchant exchanges SSL certificates and enables IP allowlist (if required).
- Responsible and Accountable: The Merchant
- Responsible and Consulted: Partner Ecosystem Management
- Time estimate: 1 day
-
Task 3: The Merchant tests and validates the Partner Ecosystem Management-Merchant integration in the sandbox (PDT) with the mock Reseller (Service Provider). If the Merchant is using the Platform-managed flow, the Merchant also completes the Reconciliation process. The Merchant is now fully integrated with the mock Reseller in the PDT environment.
- Responsible and Accountable: The Merchant
- Consulted: Partner Ecosystem Management
- Time estimate: 2.5 days
-
Task 4: The Partner Ecosystem Management team certifies the Merchant integration with Partner Ecosystem Management in the sandbox (PDT).
- Responsible and Accountable: Partner Ecosystem Management
- Informed: The Merchant
- Time estimate: 2.5 days
- Task 1: The Partner Ecosystem Management team prepares and hands over the Partner Ecosystem Management production environment. The Partner Ecosystem Management team sets up a Merchant Admin and a Merchant organization in the production environment in Partner Ecosystem Management.
- Responsible and Accountable: Partner Ecosystem Management
- Informed: The Merchant
- Time estimate: 1.5 days
- Task 2: The Merchant performs the required configuration tasks in the production environment.
- Responsible and Accountable: The Merchant
- Time estimate: 1.5 days
- Task 3: The Merchant completes validation tasks with Partner Ecosystem Management in the production environment.
- Responsible and Accountable: The Merchant
- Responsible and Accountable: Partner Ecosystem Management
- Time estimate: 2 days
Integration with a Real Reseller (Service Provider) in Partner Ecosystem Management
This section contains timeline information concerning a Merchant fully integrating with Partner Ecosystem Management using a real Reseller (Service Provider). The majority of our cases add up to approximately 10 days in total. Consider the following assumptions for this real Reseller and Merchant integration timeline:- The Merchant is fully integrated with Partner Ecosystem Management. (The configuration has been done, which includes configuration of the product code, token expiry time, etc.)
- Partner Ecosystem Management environments are already connected with the corresponding Reseller environments.
- The timeline estimate from the Reseller side is documented separately.
- Task 1: If the Partner Ecosystem Management representative says the Merchant is required to move to the sandbox (PDT) environment with the real Reseller, the Merchant adds an API key for the Reseller in the sandbox environment. In the production environment, the Merchant adds an API key for the Reseller.
- Responsible and Accountable: The Merchant and the Reseller (if the Platform-managed flow is being used)
- Informed: Partner Ecosystem Management
- Time estimate: 1.5 days
- Task 2 (Platform-managed flow only): If the Partner Ecosystem Management representative says it’s required, the Merchant registers webhooks for the real Reseller in the sandbox (PDT) environment. In the production environment, the Merchant registers webhooks for the real Reseller.
- Responsible and Accountable: The Merchant
- Informed: Partner Ecosystem Management
- Time estimate: 1.5 days
- Task 3: If required, integration testing and validation are conducted in the sandbox (PDT) environments (Reseller dependent).
- Responsible and Accountable: The Merchant and the Reseller
- Consulted: Partner Ecosystem Management
- Time estimate: 5 days
- Task 4: Product Verification Testing (PVT) and validation are conducted in the live production environment.
- Responsible and Accountable: The Merchant and the Reseller
- Consulted: Partner Ecosystem Management
- Time estimate: 5 days

