From 4c541750d2f0125eea6d7c409af3ae252958d757 Mon Sep 17 00:00:00 2001 From: Devin Michael Date: Mon, 31 Aug 2026 15:56:48 +0700 Subject: [PATCH 1/5] docs: cover fraud screening and bulk gateway moves --- .../docs/features/payments/fraud-screening.mdx | 15 +++++++++++++++ content/docs/features/payments/meta.json | 1 + .../managing-subscriptions.mdx | 8 ++++++++ 3 files changed, 24 insertions(+) create mode 100644 content/docs/features/payments/fraud-screening.mdx diff --git a/content/docs/features/payments/fraud-screening.mdx b/content/docs/features/payments/fraud-screening.mdx new file mode 100644 index 0000000..3652b1b --- /dev/null +++ b/content/docs/features/payments/fraud-screening.mdx @@ -0,0 +1,15 @@ +--- +title: "Fraud Screening" +description: "Understand fraud screening, rejected checkouts, and risk review options" +--- +## Fraud Screening + +Next Commerce screens checkout attempts for fraud before sending a payment to the gateway. An attempt that exceeds the platform-managed risk tolerance is rejected before a cart, order, or gateway transaction is created. + +This can look like a gateway problem because the customer sees a checkout error while the gateway has no matching transaction. Review these attempts under **Dashboard > MaxMind Logs**. + +## Risk Settings and Review + +The fraud threshold is managed by NEXT and is not configurable per store in the Dashboard. Next Commerce does not currently provide a manual review queue for attempts above the threshold. + +The MaxMind log identifies flagged attempts, but the Dashboard does not show the individual risk factors behind each score. If a legitimate customer is blocked, contact NEXT Support with the store, customer email address, and approximate attempt time. The team can review the risk signals and report a false positive. diff --git a/content/docs/features/payments/meta.json b/content/docs/features/payments/meta.json index 3421f15..8d4e94c 100644 --- a/content/docs/features/payments/meta.json +++ b/content/docs/features/payments/meta.json @@ -11,6 +11,7 @@ "external-payment-methods", "authorize-and-capture-payments", "disputes-guide", + "fraud-screening", "block-lists", "payment-failure-cascading", "transaction-response-codes" diff --git a/content/docs/manage/subscriptions-guide/managing-subscriptions.mdx b/content/docs/manage/subscriptions-guide/managing-subscriptions.mdx index cb446d4..798541a 100644 --- a/content/docs/manage/subscriptions-guide/managing-subscriptions.mdx +++ b/content/docs/manage/subscriptions-guide/managing-subscriptions.mdx @@ -6,6 +6,14 @@ description: "Manage individual subscriptions in your store" From the **Subscriptions** menu you can view and access all subscriptions, and perform certain management [**Actions**](/docs/manage/subscriptions-guide#subscriptions-list-actions) on one, or multiple subscriptions in bulk. +## Change payment gateways in bulk + +To move several subscriptions to another payment gateway, open **Subscriptions**, select the subscriptions on the current page, then choose **Actions > Change Payment Gateway**. The new gateway will process each selected subscription's next renewal and all future renewals. + +Before making the change, confirm that the destination gateway supports every selected subscription's currency. A subscription cannot move to a gateway that does not process its billing currency. + +The list action applies to the subscriptions selected on the current page. For a migration that spans many pages, use the [Bulk Subscription Updates skill](https://github.com/NextCommerceCo/skills/tree/main/next-bulk-subscription). Run its dry-run step first to check the proposed changes before updating live subscriptions. + ## Subscription Details View Click **View** to see the Subscription Details view, which displays an overview of the Subscription, the items contained in it, the orders history, any events that have taken place during its lifecycle on the Timeline, with available actions to manage it. From e37385123cfb6cc5bc08e81dc053fe3252bf8a80 Mon Sep 17 00:00:00 2001 From: Devin Michael Date: Mon, 31 Aug 2026 19:19:23 +0700 Subject: [PATCH 2/5] docs: correct risk screening guide --- .../features/payments/fraud-screening.mdx | 33 ++++++++++++++----- 1 file changed, 25 insertions(+), 8 deletions(-) diff --git a/content/docs/features/payments/fraud-screening.mdx b/content/docs/features/payments/fraud-screening.mdx index 3652b1b..0fe310e 100644 --- a/content/docs/features/payments/fraud-screening.mdx +++ b/content/docs/features/payments/fraud-screening.mdx @@ -1,15 +1,32 @@ --- -title: "Fraud Screening" -description: "Understand fraud screening, rejected checkouts, and risk review options" +title: "Risk Screening" +description: "Set your risk tolerance and review blocked checkout attempts" --- -## Fraud Screening +## Risk Screening -Next Commerce screens checkout attempts for fraud before sending a payment to the gateway. An attempt that exceeds the platform-managed risk tolerance is rejected before a cart, order, or gateway transaction is created. +Next Commerce scores every checkout from 0 to 100 before payment is taken. If a checkout's score is above your store's risk tolerance, the payment is declined and no order is created. -This can look like a gateway problem because the customer sees a checkout error while the gateway has no matching transaction. Review these attempts under **Dashboard > MaxMind Logs**. +## Review Blocked Checkouts -## Risk Settings and Review +Go to **Payments > Risk** to review checkout attempts that were blocked by risk screening. The list shows each attempt's: -The fraud threshold is managed by NEXT and is not configurable per store in the Dashboard. Next Commerce does not currently provide a manual review queue for attempts above the threshold. +* Risk review ID +* Customer email address +* Risk score +* Amount +* Card ending +* IP country +* Date and time -The MaxMind log identifies flagged attempts, but the Dashboard does not show the individual risk factors behind each score. If a legitimate customer is blocked, contact NEXT Support with the store, customer email address, and approximate attempt time. The team can review the risk signals and report a false positive. +Search the list by customer email address, then select **View** to open a risk review. + +The risk review compares the checkout's risk score with the store's risk tolerance and confirms why the attempt was blocked. **Risk Signals** shows the factors that raised or lowered the score. Select **All Reviewed Data** to inspect the available IP address, email, card, billing, and shipping details for the attempt. + +## Set the Risk Tolerance + +Go to **Settings > Payments**, then find the **Risk** section. Use the **Risk Tolerance** slider to choose a value from 10 to 90: + +* **10** is the strictest setting. Lower values block more potentially legitimate customers. +* **90** is the most permissive setting. Higher values allow more potentially fraudulent checkouts through. + +Next Commerce recommends a risk tolerance of **50**. After choosing a value, select **Save Changes**. From 79984b7d67c4b08518340ae49fa1e932e03a2d3a Mon Sep 17 00:00:00 2001 From: Devin Michael Date: Mon, 31 Aug 2026 19:28:09 +0700 Subject: [PATCH 3/5] docs: clarify agent-assisted bulk migrations --- .../manage/subscriptions-guide/managing-subscriptions.mdx | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/content/docs/manage/subscriptions-guide/managing-subscriptions.mdx b/content/docs/manage/subscriptions-guide/managing-subscriptions.mdx index 798541a..a4fa02e 100644 --- a/content/docs/manage/subscriptions-guide/managing-subscriptions.mdx +++ b/content/docs/manage/subscriptions-guide/managing-subscriptions.mdx @@ -12,7 +12,13 @@ To move several subscriptions to another payment gateway, open **Subscriptions** Before making the change, confirm that the destination gateway supports every selected subscription's currency. A subscription cannot move to a gateway that does not process its billing currency. -The list action applies to the subscriptions selected on the current page. For a migration that spans many pages, use the [Bulk Subscription Updates skill](https://github.com/NextCommerceCo/skills/tree/main/next-bulk-subscription). Run its dry-run step first to check the proposed changes before updating live subscriptions. +The list action applies to the subscriptions selected on the current page. + + + +For a migration that spans multiple pages, ask an AI agent with the NEXT skills package to run the [Bulk Subscription Updates skill](https://github.com/NextCommerceCo/skills/tree/main/next-bulk-subscription). This workflow runs outside the Dashboard and updates subscriptions through the Admin API. Have the agent run a dry run first, then review the proposed changes before approving updates to live subscriptions. + + ## Subscription Details View From 3efc01bfac1e8024039d23cc922aeba9f8093d61 Mon Sep 17 00:00:00 2001 From: Devin Michael Date: Mon, 31 Aug 2026 19:32:31 +0700 Subject: [PATCH 4/5] docs: rename risk screening page --- content/docs/features/payments/meta.json | 2 +- .../payments/{fraud-screening.mdx => risk-screening.mdx} | 0 2 files changed, 1 insertion(+), 1 deletion(-) rename content/docs/features/payments/{fraud-screening.mdx => risk-screening.mdx} (100%) diff --git a/content/docs/features/payments/meta.json b/content/docs/features/payments/meta.json index 8d4e94c..47b436f 100644 --- a/content/docs/features/payments/meta.json +++ b/content/docs/features/payments/meta.json @@ -11,7 +11,7 @@ "external-payment-methods", "authorize-and-capture-payments", "disputes-guide", - "fraud-screening", + "risk-screening", "block-lists", "payment-failure-cascading", "transaction-response-codes" diff --git a/content/docs/features/payments/fraud-screening.mdx b/content/docs/features/payments/risk-screening.mdx similarity index 100% rename from content/docs/features/payments/fraud-screening.mdx rename to content/docs/features/payments/risk-screening.mdx From 6a4bfc301a680f05e4a9952cf0f758a9dcd0841c Mon Sep 17 00:00:00 2001 From: Devin Michael Date: Mon, 31 Aug 2026 19:54:41 +0700 Subject: [PATCH 5/5] docs: pin bulk subscription skill link --- .../docs/manage/subscriptions-guide/managing-subscriptions.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/docs/manage/subscriptions-guide/managing-subscriptions.mdx b/content/docs/manage/subscriptions-guide/managing-subscriptions.mdx index a4fa02e..4d067fe 100644 --- a/content/docs/manage/subscriptions-guide/managing-subscriptions.mdx +++ b/content/docs/manage/subscriptions-guide/managing-subscriptions.mdx @@ -16,7 +16,7 @@ The list action applies to the subscriptions selected on the current page. -For a migration that spans multiple pages, ask an AI agent with the NEXT skills package to run the [Bulk Subscription Updates skill](https://github.com/NextCommerceCo/skills/tree/main/next-bulk-subscription). This workflow runs outside the Dashboard and updates subscriptions through the Admin API. Have the agent run a dry run first, then review the proposed changes before approving updates to live subscriptions. +For a migration that spans multiple pages, ask an AI agent with the NEXT skills package to run the [Bulk Subscription Updates skill](https://github.com/NextCommerceCo/skills/tree/a9221c9df56473b5b05fd0f98db37b867cee2767/next-bulk-subscription). This workflow runs outside the Dashboard and updates subscriptions through the Admin API. Have the agent run a dry run first, then review the proposed changes before approving updates to live subscriptions.