MATCH listing is a workflow,
not a spreadsheet
MATCH listing starts with detection, passes through investigation, and ends with a structured submission that carries its own evidence. Kenal AURA runs the whole chain (entity discovery, case management, structured resolution codes, and evidence bundling) in one operating layer.
Summary
Kenal AURA is the merchant lifecycle risk operations platform for acquirers and PSPs with MATCH listing obligations. Detect violations continuously, investigate with SLA discipline, resolve with structured reason codes, and ship evidence bundles that hold up under scheme scrutiny. See also the MATCH list glossary entry for background on the list itself.
Detection is where MATCH starts
A merchant does not declare when it pivots into a MATCH-reason category. Kenal AURA's entity discovery sweeps the public web for undeclared URLs, its web change detection catches category pivots on declared URLs, and its MCC drift detection flags when scanned content stops matching the approved category. Detection is continuous, not periodic.
Investigation with structured outcomes
Every alert transitions into a case with an owner and an SLA clock. Analysts resolve with a fixed enum of reason codes: false positive, merchant warned, content removed, suspended, terminated, MATCH listed. Free-text 'notes' fields are not enough for a MATCH submission. Structured resolution codes are.
Evidence bundled, not reconstructed
A MATCH submission needs screenshots, classification rationale, timestamps, and investigation history. Kenal AURA builds that bundle automatically from the case data: scan screenshots with SHA-256 hashes, the specific BRAM rule that fired, the analyst decision chain, and the resolution code. Open the case, export the bundle, submit.
Backed by chain-of-custody
Every screenshot and content capture is stored with an integrity hash and object lock for the 7-year card-scheme retention window. A MATCH submission that references evidence from two years ago is still backed by immutable storage on the other end. Chain of custody is not a document you draft. It is a property the platform enforces.
Modules that power this
Entity Discovery
Public-web sweep for undeclared URLs, laundering fronts, and secondary stores.
Learn moreInvestigation Workflows
SLA-governed case management with structured resolution reason codes.
Learn moreCompliance Reporting and Evidence
Evidence packages with SHA-256 hashes, version IDs, and 7-year immutable retention.
Learn moreWeb Change Detection
Continuous multilingual crawling and BRAM-aligned content classification.
Learn morePinned-Page Drift
Lock policy pages and catch silent T&C rewrites before they become MATCH events.
Learn moreMCC Drift Detection
Alert when scanned content moves outside the approved MCC family.
Learn moreFrequently asked questions
- What is the MATCH list, exactly?
- MATCH is Mastercard's Member Alert to Control High-Risk Merchants list: a registry of merchants and principals that have been terminated for specific reasons. Acquirers must screen against MATCH before onboarding and add merchants to it when the termination reason matches the defined codes. Our /glossary/match-list entry covers the full background.
- Does Kenal AURA submit to MATCH on our behalf?
- No. MATCH submissions go through the acquirer's Mastercard-provided channel. Kenal AURA produces the structured evidence bundle and the case history that the submission depends on: the classification rationale, the screenshots with integrity hashes, the investigation timeline, and the structured resolution code. Submitting remains an acquirer action.
- How long is the evidence retained?
- 7 years, on immutable storage with SHA-256 integrity hashes and object lock. This matches the card-scheme retention requirement so a MATCH submission referencing evidence from years ago still has the original backing when audited.
- Can we use Kenal AURA for MATCH screening on incoming merchants?
- MATCH screening (checking whether a merchant is already on the list before onboarding) is a Mastercard-provided API call, so the acquirer remains responsible for that integration. Kenal AURA handles the other direction: detection, investigation, and the structured evidence needed to submit to MATCH when a termination qualifies.