Feature Module
Compliance Reporting and Evidence
Create consistent evidence packages from scan capture to investigation closure and reporting output.
How it works
Evidence captured at scan time
Every scan produces screenshots, extracted text, classification results, and content hashes, automatically stored with timestamps and integrity checksums.
Evidence linked through investigation
When an alert becomes a case, the supporting evidence is linked to the investigation. Analyst actions and decisions are recorded with evidence references.
Reports generated from structured data
Monthly MMP reports are generated in an Excel format aligned to Mastercard's MMP reporting requirements, pulling directly from scan, alert, and investigation records.
Reports
Generate and download compliance reports
MMP Compliance
All merchants, alerts, resolution details
SLA Compliance
Deadlines, escalation rates
Risk Portfolio
Merchant breakdown, top flagged
Report Month
Type
MMP Compliance
| Type | Month | Status | Download |
|---|---|---|---|
| MMP Compliance | 2026-03 | completed | |
| SLA Compliance | 2026-03 | completed | |
| MMP Compliance | 2026-02 | completed | |
| Risk Portfolio | 2026-02 | completed |
Evidence package model
Each scan produces a structured evidence manifest: screenshots, extracted text, classification results, content hashes, and metadata, all timestamped and stored with SHA-256 integrity checksums. When an alert is created, the specific artifacts that support the finding are linked to the alert record.
Reporting operations
Monthly MMP reports are generated in an Excel format aligned to the Mastercard MMP reporting requirements, with the column structure, naming convention, and data fields that the format expects. Reports pull directly from scan, alert, and investigation records. No manual data assembly. A golden template controls formatting so the output is consistent month to month.
Audit readiness
The system can produce the full monitoring history for any merchant: scan results, alerts, investigation decisions, and resolutions. Evidence is stored with version IDs and integrity hashes to prove it hasn't been altered since collection.
Incident report generation
AURA generates incident-specific reports that compile the full evidence chain for a particular merchant or violation: monitoring timeline, detection point, investigation actions, and resolution.
Frequently asked questions
- What is included in evidence records?
- Screenshots, extracted page text, classification results with confidence scores, content hashes, timestamps, and analyst decision rationale, all linked to the specific scan and alert that produced them.
- How does reporting stay consistent?
- Reports are generated from a golden Excel template aligned to the Mastercard MMP reporting format. Data is pulled from structured records, not assembled manually. Column headers, naming conventions, and date formats are validated at generation time.
- How long is evidence retained?
- Evidence is stored with 7-year retention in compliance with Mastercard requirements. Active evidence is in hot storage; older evidence transitions to archive storage after 1 year.
- Can evidence be exported for external use?
- Yes. Evidence packages can be exported as structured bundles for regulator submissions, card scheme inquiries, or legal proceedings. Each export includes integrity checksums.