Connect Mercado Pago to Nevian

Time needed: about 10 minutesLast updated:

Connect Mercado Pago so sales and payment changes reach Nevian and can be matched to the visit that brought the buyer.

What you need

Availability. This connection is not available in this version of the panel yet. Use this guide to prepare the account settings; continue only when its named integration and credential fields appear in your workspace. Do not send its events to Custom or another provider URL.

  • A Mercado Pago account with permission to configure notifications.
  • An active Nevian plan and an owner, admin or member role. Viewers cannot connect integrations.
  • Keep the checkout and Nevian tabs open side by side.

Steps

  1. In Nevian, open Integrations → Add integration (Connect provider in an empty workspace), choose Mercado Pago and click Next with the platform open in another tab.

    Drawing: Connect Mercado Pago. 1 · Open platform: Have your account open in another tab; 2 · Copy the URL: Next creates your private connection URL

  2. Copy the complete Webhook URL. Keep it private and leave this window open while you configure Mercado Pago.

    Drawing: Connect Mercado Pago. Webhook URL: https://track.example.com/wh/mercadopago/••••••••; Webhook secret signature: Required account fields are saved with Next

  3. Open Suas integrações, choose the application used by your checkout, then Webhooks → Configurar notificações.

    Drawing: Mercado Pago · webhook configuration. Application: The application your checkout uses; Production mode URL: Paste the Nevian URL; Events: Payments · Order (Mercado Pago)

  4. Set the production destination URL, select payment and order notifications, and save. Copy the generated webhook signature secret and the same application’s production Access Token into the matching Nevian fields.

    Drawing: Mercado Pago · delivery settings. Destination: Your private Nevian Webhook URL; Scope: The products and events described in this step

  5. Return to Nevian, enter Webhook secret signature and click Next to save it before sending an event. Copy it from the same account and webhook you just configured.

    Drawing: Connect Mercado Pago. Webhook secret signature: ••••••••••••••••; Keep private: Never put account credentials in a page or ad link

  6. Use a test-user purchase. The dashboard simulator supplies a nonexistent payment ID, so a payment-not-found log from it does not prove order import. Test-user purchases and events with live mode off are recognized as tests by the prepared integration. Back in Nevian, look for Connected, then click Done.

    Drawing: Connect Mercado Pago. Connection: Connected; Last event: Received just now

Access Token is also required: a notification contains an ID, so the receiver needs to read the payment from the API. Keep this credential in the integration settings, never in a website or ad URL.

Check that it works

  • Open Logs → Webhooks and confirm the provider, order ID, event and result. A delivered webhook can be logged without creating a sale when the event is informational.
  • Pass the visit ID in external_reference when your server creates the preference or order. Payment links made in the Mercado Pago panel do not supply this notification flow.

Problems

Waiting for the first event…

Check the complete URL, event subscriptions and product scope. If you rotated the integration key, replace the URL in the provider too.

The call was rejected

Read the reason in Logs → Webhooks. Check the secret when one is configured, then resend the original event after fixing the configuration.

No matching click

Check the click ID instructions above on a real ad visit. A provider test usually has no ad click; that alone does not mean delivery failed.

Still stuck? Write to [email protected].

Images are our own drawings and configuration diagrams, not screenshots. Use the current values from your account; the examples contain no live credentials.