slug: mastercard provider: Mastercard generated_by: planning/capability-mapping/scripts/classify_capabilities.py model: claude-opus-5 frame: - Banking & Capital Markets min_confidence: 0.7 capability_model: source: https://github.com/vincentmakes/turbo-ea-capabilities license: CC-BY-4.0 attribution: Turbo EA Capabilities by Vincent Verdet — Turbo EA, https://github.com/vincentmakes/turbo-ea-capabilities, CC BY 4.0 notice: NOTICE edge_count: 23 edges: - tag: Cards spec_file: mastercard-cards-api-openapi.yml capability_id: BC-1340.60 capability_id_l1: BC-1340 capability_name: Card Issuance Management confidence: 0.95 evidence: POST /prepaid-cards createPrepaidCard 'Mastercard **prepaid Card Issuance** - Issue Prepaid Card to Existing or New Client'; 'MI Issuing supports the issuance of primary, supplementary, and add-on cards in digital and physical modes' reason: Operations create/issue debit and prepaid cards — plainly card issuance. - tag: Confirmed Fraud Management spec_file: mastercard-confirmed-fraud-management-api-openapi.yml capability_id: BC-1400.30 capability_id_l1: BC-1400 capability_name: Fraud Detection & Investigation Management confidence: 0.9 evidence: '''The Fraud and Loss Database (FLD) is the Mastercard_repository for fraud transactions''; PUT /issuer-frauds ''Change an Existing Fraud Record''' reason: Maintenance of confirmed fraud transaction records — fraud detection and investigation/reporting. - tag: Confirmed Fraud Submission spec_file: mastercard-confirmed-fraud-submission-api-openapi.yml capability_id: BC-1400.30 capability_id_l1: BC-1400 capability_name: Fraud Detection & Investigation Management confidence: 0.9 evidence: POST /mastercard-frauds submitMastercardFraud 'Add a New Fraud Record Using Minimal Input Parameters for Mastercard Built Transactions.' reason: Submission of confirmed fraud records to the Fraud and Loss Database is fraud case reporting/detection management. - tag: Fraud spec_file: mastercard-fraud-api-openapi.yml capability_id: BC-1400.30 capability_id_l1: BC-1400 capability_name: Fraud Detection & Investigation Management confidence: 0.9 evidence: PUT /fraud-states — "Delete an Existing Fraud Record or Confirm a Suspended Fraud Record"; GET /fraud-statuses/icas/{ica} — "Get Status of an Existing Fraud Record"; schemas SuspectedFraudStateChange, CardInPossession reason: Operations maintain and query fraud records on card transactions (suspected vs confirmed fraud), which is card/payment fraud detection and investigation, the core of financial crime fraud management. Not a homograph — the schemas explicitly model fraud state and card possession. - tag: Mastercard spec_file: mastercard-mastercard-api-openapi.yml capability_id: BC-1400.30 capability_id_l1: BC-1400 capability_name: Fraud Detection & Investigation Management confidence: 0.88 evidence: POST /mastercard-frauds — "Add a New Suspected Fraud Record"; "sends a potentially fraudulent transaction for review to the relevant issuer to determine if the suspected transaction is fraudulent or valid" reason: Although the tag is just the vendor name, the operations submit and update suspected fraud records for issuer investigation and confirmation, which is transaction fraud detection and investigation. Schemas SuspectedFraud and Fraud confirm the reading. - tag: Account Opening spec_file: mastercard-account-opening-api-openapi.yml capability_id: BC-1300.10 capability_id_l1: BC-1300 capability_name: Customer Onboarding Management confidence: 0.8 evidence: 'POST /openings retrieveAccountOpeningInsights Response will provide device, IP and user insights; schemas: AccountOpeningData, IPRiskScore, MatchToName' reason: Provides device/IP/identity risk insights at account opening, directly supporting customer onboarding and identity verification for account opening. recovered_from: capability-edges-sweep.json - tag: Aggregate spec_file: mastercard-aggregate-api-openapi.yml capability_id: BC-740.20 capability_id_l1: BC-740 capability_name: Climate & Carbon Management confidence: 0.8 evidence: GET /issuers/users/{userid}/aggregate-carbon-scores — "Fetches Monthly Aggregate Carbon Score for the Transactions Made for the Current Month"; schema AggregateCarbonScore reason: The operation computes a carbon score for a user's transactions, i.e. carbon footprint calculation and disclosure. That is Climate & Carbon Management; the title's bill-payment framing is spurious per the split-spec caveat. recovered_from: capability-edges-sweep.json - tag: Confirmations spec_file: mastercard-confirmations-api-openapi.yml capability_id: BC-1340.10 capability_id_l1: BC-1340 capability_name: Payment Initiation Management confidence: 0.8 evidence: POST /payment-requests/{payment_request_lifecycle_id}/payment-confirmation-advices confirmPaymentAdvice 'Mastercard Confirm Payment'; schemas Debtor, PaymentConfirmationAdvice, Payment, Amount reason: Confirmation/authorisation step of an account-to-account payment request; payment instruction confirmation fits Payment Initiation Management. - tag: Conversions spec_file: mastercard-conversions-api-openapi.yml capability_id: BC-1340.40 capability_id_l1: BC-1340 capability_name: Cross-Border Payment Management confidence: 0.8 evidence: '''access daily cardholder currency conversion rates for cross-border payments when the transaction currency differs from the cardholder''s billing currency''; GET /conversion-rate getConversionDetailUsingGET' reason: FX conversion rates for cross-border card transactions map to Cross-Border Payment Management (international payments, FX). - tag: Approvals spec_file: mastercard-approvals-api-openapi.yml capability_id: BC-1320.20 capability_id_l1: BC-1320 capability_name: Credit Underwriting & Decisioning Management confidence: 0.75 evidence: POST /approvals planApproval "Approve or decline an installment plan." — "Mastercard Installments program enables ... Buy Now, Pay Later (BNPL) players to offer installment plans ... utilizing either existing or new lines of consumer credit" reason: The operations decide (approve/decline) consumer installment-credit plans and report plan approval status, which is credit decisioning on a lending product rather than mere payment processing. - tag: Documents spec_file: mastercard-documents-api-openapi.yml capability_id: BC-1300 capability_id_l1: BC-1300 capability_name: Banking Customer Management confidence: 0.75 evidence: '''Add and Validate a Document - Confirm the details of a document.''; ''Add and Validate a Document - Resolve a conflict between identity attributes.''; vendor: ''helps businesses and organizations verify the identity of their customers''' reason: Operations perform identity document verification and identity-attribute confirmation for customers — clearly banking customer identity/due-diligence work. Ambiguous between onboarding identity verification (BC-1300.10) and KYC/CDD (BC-1300.20), so only the L1 is asserted. - tag: Payment Requests spec_file: mastercard-payment-requests-api-openapi.yml capability_id: BC-1340.10 capability_id_l1: BC-1340 capability_name: Payment Initiation Management confidence: 0.75 evidence: '''POST /payment-request-retrievals retrievePaymentRequest Mastercard Retrieve Payment Request Details.''; schemas NewPaymentRequestDetailRetrieval, DebtorAckForPaymentRetrieval, TransactionAcknowledgement' reason: Account-to-Account Commerce debtor-side retrieval of payment request details is part of capturing and authorising a payment instruction before it is executed, which is payment initiation management. - tag: Plans spec_file: mastercard-plans-api-openapi.yml capability_id: BC-1320 capability_id_l1: BC-1320 capability_name: Credit & Lending Management confidence: 0.75 evidence: '''POST /plans savePlan Notify Mastercard when a consumer chooses a previously presented offer, which is henceforth called as an Installment Plan.''; ''GET /plans/{plan_id} getPlan Retrieves Buy Now, Pay Later installment plan.''; schemas ScheduledRepayments, PlanInstallmentInformation' reason: Creation and retrieval of consumer BNPL installment plans with repayment schedules is credit and lending management. Left at L1 because the operations straddle origination (plan booking from an accepted offer) and servicing (schedule retrieval). - tag: Routing spec_file: mastercard-routing-api-openapi.yml capability_id: BC-1340 capability_id_l1: BC-1340 capability_name: Payments & Card Management confidence: 0.75 evidence: POST /isRoutingValid "Bill Payment Validator Service Returns the Processing Status for a Potential Rpps Transaction"; schema BillPayAccountValidation reason: Validates biller/account routing on the RPPS push bill-payment network before a payment is submitted — plainly payment initiation/processing within Payments & Card Management. Left L2 unset because the surface straddles initiation validation and processing routing. - tag: Transactions spec_file: mastercard-transactions-api-openapi.yml capability_id: BC-1400.30 capability_id_l1: BC-1400 capability_name: Fraud Detection & Investigation Management confidence: 0.75 evidence: '"businesses are faced with ensuring that customers experience smooth, frictionless, and secure commerce while balancing their risk of fraudulent transactions"; schemas IpRisk, EmailRiskScore, RiskFactor, TrustFactor, DeviceInsights' reason: The single operation retrieveTransactionInsights returns identity/device risk insights on card-not-present transactions — i.e. fraud screening/detection rather than payment execution. Maps to fraud detection; some ambiguity vs. card transaction fraud screening (BC-1340.70), so confidence held below 0.8. - tag: Lost Stolen spec_file: mastercard-lost-stolen-api-openapi.yml capability_id: BC-1340.60 capability_id_l1: BC-1340 capability_name: Card Issuance Management confidence: 0.72 evidence: POST /lost-stolen-cards — "Allows a consumer to replace a card that was lost or stolen, with a new card." reason: The operation replaces a lost or stolen payment card with a newly issued card, which is card issuance/replacement in the card lifecycle. Confidence tempered because card replacement requests are also a customer-servicing act (BC-1300.30), but the issuance of a replacement card is the substantive outcome. - tag: Verifications spec_file: mastercard-verifications-api-openapi.yml capability_id: BC-1300 capability_id_l1: BC-1300 capability_name: Banking Customer Management confidence: 0.72 evidence: POST /source-verifications/{issuing_country}/passports — "Verifies the details of a passport document with an identity verification provider"; "Add & Validate an Email Address Verify an OTP Code" reason: Operations perform identity document and contact-point verification (passport, driving licence, Medicare card, email/SMS OTP) building a verified identity record — customer identity verification within banking customer management. Ambiguous between onboarding/account-opening verification (BC-1300.10) and KYC/CDD (BC-1300.20), so only L1 asserted. recovered_from: capability-edges-sweep.json - tag: Benefit-Allocations-Card-Management spec_file: mastercard-benefit-allocations-card-management-api-openapi.yml capability_id: BC-1340.60 capability_id_l1: BC-1340 capability_name: Card Issuance Management confidence: 0.7 evidence: POST /cards cardReplacement Mastercard Replace Card Number for a Cardholder; PUT /cards freezeUnfreeze Mastercard Freeze/unfreeze a Card for Benefits reason: Operations perform card lifecycle actions — replacing a cardholder's card number and freezing/unfreezing a card — which is card issuance and card-status management rather than any employee-benefits capability. recovered_from: capability-edges-sweep.json - tag: Catalogs spec_file: mastercard-catalogs-api-openapi.yml capability_id: BC-420.40 capability_id_l1: BC-420 capability_name: Loyalty & Retention Management confidence: 0.7 evidence: '''A rewards program allows for the retrieval of catalogs or items based on search criteria''; GET /catalogs getCatalogs ''Returns a list of all rewards catalogs for a given program.''' reason: Rewards catalog retrieval for a loyalty/redemption program maps to Loyalty & Retention Management; some ambiguity as it is a catalogue-serving surface. - tag: Footprints spec_file: mastercard-footprints-api-openapi.yml capability_id: BC-740.20 capability_id_l1: BC-740 capability_name: Climate & Carbon Management confidence: 0.7 evidence: POST /transaction-footprints — "Mastercard Calculate Transaction Footprints"; "visibility into the environmental impact based on their spending habits" reason: The single operation computes a carbon/environmental footprint from payment transaction data, which realises carbon footprint calculation and climate disclosure rather than any payment-processing capability. Schema MCTransactionFootprint confirms the output is a footprint measure. Moderate confidence because the surface is a single calculation endpoint embedded in a card-issuer context. - tag: Lifecycle spec_file: mastercard-lifecycle-api-openapi.yml capability_id: BC-1340.20 capability_id_l1: BC-1340 capability_name: Payment Processing Management confidence: 0.7 evidence: POST /payment-requests/{payment_request_lifecycle_id}/status-retrievals — "Payment Request Status Retrieval Request"; POST .../refunds/{refund_request_lifecycle_id}/payment-confirmations — "Refund Payment Confirmation" reason: Despite the generic tag, the operations track account-to-account payment request status, refund account resolution and refund confirmations — processing and lifecycle handling of payment instructions. L2 payment processing chosen over initiation because the endpoints act on already-created payment requests; confidence 0.7 given the initiation/processing boundary is blurred. - tag: Sources spec_file: mastercard-sources-api-openapi.yml capability_id: BC-1300.10 capability_id_l1: BC-1300 capability_name: Customer Onboarding Management confidence: 0.7 evidence: '"Verifies the details of a passport document with an identity verification provider"; POST /source-verifications/{issuing_country}/driving-licenses' reason: Operations verify government identity documents against an identity verification provider — identity verification supporting account opening. Sub-capability could arguably be KYC/CDD, hence 0.7 rather than higher. recovered_from: capability-edges-sweep.json - tag: Transaction spec_file: mastercard-transaction-api-openapi.yml capability_id: BC-740.20 capability_id_l1: BC-740 capability_name: Climate & Carbon Management confidence: 0.7 evidence: POST /payment-cards/transaction-footprints/aggregates — 'Fetches carbon score for payment cards and aggregates the same on a weekly and monthly basis'; schemas TransactionFootprint, ClimateProfile reason: Despite the generic 'Transaction' tag, the operations compute and aggregate carbon footprints from card transaction data — a carbon measurement service rather than payment processing. recovered_from: capability-edges-gap.json