Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      


Updated on June 12, 2022

This release includes the processing rules and end-to-end interface for Mastercard s new MasterCom interface. Validation rules ensure chargebacks meet Mastercard s disputes rules. Smart dispute for Issuers supports MCOM API’s (SDK version 6) for new MCOM processing. Maestro chargebacks are still processed on legacy Chargeback processing as Maestro association has not switched onto MCOM interface yet. This release also includes the latest MasterCom related change i.e., the MCOM Collaboration Layer.

Pega Smart Dispute for Issuers

List of reason codes supported by Pega Smart Dispute for Issuers in MCOM are as following:

Reason codes in Mastercard

Reason CodeDescription
4837No Cardholder Authorization
4849Questionable Merchant Activity
4854Cardholder Dispute - Not Elsewhere Classified (U.S Region only)
4863Cardholder Does Not Recognize - Potential Fraud (this reason code will be retired as a part of the 20.1 compliance release)
4870Chip Liability Shift
4871Chip/PIN Liability Shift - Lost/Stolen/Never Received Issue
4808Authorization related Chargeback
4834Point of Interaction Error
4853Cardholder Dispute
4850Installment Billing Dispute

List of reason codes supported by Pega Smart Dispute for Issuers in Maestro are as following:

Reason codes in Maestro

Reason CodeDescription
17Cash Dispute-ATM Only
30Cardholder Disputed Amount (U.S. Shared Deposits Only)
70Chip Liability Shift
71Transaction Amount Differs
73Duplicate Transaction
74No Cardholder Authorization
75Credit Not Received
79Goods or Services Not Provided
80Late Presentment
95Invalid Adjustment: Account Closed
96Invalid Adjustment: Insufficient Funds

For more details on MCOM and Smart Dispute integration capabilities with Mastercard, refer Mastercard Claims Manager overview document on Pega community.

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us