General

Under the General section, you can set or edit metadata and some integration API keys for your app:

Name
The name for your application in Superwall. This isn't user-facing and only used within Superwall. You can change it anytime.

Apple App ID
Fill in your app's Apple identifier here. You can find it by going to App Store Connect -> General -> App Information.

Bundle ID
Fill in your iOS app's bundle identifier exactly as it appears in App Store Connect or Xcode. Bundle IDs are case-sensitive, and the casing must match when configuring Apple keys such as your In-App Purchase configuration.

If the app has no bundle ID saved, Superwall lists the bundle IDs your app's SDK reported in the last 30 days, and the Bundle ID row becomes a dropdown. Android apps get the same dropdown in the Android package name row.

The dropdown has:

• The reported bundle IDs, most likely first. Under each one is why it's listed: its App Store name and icon when Apple lists it, otherwise how many production devices use it, or Sandbox only when only test builds reported it. On iOS, App Store installs count as production devices, and simulator, Xcode and TestFlight builds count as sandbox. On Android, release builds count as production, including Google Play testing tracks, and debug builds count as sandbox.
• Enter manually, which turns the row back into a text field. Click the list icon in the field to go back to the dropdown.
• Copy prompt, which copies a prompt for your coding agent, like Claude Code or Cursor, to find the bundle ID in your project. The prompt asks the agent to tell you the bundle ID without changing any files.

When one bundle ID has at least 90% of production devices, or it's the only one reported, the row shows it with a Suggested badge. Superwall doesn't fill it in for you. Choose a bundle ID from the dropdown, then click Save changes.

If the SDK hasn't reported a bundle ID, the row is a plain text field, with a button that copies the same prompt.

If the bundle ID you choose would leave production devices on other bundle IDs, a warning under the row says how many. Superwall's SDK can run a build in test mode when its bundle ID isn't the one saved here. A build still matches if its bundle ID starts with the saved one followed by a dot, like an extension's com.example.app.widget. In test mode, purchases are simulated instead of charged. On iOS, events also go to sandbox.

Which builds run in test mode depends on the platform and SDK version:

• Android SDK 2.7.4 and later: builds whose package name doesn't match.
• iOS SDK 4.18.0 and later: simulator, TestFlight and development builds whose bundle ID doesn't match. App Store builds ignore the mismatch.
• iOS SDK 4.14.0 to 4.17.x: every build whose bundle ID doesn't match, including App Store builds.

Earlier SDK versions don't have test mode. The warning counts every production device on another bundle ID, whichever SDK version it runs. See Test mode for iOS and Android.

Apple Custom URL Scheme
We use URL schemes to perform deep link logic and for in-app previews of paywalls for iOS apps. To learn more about setting up deep links, visit this doc.

Application settings

Here, you can enter metadata about your app that corresponds to your Stripe integration.

1. Icon: An icon to represent your app, we recommend using the same one that your app does. This will appear on the checkout and subscription management pages.

2. Web Paywall Domain: The domain your paywalls will be shown from. This was set when the Stripe app was created, and cannot be changed.

3. Application Name: The name of your app, we recommend using the same name as your app.

4. Support URL: A URL to your support page. This will be shown on the checkout and subscription management pages.

5. Support Email: An email you provide customers for support questions and general reach out

6. Redeemable on Desktop: If your app is an iPad app on Mac, enable this option so that users can redeem products on their Mac. If you aren't using iPads Apps on the Mac, you can disable this. If this is disabled, users who open the redemption page on a desktop see a QR code to finish on their phone or tablet.

Stripe Live Configuration

This section allows you to connect Stripe keys with Superwall. You will need a:

1. Publishable Key: A Stripe publishable key. Stripe creates this key for you, you don't need to generate it yourself.
2. Restricted Key: The restricted key that Superwall's Stripe app generates for you when you install it. It starts with rk_live_. Copy it from Stripe and paste it here — you don't create this key yourself.

You can find these keys in your Stripe account. If you need help getting set up, check out the docs here.

Stripe Sandbox Configuration

The sandbox configuration allows you to test purchasing flows with your web checkout integration. If you need to find these keys, you can find them in your Stripe account.

1. Publishable Key: A Stripe publishable key. Stripe creates this key for you, you don't need to generate it yourself.
2. Restricted Key: The restricted key that Superwall's Stripe app generates for you when you install it in test mode. It starts with rk_test_. Copy it from Stripe and paste it here — you don't create this key yourself.

iOS configuration

This section has critical information for your iOS app. Without it, web checkout won't work on iOS.

1. Apple Custom URL Scheme (no slashes): Your custom URL scheme. If you haven't set this up, view the documentation.
2. Apple App ID: Your app's Apple ID. You can find this in App Store Connect -> General -> App Information.

Android configuration

This section appears when your project has an Android app, and has critical information for that app. Fill in Google Custom URL Scheme, Android Package Name and Android App Fingerprints. See Android configuration for what each field does.