MCC Checker

MCC Checker verifies merchant category codes: it checks whether a merchant's assigned MCC fits its website or business description and suggests better-fitting MCCs, with high-risk flags and each PSP's likely stance from its public policies.

Best for: Merchant onboarding and underwriting teams, acquirer risk teams, and PSP sales teams checking whether a prospect fits their appetite.

How to check a merchant category code (MCC)

1. Add merchants to Merchants with a url and/or description and the assignedMcc.
2. Leave Include PSP appetite on to see provider policy notes.
3. Click Start and review verdict, suggestedMccs and highRiskFlags.

How it works

Fetches the homepage (title, meta and visible text) and/or uses your description, then scores about 55 MCCs with transparent keyword rules (no paid AI). MCC descriptions come from the public greggles/mcc-codes list (Unlicense). The provider appetite dataset (data/provider_appetite.json) summarises public restricted/prohibited business pages from Stripe, PayPal UK, Square UK, Adyen, GoCardless, SumUp UK and Checkout.com, with a source URL and capture date for every entry. scripts/refresh_appetite.py re-checks the pages and flags changes. Worldpay has no public list, so it isn't included.

Output

url, assignedMcc, verdict, suggestedMccs, highRiskFlags, miscodingNotes, riskCategories, providerAppetite, fetchError

Pricing (pay-per-event)

• merchant-checked: $0.005 per result ($5 / 1,000). Platform usage is included; you pay only for results.
• Example: 10,000 merchants cost $50.00.

Example input

{
  "merchants": [
    {
      "url": "https://www.pokerstars.uk",
      "assignedMcc": "7995"
    },
    {
      "description": "Crypto exchange, buy bitcoin with card",
      "assignedMcc": "6012"
    }
  ]
}

Example output

Values below are illustrative.

{
  "url": "https://example-casino.com",
  "assignedMcc": "5816",
  "verdict": "mismatch",
  "suggestedMccs": [
    {
      "mcc": "7995",
      "confidence": 0.9,
      "highRisk": true
    }
  ],
  "highRiskFlags": [
    {
      "mcc": "7995",
      "reason": "Gambling..."
    }
  ],
  "miscodingNotes": [
    "Gambling content under a gaming/retail MCC..."
  ],
  "riskCategories": [
    "gambling"
  ],
  "providerAppetite": [
    {
      "provider": "Stripe",
      "likelyStance": "restricted",
      "likelyStanceLabel": "Restricted",
      "sourceUrl": "https://stripe.com/legal/restricted-businesses"
    },
    {
      "provider": "Square (UK)",
      "likelyStance": "manual_review_likely",
      "likelyStanceLabel": "Not stated – usually decided by manual review",
      "sourceUrl": "https://squareup.com/gb/en/legal/general/ua"
    }
  ],
  "fetchError": null
}

Use it via API, schedules and integrations

Run it in Apify Console, or call it from your own code with the Apify API or the Python and JavaScript clients. Save an input as a task and add a schedule to run it regularly, and send results to Slack, email, webhooks, Zapier, Make or n8n with Apify integrations. AI agents can find and run it through the Apify MCP server.

from apify_client import ApifyClient

client = ApifyClient("YOUR_APIFY_TOKEN")
run = client.actor("sterlingverify/mcc-checker").call(run_input={"merchants": [{"description": "Crypto exchange, buy bitcoin with card", "assignedMcc": "6012"}]})
for item in client.dataset(run["defaultDatasetId"]).iterate_items():
    print(item)

FAQ

Does it use AI?

No LLM is used. It scores about 55 MCCs with transparent keyword rules.

Is the PSP stance an approval decision?

No. It is guidance summarised from public policy pages on the capture date shown, not an approval guarantee.

Disclaimer

Guidance only, not an approval guarantee. MCC suggestions are keyword-based and can be wrong; the acquirer and card scheme rules decide the correct MCC. Provider appetite is summarised from each provider's public policy pages on the capture date shown. It is guidance only — not an approval guarantee — and providers decide case by case and change their policies. A stance of manual_review_likely (label: "Not stated – usually decided by manual review") means the category was not listed as allowed, restricted or prohibited on the public page; blanks are usually decided by manual review on the provider's side. Not affiliated with any provider or card scheme. Not legal or compliance advice.

Related sterlingVerify tools

Part of the sterlingVerify UK payments, KYB and data toolkit on Apify Store:

• Merchant Website Compliance Checker for Onboarding: onboarding review of a merchant's website
• Payments Stack Detector: find which PSPs, wallets and BNPL a store uses
• PCI Readiness Scanner: passive checkout security check with a likely SAQ type
• BIN Lookup: bulk BIN lookup for scheme, type, issuer and country
• Payments Region Checker: EEA, SEPA, SCA and interchange classification by country or BIN