Snippet status
Open a merchant → Overview → App. The badge is Snippet status. Check snippet (title Re-check this merchant now and update the shared snapshot) re-checks this merchant only. Install the tag itself from Merchant Snippet Integration.
Where to find it
Merchant detail → App / environment card area → Snippet status, with Check snippet to refresh. The same card lists Pages with embed snippets from that snapshot, and Detected snippet when the scanned environment disagrees with the App badge. Check env on that card runs Check snippet and then Environment integrity.
How it is computed
Status comes from merchant-api snapshot checks (monitor + source verification) and refreshes on demand via Check snippet.
- Monitor API path:
/api/snippets/snapshots/*on merchant-api - Monitor backend: Cloud Function
monitorineurope-west2
Check snippet
Check snippet on the App card (title Re-check this merchant now and update the shared snapshot) re-checks only the open merchant. Check env runs this first, then Environment integrity.
- Toast Checking snippet... as soon as the click is accepted.
- The write is
POST /api/snippets/snapshots/merchant/:idwith that merchant’s known URLs. It updates today’s shared snapshot (the same file Sync Snippets rebuilds for every merchant) and this row’s Snippet status, details, timestamp, scanned environment / domain, Pages with embed snippets, and source-verification extras. - Success toast Snippet check updated. The App card and merchants table badge reload from that response. If you were in Edit Merchant, edit mode exits so the card can redraw.
- Failure toast is the API
message/error, or Failed to check snippet. The previous snapshot stays until a later check succeeds.
Daily snapshot vs on-demand: Snippet snapshot.
Status meanings
These labels appear on the merchants table and the App card. Snapshot
JSON still uses internal keys (deployed, not_deployed, no_domain,
error, checking, unknown).
| Badge | Internal key | Meaning |
|---|---|---|
| Snippet found | deployed | Monitor / source scan confirmed an active FinMatch SDK. |
| Snippet missing | not_deployed | No active FinMatch SDK detected (including commented-out). |
| No domain | no_domain | Merchant has no domain configured to scan. |
| Error | error | Scan failed (network / service / runtime). |
| Checking | checking | Snapshot load or Check snippet is in progress. |
| Unknown | unknown / empty | Not in the latest snapshot, or the row has no status. |
There is no operator badge named Deployed or Missing. Older docs used those words for the same two states as Snippet found and Snippet missing.
Use Snippet details for the exact scan result text behind the badge.
How the shared daily snapshot is built: Snippet snapshot.
Snippet details
Common detail strings:
| Detail text | Meaning |
|---|---|
Found in <head> | Snippet script found in head. |
| Found in DOM | Snippet found outside head. |
| Found commented script - needs activation | Script present but commented out. |
| Snippet not detected | No active FinMatch snippet found. |
| No domain configured | Merchant has no domain to scan. |
| No domain provided | Monitor received no domain value. |
| Source verification detected… | Source scan found the SDK even when the monitor did not. |
| Monitor failed: … | Monitor endpoint / HTTP error. |
| Other error text | Raw network / runtime error from the scan. |