---
title: "Checkout monitor"
description: "An hourly check that your checkout button still leads to your checkout."
---

> Documentation Index
> Fetch the complete documentation index at: https://use-protect.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Checkout monitor

> **Pilot**
>
> The checkout monitor is in pilot. If **Storefront → Scans** is not shown, the monitor is not yet enabled for your store.

A compromised app or script can redirect shoppers from your checkout button to a phishing page, and often does so only some of the time. The checkout monitor opens one product in a fresh browser every hour, clicks through to checkout the way a guest would, and reports any attempt to navigate somewhere unexpected.

It answers one question: did this journey try to leave your store before reaching the checkout?

## Set up the journey

Open **Storefront → Scans** and fill in **Journey**:

1. Choose one product, and optionally a **Variant ID**.
2. Enter the CSS selector of your **Add to cart** button.
3. If your theme opens a cart drawer or cart page first, enter its selector under **Cart control (optional)**.
4. Enter the selector of your **Checkout** button.

Your Shopify domains are expected automatically. If your checkout legitimately passes through another site, add it under **Additional expected origins**, one `https` origin per line, up to five. Add an origin only after you have reviewed it; every origin you add is one the monitor will no longer flag.

## Read a check

| Result | Meaning |
|---|---|
| Expected checkout reached | The checkout loaded on one of your domains, and nothing unexpected happened in the five seconds after. |
| Suspicious navigation observed | A page or popup tried to load from an origin that is not expected. The monitor stopped the request in its own browser and recorded where it was going. |
| Check incomplete | The journey could not finish, so there is no result either way. The reason is shown, for example a selector that no longer matches. |

The screen shows the **Latest check**, the **Last completed check**, the **Next check** time and 30 days of **Recent checks**. Use **Scan now** to run one immediately.

An incomplete check is not a pass. If checks keep ending incomplete after a theme change, update the selectors.

## When a finding opens

Protect emails your store's contact address once: the destination that was attempted, and the steps that led to it. Later sightings of the same finding update its last-seen time without another email.

The evidence lists each step and each navigation, with origin and path only. Query strings, cookies, page content and screenshots are not kept.

A finding stays open, and stays visible beside later clean checks, until you close it with a **Reason for closing**. Closing records your review; it does not fix anything. If the same navigation is seen again, the finding reopens.

> **If you see a finding**
>
> A finding means the monitor saw the redirect attempt. It does not identify which app or script caused it, and it is not proof that your store is compromised. Review the recorded steps and destination, then look at apps and theme code that changed recently.

## What it does not cover

Listed in the app under **Coverage**:

- Only one product, on desktop Chromium, from one location. Other products, devices and regions are not checked.
- Skimmers that stay on your own domain, and payment overlays embedded in the page.
- Logged-in, express and payment-completion steps. The monitor never fills in a field, selects a payment method or places an order.
- A navigation that stays on your domain but leaves the product, cart and checkout pages ends the check as incomplete, not suspicious.

The monitor's visits do not count as sessions, are not charged as usage, and are not subject to your rules, so bot detection does not block them.

Source: https://use-protect.com/docs/storefront/checkout-monitor/index.mdx
