mp-checkout-bricks

Integrate Mercado Pago Checkout Bricks into Claude Code plugins for payment flows.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Integrates Mercado Pago Checkout Bricks into Claude Code plugins, enabling teams to build end-to-end payment experiences by coordinating Payment Brick, Card Payment Brick, Wallet Brick, and Status Screen.

Core Features & Use Cases

  • Modular brick components (Payment Brick, Card Payment Brick, Wallet Brick, Status Screen) that can be orchestrated in marketplaces and apps.
  • Supports Orders API automatic flow, 3DS handling, backUrls, and multi-country payment methods across MLA/MLB/ MLM/MCO/MLC/MPE/MLU.
  • Real-world use: a marketplace embeds a unified checkout to accept cards, wallets, and cash-like methods with post-payment status display.

Quick Start

Create a real Mercado Pago preference, configure initialization for the chosen Brick, and render the Brick in your frontend.

Frequently Asked Questions about mp-checkout-bricks

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

FAQPage Schema
How do I integrate Mercado Pago Checkout Bricks for end-to-end payment flows?

Integrate Mercado Pago Checkout Bricks by creating a real Preference ID, configuring initialization payloads for your chosen Brick, and rendering it in your frontend to handle the complete payment flow. The skill supports Payment, Card Payment, Wallet, and Status Screen Bricks.

Can I use multiple Mercado Pago Bricks together in a single checkout?

Yes, multi-brick orchestration allows you to combine Payment Brick, Card Payment Brick, Wallet Brick, and Status Screen within a single marketplace or app checkout experience to process cards, wallets, and cash-like payments.

Does the Mercado Pago integration support 3DS and country-specific payment methods?

Yes, the integration supports 3DS handling and multi-country payment methods across seven Mercado Pago markets, including MLA, MLB, MLM, MCO, MLC, MPE, and MLU, ensuring localized payment processing.

What is the best way to handle post-payment status display with Mercado Pago?

Use the Status Screen Brick to display post-payment status to users. It integrates with the Orders API automatic flow and backUrls configuration to provide structured transaction feedback after payment completion.

Why does my Mercado Pago Brick initialization fail without a Preference ID?

Brick initialization requires a real Preference ID generated server-side. The skill enforces proper creation of Preference IDs, correct initialization payloads, and callback handling to prevent integration errors and manage payment failures.