Setup 3 · Verify your mobile app

A Web2App Funnel ends in your app: the visitor pays on the web, opens the app, and the subscription is activated there. This third setup section checks that your app is ready for that handover. It takes about fifteen minutes and, unlike the previous sections, may require a new release of your app.

Open Web2App → Setup, section 3. Verify your mobile app setup: https://console.purchasely.io/web2app?tab=setup.

3.1 SDK version

Activating a web subscription in the app relies on the Purchasely SDK: it intercepts the redemption link, calls Purchasely, refreshes the user's entitlements and confirms the activation to the user. This logic ships with SDK 6.1. Users running an older version of your app can still pay on the web, but cannot activate the subscription in the app.

The step shows, for each platform, the SDK versions detected in the events received from your app over the last 28 days, with the average number of app starts per day and the share of each version. A platform with no event over the period shows Not detected.

1. If needed, update the Purchasely SDK to 6.1 or later and ship a new build: iOS, Android, React Native, Flutter, Cordova.
2. Once the new version is live on the stores, click Confirm this platform runs SDK 6.1 or later for each platform. The step is complete when every platform has been confirmed.

3.2 Configure your app scheme

After the payment, the success screen and the receipt email open your app through a custom URL scheme, for example yourapp. The scheme tells the phone which app to open. Purchasely builds the link; you declare the scheme in your app and in the Console.

In the Console

1. In step 3.2, select the Apple tab and enter your iOS scheme, for example yourapp.
2. Select the Google tab and enter your Android scheme. It is usually the same.
3. Save each tab. The scheme is shared with App settings → Stores, where you can also edit it.

Purchasely picks the iOS or Android scheme according to the device that opens the redemption link.

In your app

Your app must declare the same scheme. If it already handles Purchasely deeplinks, nothing changes.

• iOS: declare the scheme under URL Types in the target's Info tab (CFBundleURLTypes in Info.plist). See Apple's guide on custom URL schemes.
• Android: add an <intent-filter> with your scheme on the activity that starts the app. See Android's guide on deep links.
• Make sure the URL received by the app is passed to the Purchasely SDK, at initialization and while the app runs, as described in Deeplinks management and SDK integration.

How do I test it?

Open the sandbox URL of a Web Flow on your phone, pay with a Stripe test card, then tap the button on the success screen. Your app must open and confirm the activation. The Test and go live page walks through the full check.

3.3 App icon & favicon

Your funnels display your app's identity at several places: the browser tab and bookmarks, the success screen that sends the visitor to the app, the download prompts and the receipt email. This step controls the two images used there.

Upload a dedicated image if you want your funnels to use a different visual than your app. Purchasely generates every size it needs from the file you upload.

Troubleshooting