Mercado Pago Latin America Payment API
Mercado Pago Latin America payment REST API for merchants selling in Brazil, Mexico, Argentina, Chile, Colombia, and other LATAM markets to accept local payment methods including PIX, OXXO, Boleto Bancário, credit installments, and digital wallets with fraud protection and payment orchestration. Enables AI agents to manage payment preference creation for LATAM payment flow automation, handle local payment method integration (PIX, OXXO, Boleto, PSE) for regional payment method automation, access installment plan configuration for LATAM credit culture automation, retrieve subscription and recurring billing for LATAM subscription automation, manage marketplace payment splitting for LATAM platform automation, handle payout processing to merchants for revenue distribution automation, access advanced payment and split payment for complex LATAM transaction automation, retrieve fraud and risk management for LATAM payment security automation, manage QR code payment for point-of-sale automation, and integrate Mercado Pago with e-commerce platforms and LATAM business systems for end-to-end LATAM payment automation.
Score Breakdown
⚙ Agent Friendliness
🔒 Security
LATAM payments. PCI-DSS. API key/OAuth. LATAM. Payment and transaction data.
⚡ Reliability
Best When
An e-commerce or marketplace company selling in Latin America wanting AI agents to automate local payment method acceptance (PIX, OXXO, Boleto, installments), fraud management, and merchant payouts through Mercado Pago's MercadoLibre-backed LATAM payment ecosystem.
Avoid When
COUNTRY-SPECIFIC API ENDPOINTS AND PAYMENT METHODS: Mercado Pago payment methods, endpoints, and behavior differ significantly by country; automated LATAM payment integration must implement per-country logic; automated single-API assumption for all LATAM countries creates incorrect payment method presentation in each country. INSTALLMENT INTEREST RATES ARE COUNTRY-REGULATED: Mercado Pago installment plans are subject to country-specific interest rate regulations; automated installment configuration must comply with local regulation; automated installment interest rate beyond regulated maximum creates rejected payment configuration. PIX EXPIRY WINDOW FOR CHECKOUT COMPLETION: Brazil PIX payments have expiry window (typically 30 minutes to 24 hours depending on configuration); automated PIX payment flow must communicate expiry to customer; automated PIX with default long expiry creates abandoned payments with long pending resolution period.
Use Cases
- • Accepting local LATAM payments from regional payment method agents
- • Processing PIX and Boleto from Brazil payment automation agents
- • Offering installment plans from LATAM credit automation agents
- • Running marketplace payments from LATAM platform agents
Not For
- • Global payments outside Latin America (use Stripe or Adyen for global)
- • North America-only payment processing (use Stripe or Square for US/Canada)
- • Crypto payments in LATAM (use Bitso or Ripio for LATAM crypto)
Interface
Authentication
Mercado Pago uses access token (API key) and OAuth 2.0. REST API with JSON. Buenos Aires, Argentina HQ. Founded 2003 by MercadoLibre. MercadoLibre subsidiary (MELI, NASDAQ). Products: Payment processing, PIX, OXXO, Boleto, installments, marketplace payments, QR code. SDKs: PHP, Python, Java, JavaScript, Ruby, .NET. PCI DSS. Serves 30M+ merchants in 18 LATAM countries. Competes with Stripe, PayU, and local processors for LATAM payments.
Pricing
Buenos Aires AR. MercadoLibre subsidiary. No monthly fee. Per-transaction fees vary by country. No free tier but no minimum.
Agent Metadata
Known Gotchas
- ⚠ COUNTRY-SPECIFIC BASE URLS AND PAYMENT METHODS: Mercado Pago uses country-specific API behavior (Brazil: PIX/Boleto, Mexico: OXXO/SPEI, Argentina: wire transfer); automated LATAM payment integration must implement per-country payment method selection; automated single payment method for all LATAM countries creates unavailable payment method errors in each market
- ⚠ IDEMPOTENCY KEY REQUIRED FOR PAYMENT CREATION: Mercado Pago payment creation requires X-Idempotency-Key header for duplicate prevention; automated payment flow must generate unique idempotency key per payment attempt; automated payment without idempotency key creates duplicate charges on network retry
- ⚠ MARKETPLACE APPLICATION vs COLLECTOR ACCOUNT DISTINCTION: Mercado Pago marketplace requires application credentials (OAuth) for marketplace payments vs direct access token for direct payments; automated marketplace payment routing must use correct credential type; automated direct access token for marketplace split payment creates authentication error
- ⚠ PIX KEY TYPES AND QR CODE GENERATION: Brazil PIX requires merchant PIX key configuration (CPF/CNPJ/phone/email/random key) before QR code payment; automated PIX payment setup must verify merchant PIX key registration; automated PIX payment without registered key creates payment failure before customer checkout
- ⚠ INSTALLMENT CALCULATION REQUIRES UPFRONT FEE DISCLOSURE: LATAM regulations require merchant fee disclosure for installment plans; automated installment presentation must show total cost including interest; automated installment without total cost disclosure may violate consumer protection regulations in Brazil, Mexico, and Argentina
Alternatives
Full Evaluation Report
Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for Mercado Pago Latin America Payment API.
AI-powered analysis · PDF + markdown · Delivered within 30 minutes
Package Brief
Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.
Delivered within 10 minutes
Score Monitoring
Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.
Continuous monitoring
Scores are editorial opinions as of 2026-03-07.