Changelog

Filter by:

July of 2026

  • Mercado Pago CLI v1.0.5: Fixes and command removals
  • Fixed

    • "capture" parameter: now sent only when the "--capture" flag is passed. It was previously included in all "mpcli payments create" requests, affecting methods that don't support it and overriding "--data" values. Review your calls if you relied on it being sent automatically.
    • Financial reports: fixed the endpoints for "mpcli reports releases list" and "settlements list", which returned errors on accounts with existing reports.

    Removed

    • "listen", "trigger", "events", and "logs" commands: removed as they are not available for general use.

    Fix

    Mercado Pago CLI

    May of 2026

  • PSE is now available as a payment method in Checkout API via Orders
  • In Checkout API via Orders, we have included PSE (Pagos Seguros en Línea) as a payment method available for integration.

    PSE is the most widely used electronic payment system in Colombia, allowing consumers to make online purchases and pay bills directly from their checking or savings accounts (debit) in real time. It acts as a secure bridge between banks and merchants, eliminating the need for credit cards.

    In addition, we have also updated our API Reference to include PSE among the available payment methods, as well as its corresponding required parameters: additional_info.payer.ip_address (the buyer's IP address from which the payment is generated), config.online.callback_url (the URL to which the buyer will be redirected after completing the payment on the bank's page. It must not be null or empty and must be no longer than 512 characters), and transactions.payments.payment_method.redirect_url (the URL to which the buyer must be redirected to complete the payment flow on the selected bank's platform).

    Addition

    Checkout API

    API Reference

    April of 2026

  • Fix in Update card endpoint documentation in the Saved Cards API
  • We corrected the documentation for the Update card endpoint in the Saved Cards API to reflect the fields the request body actually accepts when updating a customer's card. The token field was removed, as the API does not accept it on this endpoint. The valid fields for the update are expiration_month, expiration_year, and cardholder (which includes name and identification).

    Fix

    API Reference

    Checkout API

    Subscriptions

    Checkout Bricks

    January of 2026

  • Update of the Orders API usage examples for Checkout API
  • We’ve updated the use case information for the Create order API to the Checkout API, now including one example for credit card payments and another for debit card payments.

    Update

    Checkout API

    API Reference