# Web Checkout FAQ Frequently asked questions about web checkout. How does restoring memberships work when you've purchased via web checkout? [#how-does-restoring-memberships-work-when-youve-purchased-via-web-checkout] When the user taps on the restore link in the paywall, we'll do the normal restore flow for on-device subscriptions. However, if you've enabled web checkout and the restored entitlements don't match the entitlements belonging to the products on the paywall, we'll present an alert asking the user if they'd like to check for purchases on the web. This will take them out of your app to the [plan management screen](/docs/web-checkout/web-checkout-managing-memberships) where they can get a redemption link to restore their purchases. Does Superwall email customers after checkout? [#does-superwall-email-customers-after-checkout] Yes. By default, Superwall emails the address used during checkout with instructions and a redemption link to activate the purchase in your app. The email is sent from `Your app name ` with the subject `Your activation link from your app name`. To turn these off, use the "Disable Superwall Emails" setting in your Stripe app settings — see [how to disable the activation link email](/docs/support/web-checkout/3969573187-how-do-i-disable-the-activation-link-email-for-web-checkout). Do customers who use Sign in with Apple Hide My Email receive web checkout emails? [#do-customers-who-use-sign-in-with-apple-hide-my-email-receive-web-checkout-emails] Yes. If customers check out with an Apple private relay address, such as `abc123@privaterelay.appleid.com`, register Superwall as an allowed email source in Apple Developer. Superwall sends web checkout emails from your app-specific Superwall address, such as `support+your-app-name@superwall.app`. These emails include activation and subscription management links. Apple can reject those emails for Hide My Email customers unless `superwall.app` is registered as an email source for Sign in with Apple. Configure this before launching web checkout: 1. Go to [Apple Developer Services Configuration](https://developer.apple.com/account/resources/services/configure). 2. Open **Configure Sign in with Apple for Email Communication**. 3. Add `superwall.app` as an email source. If you prefer to authorize a specific sender, add your app's Superwall sender address, such as `support+your-app-name@superwall.app`. Once registered, Apple will allow emails from Superwall to be delivered to private relay addresses. For Apple's requirements, see [Configure private email relay service](https://developer.apple.com/help/account/capabilities/configure-private-email-relay-service). > **Warning** If you skip this step, customers who use **Hide My Email** may not receive web checkout emails from Superwall. If customers already checked out before the email source was registered, ask them to request a new link from your `https://{your-domain}.superwall.app/manage` page after the sender is configured. What happens if a user taps the redemption link multiple times or shares it? [#what-happens-if-a-user-taps-the-redemption-link-multiple-times-or-shares-it] Redemption codes are single-use and tied to a specific device. Once a code has been redeemed, it cannot be used again on a different device. However, users can visit the manage page and request a new redemption link. This generates a new code that can be used to activate access on another device. Without accounts (`identify` not called) [#without-accounts-identify-not-called] If you're not using accounts with Superwall (i.e. you never call `identify`), we allow up to **five active devices** per user. When a sixth device redeems a code, the **first device** to have redeemed a code will automatically lose access. This helps prevent abuse while still supporting reasonable multi-device usage. With accounts (`identify` called) [#with-accounts-identify-called] If you are using accounts with Superwall (i.e. you call `identify` with an `appUserId` when someone logs in), then entitlements are tied to the user ID, not the individual device. * If two different `appUserIds` redeem codes, **only the most recently identified user will retain access**. * If the **same `appUserId` is used across multiple devices**, all those devices will **automatically share access** without needing to redeem again. This system ensures flexibility while protecting against unauthorized sharing of redemption codes. How do I associate a web checkout purchase with a user in my app? [#how-do-i-associate-a-web-checkout-purchase-with-a-user-in-my-app] The short answer — use Superwall's [user identification APIs](/docs/sdk/quickstart/user-management#identified-users). When you configure Superwall, or a user signs in or out, you can always associate their login status to Superwall's SDK: ```swift Superwall.shared.identify(userId: user.id) ``` This will ensure that the user is associated with the web checkout purchase. A user paid on the web and can't access their purchase in the app. What should I do? [#a-user-paid-on-the-web-and-cant-access-their-purchase-in-the-app-what-should-i-do] Direct them to your app's plan management page so they can retrieve their redemption link or manage billing. For example: `http://yourapp.superwall.app/manage` Can I sell lifetime or consumable products through Stripe? [#can-i-sell-lifetime-or-consumable-products-through-stripe] Yes. Create a Stripe one-time price, import it into Superwall, and add it to a web paywall. For lifetime access, attach the entitlement the product should unlock. For consumables, usually leave the product without an entitlement and use `CustomerInfo.nonSubscriptions` to credit the user's account after purchase. Learn more in [Stripe One-Time Purchases](/docs/web-checkout/web-checkout-stripe-one-time-purchases). When should I use Redirect mode instead of Redeem mode? [#when-should-i-use-redirect-mode-instead-of-redeem-mode] Use **Redirect mode** when you need to: * Show a custom success or onboarding page after purchase * Perform additional verification or collect more information before granting access * Integrate with your own deep linking or authentication infrastructure * Track conversions in your own analytics before redemption Use **Redeem mode** (the default) when: * You want Superwall to handle the entire redemption flow automatically * You don't need custom post-purchase logic * You want the simplest integration Most apps should use Redeem mode. You can always switch between modes in your [Application Settings](/docs/web-checkout/web-checkout-configuring-stripe-keys-and-settings#post-purchase-behavior). What data is passed to my redirect URL in Redirect mode? [#what-data-is-passed-to-my-redirect-url-in-redirect-mode] When using Redirect mode, the following query parameters are automatically appended to your custom URL: **Standard parameters**: * `app_user_id` - The user's identifier from your app (if you called `identify`) * `email` - The user's email address from checkout * `stripe_subscription_id` - The Stripe subscription ID, or the Stripe Checkout session ID for one-time purchases **Custom parameters**: Any placement parameters you set when creating the web checkout link will also be included. **Example redirect**: ``` https://yourapp.com/success? app_user_id=user_123& email=user@example.com& stripe_subscription_id=sub_1234567890& campaign_id=summer_sale ``` You can use this data to verify the purchase, link it to your user account, or perform custom onboarding. Learn more about [post-checkout redirecting](/docs/sdk/guides/web-checkout/post-checkout-redirecting).