Changelog

301 redirects now apply to storefront channels only

We are beginning to roll out a fix so that the 301 redirects are only created for storefront channels, meaning any channel with a type of storefront.

The rollout starts on November 10, 2026.

• Storefront channels unchanged. All channels with a type of storefront still get automatic redirects, including Stencil (bigcommerce), Catalyst, Next, WordPress, and custom storefront channels.
• Non-storefront channels skipped. Channels with other types, such as marketplace and marketing channels, no longer get 301 redirects, because they don’t serve storefront pages.
• Existing redirects kept. Redirects that were already created for non-storefront channels are not removed at this time.

For details, see the Redirects overview.

Retrieve staff action logs with the Store Logs API

The Store Logs V3 API now includes a Staff Action Logs endpoint, so you can audit what staff users did in a store’s control panel over a given period.

• New endpoint: GET /stores/{store_hash}/v3/store/stafflogs returns staff action log entries with the staff username, IP address, timestamp, summary, and action details.
• Required time window: send timestamp:min as a Unix timestamp. Add timestamp:max to set the end of the window, which defaults to the current time. The window must not exceed 90 days.
• Filters, paging, and sorting: filter by staff_username, service_name, summary, ipaddress, or userid, and use limit, page, sort, and direction to page through and order results.
• Authentication: requests use the existing store_logs_read_only OAuth scope, the same as System Logs.

For details, see the Store Logs API reference.

Clearer error for duplicate Worldpay Access payments at checkout

When a shopper pays at checkout and Worldpay Access rejects the payment as already processed, the checkout payment request now returns a duplicate_transaction error instead of a generic server error.

• Error code: the response carries duplicate_transaction rather than server_error, so a repeated transaction reference is distinguishable from a gateway failure.
• HTTP status: these checkout payment requests return 400 Bad Request instead of 500 Internal Server Error.
• No setup changes: you don’t need to change your Worldpay Access settings.

For details, see the Payments overview.