Docs: align guides with recent platform releases

content/docs/apps/campaigns-app/campaign-analytics.mdx

@@ -2,11 +2,11 @@
 title: "Campaign Analytics"
 description: "Track the traffic and performance of your campaigns in detail"
 ---
-To set up Campaign Analytics on your custom funnels, from the Campaigns App main list view, click on your campaign name, or choose **View**, then **Integration.**
+To set up Campaign Analytics on a custom funnel, open the campaign, select **Developer**, and find the **Session Tracking** section.
 
 <Callout type="info">
 
-Copy the script shown on **Session Tracking Integration** to every page of your funnel to enable session tracking in Campaigns App.
+Copy the script shown under **Session Tracking** to every page of your funnel to enable session tracking in Campaigns App.
 
 Campaigns using the [**Campaign Cart JS SDK**](https://developers.nextcommerce.com/docs/campaigns/cart-system) will automatically include Analytics on connected pages.
 
@@ -41,3 +41,29 @@ Every URL that users have visited in your funnel is reflected in this list, with
 ### Performance by Device & Browser
 
 View at a glance your traffic patterns and performance by device type and browser.  Conversion rates are shown by percentage to help identify areas for optimization.
+
+## Analytics Provider Data
+
+Campaign analytics events include the following campaign identifiers across supported providers:
+
+* `campaign_id`
+* `campaign_name`
+* `campaign_currency`
+* `campaign_language`
+* `campaign_session_id`
+
+These fields make it possible to segment events by campaign and join provider data back to Campaigns App sessions and order attribution. Cart and checkout events also include applied coupon and discount amounts when those values are available.
+
+The Campaigns Cart SDK's RudderStack integration follows RudderStack's ecommerce event conventions and includes product details plus session-based `cart_id` and `checkout_id` values. See the [**Campaign analytics developer guides**](https://developers.nextcommerce.com/docs/campaigns/analytics) for provider setup and event details.
+
+## Debug Analytics Delivery
+
+Open the in-page analytics debug panel on the campaign page to review the event timeline and delivery status for each configured provider. The panel distinguishes failed sends from successful delivery.
+
+The Campaigns Cart SDK also reports setup warnings when:
+
+* the campaign API key is missing
+* an analytics provider is missing a required setting
+* a provider's script does not load
+
+Use the named warning to correct the campaign configuration, then send a test event and confirm that the provider reports a successful delivery.

content/docs/apps/campaigns-app/index.mdx

@@ -68,9 +68,20 @@ Next, from the **Campaigns App** main workspace, select **New Campaign** to conf
 * **Statement Descriptor** - define a custom descriptor to appear on your customer's card statement for your campaign (for payment gateways supporting dynamic descriptors only).
 * **Enable Package Retail Price & Quantity** - compatibility setting for existing campaigns that still depend on package-level Retail Price or Quantity fields. Leave disabled for new campaigns and use [Offers & Discounts](/docs/apps/campaigns-app/campaigns-offers-and-discounts) for quantity pricing and compare-at savings.
 
+### Campaign Workspace
+
+Open a campaign to work from its first-class **Analytics**, **Packages**, and **Settings** tabs.
+
+Use the campaign's **Developer** workspace for:
+
+* installation details
+* Campaigns API context
+* session tracking setup
+* campaign request logs
+
 ### Campaigns App Logs
 
-From the Campaigns App sidebar, select **Logs**. The activity logs show recent Campaigns API requests and responses for debugging checkout, payment, upsell, and tracking behavior.
+Open **Developer** from a campaign, then use the **Logs** section to inspect that campaign's recent Campaigns API requests and responses. To investigate activity across campaigns, select **Logs** from the Campaigns App submenu.
 
 Logs are filterable by the following factors to help with debugging and performance analysis:
 

content/docs/apps/meta.json

@@ -8,7 +8,6 @@
     "everflow",
     "gorgias",
     "klaviyo",
-    "maxmind-minfraud",
     "meta-pixel",
     "midigator",
     "shipstation",

content/docs/features/payments/index.mdx

@@ -6,7 +6,7 @@ description: "Set up and manage Gateways, Payment Apps, and more"
 
 Next Commerce supports a variety of global gateways for bankcard transactions, encompassing credit and debit cards such as Visa, Mastercard, AMEX, Discover, Maestro, JCB and more.
 
-Beyond bankcards, Next Commerce supports [**Alternative Payment Methods**](/docs/features/payments/stripe-apms) including **Buy Now, Pay Later** options (Affirm, Klarna), digital wallets (TWINT, Stripe Link, [Apple Pay](/docs/features/payments/apple-pay), [Google Pay](/docs/features/payments/google-pay)), [PayPal](/docs/features/payments/paypal), and European bank payment methods.
+Beyond bankcards, Next Commerce supports [**Alternative Payment Methods**](/docs/features/payments/stripe-apms), including Buy Now, Pay Later options such as Affirm and Klarna; TWINT and Swish through NEXT Payments; iDEAL and Bancontact through NEXT Payments or Stripe; Stripe Link; [Apple Pay](/docs/features/payments/apple-pay); [Google Pay](/docs/features/payments/google-pay); and [PayPal](/docs/features/payments/paypal).
 
 If you don't see your payment gateway listed as supported, just ask us.
 

content/docs/features/payments/stripe-apms.mdx

@@ -3,7 +3,28 @@ title: "Alternative Payment Methods"
 description: "Offer Buy Now Pay Later, bank payments, and wallet methods alongside card payments"
 ---
 
-Next Commerce supports a range of alternative payment methods (APMs) beyond traditional bankcards, including Buy Now Pay Later (BNPL), bank transfers, and digital wallets. These methods are available on the storefront checkout, and many are also available for custom checkouts via the Admin API.
+Next Commerce supports a range of alternative payment methods (APMs) beyond traditional bankcards, including Buy Now Pay Later (BNPL), bank payments, and digital wallets. These methods are available on the storefront checkout, and many are also available for custom checkouts via the Admin API.
+
+Availability depends on the payment gateway connected to your store.
+
+| Method | Primary market | NEXT Payments | Stripe |
+| --- | --- | --- | --- |
+| Affirm | United States and Canada | Yes | No |
+| Klarna | North America, Europe, and Oceania | Yes | Yes |
+| TWINT | Switzerland | Yes | No |
+| Swish | Sweden | Yes | No |
+| Stripe Link | Stripe-supported markets | No | Yes |
+| iDEAL | Netherlands | Yes | Yes |
+| Bancontact | Belgium | Yes | Yes |
+| Sofort | Selected European markets | No | Yes |
+| Giropay | Germany | No | Yes |
+| SEPA Direct Debit | Eurozone | No | Yes |
+
+<Callout type="info">
+
+For methods offered through NEXT Payments, enable the method in your NEXT Payments account first. After it is available on the account, go to **Settings > Payments**, select the NEXT Payments gateway, and enable it for the store.
+
+</Callout>
 
 ## Buy Now, Pay Later
 
@@ -59,6 +80,16 @@ TWINT is a **NEXT Payments exclusive** payment method. It is not available throu
 
 </Callout>
 
+### Swish
+
+**Swish** is a local payment method for customers in Sweden. It is available to merchants processing through **NEXT Payments**.
+
+- Intended for merchants selling to customers in **Sweden**
+- Uses the connected NEXT Payments account
+- Appears as an alternative payment method at checkout once enabled
+
+Enable Swish in your NEXT Payments account first. Once it is available, go to **Settings > Payments**, select your NEXT Payments gateway, and enable **Swish** from the **Alternative Payment Methods** card.
+
 ### Stripe Link
 
 **Stripe Link** saves and autofills customer payment and shipping details across Stripe-powered checkouts, reducing friction and accelerating checkout.
@@ -74,21 +105,37 @@ For [**Apple Pay**](/docs/features/payments/apple-pay) and [**Google Pay**](/doc
 
 ## European Bank Payments
 
-The following bank payment methods are available for merchants using **Stripe** as their gateway. These are especially useful for merchants selling in European markets.
+### iDEAL
+
+**iDEAL** is a bank redirect payment method for customers in the Netherlands. It is available through **NEXT Payments** and **Stripe**.
+
+To enable iDEAL through NEXT Payments, add it to your NEXT Payments account first. Once it is available, go to **Settings > Payments**, select the NEXT Payments gateway, and enable **iDEAL** from the **Alternative Payment Methods** card.
+
+For Stripe, go to **Settings > Payments**, select the Stripe gateway, and enable **iDEAL**.
+
+### Bancontact
+
+**Bancontact** is a bank redirect payment method for customers in Belgium. It is available through **NEXT Payments** and **Stripe**.
+
+To enable Bancontact through NEXT Payments, add it to your NEXT Payments account first. Once it is available, go to **Settings > Payments**, select the NEXT Payments gateway, and enable **Bancontact** from the **Alternative Payment Methods** card.
+
+For Stripe, go to **Settings > Payments**, select the Stripe gateway, and enable **Bancontact**.
+
+### Stripe European Bank Methods
+
+These additional bank payment methods are available through Stripe:
 
 | Method | Markets | Type |
-|--------|---------|------|
-| **iDEAL** | Netherlands | Bank redirect |
-| **Bancontact** | Belgium | Bank redirect |
+| --- | --- | --- |
 | **Sofort** | Germany, Austria, Belgium, Netherlands, Spain | Bank redirect |
 | **Giropay** | Germany | Bank redirect |
-| **SEPA Direct Debit** | Eurozone (36 countries) | Bank debit |
+| **SEPA Direct Debit** | Eurozone | Bank debit |
 
-To enable any of these methods, navigate to **Settings > Payments**, select your Stripe gateway, and enable the method from the **Alternative Payment Methods** card.
+To enable one of these methods, go to **Settings > Payments**, select the Stripe gateway, and enable it from the **Alternative Payment Methods** card.
 
 <Callout type="info">
 
-These methods may be available in specific regions only. Consult Stripe's documentation for current availability and requirements per market.
+Payment-method availability and onboarding requirements vary by region and account. Review the requirements shown in your payment account before enabling a method on the store.
 
 </Callout>
 

content/docs/meta.json

@@ -29,7 +29,6 @@
     "apps/meta-pixel",
     "apps/gorgias",
     "apps/klaviyo",
-    "apps/maxmind-minfraud",
     "apps/midigator",
     "apps/taxjar",
     "apps/shipstation",

content/docs/start-here/get-started/add-locations-and-languages.mdx

@@ -51,6 +51,12 @@ When adding additional currencies, automatically assign a price record to your p
 * **Add Local Pricing** - select the checkbox to apply the current exchange rate to add prices to products or shipping methods.
 * **Use Price Rounding Rule** - to preserve pricing presentation, optionally use a rounding rule for the calculated sub currency pricing.
 
+### Automatic Currency Pricing
+
+Storefront localization settings can automatically create product prices in each configured currency using current foreign exchange rates. Automatic pricing rules also apply when new products are imported through the API, so new catalogue items receive prices in the store's configured currencies without a separate manual pass.
+
+Configure the forex pricing rule and any price-rounding behavior from **Settings > Localization**. Review locally set prices before enabling an automatic rule so that each market keeps the intended price presentation.
+
 <Callout type="info">
 
 **Note:** For reporting purposes, transactions in all other currencies are converted to the base reporting currency in the Dashboard: **USD**<br />

content/docs/start-here/get-started/add-payment-providers.mdx

@@ -26,7 +26,13 @@ Once a Gateway has been added to your store, you can specify
 * Enable [**3DS**](/docs/features/payments/3ds2-payments) support (optional), and assign a [**3DS Merchant Profile**](/docs/features/payments/3ds2-payments#3ds2-merchant-profiles) to the gateway
 * Connect an [**Apple Pay**](/docs/features/payments/apple-pay) profile (optional)
 * Connect a [**Google Pay**](/docs/features/payments/google-pay) profile (optional)
-* Enable [**Alternative Payment Methods**](/docs/features/payments/stripe-apms) — Affirm, Klarna, TWINT, Stripe Link, and European bank payments (optional)
+* Enable [**Alternative Payment Methods**](/docs/features/payments/stripe-apms), including Affirm, Klarna, TWINT, Swish, Stripe Link, iDEAL, Bancontact, and other European bank payments (optional)
+
+<Callout type="info">
+
+Some NEXT Payments methods must be enabled on the NEXT Payments account before they can be enabled on the store gateway. If the payment methods table shows an account-level warning, use its shortcut to open your NEXT Payments account, complete that step, then return to the gateway settings.
+
+</Callout>
 
 <Callout type="info">
 
@@ -61,7 +67,7 @@ This rule prevents a gateway that does not support a given card type or currency
 ### General Payment Settings
 
 * Assign a Gateway Group to use as the default on your storefront with the **Default Gateway Group** setting.  Assigning a Gateway Group will override any previously configured "Default" gateway for each currency.
-* Set the **Throttle Attempts for Declining Bankcards** flag, to limit a cardholder from re-attempting an already-declined transaction more than 4 times in a single session.
+* Enable **Throttle Attempts for Declining Bankcards** to allow three failed attempts per card within ten minutes. Further attempts with that card are blocked until the window passes.
 * Set **Disputes Handling** actions at this step, such as automating the adding of customers with payment disputes to [**Block Lists**](/docs/features/payments/block-lists), Cancelling Orders, and Canceling Subscriptions.
 * Set the **Subscription Cancel Reason** to assign to subscriptions that fail automatically due to failed recurring payments. Configure the rest of your subscription settings before launch if you sell subscriptions.
 

content/docs/start-here/get-started/checkout-settings-and-policies.mdx

@@ -24,7 +24,19 @@ Navigate to **Settings > Checkout** to customize your storefront’s checkout.
 
 ### Checkout Layout
 
-Choose from a Three Page Checkout flow (default) or a more streamlined Single Page Checkout for your storefront checkout.
+All stores use the single-page checkout flow. Use **Checkout Configurations** to control its visual design and the settings below to control checkout behavior.
+
+### Address Autocomplete
+
+Enable address autocomplete to suggest matching addresses while a customer types. When the customer selects a suggestion, checkout fills the street address, city, state or region, postal code, and country fields.
+
+Address suggestions support keyboard navigation, so customers can move through the list with the arrow keys and make a selection without using a mouse.
+
+<Callout type="info">
+
+Checkout address autocomplete is separate from the Google Maps setting for the storefront order-status page described below.
+
+</Callout>
 
 #### Cart Max Item Quantity