superwall · claude · Aug 17, 2026
diff --git a/content/docs/dashboard/dashboard-settings/overview-settings.mdx b/content/docs/dashboard/dashboard-settings/overview-settings.mdx
@@ -55,7 +55,7 @@ Here, you can enter metadata about your iOS app that corresponds to your Stripe
 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. **Secret Key:** A Stripe secret key that you create. Once you've made one, paste it here.
+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](https://dashboard.stripe.com/settings/apps/com.superwall.stripe-rak). If you need help getting set up, check out the docs [here](/web-checkout/web-checkout-configuring-stripe-keys-and-settings).
 
@@ -64,7 +64,7 @@ You can find these keys [in your Stripe account](https://dashboard.stripe.com/se
 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](https://dashboard.stripe.com/test/settings/apps/com.superwall.stripe-rak).
 
 1. **Publishable Key:** A Stripe publishable key. Stripe creates this key for you, you don't need to generate it yourself.
-2. **Secret Key:** A Stripe secret key that you create. Once you've made one, paste it here.
+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
 

diff --git a/content/docs/support/web-checkout/web-checkout-revenue-tracking-is-automatic.mdx b/content/docs/support/web-checkout/web-checkout-revenue-tracking-is-automatic.mdx
@@ -33,7 +33,7 @@ It can take a few minutes for new transactions to appear in your dashboard metri
 
 If you have completed purchases in Stripe but no conversions showing in Superwall:
 
-1. **Verify your Stripe keys are configured correctly** - Check that both your Publishable Key and Secret Key are entered in Settings and show "Configured"
+1. **Verify your Stripe keys are configured correctly** - Check that both your Publishable Key and Restricted Key are entered in Settings and show "Configured"
 2. **Check you're using the correct mode** - If testing, ensure you're using Sandbox keys with test purchases. Production keys are required for live transactions.
 3. **Confirm the purchase was made through Superwall** - Only purchases initiated through Superwall paywalls will be tracked. Direct Stripe purchases outside of Superwall will not appear.
 4. **Allow time for data to sync** - New transactions may take a few minutes to appear in your analytics

diff --git a/content/docs/web-checkout/web-checkout-configuring-stripe-keys-and-settings.mdx b/content/docs/web-checkout/web-checkout-configuring-stripe-keys-and-settings.mdx
@@ -133,7 +133,7 @@ After installation, you'll receive a **Publishable Key** and a **Restricted Secr
 #### Step 7: Configure Superwall
 Paste the keys into the corresponding fields in Superwall:
 - **Publishable Key**: Your Stripe publishable key from the app
-- **Secret Key**: The restricted secret key provided by the app
+- **Restricted Key**: The restricted secret key provided by the app. It starts with `rk_live_`.
 
 Then **click** on **Update Configuration** to save your changes.
 
@@ -180,12 +180,16 @@ Click **Reveal test key** to view your test mode API keys:
 <Frame>![](/images/stripe-test/step-4-reveal-api-key.png)</Frame>
 
 #### Step 5: Copy Your Test Keys
-Copy both the **Publishable Key** and **Secret Key**:
+Copy both the **Publishable Key** and **Restricted Secret Key**:
 
 <Frame>![](/images/stripe-test/step-5-copy-api-key.png)</Frame>
 
 #### Step 6: Configure Superwall
-Paste both keys into the Sandbox Configuration fields in Superwall, then **click** on the **Update Configuration** button.
+Paste the keys into the corresponding Sandbox Configuration fields in Superwall:
+- **Publishable Key**: Your Stripe test mode publishable key from the app
+- **Restricted Key**: The restricted secret key provided by the app in test mode. It starts with `rk_test_`.
+
+Then **click** on the **Update Configuration** button.
 
 This section should say "Configured" at the top right if setup was successful.
 

diff --git a/content/docs/web-checkout/web-checkout-managed-payments.mdx b/content/docs/web-checkout/web-checkout-managed-payments.mdx
@@ -34,7 +34,7 @@ Managed Payments applies when Superwall creates a Stripe Checkout session, which
     In your Web Checkout app, open **Settings** and select **Stripe Configuration**.
   </Step>
   <Step title="Confirm your Stripe keys are configured">
-    Managed Payments is disabled until the current environment has a valid publishable key and secret key. Configure live keys for production purchases and sandbox keys for test purchases.
+    Managed Payments is disabled until the current environment has a valid publishable key and restricted key. Configure live keys for production purchases and sandbox keys for test purchases.
   </Step>
   <Step title="Turn on Managed Payments">
     In the Managed Payments card, turn on the **Managed Payments** switch. Superwall checks any available product eligibility information for the current environment, then checks whether the connected Stripe account can use Managed Payments.