slug: mercado-pago
provider: Mercado Pago
generated_by: planning/capability-mapping/scripts/classify_capabilities.py
model: claude-opus-5
frame:
- Software & Technology
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: 4
edges:
- tag: Customers
  spec_file: mercado-pago-customers-api-openapi.yml
  capability_id: BC-420.10
  capability_id_l1: BC-420
  capability_name: Customer Data Management
  confidence: 0.75
  evidence: 'POST /v1/customers  createCustomer  Create A Customer; PUT /v1/customers/{id}  updateCustomer;
    schemas: Customer, CustomerRequest'
  reason: Straightforward CRUD and search over customer master records, which realises customer data management.
- tag: Subscriptions
  spec_file: mercado-pago-subscriptions-api-openapi.yml
  capability_id: BC-4240
  capability_id_l1: BC-4240
  capability_name: Subscription Lifecycle Management
  confidence: 0.75
  evidence: 'POST /preapproval  createSubscription  Create A Subscription; schemas: Subscription, SubscriptionRequest,
    AutoRecurring'
  reason: Create, search, read and update of subscriptions (preapprovals) with auto-recurring terms —
    subscription lifecycle management. Operations span creation and in-life modification, so the L1 is
    asserted without choosing a single sub-capability.
- tag: Payments
  spec_file: mercado-pago-payments-api-openapi.yml
  capability_id: BC-4250.40
  capability_id_l1: BC-4250
  capability_name: Payment Collection & Dunning
  confidence: 0.7
  evidence: 'POST /v1/payments  createPayment  Create A Payment; PUT /v1/payments/{id}/cancel  cancelPayment;
    schemas: PaymentCreateRequest, PaymentSearchResults'
  reason: Core payment creation, search and cancellation — payment authorisation and collection. BC-4250.40
    is the only candidate covering payment collection, though the frame's subscription-billing wording
    is an imperfect fit for a merchant acquirer.
- tag: Plans
  spec_file: mercado-pago-plans-api-openapi.yml
  capability_id: BC-4240.10
  capability_id_l1: BC-4240
  capability_name: Plan & Entitlement Design
  confidence: 0.7
  evidence: POST /preapproval_plan  createPlan  Create A Subscription Plan
  reason: Operations define and maintain recurring subscription plans (preapproval plans) with amount/frequency,
    which is plan definition for a subscription commercial model. Mapped to Plan & Entitlement Design,
    though the vendor's angle is recurring-payment plans rather than feature entitlements, hence moderate
    confidence.