This Open API specification serves as a standardized framework for describing and defining the capabilities of the Matrix Client-Server Notifications API. It outlines how clients can interact with the API, providing a structured approach to document endpoints, operations, and other integration details. This specification is intended to promote clarity, consistency, and ease of use for developers and consumers of the API, ensuring efficient communication between systems.
This Open API specification serves as a standardized framework for describing and defining the capabilities of the Matrix Client-Server message redaction API. It outlines how clients can interact with the API, providing a structured approach to document endpoints, operations, and other integration details. This specification is intended to promote clarity, consistency, and ease of use for developers and consumers of the API, ensuring efficient communication between systems.
This Open API specification serves as a standardized framework for describing and defining the capabilities of the Matrix Client-Server Key Backup API. It outlines how clients can interact with the API, providing a structured approach to document endpoints, operations, and other integration details. This specification is intended to promote clarity, consistency, and ease of use for developers and consumers of the API, ensuring efficient communication between systems.
This Open API specification serves as a standardized framework for describing and defining the capabilities of the Matrix Client-Server filter API. It outlines how clients can interact with the API, providing a structured approach to document endpoints, operations, and other integration details. This specification is intended to promote clarity, consistency, and ease of use for developers and consumers of the API, ensuring efficient communication between systems.
This Open API specification serves as a standardized framework for describing and defining the capabilities of the Matrix Client-Server device management API. It outlines how clients can interact with the API, providing a structured approach to document endpoints, operations, and other integration details. This specification is intended to promote clarity, consistency, and ease of use for developers and consumers of the API, ensuring efficient communication between systems.
This Open API specification serves as a standardized framework for describing and defining the capabilities of the Matrix Client-Server Event Context API. It outlines how clients can interact with the API, providing a structured approach to document endpoints, operations, and other integration details. This specification is intended to promote clarity, consistency, and ease of use for developers and consumers of the API, ensuring efficient communication between systems.
This Open API specification serves as a standardized framework for describing and defining the capabilities of the Matrix Client-Server Cross Signing API. It outlines how clients can interact with the API, providing a structured approach to document endpoints, operations, and other integration details. This specification is intended to promote clarity, consistency, and ease of use for developers and consumers of the API, ensuring efficient communication between systems.
This Open API specification serves as a standardized framework for describing and defining the capabilities of the Matrix Client-Server Directory API. It outlines how clients can interact with the API, providing a structured approach to document endpoints, operations, and other integration details. This specification is intended to promote clarity, consistency, and ease of use for developers and consumers of the API, ensuring efficient communication between systems.
This Open API specification serves as a standardized framework for describing and defining the capabilities of the Matrix Client-Server Client Config API. It outlines how clients can interact with the API, providing a structured approach to document endpoints, operations, and other integration details. This specification is intended to promote clarity, consistency, and ease of use for developers and consumers of the API, ensuring efficient communication between systems.
This Open API specification serves as a standardized framework for describing and defining the capabilities of the Matrix Client-Server Content Repository API. It outlines how clients can interact with the API, providing a structured approach to document endpoints, operations, and other integration details. This specification is intended to promote clarity, consistency, and ease of use for developers and consumers of the API, ensuring efficient communication between systems.
This Open API specification serves as a standardized framework for describing and defining the capabilities of the Matrix Client-Server Client Config API. It outlines how clients can interact with the API, providing a structured approach to document endpoints, operations, and other integration details. This specification is intended to promote clarity, consistency, and ease of use for developers and consumers of the API, ensuring efficient communication between systems.
This Open API specification serves as a standardized framework for describing and defining the capabilities of the Matrix Client-Server Account Identification API. It outlines how clients can interact with the API, providing a structured approach to document endpoints, operations, and other integration details. This specification is intended to promote clarity, consistency, and ease of use for developers and consumers of the API, ensuring efficient communication between systems.
This Open API specification serves as a standardized framework for describing and defining the capabilities of the Matrix Client-Server Application Service Room Directory API. It outlines how clients can interact with the API, providing a structured approach to document endpoints, operations, and other integration details. This specification is intended to promote clarity, consistency, and ease of use for developers and consumers of the API, ensuring efficient communication between systems.
This Open API specification serves as a standardized framework for describing and defining the capabilities of the Matrix Client-Server Capabilities API. It outlines how clients can interact with the API, providing a structured approach to document endpoints, operations, and other integration details. This specification is intended to promote clarity, consistency, and ease of use for developers and consumers of the API, ensuring efficient communication between systems.
This Open API specification serves as a standardized framework for describing and defining the capabilities of the Matrix Client-Server Administration API. It outlines how clients can interact with the API, providing a structured approach to document endpoints, operations, and other integration details. This specification is intended to promote clarity, consistency, and ease of use for developers and consumers of the API, ensuring efficient communication between systems.
This Open API specification serves as a standardized framework for describing and defining the capabilities of the Matrix Client-Server Account Administrative Contact API. It outlines how clients can interact with the API, providing a structured approach to document endpoints, operations, and other integration details. This specification is intended to promote clarity, consistency, and ease of use for developers and consumers of the API, ensuring efficient communication between systems.
This Open API specification serves as a standardized framework for describing and defining the capabilities of the Matrix Application Service API. It outlines how clients can interact with the API, providing a structured approach to document endpoints, operations, and other integration details. This specification is intended to promote clarity, consistency, and ease of use for developers and consumers of the API, ensuring efficient communication between systems.
This Open API specification serves as a standardized framework for describing and defining the capabilities of the MATOOMA. It outlines how clients can interact with the API, providing a structured approach to document endpoints, operations, and other integration details. This specification is intended to promote clarity, consistency, and ease of use for developers and consumers of the API, ensuring efficient communication between systems.
The Masterpass v7 Checkout API provides checkout services for all Masterpass Wallets. This API can be used by Merchants and PSPs Contact Support: Name: No Contact Email: email@example.com
Card Based Consent - Transaction Notification Service - Inbound Contact Support: Name: API Support Email: apisupport@mastercard.com
API for the Mastercard Track Decision Engine Service (TDE). The goal of this API is to provide buyers optimized payment recommendations based on their preferences and the supplier they want to pay. Contact Support: Name: API Support Email: apisupport@mastercard.com
Mastercard Standard Currency Conversion Calculator provides access to daily cardholder currency conversion rates for cross-border payments where the transaction currency differs from the cardholder billing currency. Contact Support: Name: API Support Email: [apisupport@mastercard.com](mailto:apisupport@mastercard.com)
A brand agnostic direct-to-merchant or acquirer API that returns transaction or device or identity scores to help with pre-authorization and pre-authentication decisioning. Powered by cross-geography and global Networks. Using this API enables merchants/ acquirer to be able to catch fraud early on & reduce fraudulent transactions while improving their risk models. Contact Support: Name: API Support Email: apisupport@mastercard.com
The Places API is designed to provide access to rich, analytics-driven merchant location information to help understand the popularity, seasonality, and other trends of storefronts. Places API can provide details such as if a store supports near-field communication or if a restaurant is currently in business. A few key features of Places are finding merchant locations based on coordinates and identifying merchants that are popular with the locals, not just among tourists. Contact Support: Name: API Support Email: [apisupport@mastercard.com](mailto:apisupport@mastercard.com)
A collection of Mastercard-provided APIs for retrieving merchant metrics that help in making lending decisions. Contact Support: Name: API Support Email: apisupport@mastercard.com
A platform to calculate user's sustainability metrics Contact Support: Name: API Support Email: apisupport@mastercard.com
Onboard Risk Check is a comprehensive solution to help acquirers make more informed decisions during merchant onboarding. It uses the ICA(Interbank Card Association) to validate and submit an Inquiry, and return an IRN(Inquiry Reference Number) which is used to get the risk profile info. Contact Support: Name: API Support Email: apisupport@mastercard.com
This is the documentation for the Merchant matching APIs. There are two APIs one for single merchant search and another for multiple merchants search. There can be 5 concurrent requests per client (could accommodate additional 10 requests in the queue per client) for single search API and 1 request per client for multiple search API. The maximum number of queries allowed for one multiple search API request is 100. For identification at ElectrifAi's end, Mastercard will be providing an x-openapi-clientid in the header of each request. The x-openapi-clientid will be a unique identifier per client and will be used to segregate the requests. Please note that the data returned in the Sandbox environment is placeholder data. While the data types reflect what will be returned in a production request, the underlying matching algorithm is not accessed. Thus, responses in the sandbox environment may change between requests. Contact Support: Name: API Support Email: apisupport@mastercard.com
Provides rich information about a given merchant. The Merchant Identifier database has information about all businesses that accept Mastercard in supported countries. This API is typically used by the credit card industry to retrieve merchant details listed on payment card account statements. For example, if an Issuer wanted to look up CAFETERIA30020523CLEVELANDOH a merchant descriptor found on a cardholder’s statement, Merchant Identifier would present the information as follows: - Merchant Category: 5813 – FAST FOOD RESTAURANTS - Merchant DBA (Doing Business As) Name: CAFETERIA 30020523 - Street: 11100 EUCLID AVE - City: CLEVELAND - State: OH Postal Code: 44106 - Country: USA - UNITED STATES IMPORTANT: Please remove all spaces from the merchant descriptor before submitting your API request. Contact Support: Name: ADS Data Services Email: [ADS_Data_Services@mastercard.com](mailto:ADS_Data_Services@mastercard.com)
API to add or delete the merchants into the DS Platform. All request and response payloads are sent in the JSON (JavaScript Object Notation) data-interchange format. Each endpoint in the API specifies the HTTP Method used to access it. <br> __Authentication__ <br>Mastercard uses OAuth 1.0a with body hash extension for authenticating the API clients. <br>This requires every request that you send to Mastercard to be signed with an RSA private key. <br> A private-public RSA key pair must be generated consisting of <br> 1. A private key for the OAuth signature for API requests. It is recommended to keep the private key in a password-protected or hardware keystore.<br> 2. A public key is shared with Mastercard during the project setup process through either a certificate signing request (CSR) or the API Key Generator. Mastercard will use the public key to verify the OAuth signature that is provided on every API call.<br> An OAUTH1.0a signer library is available on [GitHub](https://github.com/Mastercard/oauth1-signer-java)<br> __The Merchant Enrollment API is provided in two environments__ <br>1. Sandbox (https://sandbox.api.mastercard.com) - Pre-production test environment containing the latest pre-release version of the real APIs, intended for full integration testing prior to moving to production. <br>2. Production (https://api.mastercard.com) - Full production environment containing the latest production API release.<br> Contact Support: Name: Service API Team name Email: apisupport@mastercard.com
Cardholder disputes usually begin when cardholders or issuers discover possible fraudulent charges or errors on accounts. Issuers and acquirers then attempt to resolve the fraudulent charges or errors by using Mastercom to navigate the dispute resolution cycle. The dispute resolution cycle includes: - Collaboration - First chargebacks - Second presentments - Pre-arbitration and arbitration cases - Pre-compliance and compliance cases - Fee collections For more information about the dispute resolution cycle, refer to [Dispute Resolution Cycle](https://developer.mastercard.com/mastercom/documentation/getting-started).
Helps acquirers identify potentially high-risk merchants before entering to a merchant agreement. Contact Support: Name: Match API Email: apisupport@mastercard.com
Mastercom Extended API Cardholder disputes usually begin when cardholders or issuers discover possible fraudulent charges or errors on accounts. Issuers and acquirers then attempt to resolve the fraudulent charges or errors by using Mastercom to navigate the dispute resolution cycle. The dispute resolution cycle includes - Collaboration - First chargebacks - Second presentments - Pre-arbitration and arbitration cases - Pre-compliance and compliance cases - Fee collections Contact Support: Name: API Support Email: [apisupport@mastercard.com](mailto:apisupport@mastercard.com)
Transactions details. Contact Support: Name: API Support Email: apisupport@mastercard.com
The Loyalty Catalog API provides the ability to retrieve the list of items and their details available for the requested program, which could enable a front-end interface for redemptions. Contact Support: Name: API Support Email: apisupport@mastercard.com
ID Verification provides the technology platform and operational service to perform real-time user identity verification for various use cases including financial services, healthcare, travel and education. Contact Support: Name: API Support Email: apisupport@mastercard.com
The Mastercard Installments Program is a unique and innovative Buy Now, Pay Later (BNPL) program that delivers greater choice at checkout, both in-store and online. It follows the Mastercard multi-party model with the introduction of an Installment Program Provider (IPP) role, and enables financial institutions, licensed lenders, FinTech, and BNPL players to offer a variety of flexible lending options to consumers across the Mastercard network through a seamless, digital experience. Contact Support: Name: API Support Email: apisupport@mastercard.com
ID For Trust Providers offer the technology platform and operational service to allow the secure storage and transmission of Digital Identity data from the user to the Relying Party after having been verified to a required level of assurance by an Identity Verification Provider. Contact Support: Name: API Support Email: apisupport@mastercard.com
This API lets you enter your merchant details for your organization, including for all of your sub-merchants. Using the Merchant Self Services API helps you onboard and integrate your company and all of your sub-merchants as quickly as possible.
The Enhanced Currency Conversion Calculator is a subscription-based service that provides access to Mastercard's current dates currency conversion rates as well as historical currency conversion rates. Additionally, the API provides access to European Central Bank (ECB) reference rates that European Economic Area (EEA) issuing customer may require for the purposes of compliance with EU Regulation 2019/518 Contact Support: Name: API Support Email: apisupport@mastercard.com
The Mastercard Blockchain REST/JSON API provides a foundation for prototyping blockchain applications and to become familiar with the principles of blockchain technology, all using an advanced, high-performance, blockchain implementation from Mastercard. The API allows you to specify your own transaction types and flows to meet any business need. A good guideline to using blockchain effectively is to first decide "What data is it that we need to share?". You will also want to check out our Smart Contract API as your functionality requirements get more complex. As your use case progresses, you will likely want to move from a fully hosted "Blockchain as a Service" solution to running your own nodes and value stores founded on our lower-level protocols and core services to truly leverage the power of this inherently distributed technology. Talk to us when you reach this point and wish to move towards a fully distributed, enterprise-grade solution. In this API, you will also find extens Contact Support: Name: No Contact Email: email@example.com
Donation platform APIs will enable API Consumers to register donors, store their cards and make donations (One-time, Monthly, Per-transaction) to different charities and programs running around the world. Contact Support: Name: API Support Email: apisupport@mastercard.com
An API to check the benefits a cardholder may have. A vendor can check if the cardholder is eligible for benefits. Contact Support: Name: API Support Email: apisupport@mastercard.com
This Open API specification serves as a standardized framework for describing and defining the capabilities of the Mastercard Create-Consent-3DS. It outlines how clients can interact with the API, providing a structured approach to document endpoints, operations, and other integration details. This specification is intended to promote clarity, consistency, and ease of use for developers and consumers of the API, ensuring efficient communication between systems.
This Open API specification serves as a standardized framework for describing and defining the capabilities of the Mastercard Consumer Clarity API. It outlines how clients can interact with the API, providing a structured approach to document endpoints, operations, and other integration details. This specification is intended to promote clarity, consistency, and ease of use for developers and consumers of the API, ensuring efficient communication between systems.
The Doconomy Aland Index API enables issuers to provide their consumers with visibility into the environmental impact based on their spending habits. This API allows an issuer to calculate the carbon footprint and water usage based on consumers’ payment transactions. This API can be used inside a banking application or website to provide meaningful and actionable insights. For additional documentation and use cases, go to [Mastercard Developers](https://developer.mastercard.com/product/doconomy-aland-index). Contact Support: Name: Mastercard Email: [apisupport@mastercard.com](mailto:apisupport@mastercard.com)
OpenAPI Specification for Carbon Calculator. For additional documentation and use cases, go to [Mastercard Developers](https://developer.mastercard.com/product/carbon-calculator). Contact Support: Name: API Support Email: apisupport@mastercard.com
OpenAPI specifications for the Carbon Calculator Experience API. This API allows Issuers to enroll their customers to the Carbon Calculator Experience platform so that they can get a carbon footprint for their transactions and provides them with an option to donate towards tree plantations In addition, this API also allows Issuers to retrieve carbon footprint aggregate data for their customers. <br/> --- * **All requests must be signed using OAuth 1.0a. Refer to the [Access Mastercard APIs](https://developer.mastercard.com/platform/documentation/using-oauth-1a-to-access-mastercard-apis/).** --- * **The Issuer must provide their user's card details and email address while enrollment. These details must be encrypted before entering transit. Refer to the [Payload Encryption](https://developer.mastercard.com/platform/documentation/security-and-authentication/securing-sensitive-data-using-payload-encryption/).** --- Contact Support: Name: API Support Email: apisupport@mastercard.com
BIN Lookup API Customers can retrieve account range information in an easy to access API that powers automated integrations without depending on acquiring partners. The API enables multiple use cases including; payment routing decisioning, improved decline logic, benefits validation, and issuer/product identification. Customers of the API also benefit from daily updates, which ensures their BIN information is always in sync with the latest updates. Customers can perform the following operations: - Fetch paginated list of BIN based account ranges - Perform search based on fields - Perform search based on account range Contact Support: Name: API Support Email: apisupport@mastercard.com
The Bill Payment Validator service allows RPPS origination (payment sender) customers to identify if a potential RPPS transaction would process successfully before transmitting the formal payment transaction, reducing RPPS payment rejects and costly payment processing exceptions. Contact Support: Name: Bill Pay Development Support Email: Bill_Pay_Development_Support@mastercard.com