How to integrate your Mercado Pago account with systeme.io

In this article, you will learn how to integrate your Mercado Pago account with systeme.io.

You will need:

To connect your systeme.io account to your Mercado Pago account, click on your profile picture and then Settings (1). Next, in the menu on the left side of your page, click Payment Gateways (2).

In the payment gateways section, click Connect (3) for the Mercado Pago option.

In the popup that appears, you will be asked to fill in the API Public Key, Access Token, and Country fields:

To generate your production credentials, log into your account and follow these steps:

1) Generate the Mercado Pago credentials

1.1 On the main panel of your Mercado Pago account, click on Settings (1).

1.2 Click the Integrations (2) option.

1.3 Next, click Your integrations (3).

1.4 Create an Application to generate these credentials by clicking the Create application button (4).

A new screen will be displayed, where you must:

  • Assign a name to your application (5).

  • Select the Online Payments (6) option.

  • In the Select the platform where you will be doing the integration, select Other platforms (7).

Now, confirm the selected options:

  • Authorize the use of your personal data
  • Select the reCAPTCHA

Click Confirm (8).

1.5 Click on Enable Credentials (9).

1.6 To activate production credentials:

  • Select an industry (sector) that best applies to your business
  • Add your business website (optional)
  • Authorize the use of your personal data
  • Select the reCAPTCHA

Finally, click the blue Enable production credentials button (10).

1.7 Mercado Pago should now have generated the following production credentials:

  • Public Key
  • Access Token

These are the credentials you need to enter in your systeme.io account to connect your Mercado Pago account as a payment method:

Note: You will have one set of credentials for each tool you use.

1.8 After generating your application and credentials, go back to your systeme.io account, enter them, and click Save (11).

2) Configuring the IPN (Webhooks) in Mercado Pago

Once the integration is done, you will receive a webhook URL that must be entered into your Mercado Pago account dashboard to allow systeme.io to process payment events.

2.1 Copy the webhook URL provided by systeme.io during the previous integration step (1).

2.2 Log in to your Mercado Pago account and go to the developer panel (https://www.mercadopago.com.br/developers/en), then click on the application you created in the previous step.

In the left-hand menu, go to the Notifications section and click on Webhooks (2).

2.3 Next, click the Configure notifications (3).

2.4 Select the Production Mode tab to enter the URL of the webhook generated by systeme.io in the Production URL field (4).

In the Recommended events for integrations with Checkout Pro field, select the event Payments, and in the Other events field, select the option Plans and subscriptions (5).

Finally, click the Save settings (6).

A popup window will be displayed to save the webhook notification settings; click Save (7) to confirm the action.

To learn more about webhook configuration, we recommend you read this article.

Notes:

  • The fields "Email," "Last name," "First name," and "Tax number" are mandatory on your payment pages for a payment to be successfully processed by Mercado Pago.
  • Only one country can be selected to integrate a Mercado Pago account (Brazil, Colombia, Mexico, or Argentina).
  • Linking a Mercado Pago account allows you to create prices in the local currency of that account (e.g., Brazilian Reais, Colombian Pesos, etc.).
  • Due to Mercado Pago limitations, it is not possible to process refunds through our system.

What happens when a Mercado Pago payment fails?

  1. Cards: Three attempts will be made. The delay between each attempt cannot be modified. To find out the delay between each attempt, please contact Mercado Pago support.
  2. Boleto, Pix: There will be three attempts, spaced 7 days apart.
Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.