Dashboard

The Home page is where you switch protection on and off, see whether anything needs your attention, and check what CTG did in the last 7 days.

Protection

The protection card switches the store between two modes:

Monitoring - nothing is blocked. CTG only counts what it would have held.
Protecting - low-value checkouts without a valid pass lose card payment.

The card’s heading tells you where you stand: Protection is off, You’re ready to turn on protection, Protection is on, or Protection is on but paused.

This is also your kill switch

Switching to monitoring stops all blocking from that moment. Nothing else needs to be undone.

Banners

Shown while CTG detects a burst of held checkouts. It says when the burst started and, depending on your settings, whether attack mode was switched on automatically, whether you might want to turn it on, or (in monitoring mode) that you need to turn on protection to stop it.

When protection is on but CTG has stopped blocking because real shoppers might not be getting passes, a red banner names the cause:

App embed is off - the app embed is missing from your storefront
No storefront tokens - no shopper has received a pass in 24 hours
Token list out of date - the app server can’t update your store
Checkout rules missing - the checkout rule or payment customization is gone

While paused, checkouts go through unchecked. Protection resumes on its own once the cause is fixed. See Troubleshooting for each fix.

Setup Guide and Readiness

Three readiness checks gate protection:

Checkout rules installed - the checkout rule and payment customization exist
Token list fresh - the app server has recently updated your store
Storefront issuing passes - the app embed is on and shoppers are receiving passes

The guide also shows your checkout test progress: Recommended until you start, In progress while you work through it, and Failed if an important row failed.

You can override the checks

If you try to turn on protection before the checks pass, CTG shows a confirmation dialog rather than refusing. Use it only if you know why a check isn’t green.

Last 7 Days

A per-day table (in your store’s local time) built from the checkouts CTG has recorded:

Checkouts - every checkout recorded that day
Held - how many your current settings would hold (or did hold, while protecting): no pass, or a forged, expired or reused one, within your threshold - or any value in attack mode
Held but ordered - held checkouts that still became orders
Bad token - checkouts that carried a forged or reused pass

Held but ordered is the number to watch

In monitoring mode, these are likely real customers the rule would have turned away. Check them before you protect. When any appear, the page shows a warning banner with the count.

It's an estimate

Returning customers and allowlisted products aren’t excluded from the table (CTG doesn’t keep customer or line-item data), and carts in a different currency than your store’s are only counted in attack mode.

Other Pages

Settings - see Protection Settings
Test your checkout - see Testing Your Checkout
Billing - plan, prevented attempts and estimated charge; see Plans & Billing
Help - an in-app FAQ with search

Shopify Flow

CTG has no notification system of its own. Instead it sends four Shopify Flow triggers you can build workflows on - for example a Slack message or an email to your team:

Card testing attack detected - with the number of held checkouts in the last hour
Card testing attack ended
Card testing protection paused - with the reason and how to fix it
Card testing protection resumed

Each trigger carries a link back to the app.