Shared risk record affecting future merchant admission
Mastercard MATCH Pro
Mastercard MATCH Pro is a shared information system about terminated merchants and their owners. Network rules require qualifying reports and pre-onboarding inquiries, while preserving an acquiring institution's discretion to accept a merchant despite an entry.
Reporting, retention and correction
The inspected Chapter 11 rule links reporting to termination and reason to believe a listed condition exists; its five-calendar-day clock runs from specified earlier decision, notice or awareness events. Potential identity matches require relevance checks. Acquirers retain accuracy responsibility and must respond to listing questions within seven days and removal requests within thirty calendar days. Neither response clock guarantees removal. Listings generally purge after five years, while some downstream records persist. Erroneous additions have a correction route; the merchant's direct PCI-compliance route is narrower than a universal appeal bypass.
Mastercard acquirers · rule scope → Mastercard MATCH Pro
must report under qualifying termination triggers
Section11.5 combines termination by merchant/acquirer with reason to believe a listed condition exists. Five calendar days runs from earlier listed decision/notice/awareness events, not effective termination; awareness is not detached from the opening condition.
Section11.13 permits removal for erroneous addition reported by an authorized user or specified cured PCI code12 noncompliance. Merchant direct application when acquirer unwilling/unable is narrow PCI route, not general bypass.
Section11.10 provides5year listing retention/purge; recipient records persist at least2years after agreement end and inquiry records365days. Central purge does not erase all downstream records or restore processing.
Mastercard MATCH Pro → Stripe published MATCH acceptance practice
is an input to restrictive underwriting
Stripe's published practice gives MATCH a restrictive onward use. No identified Stripe decision or acquiring-bank identity is established; its1workingday summary differs from the August network5calendar-day rule.
The appellate record describes Merrick's termination and MATCH listing of eGumball; its record showed Merrick alone could request this listing's addition/removal. Accuracy and final remedy remain unresolved.
Mastercard MATCH Pro → MATCH authorized acquirers and service providers
provides retroactive alerts after inquiries
Section11.6.4 describes alerts for later added information within365days after an inquiry, visible30days and once in batch results. Recipient next steps remain separate; no closure cascade observed.
MATCH authorized acquirers and service providers → Mastercard MATCH Pro
must inquire before agreement or acceptance
Section11.6 requires inquiry before signing/enabling acceptance. Exact/phonetic or spelling hits are possible identity matches requiring relevance checks, not proof of misconduct.
Anti-Piracy Policy conditionally requires MATCH notice if the acquirer terminates the merchant; no particular WIPO/Creative merchant report is established.
Section11.5 combines termination by merchant/acquirer with reason to believe a listed condition exists. Five calendar days runs from earlier listed decision/notice/awareness events, not effective termination; awareness is not detached from the opening condition.
Section11.6 requires inquiry before signing/enabling acceptance. Exact/phonetic or spelling hits are possible identity matches requiring relevance checks, not proof of misconduct.
Section11.6.4 describes alerts for later added information within365days after an inquiry, visible30days and once in batch results. Recipient next steps remain separate; no closure cascade observed.
Section11.10 provides5year listing retention/purge; recipient records persist at least2years after agreement end and inquiry records365days. Central purge does not erase all downstream records or restore processing.
Section11.13 permits removal for erroneous addition reported by an authorized user or specified cured PCI code12 noncompliance. Merchant direct application when acquirer unwilling/unable is narrow PCI route, not general bypass.
Stripe's published practice gives MATCH a restrictive onward use. No identified Stripe decision or acquiring-bank identity is established; its1workingday summary differs from the August network5calendar-day rule.
The appellate record describes Merrick's termination and MATCH listing of eGumball; its record showed Merrick alone could request this listing's addition/removal. Accuracy and final remedy remain unresolved.