Skip to navigation

Control Panel users can use metafield and EventBridge GraphQL fields with store permissions

Control Panel users who are not the store owner can now use several Admin GraphQL fields when they hold the matching store permission; until now these fields answered You do not have permission to do this operation for every user except the store owner. Access with API account tokens is unchanged.

  • Single metafield lookups: the metafield query on store accepts any metafield read permission, such as Manage Products, Manage Orders, Manage Customers or Manage Settings. We are beginning to restrict these reads to the resource types the user’s permissions cover, matching the existing metafields list query; you may notice this over the coming weeks. Once restricted, a user with Manage Orders can read order metafields but not product metafields.
  • Deleting metafields: the deleteMetafield mutation accepts the Manage Settings permission, the same permission createMetafield and updateMetafield already accept.
  • Amazon EventBridge event sources: the eventSources query on store accepts List Store API Tokens, createEventSource accepts Create Store API Tokens, and deleteEventSource accepts Delete Store API Tokens. These are the permissions that gate the Store API Accounts area of the control panel, so users who manage API accounts can now manage EventBridge event sources there too.
  • Reassigning metafield owners: the reassignMetafieldsOwner mutation still requires the store_metafield_change_owner scope for API accounts and additionally accepts Control Panel users holding Grant High-Risk Store Permissions.
  • Unchanged: API account tokens keep the same OAuth scope requirements and the GraphQL schema does not change.

For details, see Metafields and Amazon EventBridge.


Authorize.net manual orders now send a MOTO indicator

We’re rolling out a fix for Authorize.net transactions on manually created orders (phone or mail orders). Previously these requests carried no indicator distinguishing them from standard ecommerce transactions, which could cause Authorize.net to hold the order for review even after the funds were captured successfully. You may notice fewer manually created orders held for review in Authorize.net over the coming weeks as this rolls out.

  • Manually created orders now send an explicit MOTO indicator — Authorize.net authorize and purchase requests for manually created orders now include a market type of mail/telephone order, so Authorize.net’s fraud review treats them appropriately.

For details, see the Payments API.


Authorize.net order description fix

We’re beginning to roll out a fix for Authorize.net manual refunds that were rejected because the order description included parentheses; you may notice the description format change over the coming weeks.

  • Order descriptions no longer include parentheses around the order number for affected stores, so merchants can submit manual refunds directly from Authorize.net without the request being rejected.

BigCommerce Payments data for PayPal fraud protection

We are beginning to roll out more complete shopper details on the orders that BigCommerce Payments sends to PayPal, so you may notice changes in how PayPal Fraud Protection Advanced and Chargeback Protection evaluate your orders over the coming weeks.

  • Card payments: orders paid by card, including saved cards, include the shopper’s billing address, email address, phone number, and name. Fraud Protection Advanced filters that you set on these details now apply to these orders and can decline a payment that a filter rejects. Previously, such filters did not match card orders from BigCommerce Payments.
  • Shopper IP address: orders paid with any BigCommerce Payments method include the IP address the shopper paid from.
  • Shipping state code: the shipping address carries the ISO state or province code, such as TX, instead of the state name.

Your Fraud Protection Advanced and Chargeback Protection settings in PayPal do not change.


Fewer Apple Pay declines with BNZ

We are beginning to roll out a fix for BNZ Apple Pay payments declined with the error “System malfunction”. You may notice fewer of these declines over the coming weeks.

  • Network authentication data: Apple Pay payments processed through BNZ include the card network’s authentication data and commerce indicator for Visa, Mastercard, and American Express.
  • No setup changes: you don’t need to change your BNZ or Apple Pay settings.

For details, see the Payments overview.


Convert option set rules to product rules from the control panel

We are beginning to roll out a self-service way to convert option set rules into product rules from the control panel, so stores that use option set rules can finish moving to the new add/edit product experience without waiting for support. If your store uses option set rules, you may see a new banner on the product page over the coming weeks.

The conversion works in steps, and you decide when to move to the next one:

  • Scan first. The banner starts with a scan of the products that use option set rules. The scan only reads your catalog and changes nothing in your store. It checks the swatch images of those products and can take a few minutes. You can leave the page while it runs and refresh to see the current status.
  • Review the result. If the scan finds no problems, you can start the conversion. If it finds swatch options with missing images, the banner shows how many products are affected. You can contact support for the list, re-upload the images and scan again, or convert anyway. If you convert anyway, some swatches may show minor issues on the storefront until you re-upload their images.
  • Convert when ready. Conversion copies each option set rule onto the products that use it. It runs in the background, so you can leave the page. Avoid editing products or option sets until it finishes. Your option sets stay in place, and conversion cannot be undone.
  • Check the outcome. When every rule is converted, the banner confirms that the migration is complete. If some products cannot be converted automatically, the banner shows how many. Support can see which products failed and why, and those products keep using their option set rules in the meantime. If a conversion fails before anything is converted, the banner tells you that nothing has changed and lets you try again.
  • New assignments stop afterward. Once a conversion has finished, you can no longer associate option sets that have rules with products.

You can close the banner at any time except while a scan or conversion is running. To bring it back, use the option in the “Legacy” badge at the top of the product page. Choosing “Remind me later” hides the banner for 30 days.