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.

You can deploy new and updated apps for Terminal devices in the Dashboard.

Add or edit a deploy group

Before you can add or edit a deploy group, you must create a Terminal location and add readers to that location. You can then assign locations to a deploy group, meaning all readers in the location receive updates from that deploy group.

After you create a deploy group, you can edit it at any time by selecting it.

Add a deploy group

1. On the Terminal apps tab, click Manage deploy groups.
2. Click Add deploy group.
3. Complete the following steps in the Add deploy group drawer:
   • Enter a group name.
   • Choose your Terminal device type.
   • If desired, select the Default deploy group checkbox to create a default deploy group. A default deploy group automatically contains all locations that aren’t explicitly assigned to a different deploy group. You can create one default deploy group per device type.
   • Click Done.

Manage deploy groups with destination charges

1. On the Terminal apps tab, click Manage deploy groups.
2. Select the deploy group from the list.
3. Click Add locations.
4. Choose the locations to add.
5. Click Done.

Manage deploy groups with direct charges

1. On the Terminal apps tab, click Manage deploy groups.
2. Select the deploy group from the list.
3. Click Add locations.
4. Select the account that you want to add locations from in the account dropdown. You must select an account before adding locations.
5. Choose the locations to add.
6. 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, and 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 you only have one app to deploy, choose that app instead.
6. Confirm the deployment details, then click Deploy. The app deploys immediately.

Share apps across multiple accounts

Use this feature if you have multiple Stripe accounts and want to deploy the same app across accounts. Sharing one app across accounts avoids constraints with package name uniqueness and duplicate app reviews.

Designate one account to create and manage the app. Only the account that owns the app can upload new app versions, but other accounts can view and deploy the app by searching for the app ID.

1. On the Terminal apps tab, click the overflow menu ().
2. Click Search for app.
3. Enter the app ID and click View app details.
4. Click Deploy version and enter the deployment details.

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: