Docs: align guides with recent platform releases#17
Conversation
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
nextcommerce-docs | 4074bc6 | Commit Preview URL Branch Preview URL |
Jul 21 2026, 06:50 AM |
![kilo-code-bot[bot]](https://avatars.githubusercontent.com/in/2193792?s=60&v=4){kind=small}
|
|
||
| ### Address Autocomplete | ||
|
|
||
| Enable address autocomplete to suggest matching addresses while a customer types. When the customer selects a suggestion, checkout fills the city, state or region, postal code, and country fields. |
There was a problem hiding this comment.
WARNING: Address autocomplete field list is incomplete
The description only lists city, state or region, postal code, and country fields, but address-autocomplete services typically also fill the street address (address line 1 / civic number). The missing reference to the street address field could mislead merchants about which fields are populated and may leave gaps if the implementation only fills the four fields listed here. Confirm against the implementation and either expand the list to include the street address or explicitly call out that the street field is not auto-filled.
Reply with @kilocode-bot fix it to have Kilo Code address this issue.
|
|
||
| * 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. | ||
| * Card payment throttling allows three failed attempts per card within ten minutes. Further attempts with that card are blocked until the window passes. |
There was a problem hiding this comment.
WARNING: Possible loss of configurability for card-payment throttling
The previous bullet documented a configurable Throttle Attempts for Declining Bankcards flag, allowing merchants to enable or adjust the threshold. The replacement sentence describes throttling as a hardcoded platform rule ("three failed attempts per card within ten minutes"), which removes the documented setting. If throttling is still configurable in Settings > Payments (or has been migrated to a different location), merchants and developers reading this guide lose the path to that option. Confirm whether the setting still exists, and if so, restore a reference to it (e.g., the flag toggle and where it lives) alongside the new rule summary.
Reply with @kilocode-bot fix it to have Kilo Code address this issue.
| ### 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 > Logs** from a campaign to inspect its recent Campaigns API requests and responses. The app-level **Logs** view can be used when you need to investigate activity across campaigns. |
There was a problem hiding this comment.
SUGGESTION: Unclear navigation path for the "app-level" Logs view
The new sentence reads: "Open Developer > Logs from a campaign to inspect its recent Campaigns API requests and responses. The app-level Logs view can be used when you need to investigate activity across campaigns." The campaign-scoped path (Developer > Logs) is clear, but the "app-level Logs view" is not tied to a specific UI location. Earlier in this page the Campaigns App sidebar items mentioned are Settings (line 45); there's no sidebar/log mention to anchor the reader. Consider naming the exact navigation (e.g., "open Campaigns App from the sidebar and choose Logs" or the equivalent menu path) so merchants can find it.
Reply with @kilocode-bot fix it to have Kilo Code address this issue.
| 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; local methods such as TWINT, Swish, iDEAL, and Bancontact; Stripe Link; [Apple Pay](/docs/features/payments/apple-pay); [Google Pay](/docs/features/payments/google-pay); and [PayPal](/docs/features/payments/paypal). |
There was a problem hiding this comment.
SUGGESTION: Grouping TWINT with iDEAL/Bancontact as "local methods" may mislead about availability
The new sentence groups "TWINT, Swish, iDEAL, and Bancontact" under "local methods such as…" Without qualification, this could read as if all four are similarly available across gateways. According to the APM table (lines 13-21) and the dedicated stripe-apms page, TWINT and Swish are NEXT Payments exclusive while iDEAL and Bancontact are available on both NEXT Payments and Stripe. Consider tightening the wording (e.g., "local methods such as the NEXT Payments-only TWINT and Swish, and the cross-gateway iDEAL and Bancontact") to avoid merchants expecting TWINT/Swish on Stripe.
Reply with @kilocode-bot fix it to have Kilo Code address this issue.
| 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 and select **Developer > Session Tracking**. |
There was a problem hiding this comment.
SUGGESTION: Navigation path "Developer > Session Tracking" should be verified against the product UI
The new instruction tells users to select Developer > Session Tracking to set up Campaign Analytics on a custom funnel. If this exact menu path has not been product-verified, merchants may not find the option (the prior flow referenced View > Integration which has been removed). Confirm the menu path against the current Campaigns App UI before merge; if it differs, update to the actual navigation (for example, the documented path on line 84 of apps/campaigns-app/index.mdx implies Developer > Logs is a sibling, so the SDK/session-tracking item lives next to it).
Reply with @kilocode-bot fix it to have Kilo Code address this issue.
Code Review SummaryStatus: No Issues Found | Recommendation: Merge All 5 issues from the previous review at
No new issues found in the incremental diff. Incremental Files Reviewed (5 files)
Previous Review Summaries (2 snapshots, latest commit 0d8951c)Current summary above is authoritative. Previous snapshots are kept for context only. Previous review (commit 0d8951c)Status: 0 New Issues Found | Recommendation: Informational Overview
The latest incremental commits on The 5 previously reported inline findings (address autocomplete completeness, card-throttle configurability, Campaigns Logs navigation, APM grouping, and Session Tracking navigation) target files outside this incremental diff and remain valid against current HEAD. They are not duplicated here. Incremental Files Reviewed (3 files)
Previous review (commit 3ab0880)Status: 5 Issues Found | Recommendation: Address before merge Overview
Issue Details (click to expand)WARNING
SUGGESTION
Files Reviewed (12 files)
Reviewed by minimax-m3 · Input: 23.2K · Output: 1.6K · Cached: 178.9K |
1 participant
Summary
Validation