Plan Mercado Pago Checkout Pro for your stores.

Why use Mercado Pago with Ordering.co

• Choose the active checkout path. Review Checkout Pro on the intended customer channel and store configuration.
• Configure the correct account. Identify the installed method and follow its returned account or credential fields.
• Scope marketplace fees deliberately. Confirm fee and allocation support for that variant and agreement before relying on it.
• Separate setup from payment results. Review project and store environment controls and use an approved test flow.

What Mercado Pago brings

Mercado Pago describes these capabilities of Checkout Pro:

• A hosted payment page where customers pay in Mercado Pago’s secure environment.
• Local payment options that vary by country, including cards and Mercado Pago account balance.
• Fraud prevention with 3DS 2.0 authentication and customer identity verification.

Marketplace fees

A marketplace fee, allocation between recipients and bank payout are separate parts of the money flow. If the installed method exposes a Marketplace Fee % field, confirm its supported behavior, recipient accounts, country eligibility and agreement. The setup guide does not establish automatic splitting or proportional refund deductions for every Mercado Pago variant. Verify the intended fee, payment, refund and settlement flow before using it in your commercial model.

Processing fees

Processing charges and payout timing follow the applicable Mercado Pago account and agreement. Confirm which account is charged, which receives the funds, and how adjustments and refunds are recorded for the installed variant.

Set up and go live

The Ordering.co Mercado Pago setup guide covers the Dashboard steps:

1. Open Stores → select a store → Payment methods and identify the active method. The catalog may offer Mercado Pago Checkout Pro while an existing method may be named Checkout-pro Mercadopago.
2. If the catalog offers installation, an administrator uses Install and completes the plugin setup before returning to the store.
3. If the installed variant has project configuration, review it in Settings → Apps & developers. Use the provider access token or environment controls that the plugin actually returns.
4. Open the method for the intended store and choose its test environment. If it shows Public Key, Access Token, Client ID and Client Secret, put the corresponding provider test values in their matching fields. Follow the actual form rather than assuming every variant has the same connection flow.
5. Review the selected channels and order types, save, and enable the method within the authorized test setup. Project mode and store mode are separate settings; review both deliberately.
6. Confirm the provider result in the approved test environment before planning production. Ask support to identify the variant if the catalog entry and existing method differ; a saved configuration alone does not prove authorization, refunds or settlement.

Keep Mercado Pago credentials private. Enter them only in the Dashboard or on Mercado Pago’s pages, never in emails, tickets, or shared documents.

More payment options

• Stripe Connect splits payments between a platform and its businesses with Stripe.
• Ordering Web is the ordering website where customers pay with Mercado Pago.

Evaluate Yape for orders in Peru

Mercado Pago’s Peru Checkout Pro overview, reviewed November 10, 2026, lists Yape among its payment options. The provider also documents a separate Yape flow for Checkout API. Checkout API and Checkout Pro are different integration products; provider support for one does not establish support in every connector.

This page concerns the Checkout Pro path in Ordering.co. Review Ordering Web and Customer App against the channels configured for the active store method. To evaluate Yape, confirm a Peru merchant account and matching application, the transaction and settlement currencies, and whether Yape appears for that account in the intended channel and checkout configuration. A generic Mercado Pago logo or a manual Yape transfer does not prove an automated Yape order-payment integration.

Include a successful payment, rejection or expiry, customer return, duplicated notification and refund in the proposed acceptance checklist. Verify the actual payment reference and order state rather than accepting a screenshot as proof. Ask who initiates the refund, where its status is recorded, whether the method supports the required refund operation, and when the customer receives it under the provider terms. Keep pending and refunded separate from paid. Use the Ordering.co setup guide and the account-specific provider terms to review the connection before enabling a live method.