mp-orders

Aggregate multiple payments under a single order via the Mercado Pago Orders API.

24|14|Updated Feb 24, 2026
One-click install
npx skills add https://github.com/mercadopago/mercadopago-claude-marketplace --skill mp-orders
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mp-orders
Source: https://github.com/mercadopago/mercadopago-claude-marketplace/tree/main/plugins/mercadopago/skills/mp-orders
Command: npx skills add https://github.com/mercadopago/mercadopago-claude-marketplace --skill mp-orders

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Mercado Pago orders are often split across multiple payments and channels, making reconciliation and lifecycle tracking complex. The mp-orders skill unifies online, offline, and QR payments under a single order, simplifying payment orchestration and visibility.

Core Features & Use Cases

  • Unified Orders API: Create an order with POST /v1/orders and attach one or more payments.
  • Orders + QR: Associate QR payments to the same order for in-store transactions.
  • Migration Path: Guidance for migrating from merchant_orders (legacy) to the Orders API.

Quick Start

Create an order via the Orders API and attach payments to cover the total amount.

Frequently Asked Questions about mp-orders

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I aggregate multiple payments under a single Mercado Pago order?

You can aggregate multiple payments by creating a unified order via the Orders API using POST /v1/orders and attaching one or more payments to cover the total amount. The mp-orders skill provides reference logic for this payment aggregation.

What is the best way to associate in-store QR payments with an online order?

To associate QR payments with an order, you can use the Orders API to link in-store QR transactions to the same unified order. This simplifies payment orchestration and lifecycle tracking across both online and offline channels.

How do I migrate from legacy merchant_orders to the unified Orders API?

Migrating from legacy merchant_orders to the Orders API involves transitioning to the POST /v1/orders endpoint to unify multi-channel payments. The skill provides specific guidance for this migration path to simplify reconciliation.

Can I track the lifecycle of an order that includes multiple payment methods?

Yes, lifecycle tracking for orders with multiple payment methods is supported through webhook-driven updates. The unified order structure aggregates these payments, providing clear visibility into the status of complex order scenarios.

Does the Mercado Pago Orders API support complex order scenarios across different channels?

Yes, the Orders API supports complex order scenarios by unifying online, in-store, and QR-enabled flows under a single order. This allows you to manage multiple payment methods and channels simultaneously.

Why should I unify my Mercado Pago payments instead of tracking them individually?

Unifying payments simplifies reconciliation and lifecycle tracking because it aggregates multiple payments and channels under a single order. This solves the complexity of managing fragmented payment data across online and in-store flows.