# Announcements source: https://developer.mastercard.com/mastercom/documentation/announcements/index.md ### 1. Updating the Mastercom API to decommission three underused endpoints {#1-updating-the-mastercom-api-to-decommission-three-underused-endpoints} April 2026: Mastercard is updating the Mastercom API by deprecating and then decommissioning underused endpoints. | Endpoint type | Affected endpoint | |--------------------------------------------------|-------------------------------------------------| | Fees | POST /v6/claims/{claim-id}/fees/loaddataforfees | | Fees (Debit Mastercard and Europe Dual Acquirer) | POST /v6/claims/{claim-id}/fee/debitmc | | Health check | GET /v6/healthcheck | For further information including effective dates, refer to [GLB 13504.1 Updates to the Mastercom API for April 2026](https://trc-techresource.mastercard.com/r/bundle/m_an13504_en-us/page/d/en-US/) in the Technical Resource Center on Mastercard Connect. *** ** * ** *** ### 2. Introducing Ethoca Consumer Clarity Call Center Integration in Mastercom {#2-introducing-ethoca-consumer-clarity-call-center-integration-in-mastercom} April 2026: Mastercard is updating the Mastercom API to provide Dual Message System issuers with enriched transaction data from Ethoca Consumer Clarity Call Center at the time of claim creation. Mastercard is updating the `GET /v6/claims/{claim-id}`in the Mastercom V6 Specification to include a new `callCenterDetailsUrl` parameter in the response. The parameter returns an HTML link to detailed Call Center transaction data. * Using the `callCenterDetailsUrl` is optional. Dual Message System issuers using the Mastercom V6 API can update their systems for the parameter and ingest the HTML link, but it is not required. For further information including effective dates, refer to [GLB 12896.2 Introducing Ethoca Consumer Clarity Call Center Integration in Mastercom (excluding India, Indonesia, Nepal, Jordan, and Tunisia)](https://trc-techresource.mastercard.com/r/bundle/m_an12896_en-us/page/d/en-US/) in the Technical Resource Center on Mastercard Connect. *** ** * ** *** ### 3. Updates to GET /v6/claims/{claim-id} and GET /v6/claims/{claim-id}/transactions/clearing/{transaction-id} {#3-updates-to-get-v6claimsclaim-id-and-get-v6claimsclaim-idtransactionsclearingtransaction-id} March 2026: Mastercard is updating the responses for `GET /v6/claims/{claim-id}` and `GET /v6/claims/{claim-id}/transactions/clearing/{transaction-id}` to include new parameters that support additional Private Data Subelements (PDSs) for Mexico domestic transactions. These updates add support for PDS 0297 and PDS 0299 in the T5G2/T5G4 Enhanced Reconciliation Report in Mastercom. The report will also be updated to include the existing PDS 0159. For further information including effective dates, refer to [GLB 12421.1 Updates to Mastercom Enhanced Reconciliation Report for New Private Data Subelements](https://trc-techresource.mastercard.com/r/bundle/m_an12421_en-us/page/d/en-US/) in the Technical Resource Center on Mastercard Connect. *** ** * ** *** ### 4. Updates to GET /v6/claims/{claim-id} {#4-updates-to-get-v6claimsclaim-id} July 2025: Mastercom is updating the response for the GET /v6/claims/ {claim-id} endpoint to include the `auditControNumber` field. For further information including effective dates, refer to [GLB 11941.1 Mastercom Technical Enhancements for July 2025](https://trc-techresource.mastercard.com/r/bundle/m_an11941_en-us/page/d/en-US/) in the Technical Resource Center on Mastercard Connect. *** ** * ** *** ### 5. Mastercom support for fraud type codes 55, 56, and 57 {#5-mastercom-support-for-fraud-type-codes-55-56-and-57} May 2025: Mastercom supports fraud type codes 55, 56, and 57 in the POST /v6/claims/{claim-id}/fraud/mastercard endpoint. For further information, refer to [GLB 11412.2 Mastercom Technical Enhancements for May 2025](https://trc-techresource.mastercard.com/r/bundle/m_an11412_en-us/page/d/en-US/) in the Technical Resource Center on Mastercard Connect. *** ** * ** *** ### 6. Mastercom API Migration to DigiCert Certificate Authority {#6-mastercom-api-migration-to-digicert-certificate-authority} 25 February 2025: Mastercard will be migrating from Entrust to DigiCert CA certificates, in response to the announcement made by Google and Mozilla to move away from Entrust CA. You are required to switch to DigiCert CA before March 24, 2025 in production to ensure a successful SSL handshake and avoid any service disruption. For further information, refer to [GLB 11190.1 Mastercom API Migration to DigiCert Certificate Authority](https://trc-techresource.mastercard.com/r/bundle/m_an11190_en-us/page/d/en-US/) in the Technical Resource Center on Mastercard Connect. *** ** * ** *** ### 7. Updates to arbitration case actions {#7-updates-to-arbitration-case-actions} January 2025: Users will see the following changes in the Mastercom V6 API for the `PUT /v6/cases/{case-id}` endpoint: > * Senders and receivers cannot provide REJECT for arbitration cases. > * Senders and receivers cannot provide REBUT for arbitration cases. For further information including effective dates, refer to [GLB 11005.1 Mastercom Technical Enhancements for January 2025](https://trc-techresource.mastercard.com/r/bundle/m_an11005_en-us/page/d/en-US/) in the Technical Resource Center on Mastercard Connect. *** ** * ** *** ### 8. Versions 2, 3, 4, and 5 have been decommissioned. {#8-versions-2-3-4-and-5-have-been-decommissioned} 21 October 2024: Mastercom decommissioned versions 2, 3, 4 and 5 of the Mastercom API. Issuers and acquirers using version 2, version 3, version 4 and version 5 of the Mastercom API must update their systems to version 6 to continue processing disputes. For further information, refer to [AN 8227 Decommissioning of Select Versions of the Mastercom API](https://trc-techresource.mastercard.com/r/bundle/m_an8227_en-us/page/z/) and [AN 6971 Decommissioning of Select Versions of the Mastercom API](https://trc-techresource.mastercard.com/r/bundle/m_AN6971_en-us/page/z/) in the Technical Resource Center on Mastercard Connect. *** ** * ** *** ### 9. Updating versions 4, 5, and 6 to decommission imagestatus endpoints. {#9-updating-versions-4-5-and-6-to-decommission-imagestatus-endpoints} October 2024: Mastercard is updating versions 4, 5, and 6 of the Mastercom API to: deprecate and decommission /imagestatus endpoints. For further information, including recommended alternatives to decommissioned endpoints, refer to [GLB 9194.1 Updates to the Mastercom API for October 2024](https://trc-techresource.mastercard.com/r/bundle/m_an9194_en-us/page/d/en-US/) in the Technical Resource Center on Mastercard Connect. *** ** * ** *** ### 10. Decommissioning version 4 and version 5 of the Mastercom APIs {#10-decommissioning-version-4-and-version-5-of-the-mastercom-apis} October 2024 : Mastercom is decommissioning version 4 and version 5 of the Mastercom API. Issuers and acquirers using version 4 and version 5 of the Mastercom API must update their systems to version 6 to continue processing disputes. For further information including effective dates, refer to [AN 8227 Decommissioning of Select Versions of the Mastercom API](https://trc-techresource.mastercard.com/r/bundle/m_an8227_en-us/page/z/) in the Technical Resource Center on Mastercard Connect. **Published date**: 12 September 2023 *** ** * ** *** ### 11. Decommissioning version 2 and version 3 of the Mastercom APIs {#11-decommissioning-version-2-and-version-3-of-the-mastercom-apis} 06 November 2023 : Mastercom is decommissioning version 2 and version 3 of the Mastercom API. Issuers and acquirers using version 2 and version 3 of the Mastercom API must update their systems to version 6 to continue processing disputes. For further information including effective dates, refer to [AN 6971 Decommissioning of Select Versions of the Mastercom API](https://trc-techresource.mastercard.com/r/bundle/m_AN6971_en-us/page/z/) in the Technical Resource Center on Mastercard Connect. **Published date**: 01 November 2022 *** ** * ** ***