> For the complete documentation index, see [llms.txt](https://docs.verifone.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.verifone.com/psdk-latest/psdk-user-guide-and-training/psdk-training-videos/android-device-out-of-box.md). # Android Device Out of Box {% embed url="" %} **Transcript**: In order to understand how the devices are configured, we will learn about the deployment mode and the merchant mode.
These modes provide insights into the process required for the device to function properly. Let's begin with the **Deployment Mode**. The first step in configuring a payment device is to load an initial software and corresponding keys. This process gets done in the deployment center and is an essential prerequisite that guarantees the device is ready to be dispatched to the merchant. After this mode is complete, it switches to Merchant Mode. In this mode a field agent or a merchant can set up the device. The process involves setting up the language and network, and adding the Device ID so the device can download software and packages specific to the merchant solution. Now that you have seen the two processes that flow through the configuration stage, let's focus on how the merchant receives and configures the device. First, new Android devices, along with the relevant accessories needed for them to function, will arrive at the merchant's location in a box. This box will also contain specific instructions on how to start the device.
Let's examine the images that are found in the device box more closely to gain a better understanding of how to set it up. First, you need to connect the device using the Verifone cable and plug it into a power source to charge. Then you need to press and hold the button on the left side of the device to turn it on. When the device starts up, it will show you some prompts to set it up, which we will see in the next slide. Now let's see the images at the top. The first illustrates the necessity of a Device ID. This number includes the configurations and requirements for installation on your device. It can be found in your Welcome Letter email, as shown in the picture. Finally, you will have a QR code that can be used for scanning the Quick Installation Guide. Have you ever set up a new smartphone? Verifone has created a similar process for setting up their devices the first time they're powered on, ensuring they meet the merchant's specific requirements. This is what we call the out of the box experience. This feature allows to preconfigure solutions so that, when devices are deployed in the field, merchants only need to complete minimal setup on their end. Know that for PSDK Semi integration, you can customize this process according to what you need the merchants to add.
Here's how it works: First, the device will prompt you to select a language, followed by a specific network and its configuration. Next, you'll be instructed to open your Welcome Letter to find the Device ID for the device. Here you can see how you will find a QR in your Welcome Letter email that you can scan with your device in order to add the Device ID. After inputting the correct number, all relevant software and configurations will begin downloading to your device. Once everything is successfully installed, you'll be notified that the Device is Ready to Use. All the setup, activation, and registration are completed during this process. Any application can register with the setup to be launched during onboarding if the solution requires any custom processing. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## 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, and the optional `goal` query parameter: ``` GET https://docs.verifone.com/psdk-latest/psdk-user-guide-and-training/psdk-training-videos/android-device-out-of-box.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.