Skip to main content
Platform security guideReviewed

Is Shopify safe? What Shopify says it secures, and what the store owner sets

Shopify runs the platform.

Who signs in to the admin, which apps are installed and which scopes they were approved for, which theme and pixels are added, where exports go and how a flagged order is handled are set or decided in each store. This guide sets out what Shopify's own terms and documentation say about both, then gives you a worksheet for your own store and a checklist for a synthetic test order placed without a real card.

Shopify shared-responsibility worksheet and test-order checklist

Keep a separate spreadsheet copy of this table for each store. Rows 1 to 12 set what Shopify's own pages say beside what is set or decided in your store: read or ask where the fourth column points, without changing anything, and write down what the fifth column asks for.

How to use it

Rows 13 to 17 are a synthetic test-order checklist that runs on a dev store you own, never the live store, with at most three checkout attempts, invented customer details, an inbox the business controls and a test payment method Shopify documents, never a real card. Never write a password, token, client secret or customer record into the worksheet. The second column was checked against the Shopify pages cited on this page on 14 November 2026.

17 rows

Shopify shared-responsibility worksheet and test-order checklist

AreaWhat Shopify's pages sayWhat is set or decided in the storeWhere to look (read only)What to write down
1. Store Owner and sign-inTerms of Service, sections 1 and 2.1: a store has one Store Owner; the account holder is responsible for keeping their password secure, and Shopify says it will not be liable for loss from a failure to maintain the account's security. Domains page: lists turning on two-step authentication for the Shopify account among the things to check. AccountType reference: a SAML account can be signed into via a SAML provider.Who the Store Owner is, which mailbox receives the primary email address (the terms say it must be monitored), and how each person signs in.The store's owner and primary email address. Ask each person with an account whether two-step authentication is on, or whether they sign in through a SAML provider.Store Owner (person or business), the primary email mailbox and who reads it, and for each account whether a second sign-in step is on. Never a code, recovery key or password.
2. Staff accounts and permissionsTerms of Service, section 2.2: staff accounts depend on the plan, each needs a full legal name and a valid email account, and the Store Owner can set permissions and is responsible for staff complying with the terms. User resource: merchants give each staff member individual permissions from the Shopify admin.Who has an account and which permissions each person holds.The store's staff list and each person's permissions. Mark anyone who can authorise app installs, view or export customers, export orders, view, update and publish themes, manage domains, add, update, deactivate or delete staff, or view admin browser sessions.Name, role, each marked permission held, whether the person still needs it, and the date read.
3. Collaborator accounts and requestsAccountType reference: a collaborator account is the account of a partner who collaborates with the merchant, and a requested account is a collaborator request the admin has not yet accepted. Custom app guide: the store owner can change staff or collaborator permissions in the Shopify admin.Which partners hold collaborator accounts, with which permissions, and what happens to pending requests.The store's list of collaborator accounts and any pending collaborator requests.Partner business, the person or team behind each account, permissions held, the project it was for and whether that project has ended, and each request still waiting for a decision.
4. Installed apps and access scopesAccess scopes guide: scopes control which store data an app can read and write, a write scope also grants read, for a new app merchants approve scopes at install, and Shopify restricts scopes for apps without a legitimate use for the data. Protected customer data page: public apps need a review for protected customer data, apart from apps installed only on development stores, and unapproved fields are redacted. API terms, section 6: access comes through the consent screen at install or private API credentials, and the developer will delete merchant data within 30 days of uninstall except where applicable law prohibits or varies that.Which apps are installed, who approved each one, and whether each is still used.Each installed app's developer, what the app is allowed to access as the store shows it, and the merchant agreement and privacy policy the API terms say the developer presents.App, developer, who installed it and when, its access in words (customers, orders, themes, script tags, pixels), whether it receives customer name, address, phone or email, and the date read.
5. Admin-created custom appsCustom app guide: new ones can no longer be created and existing ones keep working; the access token is shown only once; changing an app's access needs the "Manage and install apps and channels" and "Develop apps" permissions plus the permissions for the resource; the key and secret cannot be rotated, and a new token comes from uninstalling and reinstalling, which disrupts requests and webhooks.Who holds "Develop apps", which custom apps exist, and where each app's token is kept outside Shopify.The custom app list, which the guide places under Apps, then "Develop apps". Read each app's name and access. Do not reveal or copy a token.App name, purpose, owner, access, the system its token is stored in (by name) and who can read that system. Never the token. Reinstalling to get a new token is a change for the app's owner, not part of this review.
6. Theme code and script tagsUser resource: the themes permission lets a staff member view, update and publish themes. Access scopes guide: read_themes and write_themes cover OnlineStoreTheme, and read_script_tags and write_script_tags cover ScriptTag. Theme app extensions page: apps built that way do not edit theme code. ScriptTag reference: a script tag is remote JavaScript code loaded into storefront pages or the Order status page of checkout, and script tags can only be used with vintage themes.Which people and apps can change the theme's files, and what third-party code the theme loads.Staff holding the themes permission (row 2), apps holding theme or script tag access (row 4), and the published theme's code, read with whoever maintains it.Theme name, who maintains it, each external script host the theme loads and the app or person it came from, and any code left by an app that is no longer installed.
7. PixelsWeb pixels page: app pixels load in a strict sandbox built on web workers, where fetch can make HTTP requests to arbitrary endpoints, each of which must explicitly support CORS; custom pixels load in a lax sandbox iframe, and pixels placed in it cannot access the top frame; app pixels honour the customer's consent signals. Access scopes guide: read_pixels, write_pixels and read_customer_events are listed against the WebPixel and ServerPixel objects; creating or updating a pixel needs write_pixels and read_customer_events together, and server pixels also need read_server_pixels and write_server_pixels, which Shopify grants on approval. Web Pixels API reference: custom pixels are configured in the pixel manager interface in the Shopify admin, and a pixel's init data includes the Cart and Customer objects.Which custom pixels exist and who added them, and which app pixels are connected.The pixel manager interface in the Shopify admin, where the Web Pixels API reference says custom pixels are configured. For each custom pixel, read its code for the hosts it sends data to and the customer fields it reads. For app pixels, the apps in row 4 that hold pixel access.Pixel name, custom or app, who added it, destination hosts, for a custom pixel the customer fields its code reads (names only), and the date read. Do not edit, disconnect or save a pixel during the review.
8. Customer data and exportsData Processing Addendum: the merchant is the data controller and Shopify the data processor for the store's customer personal data, for Services that rely on Shopify processing it, except for the Appendix E services; Shopify will implement and maintain technical and organisational measures designed to protect that data and, as applicable data protection laws require, give notice upon confirming a personal data breach. User resource: separate permissions to export customers, orders, draft orders and gift cards.Who can export customer and order data, and what happens to each exported file.Staff holding export permissions (row 2). Ask each of them where exported files are saved, shared and deleted.Who can export what, where the files are kept and for how long, and who else can open that location. Record only that customer data is present there, never the data.
9. WebhooksVerifying deliveries page: each HTTPS delivery carries an HMAC signature in X-Shopify-Hmac-SHA256, made with the app's client secret and the raw body, to verify before processing; X-Shopify-Webhook-Id helps skip duplicates; for HTTPS delivery, Shopify retries 8 times over 4 hours and, after 8 consecutive failures, deletes a subscription configured using the Admin API. Protected customer data page: webhooks that relate to a single customer or order are protected customer data.Which servers the store's apps and developers have set to receive events, and what each does with the payload.A list from your developers of each endpoint and topic, and their answer, with the code if they can show it, on whether the endpoint verifies the HMAC signature before processing.Endpoint host, topics, owner, HMAC verified (yes, no or unknown), where the client secret is stored by name, where payloads are logged, and who reads the app's emergency developer email. Never the secret.
10. Domains and DNSDomains page: a domain bought through Shopify connects automatically, gets SSL automatically, has registrar lock on by default and auto-renews by default; a domain at another registrar is connected with an A record for the root and a CNAME for www set to the values shown in the Shopify admin. User resource: the domains permission covers viewing, buying and managing domains.Where each domain is registered, who holds that login, and whether renewal is set.The store's domain list, and for a domain kept elsewhere, the DNS records wherever that domain's DNS is managed.Each domain and subdomain, registrar, auto-renew on or off, renewal date, who holds the registrar login, staff with the domains permission, and any DNS record pointing at Shopify for a name the store no longer uses.
11. Fraud review and chargebacksTerms of Service, section 4: fraudulent transactions are among the aspects of a sale the merchant is responsible for. Order reference: each order carries a risk assessment summary with fraud analysis and risk scoring. Shopify Protect page: cover for eligible fraud-based chargebacks on Shop Pay transactions through Shopify Payments applies to US stores only.Who reviews flagged orders, and what they check before fulfilling or cancelling one.The risk summary on recent orders, and the people and any fraud apps involved in deciding them.Reviewer, the checks used, where decisions are recorded, fraud apps installed with their access, and whether the store falls within Shopify Protect on its page's terms.
12. Card data and checkoutTerms of Service, section 12: where Shopify stores, processes or transmits "Account Data" on the merchant's behalf, Shopify acknowledges it is responsible for securing that data in line with PCI DSS as it applies; to the extent a merchant impairs its security, for example by bypassing technical limitations or using third-party proxies, Shopify is not responsible for its security. Section 4: the merchant agrees to use Shopify Checkout for online store sales.Anything that collects or relays card details outside Shopify Checkout, and the scripts on the order status page.Script tags and apps with access to orders or checkout (rows 4 and 6), and any payment page or proxy the business runs itself.Each place card details could be entered other than Shopify Checkout and who runs it, and each script on the order status page by host. The payment script controls guide covers what to do with that list.
13. Test order: where it runs, and its limitsDev stores page: dev stores are testing environments you own and control, always password protected and unable to process real transactions; the requirements for creating one include a Shopify Partner account or a merchant store with developer permissions. Shop Pay testing guide: while Shopify Payments test mode is on, no real payments are captured.Which dev store is used, and which of the live store's apps, pixels, webhook subscriptions and theme it carries.A dev store you own only, never the live store. At most three checkout attempts in all, counting any declined attempt. No load and no repeat runs. Before the run, confirm with each app's owner that no app on the dev store is connected to a live account that ships goods, takes payment or messages customers, and that no pixel on the dev store sends events to a live analytics or advertising account.Dev store name, date, who ran it, and what it carries and lacks compared with the live store.
14. Test order: synthetic customer and paymentDev stores page: orders can be tested using Shopify's Test payment gateway or by activating test mode for the payment provider. Order reference: test orders are made using the Shopify Bogus Gateway or a payment provider with test mode enabled. Shop Pay testing guide: lists Shopify Payments test card numbers, including a test card number that simulates a generic declined card.An invented customer name carrying a marker such as SHOPTEST-1114, and an email address and phone number the business controls.Check out on the dev store with the Test payment gateway or the payment provider's test mode, as the dev stores page names them. With Shopify Payments in test mode, use a test card number from the Shop Pay testing guide's list. Never a real card.The payment method as the page names it, the test card's brand (not its number), the marker, and the time of each attempt.
15. Test order: the order recordOrder reference: a test field records whether the order is a test, and a test order cannot be converted into a real order or the other way round; a risk assessment summary provides fraud analysis and risk scoring.How the store's staff would see this order.The test order as the dev store's admin shows it.Whether the order shows as a test, what the risk summary says, which customer fields were stored, and which staff accounts can see it.
16. Test order: what left the storeVerifying deliveries page: each HTTPS delivery carries an HMAC signature in the X-Shopify-Hmac-SHA256 header, and the X-Shopify-Webhook-Id header can be used to detect duplicates. Web pixels page: a pixel can subscribe to customer events published as a customer browses. The dev stores page and the Shop Pay testing guide do not say whether a test order sends notifications.Which emails, webhook deliveries, pixel requests and app records the order produced.The controlled inbox; each endpoint's own log; the browser's developer tools network panel during checkout, noting host names only; and each app on the dev store that shows orders.Each email (sender and subject), each endpoint that logged a delivery with its topic and whether the HMAC check passed, each host the browser sent requests to, and each app holding a copy of the order.
17. Test order: clean-upOrder reference: a test order cannot be converted into a real order. Dev stores page: deleting a dev store is permanent, and its data is purged and cannot be restored.What the test created outside the dev store, and who removes it.Each app, inbox, endpoint log and analytics tool that received the marker.Each record carrying the marker, where it lives, who removes it and the date. The record's owner deletes it in the system that holds it once the review is over.

Area

What Shopify's pages say

  1. 1. Store Owner and sign-in
    What Shopify's pages say
    Terms of Service, sections 1 and 2.1: a store has one Store Owner; the account holder is responsible for keeping their password secure, and Shopify says it will not be liable for loss from a failure to maintain the account's security. Domains page: lists turning on two-step authentication for the Shopify account among the things to check. AccountType reference: a SAML account can be signed into via a SAML provider.
    What is set or decided in the store
    Who the Store Owner is, which mailbox receives the primary email address (the terms say it must be monitored), and how each person signs in.
    Where to look (read only)
    The store's owner and primary email address. Ask each person with an account whether two-step authentication is on, or whether they sign in through a SAML provider.
    What to write down
    Store Owner (person or business), the primary email mailbox and who reads it, and for each account whether a second sign-in step is on. Never a code, recovery key or password.
  2. 2. Staff accounts and permissions
    What Shopify's pages say
    Terms of Service, section 2.2: staff accounts depend on the plan, each needs a full legal name and a valid email account, and the Store Owner can set permissions and is responsible for staff complying with the terms. User resource: merchants give each staff member individual permissions from the Shopify admin.
    What is set or decided in the store
    Who has an account and which permissions each person holds.
    Where to look (read only)
    The store's staff list and each person's permissions. Mark anyone who can authorise app installs, view or export customers, export orders, view, update and publish themes, manage domains, add, update, deactivate or delete staff, or view admin browser sessions.
    What to write down
    Name, role, each marked permission held, whether the person still needs it, and the date read.
  3. 3. Collaborator accounts and requests
    What Shopify's pages say
    AccountType reference: a collaborator account is the account of a partner who collaborates with the merchant, and a requested account is a collaborator request the admin has not yet accepted. Custom app guide: the store owner can change staff or collaborator permissions in the Shopify admin.
    What is set or decided in the store
    Which partners hold collaborator accounts, with which permissions, and what happens to pending requests.
    Where to look (read only)
    The store's list of collaborator accounts and any pending collaborator requests.
    What to write down
    Partner business, the person or team behind each account, permissions held, the project it was for and whether that project has ended, and each request still waiting for a decision.
  4. 4. Installed apps and access scopes
    What Shopify's pages say
    Access scopes guide: scopes control which store data an app can read and write, a write scope also grants read, for a new app merchants approve scopes at install, and Shopify restricts scopes for apps without a legitimate use for the data. Protected customer data page: public apps need a review for protected customer data, apart from apps installed only on development stores, and unapproved fields are redacted. API terms, section 6: access comes through the consent screen at install or private API credentials, and the developer will delete merchant data within 30 days of uninstall except where applicable law prohibits or varies that.
    What is set or decided in the store
    Which apps are installed, who approved each one, and whether each is still used.
    Where to look (read only)
    Each installed app's developer, what the app is allowed to access as the store shows it, and the merchant agreement and privacy policy the API terms say the developer presents.
    What to write down
    App, developer, who installed it and when, its access in words (customers, orders, themes, script tags, pixels), whether it receives customer name, address, phone or email, and the date read.
  5. 5. Admin-created custom apps
    What Shopify's pages say
    Custom app guide: new ones can no longer be created and existing ones keep working; the access token is shown only once; changing an app's access needs the "Manage and install apps and channels" and "Develop apps" permissions plus the permissions for the resource; the key and secret cannot be rotated, and a new token comes from uninstalling and reinstalling, which disrupts requests and webhooks.
    What is set or decided in the store
    Who holds "Develop apps", which custom apps exist, and where each app's token is kept outside Shopify.
    Where to look (read only)
    The custom app list, which the guide places under Apps, then "Develop apps". Read each app's name and access. Do not reveal or copy a token.
    What to write down
    App name, purpose, owner, access, the system its token is stored in (by name) and who can read that system. Never the token. Reinstalling to get a new token is a change for the app's owner, not part of this review.
  6. 6. Theme code and script tags
    What Shopify's pages say
    User resource: the themes permission lets a staff member view, update and publish themes. Access scopes guide: read_themes and write_themes cover OnlineStoreTheme, and read_script_tags and write_script_tags cover ScriptTag. Theme app extensions page: apps built that way do not edit theme code. ScriptTag reference: a script tag is remote JavaScript code loaded into storefront pages or the Order status page of checkout, and script tags can only be used with vintage themes.
    What is set or decided in the store
    Which people and apps can change the theme's files, and what third-party code the theme loads.
    Where to look (read only)
    Staff holding the themes permission (row 2), apps holding theme or script tag access (row 4), and the published theme's code, read with whoever maintains it.
    What to write down
    Theme name, who maintains it, each external script host the theme loads and the app or person it came from, and any code left by an app that is no longer installed.
  7. 7. Pixels
    What Shopify's pages say
    Web pixels page: app pixels load in a strict sandbox built on web workers, where fetch can make HTTP requests to arbitrary endpoints, each of which must explicitly support CORS; custom pixels load in a lax sandbox iframe, and pixels placed in it cannot access the top frame; app pixels honour the customer's consent signals. Access scopes guide: read_pixels, write_pixels and read_customer_events are listed against the WebPixel and ServerPixel objects; creating or updating a pixel needs write_pixels and read_customer_events together, and server pixels also need read_server_pixels and write_server_pixels, which Shopify grants on approval. Web Pixels API reference: custom pixels are configured in the pixel manager interface in the Shopify admin, and a pixel's init data includes the Cart and Customer objects.
    What is set or decided in the store
    Which custom pixels exist and who added them, and which app pixels are connected.
    Where to look (read only)
    The pixel manager interface in the Shopify admin, where the Web Pixels API reference says custom pixels are configured. For each custom pixel, read its code for the hosts it sends data to and the customer fields it reads. For app pixels, the apps in row 4 that hold pixel access.
    What to write down
    Pixel name, custom or app, who added it, destination hosts, for a custom pixel the customer fields its code reads (names only), and the date read. Do not edit, disconnect or save a pixel during the review.
  8. 8. Customer data and exports
    What Shopify's pages say
    Data Processing Addendum: the merchant is the data controller and Shopify the data processor for the store's customer personal data, for Services that rely on Shopify processing it, except for the Appendix E services; Shopify will implement and maintain technical and organisational measures designed to protect that data and, as applicable data protection laws require, give notice upon confirming a personal data breach. User resource: separate permissions to export customers, orders, draft orders and gift cards.
    What is set or decided in the store
    Who can export customer and order data, and what happens to each exported file.
    Where to look (read only)
    Staff holding export permissions (row 2). Ask each of them where exported files are saved, shared and deleted.
    What to write down
    Who can export what, where the files are kept and for how long, and who else can open that location. Record only that customer data is present there, never the data.
  9. 9. Webhooks
    What Shopify's pages say
    Verifying deliveries page: each HTTPS delivery carries an HMAC signature in X-Shopify-Hmac-SHA256, made with the app's client secret and the raw body, to verify before processing; X-Shopify-Webhook-Id helps skip duplicates; for HTTPS delivery, Shopify retries 8 times over 4 hours and, after 8 consecutive failures, deletes a subscription configured using the Admin API. Protected customer data page: webhooks that relate to a single customer or order are protected customer data.
    What is set or decided in the store
    Which servers the store's apps and developers have set to receive events, and what each does with the payload.
    Where to look (read only)
    A list from your developers of each endpoint and topic, and their answer, with the code if they can show it, on whether the endpoint verifies the HMAC signature before processing.
    What to write down
    Endpoint host, topics, owner, HMAC verified (yes, no or unknown), where the client secret is stored by name, where payloads are logged, and who reads the app's emergency developer email. Never the secret.
  10. 10. Domains and DNS
    What Shopify's pages say
    Domains page: a domain bought through Shopify connects automatically, gets SSL automatically, has registrar lock on by default and auto-renews by default; a domain at another registrar is connected with an A record for the root and a CNAME for www set to the values shown in the Shopify admin. User resource: the domains permission covers viewing, buying and managing domains.
    What is set or decided in the store
    Where each domain is registered, who holds that login, and whether renewal is set.
    Where to look (read only)
    The store's domain list, and for a domain kept elsewhere, the DNS records wherever that domain's DNS is managed.
    What to write down
    Each domain and subdomain, registrar, auto-renew on or off, renewal date, who holds the registrar login, staff with the domains permission, and any DNS record pointing at Shopify for a name the store no longer uses.
  11. 11. Fraud review and chargebacks
    What Shopify's pages say
    Terms of Service, section 4: fraudulent transactions are among the aspects of a sale the merchant is responsible for. Order reference: each order carries a risk assessment summary with fraud analysis and risk scoring. Shopify Protect page: cover for eligible fraud-based chargebacks on Shop Pay transactions through Shopify Payments applies to US stores only.
    What is set or decided in the store
    Who reviews flagged orders, and what they check before fulfilling or cancelling one.
    Where to look (read only)
    The risk summary on recent orders, and the people and any fraud apps involved in deciding them.
    What to write down
    Reviewer, the checks used, where decisions are recorded, fraud apps installed with their access, and whether the store falls within Shopify Protect on its page's terms.
  12. 12. Card data and checkout
    What Shopify's pages say
    Terms of Service, section 12: where Shopify stores, processes or transmits "Account Data" on the merchant's behalf, Shopify acknowledges it is responsible for securing that data in line with PCI DSS as it applies; to the extent a merchant impairs its security, for example by bypassing technical limitations or using third-party proxies, Shopify is not responsible for its security. Section 4: the merchant agrees to use Shopify Checkout for online store sales.
    What is set or decided in the store
    Anything that collects or relays card details outside Shopify Checkout, and the scripts on the order status page.
    Where to look (read only)
    Script tags and apps with access to orders or checkout (rows 4 and 6), and any payment page or proxy the business runs itself.
    What to write down
    Each place card details could be entered other than Shopify Checkout and who runs it, and each script on the order status page by host. The payment script controls guide covers what to do with that list.
  13. 13. Test order: where it runs, and its limits
    What Shopify's pages say
    Dev stores page: dev stores are testing environments you own and control, always password protected and unable to process real transactions; the requirements for creating one include a Shopify Partner account or a merchant store with developer permissions. Shop Pay testing guide: while Shopify Payments test mode is on, no real payments are captured.
    What is set or decided in the store
    Which dev store is used, and which of the live store's apps, pixels, webhook subscriptions and theme it carries.
    Where to look (read only)
    A dev store you own only, never the live store. At most three checkout attempts in all, counting any declined attempt. No load and no repeat runs. Before the run, confirm with each app's owner that no app on the dev store is connected to a live account that ships goods, takes payment or messages customers, and that no pixel on the dev store sends events to a live analytics or advertising account.
    What to write down
    Dev store name, date, who ran it, and what it carries and lacks compared with the live store.
  14. 14. Test order: synthetic customer and payment
    What Shopify's pages say
    Dev stores page: orders can be tested using Shopify's Test payment gateway or by activating test mode for the payment provider. Order reference: test orders are made using the Shopify Bogus Gateway or a payment provider with test mode enabled. Shop Pay testing guide: lists Shopify Payments test card numbers, including a test card number that simulates a generic declined card.
    What is set or decided in the store
    An invented customer name carrying a marker such as SHOPTEST-1114, and an email address and phone number the business controls.
    Where to look (read only)
    Check out on the dev store with the Test payment gateway or the payment provider's test mode, as the dev stores page names them. With Shopify Payments in test mode, use a test card number from the Shop Pay testing guide's list. Never a real card.
    What to write down
    The payment method as the page names it, the test card's brand (not its number), the marker, and the time of each attempt.
  15. 15. Test order: the order record
    What Shopify's pages say
    Order reference: a test field records whether the order is a test, and a test order cannot be converted into a real order or the other way round; a risk assessment summary provides fraud analysis and risk scoring.
    What is set or decided in the store
    How the store's staff would see this order.
    Where to look (read only)
    The test order as the dev store's admin shows it.
    What to write down
    Whether the order shows as a test, what the risk summary says, which customer fields were stored, and which staff accounts can see it.
  16. 16. Test order: what left the store
    What Shopify's pages say
    Verifying deliveries page: each HTTPS delivery carries an HMAC signature in the X-Shopify-Hmac-SHA256 header, and the X-Shopify-Webhook-Id header can be used to detect duplicates. Web pixels page: a pixel can subscribe to customer events published as a customer browses. The dev stores page and the Shop Pay testing guide do not say whether a test order sends notifications.
    What is set or decided in the store
    Which emails, webhook deliveries, pixel requests and app records the order produced.
    Where to look (read only)
    The controlled inbox; each endpoint's own log; the browser's developer tools network panel during checkout, noting host names only; and each app on the dev store that shows orders.
    What to write down
    Each email (sender and subject), each endpoint that logged a delivery with its topic and whether the HMAC check passed, each host the browser sent requests to, and each app holding a copy of the order.
  17. 17. Test order: clean-up
    What Shopify's pages say
    Order reference: a test order cannot be converted into a real order. Dev stores page: deleting a dev store is permanent, and its data is purged and cannot be restored.
    What is set or decided in the store
    What the test created outside the dev store, and who removes it.
    Where to look (read only)
    Each app, inbox, endpoint log and analytics tool that received the marker.
    What to write down
    Each record carrying the marker, where it lives, who removes it and the date. The record's owner deletes it in the system that holds it once the review is over.

Is Shopify safe? Where Shopify's statements end and the store's settings begin

Shopify is a hosted commerce platform.

Its Terms of Service describe a platform that includes, among other features, tools for merchants to build and customise online stores, sell in several places, manage products, inventory, payments, fulfilment, shipping, business operations, marketing and advertising, and engage with existing and potential customers.

Its domains page says a merchant does not need to buy separate web hosting, because every Shopify plan comes with hosting. So an online store on that hosting needs no web server of the owner's own.

The Terms of Service also count an online store hosted on a third-party website, and a storefront built on the Storefront API, as a Store. The owner picks a theme, installs apps, gives people access and takes orders.

Section 4 of the Terms of Service is plain about who answers for what. It says the merchant is the seller or merchant of record for all sales, and is responsible for the creation and operation of the store, its materials, the goods and services sold, and all aspects of the transactions with its customers, which the section says includes fraudulent transactions.

It also says Shopify has no responsibility for the merchant's store, the goods or services sold, or any aspect of the transaction between the merchant and its customers.

Customer data follows a similar split. Shopify's Data Processing Addendum says the merchant acts as the data controller and Shopify as the data processor for the personal data of the store's customers, in connection with the merchant's use of Services that rely on Shopify processing that data, except for the services its Appendix E describes.

The same addendum says the merchant alone is responsible for working out its own legal and regulatory obligations, including whether the technical and organisational measures of the Services are consistent with them.

This page therefore does not answer "is Shopify safe" with a yes or a no. What Shopify provides is described in Shopify's own pages, and a store owner reads those statements as Shopify makes them. What is set or decided inside one store can be read and written down.

The sections below take each area in turn: what Shopify says it provides, what is set in the store, and which row of the worksheet records it.

What Shopify's own pages say it provides

Start with card data.

Section 12 of the Terms of Service says that where the Services involve Shopify storing, processing or transmitting "Account Data", as PCI DSS defines that term, on the merchant's behalf, Shopify acknowledges that it is responsible for securing that data in line with PCI DSS as it applies.

The same section says the merchant agrees not to impair the security of Account Data, including by modifying, bypassing or circumventing the technical limitations of the Services or by using third-party proxies or other interventions that impair it, and that to the extent a merchant does so, Shopify is not responsible for the security of Account Data.

Section 4 adds that the merchant agrees to use Shopify Checkout for sales associated with its online store.

On audits and data handling, Shopify's security page says Shopify has been issued SOC 2 Type II and SOC 3 reports for the service it provides to its customers. The Data Processing Addendum says Shopify will implement and maintain appropriate technical and organisational measures designed to protect the personal data of the store's customers against unauthorised or unlawful processing and against accidental loss, destruction, damage, theft, alteration or disclosure, and that, as data protection laws require, Shopify will give the merchant notice upon confirming a personal data breach.

Shopify also limits what an app can ask for. Its access scopes guide says Shopify restricts access to scopes for apps that do not have a legitimate use for the associated data, and that for a new app, merchants approve the scopes when they install it.

For customer details, Shopify's protected customer data page says Shopify will approve an app to use that data if the requested data is the minimum the app needs to provide its functionality.

For a domain bought through Shopify, the domains page says SSL is issued automatically and registrar lock is enabled by default to help prevent unauthorised transfers.

This guide records each of these as a statement Shopify makes about its own systems. A store owner reads them; the worksheet does not ask anyone to verify them.

What Shopify's terms leave with the account holder

Section 1 of the Terms of Service makes the account holder responsible for keeping their password secure, and says Shopify cannot and will not be liable for loss or damage from a failure to maintain the security of the account and password.

It also says the account holder must monitor the primary email address given to Shopify. Section 4 says the merchant is solely responsible for the activity that occurs using its API credentials and for keeping them secure.

Section 2 sets up who is in charge. A store can be associated with only one Store Owner, and where someone signs up for their employer, the employer is the Store Owner. Depending on the pricing plan, the account can have one or more staff accounts, each with a full legal name and a valid email account, and the Store Owner can set permissions that decide the level of access staff accounts have to specific business information.

The Store Owner is responsible for making sure its employees, agents and subcontractors, including those working through staff accounts, comply with the Terms of Service, and for any breach by them.

The rest of this guide covers settings that the Store Owner, or someone the owner has given access, sets in the store: who holds an account and with which permissions, which apps are installed and what they may read, what code the theme loads, which pixels collect data, where exported customer files end up, which servers the store's apps and developers have set to receive its webhooks, how the domain is pointed and renewed, and who decides what happens to a flagged order. Each has a row in the worksheet.

Staff and collaborator accounts

Shopify's GraphQL Admin API reference lists the account types a staff member can have.

Among them are regular accounts, which can access the Shopify admin; collaborator accounts, each described as the account of a partner who collaborates with the merchant; collaborator team member accounts; restricted accounts, which cannot access the admin; and SAML accounts, which can be signed into through a SAML provider. A requested account is one where the admin has not yet accepted the request to create a collaborator account.

Permissions are set person by person. Shopify's REST Admin API reference for the User resource says that, from the Shopify admin, merchants can give each staff member individual permissions that control access to a part of Shopify, and it lists the permissions a staff account can hold.

Several of them bear directly on security: authorising the installation of applications; viewing, creating, editing and deleting customers; exporting customers and exporting orders; viewing, updating and publishing themes; viewing, buying and managing domains; adding, updating, activating, deactivating and deleting staff; and viewing Shopify admin browser sessions.

Other Shopify pages do not always use the API reference's names. Shopify's guide to admin-created custom apps, for example, names permissions such as "Manage and install apps and channels" and "Develop apps".

That same guide shows how far a collaborator can reach. It says anyone with a staff or collaborator account can change what an admin-created custom app can access, provided they hold the "Manage and install apps and channels" permission, the "Develop apps" permission and the permissions for the resource being changed, and that the store owner can change staff or collaborator permissions in the Shopify admin.

The pages cited here do not say whether a collaborator account's access ends when a project does, so the worksheet lists each one with the project it was for and whether that project has ended.

Sign-in is the other half of access. Shopify's domains page lists turning on two-step authentication for the Shopify account among the things to check for domain privacy and security, and the AccountType reference describes a SAML account as one that can be signed into via a SAML provider. The worksheet records, for each person, whether a second sign-in step is on, never a code or a recovery key.

When someone leaves, this page suggests reading their account before anything changes: the permissions it held, whether it could export customers or authorise app installs, and which admin-created custom apps it could edit. Changing or removing the account is a separate step: the custom app guide says the store owner can change staff or collaborator permissions in the Shopify admin, and the User resource lists permissions to deactivate and to delete staff.

Shopify app security: scopes, customer data and what an app keeps

An app reaches a store's data through access scopes.

Shopify's access scopes guide says scopes control which store data an app can read and write, asks developers to request only the data their app needs to function, and notes that any scope that writes a resource also grants read access to it.

For the worksheet, note these pairs: read_customers and write_customers cover the Customer object, read_themes and write_themes cover OnlineStoreTheme, and read_script_tags and write_script_tags cover ScriptTag, which the theme code section below describes.

Order access has a time limit by default: the scopes guide says read_orders and write_orders cover orders created within the last 60 days, and read_all_orders extends either one to older orders.

Installation is the moment of consent. Section 6 of the Shopify API License and Terms of Use says that before a developer accesses a merchant's store or its data, the merchant must grant access through a consent screen Shopify provides when the app is installed, or through the merchant's private API credentials.

What was declared and what was granted can differ: the scopes guide says a scope takes effect only after it is approved on the store, and that optional scopes are granted separately, after installation.

Customer details carry an extra review for public apps. Shopify's protected customer data page sets out levels of access: level 0 for no customer data, level 1 for customer data excluding name, address, phone and email fields, and level 2 for customer data including name, address, phone or email fields.

A public app needs a review for level 1 or level 2, though the page says no request for review is needed for an app installed only on development stores.

A custom app has level 1 and level 2 always available, and an admin-created custom app has level 1 always available, with level 2 varying by plan. The page says responses include only approved fields, and unapproved fields are redacted.

After an app is removed, the API terms describe what the developer has agreed to. Section 6 says a developer that accesses merchant data will delete all originals, copies and reproductions of it within 30 days when the merchant uninstalls the app, except where applicable law prohibits or varies that, and will notify Shopify of an actual or suspected breach of merchant data immediately upon, and no later than 24 hours after, becoming aware of it.

For apps distributed through the Shopify App Store, Shopify's privacy law compliance page says Shopify sends a shop/redact webhook 48 hours after a store owner uninstalls the app, so the app can erase that store's data.

Section 7 of the API terms says the app is installed and run on the developer's server or another server, not on Shopify's servers.

The API terms also set what a developer tells the merchant. For public and custom apps, the developer presents a merchant agreement that informs merchants, among other things, that the developer is solely responsible for the app and that Shopify is not liable for any fault in the app or any harm that may result from its installation or use, along with a privacy policy describing the merchant data the app will access.

On this page's reading, each public or custom app on the store should come with a merchant agreement and privacy policy from its developer, and the worksheet asks you to read them.

Stores that have been running for a while may also hold admin-created custom apps. Shopify's guide says new ones can no longer be created and that existing ones are unaffected and continue to work. Their API access token is shown only once, when it is generated.

The guide says the API key and secret cannot be rotated, and describes getting a new access token by uninstalling and reinstalling the app, which disrupts the app's requests and webhooks until its code is updated.

That is a change to plan with the app's owner, not part of a review. How an app's install grant works in general is the subject of the OAuth and OpenID Connect guide in this library.

Theme code and the scripts that load on storefront pages

The theme sets the appearance of the online store, as section 9.6 of the Terms of Service describes it, so it matters who can change it.

The User resource lists a themes permission that lets a staff member view, update and publish themes, and the access scopes guide lists read_themes and write_themes as the scopes that cover OnlineStoreTheme. On this page's reading, both people and apps can therefore hold the ability to change what the storefront serves.

Shopify's page on theme app extensions describes a route for apps: apps built in that framework do not edit theme code, and merchants can use the theme editor to configure exposed settings and add app blocks.

The ScriptTag reference describes an older route. It says a script tag represents remote JavaScript code loaded into the pages of a shop's storefront or the Order status page of checkout, that script tags can only be used with vintage themes, and that an app which integrates with a theme and is submitted to the Shopify App Store must use theme app extensions instead of script tags.

That leaves two questions for the worksheet. Which people and apps can change the theme's files, and which code in the theme, or loaded into it by a script tag, came from an app or a person no longer involved with the store. This page treats any theme code an app wrote directly, rather than through a theme app extension, as something to confirm by reading the theme after the app is removed, not something to assume has gone.

Scripts on the checkout and order status pages raise payment-page questions of their own, which the payment script controls guide covers.

Pixels and customer events

Shopify's web pixels page describes pixels as JavaScript code snippets that run on the online store and collect behavioural data, which Shopify calls customer events, for marketing campaign optimisation and analytics.

As a customer browses, those events are published to a Shopify data layer, and a pixel can subscribe to them and transform the payloads into the format its own data collection endpoint needs.

Shopify's web pixels page describes a strict sandbox and a lax sandbox. Web pixel app extensions, which app developers create, load in the strict sandbox, built on web workers. The page says only the globals it lists are certain to be present there. Fetch is among them, and the page says it can be used to make HTTP requests to arbitrary endpoints and that any such request must explicitly support cross-origin resource sharing (CORS).

Custom pixels, which the Web Pixels API reference says are configured in the pixel manager interface in the Shopify admin, load in the lax sandbox: an iframe whose sandbox attribute is defined with the allow-scripts and allow-forms values.

Pixels placed in it cannot access the top frame. The web pixels page says Shopify strongly recommends that developers create apps rather than have merchants create custom pixels, for greater integration.

The sandbox limits what a pixel can take from the page around it, and Shopify also passes data in. The Web Pixels API reference says a pixel's init object is a snapshot of the page at render time, with a data field that provides the Cart and Customer objects.

The web pixels page also says app pixels honour the consent signals a customer chooses: where customers must consent to tracking, an app pixel's callbacks run only after consent is given, and where tracking is on by default with an opt-out, they run until the customer opts out.

The worksheet records, for each pixel, who added it and where its data goes, and for a custom pixel, which customer fields its code reads, without editing or disconnecting anything.

Customer exports and the copies that leave Shopify

The User resource lists separate permissions to export customers, to export orders, to export draft orders, and to view, create, issue and export gift cards to a CSV file.

An export is a copy of store data outside the admin. This page treats each one as a file that someone now has to look after, outside the measures the Data Processing Addendum describes, which are Shopify's measures for the data it processes.

Apps and webhooks make copies too. Shopify's protected customer data page counts customer, order, shipping, fulfilment, checkout and gift card data that relate to a single customer as protected customer data, among other types, along with the webhooks and metafields that relate to a single customer or order.

An app approved for that data receives it in its API responses and webhooks, and what it may keep, and for how long, is set out in the API terms described above.

The worksheet records who holds each export permission, where exported files are stored and how long they stay there, and which apps receive customer fields, without opening an export to copy anything out of it. The sensitive data exposure guide goes into what an export should hold and how to keep fields out of one.

Webhooks: what the receiving endpoint has to check

A webhook is Shopify sending an event, such as a new order, to a server that someone else runs.

Shopify's page on verifying webhook deliveries says each HTTPS delivery carries a base64-encoded HMAC signature in the X-Shopify-Hmac-SHA256 header, generated with the app's client secret and the raw request body, and tells developers to verify it before processing to confirm the delivery came from Shopify.

For a developer checking the signature in their own code, the issues it says to watch for are a body parser that parses the body before verification runs, verification middleware placed after body parsing, and wrong encoding.

The same page says a delivery can arrive more than once, for example after a network timeout or a retry, and suggests idempotent processing or using the X-Shopify-Webhook-Id header to skip duplicates. For HTTPS delivery, it says that if Shopify receives no response or an error, it retries 8 times over the next 4 hours.

After 8 consecutive failures, a subscription configured using the Admin API is deleted automatically, and warning emails go to the app's emergency developer email address.

Shopify's protected customer data page counts webhooks that relate to a single customer or order as protected customer data. On this page's reading, an endpoint that receives order events is handling customer data. The privacy law compliance page says every app distributed through the Shopify App Store must subscribe to the compliance topics customers/data_request, customers/redact and shop/redact, and that an app must return 401 Unauthorized when a mandatory compliance webhook arrives with an invalid Shopify HMAC header.

The worksheet does not send anything to an endpoint. It records each endpoint the store's apps and developers have set up, the topics it receives, whether its code verifies the HMAC signature as the developer shows or reports it, where the client secret is stored by name, and who reads the emergency developer email.

Domains, DNS and certificates

Shopify's domains page describes buying a domain through Shopify and connecting one kept at another registrar.

A domain bought through Shopify is registered in the merchant's name through Shopify's accredited registrar partners, connects to the store automatically, gets SSL issued automatically, has registrar lock enabled by default and is set to auto-renew by default. A domain kept at another registrar is connected by setting an A record for the root domain and a CNAME record for www to the values shown in the Shopify admin.

The same page suggests keeping auto-renew on to avoid lapses and keeping the payment method and contact information current. The User resource lists a domains permission that lets a staff member view, buy and manage domains. For a domain kept elsewhere, the records that point it at Shopify are set outside Shopify, wherever that domain's DNS is managed, so the worksheet records who holds that login as well as who holds the permission in Shopify.

A leftover DNS record for a subdomain that no longer points at the store is what the subdomain takeover guide in this library deals with.

Shopify fraud protection: what Shopify flags and what the merchant decides

Section 4 of the Terms of Service lists fraudulent transactions among the aspects of a sale the merchant is responsible for.

Shopify supplies information for that decision. Its Order reference describes a risk assessment summary on each order that provides fraud analysis and risk scoring to help identify potentially fraudulent orders, for use in decisions about fulfilment and payment processing.

Shopify Protect is Shopify's chargeback cover for Shop Pay orders. Its page says it covers the total order cost and the chargeback fee, and handles the dispute, on protected fraud-based chargebacks, for eligible Shop Pay transactions authorised through Shopify Payments. It says eligibility requires fulfilment and a tracking number for each order within seven days of order receipt, with orders shipped using an approved carrier.

The same page says coverage applies to US stores only, and that terms and conditions apply. On that page's terms, a store outside the US is not covered.

Either way, this page treats the decision on a flagged order as the store's own, since section 4 of the Terms of Service places fraudulent transactions with the merchant.

The worksheet asks who reviews flagged orders, what they check before fulfilling or cancelling one, which fraud apps are installed and what scopes they hold, and where each decision is recorded. It does not ask anyone to change a fraud rule.

A synthetic test order, without a real card

A test order shows where a sale's data goes: which emails are sent, which apps and endpoints receive it, which hosts the browser talks to during checkout and how the order appears to staff.

Shopify documents ways to pay for one without a real card. Its dev stores page says orders can be tested using Shopify's Test payment gateway or by activating test mode for the payment provider. Its Order reference says test orders are made using the Shopify Bogus Gateway or a payment provider with test mode enabled, and that a test order cannot be converted into a real order, or a real order into a test one.

Where the order runs decides what it can disturb. Shopify's guide to testing Shop Pay says test mode is a feature of Shopify Payments, that while it is activated no real payments are captured, and that it should be deactivated after testing so real payments are captured when customers complete checkout.

On a live store, switching it on is a change to the payment settings, made while real customers may be checking out. The checklist does not ask for it, and runs on a dev store instead. Shopify's dev stores page describes dev stores as testing environments you own and control that let you build and test apps without affecting any live store, says they are always password protected and cannot process real transactions, and lists a Shopify Partner account or a merchant store with developer permissions among the requirements for creating one.

A dev store is a stand-in, not a copy. It carries only the apps, pixels, webhook subscriptions and theme set up on it. The dev stores page says that to install third-party apps there, you or the owner of your organisation need to verify your identity, and that for apps using App Pricing, an app from another Partner organisation can be used on free plans or any plan that Partner has marked as free to test.

Record what the dev store carries and what it lacks, because the test order says nothing about anything it lacks.

Use invented customer details and an email address the business controls. The Shop Pay testing guide lists Shopify Payments test card numbers for successful transactions and a test card number that simulates a generic declined card, and says cards added to Shop Pay with its test_card nickname are processed in test mode with no real charges.

Neither that guide nor the dev stores page says whether a test order sends the store's customer or staff notifications, so the checklist records what arrives at the controlled inbox. The checklist caps the run at three checkout attempts.

How to fill in the shared-responsibility worksheet

Paste the table into a spreadsheet and keep one copy per store.

Rows 1 to 12 are readings taken from the live store. Rows 13 to 17 are the test-order checklist and run on a dev store only.

  • Every reading row is read-only. Nothing in rows 1 to 12 changes a setting, removes an account, uninstalls an app, edits a theme or pixel, generates a token or sends a request to anyone else's service.
  • Record secrets by fact: whether a token, client secret or registrar password exists, where it is stored and who can read it. Do not write down the value itself, and do not reveal a token just to check it is still there.
  • Where a row asks about stored data, such as an export folder, an endpoint log or an app's records, record whether customer data is present and where, not the data itself.
  • Write the date and the reader on each row, and the date you read each Shopify page the second column cites. Shopify's terms and documentation change.
  • Anything you want changed goes to the Store Owner, or to the staff member who holds that permission, as a separate task. Read the row again once they have made the change in the admin.
  • Fill it in again when someone with admin access leaves, an app is installed or removed, the theme is replaced, a pixel is added or the domain moves.

Where a store owner's review stops

The worksheet is a record of one store on one date, and these sit beyond its reach:

  • Anything inside Shopify's own systems. For those you have Shopify's statements, in its terms, its Data Processing Addendum and its security page.
  • What an app does with data on its developer's servers. The API terms set what the developer agrees to; the worksheet can only record what the app was allowed to read.
  • What a pixel or script sends after its code changes. The worksheet records code and destinations on the date they were read.
  • Whether an export, a webhook payload or an app's copy has already been passed on. The worksheet records where copies are meant to be.
  • Whether an account, app or theme has already been misused. That is incident response work. Shopify's Security Response page sends security questions and concerns, other than reports of a potential security issue with Shopify itself, to a support request.
  • A test order on a dev store describes the dev store. The live store can differ in apps, pixels, webhooks and theme.

What Shopify's terms say before anyone tests a store

This page makes no statement about what Shopify permits a merchant, a developer or anyone else to test.

Read Shopify's own pages on the day, and decide with them in hand. The passages below are the ones this page draws on.

Section 1 of the Terms of Service says the Shopify User (or, when the service is used as a business, the business employing them) agrees not to work around, bypass or circumvent any of the technical limitations of the Services, which the clause says includes decompiling, disassembling or otherwise reverse engineering them.

The same section says they agree not to access the Services, or monitor any material or information from them, using any robot, spider, scraper or other automated means.

Section 2 of the Shopify API License and Terms of Use says a developer using the API will not engage in any activity that interferes with, disrupts, harms, damages or accesses in an unauthorised manner the servers, security, networks, data, applications or other properties or services of Shopify or any third party, and that interference with any Service feature used in connection with Shopify Checkout without Shopify's express written authorisation is prohibited.

For security reports, the security.txt file on www.shopify.com gives Shopify's HackerOne page as its policy, and Shopify's Security Response page asks anyone who has discovered a potential security issue with Shopify to report it there. Read that policy in full before anyone tests anything that touches a Shopify store, and where the terms leave doubt, get Shopify's answer in writing first.

Shopify stores and Clever Ops

Clever Ops does not test live Shopify storefronts: they are outside its web security services.

That rules out a Shopify store audit, a penetration test of a Shopify store and a scan of one, and this page describes none of them. The worksheet and the test-order checklist are informational, for the store owner, the staff and developers who look after the store, or another provider to use.

The sensitive data exposure, payment script controls, OAuth and OpenID Connect and hacked website guides in this library go further into the subjects this page touches. If a Shopify account, app or theme may already have been misused, the first calls are to Shopify Support and to an incident response specialist.

Frequently asked questions

Section 12 of Shopify's Terms of Service says that where Shopify stores, processes or transmits "Account Data", as PCI DSS defines it, on the merchant's behalf, Shopify acknowledges that it is responsible for securing that data in line with PCI DSS as it applies. The same section says that to the extent a merchant impairs the security of Account Data, for example by bypassing the technical limitations of the Services or using third-party proxies, Shopify is not responsible for its security. Section 4 says the merchant agrees to use Shopify Checkout for sales associated with its online store.

Section 4 of Shopify's Terms of Service lists fraudulent transactions among the aspects of a sale the merchant is responsible for. Shopify's Order reference describes a risk assessment summary on each order, with fraud analysis and risk scoring to help identify potentially fraudulent orders. Shopify Protect, which covers eligible fraud-based chargebacks on Shop Pay transactions authorised through Shopify Payments, applies to US stores only, according to its page.

Shopify's pages tie it to the access scopes the app holds and, for a public app, to Shopify's review. Shopify's protected customer data page puts customer data including name, address, phone or email fields at level 2. It says a public app needs a review for that level, apart from an app installed only on development stores, while a custom app has it always available and, for an admin-created custom app, level 2 varies by plan. Fields an app is not approved for are redacted. Shopify's scopes guide says access scopes control which store data an app can read and write, and that for a new app, merchants approve the scopes when they install it.

Section 6 of Shopify's API terms says a developer that accessed merchant data will delete all originals, copies and reproductions of it within 30 days when the merchant uninstalls the app, except where applicable law prohibits or varies that. For apps distributed through the Shopify App Store, Shopify's privacy law compliance page says Shopify sends a shop/redact webhook 48 hours after uninstallation so the app can erase that store's data. Code an app wrote into theme files is a separate question, and the worksheet asks you to read the theme after an app is removed.

This page makes no statement about what Shopify permits. Section 1 of Shopify's Terms of Service says the Shopify User, or the business employing them when the service is used as a business, agrees not to access the Services, or monitor material from them, using any robot, spider, scraper or other automated means, and not to work around, bypass or circumvent the technical limitations of the Services. The security.txt file on www.shopify.com gives Shopify's HackerOne page as its policy for security reports. Read the terms and that policy on the day, and get Shopify's answer in writing before anything is tested.

Shopify's dev stores page says orders can be tested using Shopify's Test payment gateway or by activating test mode for the payment provider, and its Order reference says test orders made with the Bogus Gateway or a provider in test mode cannot be converted into real orders. Its Shop Pay testing guide says no real payments are captured while Shopify Payments test mode is on, and to deactivate it after testing. So that no payment setting changes on the live store, the checklist on this page runs on a dev store.

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.