Deploy your app

After Stripe reviews and approves your app for deployment, we notify you by email, in the Dashboard, or through a webhook. You can then follow the instructions below to deploy your app.

During deployment, your app is immediately sent and downloaded to your device. The device reboots to install the app. Devices reboot every 24 hours and apply any updates automatically. To check for and apply updates immediately, you can manually reboot your device.

Add or edit a deploy group

Before you can add or edit a deployment group, you must create a Terminal location and add readers to that location.

After you create a deploy group, you can edit it at any time by clicking edit next to the location.

1. In the Dashboard, click Developers > Apps.
2. On the Terminal apps tab, click Manage deploy groups.
3. Click Add deploy group.
4. Complete the following steps in the Deploy group window:
   • Enter a group name.
   • Choose your Terminal device type.
   • Choose the location(s) to add.
   • Click Done.

Deploy an app version

You can deploy your app after a Stripe reviewer approves it.

1. On the Terminal apps tab, choose the app that you want to deploy.
2. On the app details page, click Deploy version.
3. Choose a version of the approved app, then click Next. You can’t deploy an earlier version of an app. The app version must be newer than the currently deployed app.
4. Choose the deploy group, then click Next.
5. Choose your preferred kiosk app, then click Next. This is the default app that launches when the Stripe reader turns on. If there’s only one app to deploy, choose that app instead.
6. Confirm the deployment details, then click Deploy. The app deploys immediately.

Deploy group best practices

You can sort devices into different deploy groups to roll out software independently and isolate fault in case of any issues. You might have fewer or more deploy groups based on tooling, risk tolerance, and specific business needs.

We recommend the following deploy group setup:

• Alpha - Contains locations that correspond to your internal devkits or internal production devices.
• Beta - Contains a small number of actual user locations. You can randomly choose these locations, select them based on meaningful criteria (for example, less risky locations), or have users opt in to the Beta deploy group based on their risk tolerance.
• General – Contains all remaining actual user locations, except those in the Alpha or Beta groups. You can use a default deploy group to avoid manually assigning each remaining location.

When your app is ready for deployment, promote deploy groups from least to most risky: