Merchant WatchRisk console · prototype

Access code

Merchant WatchRisk console · prototype

Your name

Recorded in the audit log with every scan, review and change, until individual logins exist.

Merchant Watch
Merchant WatchPrototype
Dashboard Alert queueEvery alert, newest first0 Enrolled merchants Add merchant Application review
More
Reports Settings Demo What's next
AI review Email alerts Slack Jira

Dashboard

Add merchant

One at a time, or a CSV of pilot merchants.

Single merchant · step 1 of 5

Merchant

    A name or a pilot ref is required. The ref is shown wherever the name would be, and must be unique.

    No real MIDs during the pilot. Use a placeholder that lets the team match it up later.

    Every active merchant is also in the nightly run at 2 am Central.

    Finishing crawls the website now and stores what you see as the approved baseline. Every scan after that compares against it. This takes up to 20 seconds.

    Bulk upload

    Upload a CSV

    1. and fill in one row per merchant.
    2. Choose the file and press Check file. Every row is validated and shown below.
    3. Press Import. Only rows marked Ready are enrolled; their baselines are captured in the background.

    Columns ref,url,mcc,approved_on,watchlist,notes, plus optional name,mid,analyst. MID is a placeholder; no real MIDs. Up to 500 rows per file.

    Enrolled merchants

    Add merchant

    Every merchant being monitored.

    Click a merchant for its change history, scans, alerts and actions. Paused merchants are skipped by the nightly run and the cadence scheduler; Scan now on their page still works.

    Application review

    Is this website the business that is applying? A one-off check before approval; nothing is enrolled or monitored.

    Step 1 · The application
    Processing request · as stated on the application

    Unlocks the Processing request checks: tickets vs the site's prices, volume that fits the business and town, a gateway with no equipment, website age vs years in business.

    Optional fields: each one unlocks a check

    Type the fields from the application. Don't paste the application itself – it carries ID and bank details.

    Recent reviews

    Alert queue

    Demo

    Pinecrest walkthrough and gateway signals. Synthetic data only.

    Demo

    Pinecrest Software Supply

    Pinecrest is a fictional merchant site for showing the risk team what a change after approval looks like. You play the merchant in its admin, then scan it here.

    1. Press Reset demo below. If Pinecrest isn't enrolled yet, press Add Pinecrest as a merchant instead.
    2. Open the Pinecrest admin
      Apply a scenario: pharmacy products, checkout off-site, refund policy deleted, unfinished site, block the scanner. Everyday noise should raise nothing; Slow swap, pressed a few times with each change cleared and accepted, shows drift since approval.
    3. On Pinecrest's page, press Scan now. A Critical alert appears there and in the alert queue, with before/after evidence.

    Reset demo puts Pinecrest back to its approved version, clears its alerts and recaptures the baseline.

    Gateway signals
    Simulated data. Synthetic sample data. Real feed: NMI partner transaction report API (pending access).
    Transaction monitoring prototype

    Upload transactions

    A CSV shaped like the partner transaction report: id,created,merchant_ref,amount,action_type,status,source,order_description,card_bin,billing_country,ip_country. Signals that cross a threshold raise an alert in the alert queue.

    What's next

    6 capabilities after the first deploy

    A pitch only: nothing on this page runs.

    • Application reviewChecks an applicant's website against the application at underwriting time, before approval.
    • Gateway transaction signalsTies volume spikes, off-MCC orders and refund swings to the site change behind them.
    • Jira ticketsOpens a ticket in the risk team's project for every alert that needs action.
    • Slack and email alertsPosts Critical alerts to a channel and emails the nightly digest.
    • Merchant Central statusEnrolls merchants at approval and shows their account status next to each alert.
    • Bedrock web searchAdds news and complaint searches to the weekly public signals, inside NMI's AWS account.

    Reports

    The last 7 and 30 days at a glance, and who reviewed what.

    Who reviewed what

    Audit log

    Settings

    Alert delivery, recipients and AI prices.

    Alert delivery

    Channels

    Each channel switches on when its Netlify environment variables are set, and stays completely off until then. Changing a variable takes effect after a redeploy.

    Email alerts

    Recipients

    Per-merchant override (optional)

    When a merchant has its own list, its alerts go only to that list.

    The global list also gets the nightly digest. Instant alert emails go out for Critical alerts only (set INSTANT_EMAIL_MIN_SEV=high to include High); everything else is in the digest.

    Cost controls

    AI prices

    Optional. When the month's AI spend passes it, the nightly digest email says so. It is not shown on the Dashboard.