diff --git a/content/docs/images/spm_paywall_override.png b/content/docs/images/spm_paywall_override.png new file mode 100644 index 0000000..10613d2 Binary files /dev/null and b/content/docs/images/spm_paywall_override.png differ diff --git a/content/docs/images/stripe-managed-payments-enabled.png b/content/docs/images/stripe-managed-payments-enabled.png new file mode 100644 index 0000000..5c894f2 Binary files /dev/null and b/content/docs/images/stripe-managed-payments-enabled.png differ diff --git a/content/docs/web-checkout/web-checkout-managed-payments.mdx b/content/docs/web-checkout/web-checkout-managed-payments.mdx index 9615f29..9bed8c7 100644 --- a/content/docs/web-checkout/web-checkout-managed-payments.mdx +++ b/content/docs/web-checkout/web-checkout-managed-payments.mdx @@ -25,15 +25,19 @@ Managed Payments applies when Superwall creates a Stripe Checkout session, which ## Enable Managed Payments + + Here, **current environment** means the live or sandbox configuration you're editing. + + In your Web Checkout app, open **Settings** and select **Stripe Configuration**. - Managed Payments is disabled until the selected Stripe 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 secret key. Configure live keys for production purchases and sandbox keys for test purchases. - In the Managed Payments card, turn on the **Managed Payments** switch. Superwall checks product eligibility and then checks whether the connected Stripe account can use 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. ![Managed Payments switch in Stripe Configuration](/images/stripe_mp_turn_on.jpg) @@ -41,25 +45,23 @@ Managed Payments applies when Superwall creates a Stripe Checkout session, which If Stripe requires terms acceptance, Superwall opens the Superwall Stripe app page for the current environment. Accept the required Stripe Connect terms, return to Superwall and turn the switch on again. - If Superwall lists ineligible products, fix the reasons shown by Stripe before enabling Managed Payments. Product tax code issues are the most common reason a product needs attention. + If Superwall finds one or more ineligible products, Managed Payments stays off and an error identifies the affected products, including any reasons Stripe returns. Fix the reported issues in Stripe, then turn on Managed Payments again. Missing or ineligible product tax codes are examples of issues Stripe can report. +After setup is complete, the Stripe configuration shows **Configured** for the current environment, and the Managed Payments card shows **Enabled**. + +![A fully configured sandbox Stripe environment with Managed Payments enabled](/images/stripe-managed-payments-enabled.png) + The Managed Payments switch controls the Web Checkout app's default payment mode. The live and sandbox Stripe cards each validate their own Stripe account and products, but the default itself is app-wide. Before launch, verify the live Stripe configuration even if you first tested the switch with sandbox keys. ## Product eligibility -When product eligibility checks are available, Superwall asks Stripe whether active products in the selected environment can use Managed Payments. The Product eligibility list shows each product and Stripe's reason when a product is ineligible. +When you turn on Managed Payments, Superwall attempts to check active products in the current environment. Any ineligible products returned by Stripe block enablement. Superwall then checks whether the connected Stripe account can use Managed Payments. -| Status | What it means | What to do | -| --- | --- | --- | -| **Eligible** | Stripe says the product can be used with Managed Payments. | No action is needed. | -| **Ineligible** | Stripe returned a product-level reason that blocks Managed Payments. | Fix the reason shown in Stripe, then recheck in Superwall. | -| **No active products found** | The connected Stripe account has no active products for this environment. | Create or import active Stripe products before testing checkout. | -| **Eligibility checks are not enabled** | Superwall cannot show per-product eligibility for this environment yet. | Continue only after confirming the account is ready with Superwall. | -| **Account not enrolled or unavailable** | Stripe rejected the eligibility check or Managed Payments availability check for this account. | Follow the message shown in Superwall, accept Stripe terms if prompted or contact Superwall. | +If Stripe reports one or more ineligible products, the switch remains off and Superwall identifies the affected products, including any reasons Stripe provides. Correct the reported issues in Stripe, then return to Superwall and turn on Managed Payments again. -If Superwall can check eligibility and one or more products are ineligible, Managed Payments will not turn on until those products are fixed. If eligibility detail is unavailable, the final enablement gate is the Stripe account availability check. +If you're using the beta version of the New Dashboard at `app.superwall.com`, a **Product eligibility** section appears beneath the Managed Payments control after the current environment is configured. When Stripe returns product data, the section shows the returned products as **Eligible** or **Ineligible** and includes any ineligibility reasons Stripe provides. Otherwise, the section explains that checks are unavailable, no active products were found or eligibility could not be loaded. The current dashboard at `superwall.com` does not show this section; it requests an eligibility result when you turn on Managed Payments and reports any ineligible products in an error. ## Override the default on a paywall @@ -71,6 +73,10 @@ The paywall-level **Managed Payments** setting appears only when all of these ar - The paywall has at least one Stripe web checkout product. - Paywall-level Managed Payments controls are enabled for the account. +In the paywall editor, open **Products** to find the override beneath the selected products. + +![Managed Payments override in the paywall editor Products panel, set to Use Account Setting](/images/spm_paywall_override.png) + | Option | Checkout behavior | | --- | --- | | **Use Account Setting** | Follow the Web Checkout app's Managed Payments default. | @@ -96,4 +102,4 @@ Managed Payments has more than one availability gate: - Stripe can still block enablement until the connected account accepts the required terms or becomes eligible for the Managed Payments preview. - Product eligibility details can be unavailable even when the app-level switch is visible. -If the Stripe Configuration card, product eligibility list or paywall override is missing, contact Superwall with the app name, Stripe environment and the paywall you are trying to configure. +If the Stripe Configuration card, product eligibility list or paywall override is missing, contact Superwall with the app name, current environment and the paywall you are trying to configure.