# Onboarding Process Once you have completed the signup formalities for the integration programme you will receive the credentials for Gamma. If you haven't received one, please write an email to . Gamma is a tool for POS partners to provide updates on the integration project and also to update the merchant details for go-live on the integration. You can understand more about Gamma [here](/downstream/resources/gamma.md). The journey of your integration starts and ends with the Gamma dashboard. As soon as you sign up with our POS partnership program, a Gamma Account is created for you and credentials will be sent out to your registered email address. Here are the 3 critical steps to be followed through the Gamma dashboard. #### **STEP I: Keep your progress updated in Gamma** This step is extremely vital as it helps us know exactly where you are in the integration and we can arrange for dialogues if we see you stuck at any stage. The below flowchart will guide you to keep Gamma updated with the progress you have made in the integration. ![Progress steps for the integration](/files/sfjdugxskb2yT91NTUL4) * **Login -** login to Gamma dashboard with the credentials. If you haven't received the same please write to `pos.support@urbanpiper.com`. * **KickStart** **-** Click on "Let's Start" button to start the integration project and update the "Status" of the APIs under "Features Checklist".

Kickstart

* **Progress -** By default, all the API status will be in the "New" state. Update the status to "In-Progress" when you are working on the API and move it to "To-be-verified" when you have completed the development for an API.
* **Completion** **-** We shall validate all the APIs marked as "To-be-verified" during the testing session and update the APIs to "Completed" if no gaps are found. Partner will be marked as "Active" post that. **STEP II: Merchant Pipeline Creation and Conversion** As the phrase above suggests, this will come into play after the integration is completed and certified and when you are ready to start onboarding your merchants into the integration. This can definitely be referred to later but we strongly recommend that you keep the merchant data populated as this would definitely be a motivation to complete the integration faster! The flowchart below will help in getting this step done. ![Merchant Pipeline Creation and Conversion in Gamma](/files/GKJfIAq9wVSOKSlIVnQy) * **Login -** login to Gamma dashboard with the credentials. * **Backlog -** Click on the "Create" button under "Backlog" to add a pipeline of a merchant and submit basic details asked in the form.
* **Conversion** - POS partnership team converts "Backlog" to "Merchant". This action will create a merchant account (Atlas) in our system. * **Creation -** Partner shall receive an email containing Atlas dashboard and Satellite Prime login details and the Auth key to populate the data in the production environment. **STEP III: Merchant Data Population for Go-Live** This would be the final step to be done before taking an outlet live. Before this step, both the previous steps should already be done. You would have the production host URL by now and are expected to push the required data through the API like store creation, menu push etc. The flowchart below will guide you to complete this step. ![Making the store go-live ready](/files/ydjKHF8b1I6j20ojhRGJ) * **Login -** login to the Gamma dashboard with the credentials. * **Webhooks -** Make sure the right API key and production URL are used at your end. Configure your webhook URLs via API or manually through Atlas. * **Stores & Menu** - Push the Stores, add the platform details for each store and Menu data using the API or configure the same through Atlas manually. Verify the data using the callbacks or through Atlas. * **Go-Live** **-** Data pushed will be verified by the Onboarding Manager post which outlet will be sent for mapping to the aggregator. Once the mapped menu will be pushed to the aggregator we will communicate the go-live. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://api-docs.urbanpiper.com/downstream/getting-started/onboarding-process.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.