How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Mastercard Member API

The Member API from Mastercard — 6 operation(s) for member.

Mastercard Member API is one of 249 APIs that Mastercard publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Member. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, code examples, a changelog, a support channel, and a getting-started guide.

This API exposes 15 operations across 6 paths, and defines 39 schemas. It is described by OpenAPI 2.0, at version 1.0.

Requests are made against the base URL https://api.example.com.

15 operations 6 paths 39 schemas 3 DELETE5 GET4 POST3 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 2.0
API Version
1.0
Base URL
https://api.example.com
Resource Areas
1

Paths & Operations 15

Across 6 paths, the API surfaces 15 operations — 3 DELETE, 5 GET, 4 POST, 3 PUT. Each is listed below with its method, path, parameters, and response codes.

Member 15
POST
/alerts/merchants/{member_id}/acquirer-reference-ids
Mastercard Create Acquirer Reference Id Config.
createAlertsAcquirerReferenceIdConfig 4 params body → 200400401403404422default
PUT
/alerts/merchants/{member_id}/acquirer-reference-ids
Mastercard Update Acquirer Reference Id Config.
updateAlertsAcquirerReferenceIdConfig 5 params body → 200400401403404422default
GET
/alerts/merchants/{member_id}/acquirer-reference-ids
Mastercard Get Acquirer Reference Id Configs.
getAlertsAcquirerReferenceIdConfigs 8 params → 200400401403404default
DELETE
/alerts/merchants/{member_id}/acquirer-reference-ids
Mastercard Delete Acquirer Reference Id Config.
deleteAlertsAcquirerReferenceIdConfig 5 params → 200400401403404default
POST
/alerts/merchants/{member_id}/sub-merchants
Mastercard Create a Sub-merchant.
createAlertsSubMerchant 4 params body → 200400401403404422default
GET
/alerts/merchants/{member_id}/sub-merchants
Mastercard Get a List of Sub-merchants.
getAlertsSubMerchants 12 params → 200400401403404default
PUT
/alerts/merchants/{member_id}/sub-merchants/{sub_merchant_id}
Mastercard Update a Sub-merchant.
updateAlertsSubMerchantDetails 5 params body → 200400401403404422default
GET
/alerts/merchants/{member_id}/sub-merchants/{sub_merchant_id}
Mastercard Get a Sub-merchant.
getAlertsSubMerchantByGuid 5 params → 200400401403404default
PUT
/alerts/merchants/{member_id}/sub-merchants/{sub_merchant_id}/status-changes
Mastercard Change Sub-merchant Status.
updateAlertsSubMerchantStatus 5 params body → 200400401403404422default
POST
/alerts/merchants/{member_id}/sub-merchants/{sub_merchant_id}/card-acceptor-ids
Mastercard Create Sub-merchant Card Acceptor Id Config.
createAlertsCardAcceptorIdConfig 5 params body → 200400401403404422default
GET
/alerts/merchants/{member_id}/sub-merchants/{sub_merchant_id}/card-acceptor-ids
Mastercard Get Sub-merchant Card Acceptor Id Configs.
getAlertsCardAcceptorIdConfigs 9 params → 200400401403404default
DELETE
/alerts/merchants/{member_id}/sub-merchants/{sub_merchant_id}/card-acceptor-ids
Mastercard Delete Sub-merchant Card Acceptor Id Config.
deleteAlertsCardAcceptorIdConfig 6 params → 200400401403404default
POST
/alerts/merchants/{member_id}/sub-merchants/{sub_merchant_id}/card-acceptor-names
Mastercard Create Sub-merchant Card Acceptor Name Config.
createAlertsCardAcceptorNameConfig 5 params body → 200400401403404422default
GET
/alerts/merchants/{member_id}/sub-merchants/{sub_merchant_id}/card-acceptor-names
Mastercard Get Sub-merchant Card Acceptor Name Configs.
getAlertsCardAcceptorNameConfigs 8 params → 200400401403404default
DELETE
/alerts/merchants/{member_id}/sub-merchants/{sub_merchant_id}/card-acceptor-names
Mastercard Delete Sub-merchant Card Acceptor Name Config.
deleteAlertsCardAcceptorNameConfig 6 params → 200400401403404default

Schemas 39

The contract defines 39 schemas that model the data the API accepts and returns. The most detailed are AlertsSubMerchantResource (9 properties), AlertsCardAcceptorNameConfig (5 properties), Error (5 properties), ResponseHeader (4 properties). Each schema is shown below with its type and property counts.

AlertsCardAcceptorNameConfig
object
Card acceptor name configuration
5 properties 1 required
User
string
Username for the user creating or modifying a resource
AlertsSubMerchantResource
object
Response containing a specific sub-merchant with details
9 properties
AcquirerReferenceId
string
The acquirer BINs that a partner currently services under their portfolio. This is represented by Mastercard DE 31 - Subfield 2 (Clearing), DE 32 (Authorizatio…
AlertsAcquirerReferenceIdConfig
object
Acquirer reference id configuration
4 properties 2 required
CardAcceptorRegion
string
A sub-element of the merchant descriptor indicating either the state, province, or region of the merchant as it appears on the cardholder's statement. Value is…
MerchantStatus
string
Merchant Status must be one of - ACTIVATED, DEACTIVATED
AlertsCardAcceptorIdConfig
object
Map of acquirer reference id and the corresponding card acceptor id
3 properties 2 required
AlertsSubMerchantCreate
object
Request used to create sub-merchants
2 properties 2 required
LastName
string
The individual's last name
ResponseTime
string
Total response time in ms
AlertsMerchantConfigId
string
Internal Universally Unique Identifier (UUID) which uniquely identifies the merchants configuration
ErrorResponse
object
Error Response object
1 property 1 required
AlertsMerchantIdentifierConfigIdOnly
object
Merchant identifier configuration Id (referring to card acceptor id or name configuration)
1 property
Errors
object
Errors object
1 property 1 required
CardAcceptorCountry
string
A sub-element of the merchant descriptor indicating the country of the merchant as it appears on the cardholder's statement. Value is not case-sensitive and ca…
CreatedOrModifiedBy
object
Timestamp and user responsible for creation or modification of the resource
2 properties
AlertsAcquirerReferenceIdConfigs
array
Acquirer reference id configurations
UserId
string
The user id of the submitter/technical contact.
CardScheme
string
Name of card scheme may be one of - MASTERCARD, VISA or any other supported schemes
AlertsMerchantMemberId
string
Internal Universally Unique Identifier (UUID) which uniquely identifies the merchants
AlertsSubMerchantStatusUpdate
object
Request used to update sub-merchant status
1 property 1 required
CardAcceptorName
string
A sub-element of the merchant descriptor that contains the merchant's name or doing business as name as it appears on the cardholder's billing statement.
FirstName
string
The individual's first name
AlertsCardAcceptorNameConfigs
object
Card acceptor name configurations for a merchant
2 properties
CardAcceptorCity
string
A sub-element of the merchant descriptor indicating the merchant city/location as it appears on the cardholder's billing statement.
MerchantCategoryCode
string
A four-digit number listed in ISO 18245 for retail financial services. MCC is used to classify the business by the type of goods or services it provides.
MerchantType
string
Merchant Type must be one of - PARTNER, ACQUIRER, SUBMERCHANT
Timestamp
string
Timestamp of the creation or modification of the resource
MerchantName
string
Merchant's partial or full name.
AlertsPageableAcquirerReferenceIdConfigs
object
Pageable response containing acquirer reference id configurations
2 properties
AlertsPageableSubMerchantResource
object
Pageable response containing sub-merchants with their details
2 properties
AlertsAcquirerReferenceIdConfigUpdate
object
Acquirer reference id configuration for update
1 property 1 required
BinOnlyMatch
boolean
Indicates whether to use only acquirer reference ID (Acquirer BIN) for merchant matching
AlertsSubMerchantDetailsUpdate
object
Request used to update sub-merchant details
2 properties 2 required
CardAcceptorId
string
Identifies the card acceptor ID assigned by the acquirer. This ID must represent a unique identifier for each merchant name/location within the acquirer BIN. T…
ResponseHeader
object
4 properties
AlertsCardAcceptorIdConfigs
object
Card acceptor id configurations for a merchant
2 properties
Error
object
Error object
5 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

mastercard-member-api-openapi.yml Raw ↑

Other APIs Mastercard publishes across the network.

Mastercard Universal Specification Submission API
Mastercard Account to Account Commerce for Creditor Service Providers
Mastercard Debtor Service Provider Resources API
Mastercard Automatic Billing Updater API
Mastercard Benefit Eligibility Service API
Mastercard Bill Pay API
Mastercard Bill Payment Validator
Mastercard BIN Lookup API
Mastercard Business Payment Controls
Mastercard Carbon Calculator API
Mastercard Carbon Calculator Experience API
Mastercard Checkout Solutions
Where this information came from

This is an independent, third-party profile of Mastercard Member API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.