Skip to main content
Platform security guideReviewed

WooCommerce security checklist: trace every gateway to its scripts, webhooks and order statuses

A WooCommerce store is a WordPress site with a payment chain attached: gateway extensions, the scripts they load at checkout, the addresses that answer their callbacks, the webhooks that carry events in and out, and the order statuses that move stock and send email.

This guide maps that chain from WooCommerce's own documentation, then gives you a dependency graph to fill in from your store and a capped staging run of test orders, a coupon, a refund and a cancellation that records how the chain behaves.

WooCommerce integration dependency graph and staging evidence log

Start a separate spreadsheet for each store, paste the table in and add one column per node from row 1. Rows 1 to 14 read the live store and change nothing on it; row 3 also adds one product to a cart on the staging copy and loads its checkout page there.

How to use it

Rows 15 to 23 run in order on a staging copy of your own store: at most three checkout submissions and one coupon reuse attempt as one invented test customer with an email inbox the business controls, then one partial refund and one status change made by staff on those orders, each gateway in the test or sandbox mode its own documentation describes, never a real card, one request at a time and no load; row 23 then has the owner of any other system that received a test record remove it. Before row 18, confirm that no webhook, shipping, accounting or other connection on the copy points at a live account. Rows 24 and 25 give the PCI DSS references as evidence for whoever manages your compliance programme, not as a compliance statement. Never record a key, secret or password, only whether one is present. The documentation column was checked on 15 November 2026. These pages were used from the copies first read on 14 November 2026: WooCommerce's settings, webhooks, REST API, roles, System Status report, payment options and update guides, its Store API and REST API authentication pages and WordPress.org listing, the Stripe extension pages other than its testing and order information guides, the PayPal Payments and WooPayments pages, the WooPayments status help text file, the WordPress Users screen page and the PCI Security Standards Council's Approved Scanning Vendor and Qualified Security Assessor pages.

25 rows

WooCommerce integration dependency graph and staging evidence log

RowWhat it tracesWhere to read itWhat the documentation saysWhat to write down
1. Nodes: gateways and checkout pluginsEvery payment gateway, and every plugin that changes the cart or checkout. Each becomes a column in your copy.WooCommerce > Settings > Payments for the providers shown as enabled, choosing neither Enable nor Manage; WooCommerce > Status, Active Plugins section, for versions.WooCommerce's settings guide says payment providers are enabled and configured at WooCommerce > Settings > Payments, and that choosing Enable turns on an available provider. The System Status report guide says the Active Plugins section displays all plugins installed and active, with their current version numbers. The gateway API guide describes form based, iFrame based, direct and offline gateways.Each node's name, version, whether it is enabled, its kind (form, iFrame, direct, offline, or not a gateway), the person or business who looks after it, and the date read.
2. Node: theme template overridesTheme files that replace WooCommerce's own templates, including those for the cart, checkout and account pages.WooCommerce > Status, Templates section.The System Status report guide says the Templates section shows any files that are overriding the default WooCommerce template pages, and also notes if the templates are outdated.Each overriding file by path, whether it is marked outdated, and who maintains the theme.
3. Edge: node to the scripts on store pagesWhich hosts each page loads code and frames from, and which node each host belongs to.On the live store, load one product page and the cart page once each with the browser's developer tools network panel open, adding nothing to the cart. On the staging copy, only after rows 15 and 16 have confirmed that nothing on the copy connects to a live account, add one product to the cart once and load the checkout page once, typing nothing into the form. Note host names only, and list anything the visit leaves on the copy, such as a cart, for row 23.PayPal Payments' troubleshooting page says its scripts load only in places where buttons or Pay Later messaging are switched on, and that enabling the Mini Cart location loads them across the whole site. The Stripe extension's card data page says it collects card data through Stripe Elements, a Stripe-hosted interface embedded via an iframe. WooPayments' PCI page says its hosted payment fields are served from the payment partner's environment.For each page: each script host and frame host, the node it belongs to or "none", and who recognises it. A host no node explains goes to the owner as a question, not a deletion. If the staging checkout differs from what the live pages suggest, say so.
4. Edge: payment buttons outside the checkoutPages other than the checkout where a gateway places buttons, and so loads its code.PayPal Payments: the Styling section's Location options, or Smart Button Locations under Standard Payments in the legacy interface. Stripe: the Express checkouts section under WooCommerce > Settings > Payments > Stripe > Payment Methods, and the options page for each set of buttons. Read without saving.PayPal Payments' settings guide lists Cart, Classic Checkout, Express Checkout, Mini Cart and Product Page among the locations. The Stripe extension's express checkout guide says the Apple Pay and Google Pay options include which pages the buttons appear on, among them the checkout page, individual product pages and the cart page, and that the options page lists where the buttons will appear.Each enabled location per node, and each page outside the checkout that therefore loads payment code.
5. Edge: inbound callbacks and gateway webhooksThe addresses on your domain that gateways call, and the events they send.Stripe: Configure connection in the Account details section, Live and Test tabs. PayPal Payments: ask whoever manages the PayPal connection for the webhook status under Expert Settings, because its settings guide says the same Settings page displays the Merchant ID, Email Address and Client ID. In the legacy interface, whose documentation says the Connection tab displays the account's API credentials, ask whoever manages the PayPal connection for the webhook status instead of opening that tab. Ask the Stripe account owner for each webhook endpoint in the Stripe dashboard and the address it sends to. For any other gateway, its own documentation.WooCommerce's gateway guide says callbacks are best added with WC-API hooks, and gives as its example PayPal Standard's callback address, built from the home URL with the wc-api query argument. The Stripe extension's webhook guide says it only uses endpoints in the format https://www.example.com/?wc-api=wc_stripe, and that both the Live and Test tabs should show the webhook status as Configured. PayPal Payments' settings guide says webhooks are registered automatically when the account is connected and that you can see the events the store is subscribed to.For each node: the callback address format, the live and test webhook status as shown, the subscribed events by name, who owns the gateway account, and any endpoint in the gateway's dashboard that no node explains. Never a signing secret. Do not press Reconfigure webhooks or Resubscribe.
6. Edge: outbound WooCommerce webhooksStore events that WooCommerce itself sends to other systems.WooCommerce > Settings > Advanced > Webhooks, the list only. For each webhook's topic and delivery address, ask the developer who set it up rather than opening its edit form, which holds the Secret field.WooCommerce's webhooks guide says a webhook has a Name, a Status (Active, Paused or Disabled), a Topic, a Delivery URL and a Secret; that the Secret generates a hash included in the request headers and defaults to the current API user's consumer secret if left blank; that the first save with the Active status sends a ping to the Delivery URL; and that WooCommerce disables a webhook after more than five consecutive delivery failures, a threshold it says a filter can change.Each webhook's name, status, topic, delivery host, the owner of the receiving system, and whether a secret was set (yes, no or unknown). Never the secret. Do not press Save webhook.
7. Edge: REST API keysOutside systems that read or write store data with a key.WooCommerce > Settings > Advanced > REST API: read the list of existing keys, and leave the Create an API key and Add Key buttons alone.WooCommerce's REST API guide says each set of keys is linked to a WordPress user, with Read, Write or Read/Write permissions, and that the Consumer Secret is shown only once. The developer authentication page says a key's use of the API conforms to the WordPress roles and capabilities of the user it belongs to, and that deleting that user stops the key working.Each key's description, linked user, permission level as the list or the integration's owner gives it, and the system that uses it. Never a key or secret, or any part of one. A key whose system nobody can name goes to the owner as a question.
8. Edge: node to order statusWhich statuses each gateway sets, and on what signal.WooCommerce > Orders: the order notes on one recent order paid through each gateway, read only.The order status guide says Processing means paid with stock reduced, On hold means awaiting confirmation with stock reduced, and after a delayed notification payment an order may move on from On hold automatically, depending on the gateway. The Stripe extension's order status guide says its automatic status updates only work if webhooks are configured correctly. The gateway API guide says payment_complete() should be called only after the provider confirms payment.For each node: the statuses it sets, the signal behind each (redirect, callback, webhook or staff), and the wording of the notes it leaves. Order numbers only, never customer details.
9. Edge: refundsHow money goes back to a customer through each gateway, and who can send it.The order notes on any past refunds; the Users screen's role filter links for Administrator and Shop Manager; the staff who process refunds. Do not open the refund form on a real order.The refunds guide says automatic refunds need a compatible gateway, that a refund recorded only in WooCommerce leaves the money to be returned outside it, that the gateway usually adds an order note after a refund through the payment method used, and to look for a "Successfully refunded" message. Processing refunds is among the Shop Manager capabilities on WooCommerce's roles page. PayPal Payments' orders guide says refunds made on paypal.com sync to the order through webhooks.Per node: whether refunds go back through the gateway or are recorded only in WooCommerce, whether past refunds show the "Successfully refunded" message, and each account that can refund, by name and role.
10. Edge: couponsDiscounts that change what an order costs, and their limits.Marketing > Coupons, each published coupon, read without saving. WooCommerce > Settings > General for whether coupons are enabled.The coupon guide says coupons are created at Marketing > Coupons and enabled at WooCommerce > Settings > General, that coupons expire on the expiry date set, and that the usage limits are "Usage limit per coupon", "Limit usage to X items" and "Usage limit per user". Allowed Emails is verified against the customer's billing email.Each live coupon's code or internal description, discount type, expiry, usage limit per coupon and per user, whether an email restriction is set, and who created it. Do not copy any customer's address out of an allowed list.
11. Edge: stockHow stock is reduced, held and returned.WooCommerce > Settings > Products > Inventory, read without saving.The products settings guide describes Manage stock and "Hold Stock (minutes)", which cancels a pending order when the limit is reached and releases its held stock, only for orders in "Pending payment". The gateway API guide gives 60 minutes as the default hold stock time when stock management is on.Whether stock management is on, the Hold Stock value, and who receives stock notifications, by role.
12. Node: live or test mode on the live storeWhether each gateway on the live store is taking real payments.Stripe: the General section of the Stripe settings, Enable test mode. PayPal Payments: ask whoever manages the PayPal connection whether Connection Status on the Settings page shows Sandbox, because its settings guide says that section displays the Merchant ID, Email Address and Client ID. WooPayments: WooCommerce > Status, WooPayments section, Test Mode and Dev Mode rows. Read without saving.The Stripe extension's settings guide says the Enable test mode box controls test mode and, unless you are testing payments, refunds, disputes or other such processes, should likely be disabled. PayPal Payments' settings guide says Connection Status displays Sandbox when test credentials are in use. The WooPayments status help text describes the Test Mode row as "Whether the payment gateway has test payments enabled or not."Live or test for each node on the live store, with the date. A live store showing test mode goes to the owner as a question.
13. Node: logsWhere the store keeps records of webhook deliveries and gateway activity.WooCommerce > Status > Logs, the list of sources only.WooCommerce's webhooks guide says WooCommerce saves logs of all events that trigger a webhook, and that the list can be filtered by the webhooks-delivery source. PayPal Payments' troubleshooting page says logs for its source are kept for 30 days. The Stripe extension's order information guide refers to a Stripe log at the same screen.Each log source present, the oldest date shown, and who can read the screen. Do not open entries to copy anything out; treat them as if they hold customer details and payloads.
14. Node: people who can change the chainAccounts that can change settings, coupons, orders and refunds.The WordPress Users screen, using the role filter links for Administrator and Shop Manager.WordPress.org's page on the Users screen says the filter links above the user table display the users assigned to each role. WooCommerce's roles page lists, among a Shop Manager's capabilities, access to WooCommerce settings, managing products and coupons, viewing, editing and deleting orders, processing refunds and viewing user details for all roles.Each account by name and role, the person behind it, and whether that person still needs the access.
15. Staging: what the copy can reachConnections on the staging copy that could carry a test order to a live system.On the copy, the Webhooks list under WooCommerce > Settings > Advanced; the recipients set at WooCommerce > Settings > Emails; and each shipping, accounting, marketing or fulfilment integration, read with whoever manages the copy. Ask how the copy sends email.WooCommerce's testing guide says test orders can trigger order emails and appear in analytics, that other extensions, plugins or services may be unable to tell test orders from real ones, that you may want to disable specific integrations before placing test orders, and that the email-blocking plugin it suggests may not prevent emails sent via an SMTP provider. The email settings guide says the New order email goes to your chosen recipients.Each webhook, integration and email route on the copy, whether it points at a live account (yes, no or unknown), and whether each email recipient is an inbox the business controls. Run nothing until no answer points at a live account and every recipient is an inbox the business controls. Disabling a connection is a change for whoever manages the copy.
16. Staging: gateway test modesThat every gateway on the copy is in its test or sandbox mode before any order.On the copy, the same places and people as row 12: where row 12 asks whoever manages a connection, ask them here too, and save nothing. For Stripe, ask the account owner where each live and test webhook endpoint delivers.The Stripe extension's testing guide describes the Enable test mode option and says both modes always use the same Stripe account. PayPal Payments' onboarding guide recommends a PayPal Sandbox account and a second sandbox account to act as the buyer. WooPayments' test accounts page says development mode keeps payments in test mode even with a real account connected. Its Safe Mode page names cloning to staging as a trigger and says Transfer your connection disconnects the site at the original address. The Stripe webhook guide says that when the saved webhook points at another site's URL, as on a staging copy, the extension skips the webhook changes it otherwise makes at each update.Each node's mode on the copy. If any shows live mode, or the Stripe test-mode endpoint delivers to the live store's address, stop and take it to the owner. If a WooPayments Safe Mode notice shows, record it and press neither of its buttons.
17. Staging: the test customer and the limitsWho the run buys as, and how much it may do.A test customer account created on the copy for the run, named with a marker such as WOOTEST-1115, with a billing email at an inbox the business controls. Payment: a test card or sandbox buyer from the gateway's own documentation.The Stripe extension's testing guide says there are test cards for scenarios such as successful payments and card declines, and that Apple Pay is tested with real card information. The coupon guide says Allowed Emails is verified against the customer's billing email.The marker, the inbox, the payment method as the gateway names it (the card brand, never a number), and the limits: at most three checkout submissions, one coupon reuse attempt, one partial refund and one status change, one at a time, no express checkout buttons, never a real card and no load.
18. Staging order 1: a paid order with a test couponA normal sale through one node, with a discount, from cart to Processing.On the copy, create one test coupon at Marketing > Coupons with "Usage limit per user" set to 1 and Allowed Emails set to the test customer's address. Then, as the test customer, buy two units of one product whose stock is managed, apply the coupon and pay with the gateway's test method. If coupons are switched off on the copy (row 10), buy without one and skip row 19. Limits: the first of the run's three checkout submissions, the gateway in the test or sandbox mode its own documentation describes, never a real card, email only to inboxes cleared in row 15, one request at a time and no load.The coupon guide describes the per-user limit and Allowed Emails. The order status guide says Processing means paid with stock reduced. The single order page guide says system notes are added for events such as status changes, payment results and webhook callbacks, and, where coupons are applied or removed on an order, that WooCommerce tracks coupon usage counts. The Stripe extension's testing guide says that after a successful test payment, a linked Charge ID on the order opens its details in the Stripe dashboard.The order number, each status with its time from the order notes, which notes came from a webhook callback, stock before and after, the coupon's usage count, each email that reached the inbox (sender and subject), each webhook delivery logged under row 6's hosts, and whether a gateway reference is shown (yes or no, not copied).
19. Staging: the coupon a second timeWhether the per-user limit holds for the same customer.On the copy, as the same invented test customer, put one eligible product in a new cart and apply the coupon once. Limits: the run's one coupon reuse attempt, with no checkout submission, no payment and no load. Do not place the order, and empty the cart afterwards.The coupon guide says the per-user limit makes a coupon invalid for that customer after the set number of uses, and that WooCommerce displays a message explaining why a coupon cannot be applied. The Store API lists cart endpoints for applying and removing coupons.Whether the coupon was refused, and the message shown, word for word.
20. Staging: a partial refund with restockMoney and stock going back for one unit of order 1.On the copy, on order 1, use the Refund button, refund one unit with "Restock refunded items" ticked, and refund through the gateway in the test or sandbox mode its own documentation describes. Limits: the run's one refund, not repeated, with the refund email going only to the test customer's inbox.The refunds guide says the gateway usually adds an order note after a refund through the payment method used, and to look for a "Successfully refunded" message. It also says a refund can restock products with the "Restock refunded items" box, and that when less than the full value is refunded the status does not change to Refunded and the email refers to a "partial refund".The refund note, whether the gateway's test dashboard shows the refund (yes or no), the order status after, stock after, and the refund email's subject.
21. Staging order 2: a declined paymentWhat a failed payment does to the order and the stock. Skip this row for any gateway whose documentation gives no decline test method.On the copy, one checkout as the invented test customer with the gateway's documented decline test card, never a real card. Limits: the second of the run's three checkout submissions, the gateway in its documented test or sandbox mode, email only to inboxes cleared in row 15, and no load. Do not retry it.The order status guide says Failed means the payment failed or was declined, that stock previously reduced returns to inventory when an order moves to Failed, and that depending on the gateway the status may not show immediately. The email settings guide describes Failed order notifications to the store and the customer.Whether an order was created and its status, stock before and after, the notes, and each email that arrived.
22. Staging order 3: paid, then cancelled by staffWhether cancelling returns stock, and whether anyone mistakes it for a refund.On the copy, one paid order as the invented test customer with the gateway's test method, never a real card. Then, as staff, choose Cancelled from the order's Status dropdown and select Update. Limits: the last of the run's three checkout submissions and its one status change, the gateway in its documented test or sandbox mode, email only to inboxes cleared in row 15, and no load.The order status guide says stock for a Cancelled order returns to inventory if inventory management is enabled, and that a cancelled order may need to be refunded. The refunds guide says changing a status to Cancelled will not automatically refund the customer. The email settings guide says a Cancelled order email goes to your chosen recipients when an order is cancelled from Processing, among other statuses.Stock after, whether the gateway's test dashboard still shows the payment as taken, the notes, and each email that arrived.
23. Staging: clean-upEverything the run created, on the copy and anywhere else.On the copy: the test orders, the test coupon and the test customer account, and nothing else. Then each system from row 15 that received anything carrying the marker.WooCommerce's testing guide says to delete test orders after testing, to prevent them from being inadvertently handled, shipped or included in the store's analytics.For every test record: the system holding it, the person who deletes it, and when. Each system's owner removes the record in that system.
24. Reference: PCI DSS v4.x Requirements 6.4.3 and 11.6.1, payment page scriptsRow 3's checkout answers as a record of the scripts on the payment page, with row 4's list of other pages that load payment code.The PCI Security Standards Council's post announcing "Payment Page Security and Preventing E-Skimming", dated 10 March 2025.The post says PCI DSS v4.x includes Requirements 6.4.3 and 11.6.1, which focus on ensuring that payment page scripts are properly authorised, checked for integrity and monitored for tampering. It gives PCI DSS v4.0.1 as the current version at the time of publication, and says the Council does not enforce compliance or determine whether specific implementations are compliant.For each script host on the checkout page: the node, the business reason, who authorised it, and how its integrity is checked, if anyone knows. A record for whoever manages your compliance programme, not a compliance statement.
25. Reference: PCI DSS v4.x Requirements 6.4.3 and 11.6.1, HTTP headers and changesWhether anyone would notice a change to the payment page or its headers.The response headers of the staging checkout page load in row 3, in the browser's developer tools; and whoever looks after the live store's code and hosting.The same post says the requirements address the need for careful management of both scripts and security-impacting HTTP headers, to prevent unauthorised changes to webpages whether in the server environment or as rendered in the consumer's browser. It says entities should work with the organisations managing their compliance programmes, such as acquirers or payment brands, to understand any specific compliance validation and reporting responsibilities.The security-related headers the staging checkout page sends, by name, marked as read on the copy, and who would be told, and how, if a script or header on the live payment page changed.

Row

What it traces

  1. 1. Nodes: gateways and checkout plugins
    What it traces
    Every payment gateway, and every plugin that changes the cart or checkout. Each becomes a column in your copy.
    Where to read it
    WooCommerce > Settings > Payments for the providers shown as enabled, choosing neither Enable nor Manage; WooCommerce > Status, Active Plugins section, for versions.
    What the documentation says
    WooCommerce's settings guide says payment providers are enabled and configured at WooCommerce > Settings > Payments, and that choosing Enable turns on an available provider. The System Status report guide says the Active Plugins section displays all plugins installed and active, with their current version numbers. The gateway API guide describes form based, iFrame based, direct and offline gateways.
    What to write down
    Each node's name, version, whether it is enabled, its kind (form, iFrame, direct, offline, or not a gateway), the person or business who looks after it, and the date read.
  2. 2. Node: theme template overrides
    What it traces
    Theme files that replace WooCommerce's own templates, including those for the cart, checkout and account pages.
    Where to read it
    WooCommerce > Status, Templates section.
    What the documentation says
    The System Status report guide says the Templates section shows any files that are overriding the default WooCommerce template pages, and also notes if the templates are outdated.
    What to write down
    Each overriding file by path, whether it is marked outdated, and who maintains the theme.
  3. 3. Edge: node to the scripts on store pages
    What it traces
    Which hosts each page loads code and frames from, and which node each host belongs to.
    Where to read it
    On the live store, load one product page and the cart page once each with the browser's developer tools network panel open, adding nothing to the cart. On the staging copy, only after rows 15 and 16 have confirmed that nothing on the copy connects to a live account, add one product to the cart once and load the checkout page once, typing nothing into the form. Note host names only, and list anything the visit leaves on the copy, such as a cart, for row 23.
    What the documentation says
    PayPal Payments' troubleshooting page says its scripts load only in places where buttons or Pay Later messaging are switched on, and that enabling the Mini Cart location loads them across the whole site. The Stripe extension's card data page says it collects card data through Stripe Elements, a Stripe-hosted interface embedded via an iframe. WooPayments' PCI page says its hosted payment fields are served from the payment partner's environment.
    What to write down
    For each page: each script host and frame host, the node it belongs to or "none", and who recognises it. A host no node explains goes to the owner as a question, not a deletion. If the staging checkout differs from what the live pages suggest, say so.
  4. 4. Edge: payment buttons outside the checkout
    What it traces
    Pages other than the checkout where a gateway places buttons, and so loads its code.
    Where to read it
    PayPal Payments: the Styling section's Location options, or Smart Button Locations under Standard Payments in the legacy interface. Stripe: the Express checkouts section under WooCommerce > Settings > Payments > Stripe > Payment Methods, and the options page for each set of buttons. Read without saving.
    What the documentation says
    PayPal Payments' settings guide lists Cart, Classic Checkout, Express Checkout, Mini Cart and Product Page among the locations. The Stripe extension's express checkout guide says the Apple Pay and Google Pay options include which pages the buttons appear on, among them the checkout page, individual product pages and the cart page, and that the options page lists where the buttons will appear.
    What to write down
    Each enabled location per node, and each page outside the checkout that therefore loads payment code.
  5. 5. Edge: inbound callbacks and gateway webhooks
    What it traces
    The addresses on your domain that gateways call, and the events they send.
    Where to read it
    Stripe: Configure connection in the Account details section, Live and Test tabs. PayPal Payments: ask whoever manages the PayPal connection for the webhook status under Expert Settings, because its settings guide says the same Settings page displays the Merchant ID, Email Address and Client ID. In the legacy interface, whose documentation says the Connection tab displays the account's API credentials, ask whoever manages the PayPal connection for the webhook status instead of opening that tab. Ask the Stripe account owner for each webhook endpoint in the Stripe dashboard and the address it sends to. For any other gateway, its own documentation.
    What the documentation says
    WooCommerce's gateway guide says callbacks are best added with WC-API hooks, and gives as its example PayPal Standard's callback address, built from the home URL with the wc-api query argument. The Stripe extension's webhook guide says it only uses endpoints in the format https://www.example.com/?wc-api=wc_stripe, and that both the Live and Test tabs should show the webhook status as Configured. PayPal Payments' settings guide says webhooks are registered automatically when the account is connected and that you can see the events the store is subscribed to.
    What to write down
    For each node: the callback address format, the live and test webhook status as shown, the subscribed events by name, who owns the gateway account, and any endpoint in the gateway's dashboard that no node explains. Never a signing secret. Do not press Reconfigure webhooks or Resubscribe.
  6. 6. Edge: outbound WooCommerce webhooks
    What it traces
    Store events that WooCommerce itself sends to other systems.
    Where to read it
    WooCommerce > Settings > Advanced > Webhooks, the list only. For each webhook's topic and delivery address, ask the developer who set it up rather than opening its edit form, which holds the Secret field.
    What the documentation says
    WooCommerce's webhooks guide says a webhook has a Name, a Status (Active, Paused or Disabled), a Topic, a Delivery URL and a Secret; that the Secret generates a hash included in the request headers and defaults to the current API user's consumer secret if left blank; that the first save with the Active status sends a ping to the Delivery URL; and that WooCommerce disables a webhook after more than five consecutive delivery failures, a threshold it says a filter can change.
    What to write down
    Each webhook's name, status, topic, delivery host, the owner of the receiving system, and whether a secret was set (yes, no or unknown). Never the secret. Do not press Save webhook.
  7. 7. Edge: REST API keys
    What it traces
    Outside systems that read or write store data with a key.
    Where to read it
    WooCommerce > Settings > Advanced > REST API: read the list of existing keys, and leave the Create an API key and Add Key buttons alone.
    What the documentation says
    WooCommerce's REST API guide says each set of keys is linked to a WordPress user, with Read, Write or Read/Write permissions, and that the Consumer Secret is shown only once. The developer authentication page says a key's use of the API conforms to the WordPress roles and capabilities of the user it belongs to, and that deleting that user stops the key working.
    What to write down
    Each key's description, linked user, permission level as the list or the integration's owner gives it, and the system that uses it. Never a key or secret, or any part of one. A key whose system nobody can name goes to the owner as a question.
  8. 8. Edge: node to order status
    What it traces
    Which statuses each gateway sets, and on what signal.
    Where to read it
    WooCommerce > Orders: the order notes on one recent order paid through each gateway, read only.
    What the documentation says
    The order status guide says Processing means paid with stock reduced, On hold means awaiting confirmation with stock reduced, and after a delayed notification payment an order may move on from On hold automatically, depending on the gateway. The Stripe extension's order status guide says its automatic status updates only work if webhooks are configured correctly. The gateway API guide says payment_complete() should be called only after the provider confirms payment.
    What to write down
    For each node: the statuses it sets, the signal behind each (redirect, callback, webhook or staff), and the wording of the notes it leaves. Order numbers only, never customer details.
  9. 9. Edge: refunds
    What it traces
    How money goes back to a customer through each gateway, and who can send it.
    Where to read it
    The order notes on any past refunds; the Users screen's role filter links for Administrator and Shop Manager; the staff who process refunds. Do not open the refund form on a real order.
    What the documentation says
    The refunds guide says automatic refunds need a compatible gateway, that a refund recorded only in WooCommerce leaves the money to be returned outside it, that the gateway usually adds an order note after a refund through the payment method used, and to look for a "Successfully refunded" message. Processing refunds is among the Shop Manager capabilities on WooCommerce's roles page. PayPal Payments' orders guide says refunds made on paypal.com sync to the order through webhooks.
    What to write down
    Per node: whether refunds go back through the gateway or are recorded only in WooCommerce, whether past refunds show the "Successfully refunded" message, and each account that can refund, by name and role.
  10. 10. Edge: coupons
    What it traces
    Discounts that change what an order costs, and their limits.
    Where to read it
    Marketing > Coupons, each published coupon, read without saving. WooCommerce > Settings > General for whether coupons are enabled.
    What the documentation says
    The coupon guide says coupons are created at Marketing > Coupons and enabled at WooCommerce > Settings > General, that coupons expire on the expiry date set, and that the usage limits are "Usage limit per coupon", "Limit usage to X items" and "Usage limit per user". Allowed Emails is verified against the customer's billing email.
    What to write down
    Each live coupon's code or internal description, discount type, expiry, usage limit per coupon and per user, whether an email restriction is set, and who created it. Do not copy any customer's address out of an allowed list.
  11. 11. Edge: stock
    What it traces
    How stock is reduced, held and returned.
    Where to read it
    WooCommerce > Settings > Products > Inventory, read without saving.
    What the documentation says
    The products settings guide describes Manage stock and "Hold Stock (minutes)", which cancels a pending order when the limit is reached and releases its held stock, only for orders in "Pending payment". The gateway API guide gives 60 minutes as the default hold stock time when stock management is on.
    What to write down
    Whether stock management is on, the Hold Stock value, and who receives stock notifications, by role.
  12. 12. Node: live or test mode on the live store
    What it traces
    Whether each gateway on the live store is taking real payments.
    Where to read it
    Stripe: the General section of the Stripe settings, Enable test mode. PayPal Payments: ask whoever manages the PayPal connection whether Connection Status on the Settings page shows Sandbox, because its settings guide says that section displays the Merchant ID, Email Address and Client ID. WooPayments: WooCommerce > Status, WooPayments section, Test Mode and Dev Mode rows. Read without saving.
    What the documentation says
    The Stripe extension's settings guide says the Enable test mode box controls test mode and, unless you are testing payments, refunds, disputes or other such processes, should likely be disabled. PayPal Payments' settings guide says Connection Status displays Sandbox when test credentials are in use. The WooPayments status help text describes the Test Mode row as "Whether the payment gateway has test payments enabled or not."
    What to write down
    Live or test for each node on the live store, with the date. A live store showing test mode goes to the owner as a question.
  13. 13. Node: logs
    What it traces
    Where the store keeps records of webhook deliveries and gateway activity.
    Where to read it
    WooCommerce > Status > Logs, the list of sources only.
    What the documentation says
    WooCommerce's webhooks guide says WooCommerce saves logs of all events that trigger a webhook, and that the list can be filtered by the webhooks-delivery source. PayPal Payments' troubleshooting page says logs for its source are kept for 30 days. The Stripe extension's order information guide refers to a Stripe log at the same screen.
    What to write down
    Each log source present, the oldest date shown, and who can read the screen. Do not open entries to copy anything out; treat them as if they hold customer details and payloads.
  14. 14. Node: people who can change the chain
    What it traces
    Accounts that can change settings, coupons, orders and refunds.
    Where to read it
    The WordPress Users screen, using the role filter links for Administrator and Shop Manager.
    What the documentation says
    WordPress.org's page on the Users screen says the filter links above the user table display the users assigned to each role. WooCommerce's roles page lists, among a Shop Manager's capabilities, access to WooCommerce settings, managing products and coupons, viewing, editing and deleting orders, processing refunds and viewing user details for all roles.
    What to write down
    Each account by name and role, the person behind it, and whether that person still needs the access.
  15. 15. Staging: what the copy can reach
    What it traces
    Connections on the staging copy that could carry a test order to a live system.
    Where to read it
    On the copy, the Webhooks list under WooCommerce > Settings > Advanced; the recipients set at WooCommerce > Settings > Emails; and each shipping, accounting, marketing or fulfilment integration, read with whoever manages the copy. Ask how the copy sends email.
    What the documentation says
    WooCommerce's testing guide says test orders can trigger order emails and appear in analytics, that other extensions, plugins or services may be unable to tell test orders from real ones, that you may want to disable specific integrations before placing test orders, and that the email-blocking plugin it suggests may not prevent emails sent via an SMTP provider. The email settings guide says the New order email goes to your chosen recipients.
    What to write down
    Each webhook, integration and email route on the copy, whether it points at a live account (yes, no or unknown), and whether each email recipient is an inbox the business controls. Run nothing until no answer points at a live account and every recipient is an inbox the business controls. Disabling a connection is a change for whoever manages the copy.
  16. 16. Staging: gateway test modes
    What it traces
    That every gateway on the copy is in its test or sandbox mode before any order.
    Where to read it
    On the copy, the same places and people as row 12: where row 12 asks whoever manages a connection, ask them here too, and save nothing. For Stripe, ask the account owner where each live and test webhook endpoint delivers.
    What the documentation says
    The Stripe extension's testing guide describes the Enable test mode option and says both modes always use the same Stripe account. PayPal Payments' onboarding guide recommends a PayPal Sandbox account and a second sandbox account to act as the buyer. WooPayments' test accounts page says development mode keeps payments in test mode even with a real account connected. Its Safe Mode page names cloning to staging as a trigger and says Transfer your connection disconnects the site at the original address. The Stripe webhook guide says that when the saved webhook points at another site's URL, as on a staging copy, the extension skips the webhook changes it otherwise makes at each update.
    What to write down
    Each node's mode on the copy. If any shows live mode, or the Stripe test-mode endpoint delivers to the live store's address, stop and take it to the owner. If a WooPayments Safe Mode notice shows, record it and press neither of its buttons.
  17. 17. Staging: the test customer and the limits
    What it traces
    Who the run buys as, and how much it may do.
    Where to read it
    A test customer account created on the copy for the run, named with a marker such as WOOTEST-1115, with a billing email at an inbox the business controls. Payment: a test card or sandbox buyer from the gateway's own documentation.
    What the documentation says
    The Stripe extension's testing guide says there are test cards for scenarios such as successful payments and card declines, and that Apple Pay is tested with real card information. The coupon guide says Allowed Emails is verified against the customer's billing email.
    What to write down
    The marker, the inbox, the payment method as the gateway names it (the card brand, never a number), and the limits: at most three checkout submissions, one coupon reuse attempt, one partial refund and one status change, one at a time, no express checkout buttons, never a real card and no load.
  18. 18. Staging order 1: a paid order with a test coupon
    What it traces
    A normal sale through one node, with a discount, from cart to Processing.
    Where to read it
    On the copy, create one test coupon at Marketing > Coupons with "Usage limit per user" set to 1 and Allowed Emails set to the test customer's address. Then, as the test customer, buy two units of one product whose stock is managed, apply the coupon and pay with the gateway's test method. If coupons are switched off on the copy (row 10), buy without one and skip row 19. Limits: the first of the run's three checkout submissions, the gateway in the test or sandbox mode its own documentation describes, never a real card, email only to inboxes cleared in row 15, one request at a time and no load.
    What the documentation says
    The coupon guide describes the per-user limit and Allowed Emails. The order status guide says Processing means paid with stock reduced. The single order page guide says system notes are added for events such as status changes, payment results and webhook callbacks, and, where coupons are applied or removed on an order, that WooCommerce tracks coupon usage counts. The Stripe extension's testing guide says that after a successful test payment, a linked Charge ID on the order opens its details in the Stripe dashboard.
    What to write down
    The order number, each status with its time from the order notes, which notes came from a webhook callback, stock before and after, the coupon's usage count, each email that reached the inbox (sender and subject), each webhook delivery logged under row 6's hosts, and whether a gateway reference is shown (yes or no, not copied).
  19. 19. Staging: the coupon a second time
    What it traces
    Whether the per-user limit holds for the same customer.
    Where to read it
    On the copy, as the same invented test customer, put one eligible product in a new cart and apply the coupon once. Limits: the run's one coupon reuse attempt, with no checkout submission, no payment and no load. Do not place the order, and empty the cart afterwards.
    What the documentation says
    The coupon guide says the per-user limit makes a coupon invalid for that customer after the set number of uses, and that WooCommerce displays a message explaining why a coupon cannot be applied. The Store API lists cart endpoints for applying and removing coupons.
    What to write down
    Whether the coupon was refused, and the message shown, word for word.
  20. 20. Staging: a partial refund with restock
    What it traces
    Money and stock going back for one unit of order 1.
    Where to read it
    On the copy, on order 1, use the Refund button, refund one unit with "Restock refunded items" ticked, and refund through the gateway in the test or sandbox mode its own documentation describes. Limits: the run's one refund, not repeated, with the refund email going only to the test customer's inbox.
    What the documentation says
    The refunds guide says the gateway usually adds an order note after a refund through the payment method used, and to look for a "Successfully refunded" message. It also says a refund can restock products with the "Restock refunded items" box, and that when less than the full value is refunded the status does not change to Refunded and the email refers to a "partial refund".
    What to write down
    The refund note, whether the gateway's test dashboard shows the refund (yes or no), the order status after, stock after, and the refund email's subject.
  21. 21. Staging order 2: a declined payment
    What it traces
    What a failed payment does to the order and the stock. Skip this row for any gateway whose documentation gives no decline test method.
    Where to read it
    On the copy, one checkout as the invented test customer with the gateway's documented decline test card, never a real card. Limits: the second of the run's three checkout submissions, the gateway in its documented test or sandbox mode, email only to inboxes cleared in row 15, and no load. Do not retry it.
    What the documentation says
    The order status guide says Failed means the payment failed or was declined, that stock previously reduced returns to inventory when an order moves to Failed, and that depending on the gateway the status may not show immediately. The email settings guide describes Failed order notifications to the store and the customer.
    What to write down
    Whether an order was created and its status, stock before and after, the notes, and each email that arrived.
  22. 22. Staging order 3: paid, then cancelled by staff
    What it traces
    Whether cancelling returns stock, and whether anyone mistakes it for a refund.
    Where to read it
    On the copy, one paid order as the invented test customer with the gateway's test method, never a real card. Then, as staff, choose Cancelled from the order's Status dropdown and select Update. Limits: the last of the run's three checkout submissions and its one status change, the gateway in its documented test or sandbox mode, email only to inboxes cleared in row 15, and no load.
    What the documentation says
    The order status guide says stock for a Cancelled order returns to inventory if inventory management is enabled, and that a cancelled order may need to be refunded. The refunds guide says changing a status to Cancelled will not automatically refund the customer. The email settings guide says a Cancelled order email goes to your chosen recipients when an order is cancelled from Processing, among other statuses.
    What to write down
    Stock after, whether the gateway's test dashboard still shows the payment as taken, the notes, and each email that arrived.
  23. 23. Staging: clean-up
    What it traces
    Everything the run created, on the copy and anywhere else.
    Where to read it
    On the copy: the test orders, the test coupon and the test customer account, and nothing else. Then each system from row 15 that received anything carrying the marker.
    What the documentation says
    WooCommerce's testing guide says to delete test orders after testing, to prevent them from being inadvertently handled, shipped or included in the store's analytics.
    What to write down
    For every test record: the system holding it, the person who deletes it, and when. Each system's owner removes the record in that system.
  24. 24. Reference: PCI DSS v4.x Requirements 6.4.3 and 11.6.1, payment page scripts
    What it traces
    Row 3's checkout answers as a record of the scripts on the payment page, with row 4's list of other pages that load payment code.
    Where to read it
    The PCI Security Standards Council's post announcing "Payment Page Security and Preventing E-Skimming", dated 10 March 2025.
    What the documentation says
    The post says PCI DSS v4.x includes Requirements 6.4.3 and 11.6.1, which focus on ensuring that payment page scripts are properly authorised, checked for integrity and monitored for tampering. It gives PCI DSS v4.0.1 as the current version at the time of publication, and says the Council does not enforce compliance or determine whether specific implementations are compliant.
    What to write down
    For each script host on the checkout page: the node, the business reason, who authorised it, and how its integrity is checked, if anyone knows. A record for whoever manages your compliance programme, not a compliance statement.
  25. 25. Reference: PCI DSS v4.x Requirements 6.4.3 and 11.6.1, HTTP headers and changes
    What it traces
    Whether anyone would notice a change to the payment page or its headers.
    Where to read it
    The response headers of the staging checkout page load in row 3, in the browser's developer tools; and whoever looks after the live store's code and hosting.
    What the documentation says
    The same post says the requirements address the need for careful management of both scripts and security-impacting HTTP headers, to prevent unauthorised changes to webpages whether in the server environment or as rendered in the consumer's browser. It says entities should work with the organisations managing their compliance programmes, such as acquirers or payment brands, to understand any specific compliance validation and reporting responsibilities.
    What to write down
    The security-related headers the staging checkout page sends, by name, marked as read on the copy, and who would be told, and how, if a script or header on the live payment page changed.

Why a WooCommerce security checklist starts with the payment chain

WooCommerce's WordPress.org listing shows it as a plugin by Automattic and describes it as the open-source ecommerce platform for WordPress.

The listing says payments can be managed with WooPayments, in the countries it names for WooPayments, or accepted through payment gateways, naming Stripe, PayPal and Square among them, and that developers can integrate virtually any service using a REST API and webhooks.

Built into WooCommerce, its payment options guide says, are free core payment options that include Cash on Delivery, Check Payments and Direct Bank Transfers (BACS), and a store can also choose from free and paid gateway extensions.

Gateway extensions are code of their own. WooCommerce's developer guide to the payment gateway API says gateways are class based and can be added through traditional plugins, and it describes form based, iFrame based, direct and offline gateways. A form based gateway redirects the customer to the payment processor on the gateway's own website.

An iFrame based gateway loads its payment system inside an iframe on the store. A direct gateway shows payment fields on the checkout page itself. An offline gateway takes no online payment.

On this page's reading, that makes each gateway, and each plugin that changes the cart or checkout, a node that can have its own connections: scripts it puts on pages, an address on your domain that answers its callbacks, webhooks that tell the store what happened, and the order statuses it sets.

A version check tells you whether a published record covers that code. It does not show how the nodes connect on your store, which is what the dependency graph on this page records.

Vulnerability records for WooCommerce itself, WooPayments, the Stripe gateway and PayPal Payments sit on their own pages in this library's WordPress plugin register. This guide names none of them and leaves version matching to those pages.

Is WooCommerce secure? What WooCommerce's pages describe, and what each store sets

The WooCommerce pages read for this guide give no yes or no, and this guide does not either.

What they describe includes where card data goes, which depends on the gateway. According to the payment options guide, the customer information checkout collects depends on the payment gateway: a store taking BACS won't process the payment itself, whereas gateways such as Stripe or PayPal need information passed from the site to that payment processor.

The gateway documentation then says where the card fields come from. The Stripe extension's documentation says it collects card data using Stripe Elements, which embeds a Stripe-hosted interface on your site via an iframe. WooPayments' documentation says it uses hosted payment fields served from its payment partner's environment.

PayPal Payments' card processing page describes two ways to take cards: a branded Debit or Credit Card button, and Advanced Card Processing, available for business accounts in select countries once PayPal approves the account, whose fields it describes as hosted fields on your website.

Read the documentation for any other gateway on your store the same way, from that gateway's own pages.

On updates, WooCommerce's update guide says to update sooner than a regular schedule when a release includes a security fix, and points to the WooCommerce Advisories page and the changelog, both of which it says flag whether a given release includes a security fix. It also says to make a current backup and test the update on a staging site whenever possible.

Then there is what is set on each store, which only a reading of that store can answer: which gateways are enabled, who holds the Shop Manager role, which REST API keys exist and which user each one belongs to, where webhooks deliver, which coupons are live and how they are limited, how stock is held for unpaid orders, and what else loads on the checkout page.

Among the capabilities WooCommerce's roles page gives a Shop Manager are access to WooCommerce settings, managing products and coupons, viewing, editing and deleting orders, processing refunds and viewing user details for all roles. Each of these settings has a row in the graph.

WooCommerce runs inside a WordPress site. WordPress roles, login, plugins and admin exposure are covered in the WordPress security audit guide in this library; this page stays with the store.

Which scripts reach a WooCommerce checkout

A gateway can decide part of what loads in the customer's browser.

PayPal Payments' troubleshooting page says its scripts load only in places where buttons or Pay Later messaging are switched on, and that because the Mini Cart location appears on almost every page, enabling that location loads them across the whole site.

The Stripe extension's express checkout guide says the options for Apple Pay and Google Pay include which pages the buttons appear on, among them the checkout page, individual product pages and the cart page. The Stripe extension's testing guide says the plugin uses the Stripe.js file.

WooCommerce's gateway guide adds that form and iFrame based gateways post data offsite, and that direct gateways require server security, such as SSL certificates, and may also require a level of PCI compliance.

Gateways are not the only source of code on the page. The System Status report's Templates section, WooCommerce's guide says, shows any files overriding the default WooCommerce template pages and notes if the templates are outdated. Analytics tags, chat widgets and checkout plugins can bring their own scripts as well.

This page's advice is to build the checkout's script list from what the browser actually loads, then match each host to a node, rather than starting from the plugin list.

PCI DSS Requirements 6.4.3 and 11.6.1

The PCI Security Standards Council's post announcing its information supplement "Payment Page Security and Preventing E-Skimming", dated 10 March 2025, says PCI DSS v4.x includes Requirements 6.4.3 and 11.6.1. It says they focus on ensuring that payment page scripts are properly authorised, checked for integrity and monitored for tampering, and that they address the need for careful management of both scripts and security-impacting HTTP headers to prevent unauthorised changes to webpages, whether in the server environment or as rendered in the consumer's browser. The post gives PCI DSS v4.0.1 as the current version at the time of publication.

The same post says the Council does not enforce compliance or determine whether specific implementations are compliant, and that entities should work with the organisations managing their compliance programmes, such as acquirers or payment brands, to understand any specific compliance validation and reporting responsibilities.

On this page's reading of the post, the graph's script and header rows gather facts about the areas it says those requirements focus on and address: which scripts run on the payment page, who authorised each one, how its integrity is checked, and which headers the page sends.

This page does not say whether either requirement applies to your store, and a filled-in graph is not a compliance statement. The payment script controls guide in this library covers the requirements themselves.

Callbacks, webhooks and the addresses that change orders

A gateway that learns the result of a payment after the customer has left the checkout needs a way back into the store.

WooCommerce's gateway guide says the best way to add a callback is with WC-API hooks, gives as its example the address PayPal Standard builds by adding the wc-api query argument to the site's home URL, and says WooCommerce calls the gateway's handler when that address is requested. The Stripe extension's webhook guide says Stripe communicates to the extension via webhooks, and that the extension only uses endpoints in the format https://www.example.com/?wc-api=wc_stripe.

Endpoints of any other kind in the Stripe dashboard, it says, likely come from other payment gateways or from third-party services that integrate with Stripe.

Inbound: what the gateways say their webhooks carry

The Stripe extension's order status guide says its automatic order status updates only work if webhooks are configured correctly, and its order information guide says the Stripe identifiers in order notes depend on having webhooks set up. PayPal Payments' settings guide says webhooks are registered automatically when the account is connected and that you can see the events the store is subscribed to.

Its documentation for the legacy settings interface calls webhooks essential, especially for Alternative Payment Methods, because the buyer's payment is captured only once a webhook confirmation arrives. Its orders guide says webhooks are what sync a refund made on paypal.com to the WooCommerce order.

While WooPayments is in Safe Mode, its Safe Mode page says, some features may not be available or will at least be unreliable, dispute and refund updates among them.

Outbound: WooCommerce's own webhooks

WooCommerce's webhooks guide describes webhooks as automatic event notifications sent to a URL of your choice, and says they can fire each time orders, products, coupons or customers are added, edited or deleted, when purchases are made, and more. Each webhook has a Secret used to generate a hash of the delivered webhook, which is included in the request headers; the guide says a blank Secret defaults to the current API user's consumer secret.

It says WooCommerce disables a webhook automatically after more than five consecutive delivery failures, a threshold the woocommerce_max_webhook_delivery_failures filter can raise or lower, and that it saves logs of all events that trigger a webhook at WooCommerce > Status > Logs, where they can be filtered by the webhooks-delivery source.

On this page's reading, each outbound webhook sends store data to another system, and the graph treats its delivery log as a place that may hold that data too. Rows 5 and 6 record the endpoints in each direction and the business that owns each one. What a receiving endpoint should check before it trusts a delivery is the subject of the Stripe webhook security guide in this library.

Order statuses: what moves an order, and what moves with it

WooCommerce's order status guide lists Draft, Pending payment, Processing, Completed, On hold, Failed, Cancelled and Refunded, and several of them carry stock with them.

Processing means payment has been received and the stock has been reduced. On hold means stock is reduced but payment still needs confirming, and the guide says that where a customer paid with a delayed notification method such as SEPA Direct Debit, the order may move on from On hold automatically once the payment clears, depending on the gateway.

If stock was previously reduced, it is returned to inventory when an order moves to Failed.

When an order is Cancelled, stock is returned if inventory management is enabled. The guide says gateways, extensions and status changes made by staff can produce other paths than its example flow.

For gateway developers, WooCommerce's gateway guide says that when payment is complete the gateway should call payment_complete(), after which WooCommerce uses either Completed or Processing and handles stock, and that it should be called only after the payment provider confirms the payment.

It also says to check that the amount paid matches the order total first, because a merchant can change the total of an unpaid order, and to set the order to On-Hold for review if they differ. The Stripe extension's order information guide describes a check of its own: before marking an order as paid it checks that the Stripe payment matches the order, and when it does not, it sets the order to On Hold and adds a note instead.

The single order page guide says system notes are added automatically by WooCommerce or extensions for events such as status changes, payment results and webhook callbacks, and are not visible to the customer. On this page's reading, the notes on a test order are where to look for which node moved it and when.

Status changes send email as well: WooCommerce's email settings guide lists, among others, a New order email to your chosen recipients, a Cancelled order email when an order is cancelled from Pending payment, Processing or On hold, Failed order notifications to the store and the customer, and Processing and Refunded order emails to the customer.

Coupons, refunds and stock restoration

Coupons, refunds and stock settings decide whether money and stock add up after an order goes through.

Each is set on the store. The staging run records a coupon in rows 18 and 19, a refund in row 20, and stock in rows 18 and 20 to 22.

Coupons

WooCommerce's coupon guide says an administrator or shop manager account is needed to manage coupons, and describes its usage limits as "Usage limit per coupon", across all customers; "Limit usage to X items"; and "Usage limit per user", after which the coupon becomes invalid for that customer. Its Allowed Emails restriction is verified against the customer's billing email.

Where coupons are applied or removed on an order, the single order page guide says WooCommerce tracks coupon usage counts and that coupons affect only unpaid orders. The Store API lists cart endpoints for applying and removing coupons, and its documentation says it is an unauthenticated API with cookie-based customer sessions.

To verify a coupon before sharing the code, the coupon guide says to apply it to an eligible cart, check the discount and total, and test a cart outside any spend, product or customer restrictions to confirm it is rejected there.

Row 18 of the staging run applies a test coupon to an eligible cart, and row 19 tries it a second time once its per-user limit is used up; the run does not test the spend, product or customer restrictions.

Refunds

WooCommerce's refunds guide describes automatic refunds, which return the customer's money through the payment method used and need a compatible gateway, and refunds that only record the order as refunded in WooCommerce, with the money returned to the customer outside it.

It says directly changing an order's status to Cancelled or Refunded will not automatically refund the customer. When a refund goes through the payment method used, it says the payment gateway usually adds an order note, and to look in the order notes for a "Successfully refunded" message to verify the refund.

A refund can restock products by ticking the "Restock refunded items" box, and when less than the full order value is refunded, the status does not change to Refunded and the shopper's email refers to a "partial refund".

The Stripe extension's documentation says it can refund orders from inside the WooCommerce interface, and PayPal Payments' orders guide describes refunding from the order screen with Refund via PayPal.

Stock held for unpaid orders

WooCommerce's products settings guide puts the inventory settings at WooCommerce > Settings > Products > Inventory. With "Hold Stock (minutes)" set, it says, the pending order is cancelled when the limit is reached and the held stock released back to available inventory, and the setting applies only to orders in the "Pending payment" status, and not orders that are "On hold".

WooCommerce's gateway guide gives the hold stock time as 60 minutes by default when stock management is on.

What happens when many requests reach a stock or coupon limit at the same moment is the subject of the race conditions guide in this library. The staging run here sends one request at a time.

Running the order, coupon, refund and stock evidence on staging

WooCommerce's testing guide sets out why test orders need care.

It says test orders can trigger order emails and appear in analytics, that WooCommerce shows no visual difference or special status for them, and that other extensions, plugins or services may be unable to tell test orders from real ones.

It suggests reviewing how each integration handles test scenarios, possibly disabling specific integrations first, deleting the test orders afterwards, and performing testing exclusively on a staging site. WooCommerce's update guide describes a staging site as a copy of the live site, created through the hosting provider or by restoring a backup to a separate WordPress installation, and says the store's database holds its products, orders, posts, pages and settings.

On this page's reading, a copy made that way can hold the same orders and settings as the live store, and the run treats it as also holding the live store's customers, webhooks and integration connections until rows 15 and 16 show otherwise. That is why the run opens by reading what the copy can reach, in those two rows, before any order is placed.

Stripe, PayPal Payments and WooPayments each describe their test or sandbox mode in their own documentation. The Stripe extension's testing guide describes an Enable test mode option in the General section, test purchases with Stripe test cards, including cards for successful payments and declines, and, after a successful test payment, a linked Charge ID on the order that opens its details in the Stripe dashboard.

The same guide says Apple Pay is tested with your real card information while in test mode. The graph never uses a real card, so express checkout buttons stay out of the run.

PayPal Payments' onboarding guide recommends a PayPal Sandbox account for testing and describes creating a second sandbox account to act as the buyer. WooPayments' test accounts page says a site in development mode keeps payments in test mode even if a real account is connected, and that WP_ENVIRONMENT_TYPE set to staging is one of the conditions that turns it on.

Its Safe Mode page names a clone from production to staging as one of the address changes that turn Safe Mode on.

The Stripe extension's webhook guide says that when the saved webhook points at another site's URL, as on a staging copy of the store, the extension skips the webhook changes it otherwise makes at each update.

The run is capped. It makes at most three checkout submissions and one coupon reuse attempt in a cart, as one invented test customer whose email address is an inbox the business controls, and staff then issue one partial refund and make one status change on those test orders.

Requests go one at a time, with no repeats and no load. If a gateway on the copy shows live mode, or any connection on the copy points at a live account, stop: switching a mode or disconnecting an integration is a change for whoever manages the copy, not a step in this worksheet.

WooCommerce security best practices from the vendor's own guides

These come from the WooCommerce and gateway pages cited above, each kept to what its page says.

Each one names the graph rows that relate to it, apart from the first, which is about how you update rather than a setting to read.

  • Update sooner than your regular schedule when a release includes a security fix, check the WooCommerce Advisories page and changelog for that flag, and, after a current backup, test updates on a staging site whenever possible, as WooCommerce's update guide says.
  • Match each REST API key to what its integration needs. WooCommerce's REST API guide says keys can be created with different permission levels depending on what the connected application needs, choosing from Read, Write and Read/Write, and its developer documentation says use of a key conforms to the linked user's WordPress roles and capabilities. Row 7 records each key.
  • Before sharing a coupon code, apply it to an eligible cart, check the discount and total, and test a cart outside any spend, product or customer restrictions to confirm it is rejected there, as the coupon guide says. Row 10 records each coupon's limits and restrictions, and rows 18 and 19 apply a test coupon on staging.
  • Use automatic refunds where the gateway supports them, which the refunds guide calls preferred, and check for the "Successfully refunded" message. The same guide says changing a status to Cancelled or Refunded does not automatically refund the customer. Rows 9 and 20 record refunds, and row 22 a cancellation.
  • Treat Stripe's Enable test mode as a setting for testing: the extension's settings guide says that unless you are testing payments, refunds, disputes or other such processes, it should likely be disabled. Row 12 records the mode on the live store.
  • Place test orders on a staging site only, with the gateway's sandbox or testing mode active where it offers one, and delete them afterwards, as the testing guide says. Rows 15 to 23 are that run.

How to fill in the dependency graph

The graph is for the store owner, an office manager with WooCommerce access, and the developer or agency who looks after the store.

Start a separate spreadsheet for each store and paste the table into it.

  • Fill in row 1 first, then add one column per node: each gateway and each plugin that changes the cart or checkout. Rows 2 to 14 then get an answer in each node's column wherever the row applies to that node, so an empty cell shows something nobody has traced yet.
  • Rows 1 to 14 read the live store. Row 3 also loads pages of your own store, and its checkout page load happens on the staging copy with one product in the cart. Apart from that one cart on the copy, nothing in those rows saves a setting or writes a record, and none of them places an order.
  • Leave every screen without saving. Several of the screens read here, or one click from them, hold actions that change the store, among them Enable on the Payments settings, Save webhook, Generate API Key, Reconfigure webhooks in the Stripe settings, and Resubscribe and Disconnect in PayPal Payments.
  • Never write a key, consumer secret, webhook secret or password into the graph. Where a screen, log or file can hold one, record only whether it is present. WooCommerce's REST API guide says the Consumer Secret is shown only once, when a key is generated, and the graph never generates one.
  • Treat logs and webhook deliveries as if they hold customer details: record which sources exist, the oldest date shown and who can read them, never their contents.
  • Rows 15 to 23 run in order on a staging copy, within the limits the rows state, and row 23 then has the owner of any other system that received a test record remove it. Rows 24 and 25 are the PCI DSS references, read against the script and header answers from row 3.
  • Fill the graph in again when a gateway or checkout plugin is added, removed or updated, when the theme changes, when an integration is connected, and when the agency or host changes.

What a review of your own store cannot show

The graph records configuration on the day it is read and the behaviour of one staging run.

It cannot show these:

  • Whether the live store behaves like the copy. The Stripe extension and WooPayments pages cited above each describe behaviour that changes on a staging copy, and the copy may carry different plugins or settings.
  • What a gateway does with a payment on its own servers, or what a receiving system does with a webhook it accepts. The graph records what the store sends and who owns the receiver.
  • Whether one customer can open another customer's orders through the account pages or an API, or whether a changed request can alter a price the server should fix. Those questions take signed-in testing of the running store.
  • Whether a script on the checkout changed after you read it, or what ran there last month.
  • Whether the store has already been compromised. That is incident response work; for the first hour after a compromise, see the hacked website guide in this library.

Your host's and your gateways' terms come first

This page makes no statement about what a hosting provider or a payment gateway permits.

WooCommerce runs on the hosting your WordPress site uses, so read your host's terms before any active test of the store, and read each gateway's own terms before relying on its test or sandbox mode. Where the terms leave doubt, get the answer in writing first.

The staging run on this page places its orders on a copy you control, with each gateway in the test or sandbox mode its own documentation describes, and row 23 has the owner of any other system that received a test record remove it.

Where a Clever Ops WordPress security audit picks up

The Clever Ops WordPress security audit covers WooCommerce stores, and on a store it adds customer accounts, orders and checkout pages to the WordPress scope.

The Customer and Shop Manager roles that WooCommerce adds are tested in the same way as the site's other roles. With two customer accounts, the audit checks whether either can open the other's orders, addresses or downloads, and with a shop manager account it checks whether the role can reach plugins, themes or administrator accounts.

Checkout testing is a separate pass, either on a staging copy or with the gateway switched to its test mode. In the cart and checkout requests the audit alters prices, quantities and coupon codes, checks that an order is marked paid only after the payment provider has confirmed the payment, and lists each script the checkout page loads.

It leaves the payment provider's hosted pages and platform untested, and its report is not a PCI DSS assessment. Clever Ops is not a PCI Approved Scanning Vendor or a Qualified Security Assessor, so a store that needs a PCI DSS external scan or an assessment should choose a provider from the PCI Security Standards Council's published list for that role.

If the store was built or is hosted by Clever Ops, the same work runs as a security review instead of an independent audit, and its report names the builder of the store and whoever runs its hosting. Malware cleanup and emergency response fall outside the service.

Frequently asked questions

The WooCommerce pages read for this guide give no yes or no, and neither does this guide. The payment options guide says the customer information collected at checkout depends on the payment gateway. The Stripe extension's documentation says card data is collected by an interface hosted on Stripe's servers, WooPayments' documentation says its hosted payment fields are served from its payment partner's environment, and the update guide says to update sooner than a regular schedule when a release includes a security fix. Gateways, API keys, webhooks, coupons, stock settings and checkout scripts are set on each store, and the dependency graph on this page records them.

WooCommerce's update guide points to the WooCommerce Advisories page for security notices and to the changelog, and says both flag whether a given release includes a security fix. WooCommerce's gateway guide says gateways can be added through traditional plugins, so read each gateway plugin's version from the Active Plugins section of WooCommerce > Status, which the System Status report guide says shows current version numbers. This library's plugin register has pages for WooCommerce, WooPayments, the Stripe gateway and PayPal Payments.

Stripe, PayPal Payments and WooPayments each document a test or sandbox mode, and WooCommerce's testing guide says to test exclusively on a staging site. The Stripe extension has an Enable test mode option and Stripe test cards, including cards for declines. Its guide says Apple Pay is tested with real card information, so this page leaves express buttons out of the run. PayPal Payments' onboarding guide recommends a PayPal Sandbox account, and WooPayments' test accounts page says a site in development mode, such as one with WP_ENVIRONMENT_TYPE set to staging, keeps payments in test mode.

Cancelling can return stock, and it does not refund the customer automatically, according to WooCommerce's guides. The order status guide says stock for a Cancelled order is returned to inventory if inventory management is enabled, and that a cancelled order may need to be refunded. The refunds guide says directly changing an order's status to Cancelled or Refunded will not automatically refund the customer, and says to complete its refund process instead. The products settings guide adds that with "Hold Stock (minutes)" set, unpaid orders in the "Pending payment" status are cancelled when the time limit is reached.

This page does not say. The PCI Security Standards Council's March 2025 post on payment page security says PCI DSS v4.x includes both requirements and that they focus on ensuring that payment page scripts are properly authorised, checked for integrity and monitored for tampering, and also address the need for careful management of both scripts and security-impacting HTTP headers. It says the Council does not enforce compliance or determine whether specific implementations are compliant, and that entities should collaborate with the organisations managing their compliance programmes, such as acquirers or payment brands, to understand any specific compliance validation and reporting responsibilities. The graph's script rows are a record you can take to them.

WooCommerce's developer documentation says the Store API provides public endpoints for customer-facing cart, checkout and product functionality, needs no API keys or authentication tokens, and returns data belonging to the current customer, whose session is cookie-based. It says the Store API cannot look up other customers and orders by ID and cannot write store data such as settings. Its checkout endpoints, which create orders from the cart and handle payments, require a Nonce Token or a Cart Token.

Scope the right test for your application

Tell us what you have built, who uses it and when it needs to launch. You will get a plain-English recommendation: a website audit, a web application test or a referral to a specialist.