Webhooks - Notifications - Mercado Pago Developers
Which documentation are you looking for?

Do not know how to start integrating? 

Check the first steps


Webhooks (also known as web callback) is a simple method that makes it easy for an app or system to provide real-time information whenever an event happens, that is, it is a way to passively receive data between two systems through of an HTTP POST.

Webhook notifications can be configured for one or more applications created in your Developer Dashboard.

Once configured, the Webhook will be sent whenever one or more registered events occur, avoiding a search job every minute in search of an answer and, consequently, a system overload and data loss whenever there is some situation. After receiving a notification on your platform, Mercado Pago will wait for a response to validate that you received it correctly

In this documentation, we will explain the necessary settings to receive messages (through the Dashboard or when creating payments), in addition to showing the necessary actions that you must take for Mercado Pago to validate that the notifications were properly received.

Configuration via Dashboard

Below, we will explain how to: specify the URLs that will be notified, configure the events from which notifications will be received, validate that the notifications you receive are sent by Mercado Pago and simulate the receipt of various types of notifications.


Configure URLs and Events

  1. If you haven't done so already, create an application in the Developer Dashboard.
  2. Once the application is created, navigate to the Webhooks section in the "Application details" page and configure the production and test URLs where notifications will be received.
  3. If you need to identify multiple accounts, at the end of the indicated URL you can indicate the parameter ?customer=(sellername) endpoint to identify the sellers.
  4. Next, select the events from which you will receive notifications in json format via an HTTP POST to the URL specified above. An event is any type of update to the reported object, including status or attribute changes. See the events that can be configured in the table below.
Notification TypeActionDescription
paymentpayment.createdPayment creation
paymentpayment.updatedPayment update
mp-connectapplication.deauthorizedAccount unbinding
mp-connectapplication.authorizedAccount linking
subscription_preapprovalcreated - updatedSubscription
subscription_preapproval_plancreated - updatedSubscription plan
subscription_authorized_paymentcreated - updatedRecurring payment for a subscription
point_integration_whstate_FINISHEDPayment process completed
point_integration_whstate_CANCELEDPayment process canceled
point_integration_whstate_ERRORAn error occurred while processing the payment attempt
deliverydelivery.updatedShipping data and order update
delivery_cancellationcase_createdShipment cancellation request
topic_claims_integration_whupdatedClaims made by sales
  1. Finally, click Save to generate a secret signature for the application. The signature is a validation method to ensure that the notifications received were sent by Mercado Pago, therefore, it is important to check the authenticity information to avoid fraud.
The functionality of validating the secret signature through the x-signature header has been temporarily suspended due to technical instabilities. We are working on a new version of the solution to ensure effective validation of your notifications.

Setup while creating payments

It is possible to configure the notification URL more specifically for each payment using the notification_url field. See below how to do this using the SDKs.

  1. In the notification_url field, indicate the URL from which notifications will be received, as shown below.
$client = new PaymentClient();

        $body = [
            'transaction_amount' => 100,
            'token' => 'token',
            'description' => 'description',
            'installments' => 1,
            'payment_method_id' => 'visa',
            'notification_url' => 'http://test.com',
            'payer' => array(
                'email' => 'test@test.com',
                'identification' => array(
                    'type' => 'CPF',
                    'number' => '19119119100'


const client = new MercadoPagoConfig({ accessToken: 'ACCESS_TOKEN' });
const payment = new Payment(client);

const body = {
 transaction_amount: '100',
  token: 'token',
  description: 'description',
  installments: 1,
  payment_method_id: 'visa',
  notification_url: 'http://test.com',
  payer: {
    email: 'test@test.com',
    identification: {
      type: 'CPF',
      number: '19119119100'

payment.create({ body: body, requestOptions: { idempotencyKey: '<SOME_UNIQUE_VALUE>' } }).then(console.log).catch(console.log);


Payment payment = new Payment();

Identification identification = new Identification();

Payer payer = new Payer();



require 'mercadopago'
sdk = Mercadopago::SDK.new('YOUR_ACCESS_TOKEN')

payment_data = {
 transaction_amount: params[:transactionAmount].to_f,
 token: params[:token],
 description: params[:description],
 installments: params[:installments].to_i,
 payment_method_id: params[:paymentMethodId],
 notification_url: "http://requestbin.fullcontact.com/1ogudgk1",
 payer: {
   email: params[:email],
   identification: {
     type: params[:docType],
     number: params[:docNumber]

payment_response = sdk.payment.create(payment_data)
payment = payment_response[:response]

puts payment

using System;
using MercadoPago.Client.Common;
using MercadoPago.Client.Payment;
using MercadoPago.Config;
using MercadoPago.Resource.Payment;

MercadoPagoConfig.AccessToken = "YOUR_ACCESS_TOKEN";

var paymentRequest = new PaymentCreateRequest
   TransactionAmount = decimal.Parse(Request["transactionAmount"]),
   Token = Request["token"],
   Description = Request["description"],
   Installments = int.Parse(Request["installments"]),
   PaymentMethodId = Request["paymentMethodId"],
   NotificationUrl = "http://requestbin.fullcontact.com/1ogudgk1",

   Payer = new PaymentPayerRequest
       Email = Request["email"],
       Identification = new IdentificationRequest
           Type = Request["docType"],
           Number = Request["docNumber"],

var client = new PaymentClient();
Payment payment = await client.CreateAsync(paymentRequest);


import mercadopago
sdk = mercadopago.SDK("ACCESS_TOKEN")

payment_data = {
   "transaction_amount": float(request.POST.get("transaction_amount")),
   "token": request.POST.get("token"),
   "description": request.POST.get("description"),
   "installments": int(request.POST.get("installments")),
   "payment_method_id": request.POST.get("payment_method_id"),
   "notification_url" =  "http://requestbin.fullcontact.com/1ogudgk1",
   "payer": {
       "email": request.POST.get("email"),
       "identification": {
           "type": request.POST.get("type"), 
           "number": request.POST.get("number")

payment_response = sdk.payment().create(payment_data)
payment = payment_response["response"]


curl -X POST \
   -H 'accept: application/json' \
   -H 'content-type: application/json' \
   -H 'Authorization: Bearer YOUR_ACCESS_TOKEN' \
   'https://api.mercadopago.com/v1/payments' \
   -d '{
         "transaction_amount": 100,
         "token": "ff8080814c11e237014c1ff593b57b4d",
         "description": "Blue shirt",
         "installments": 1,
         "payment_method_id": "visa",
         "issuer_id": 310,
         "notification_url": "http://requestbin.fullcontact.com/1ogudgk1",
         "payer": {
           "email": "test@test.com"


  1. Implement the notifications receiver using the following code as an example:


 switch($_POST["type"]) {
     case "payment":
         $payment = MercadoPago\Payment::find_by_id($_POST["data"]["id"]);
     case "plan":
         $plan = MercadoPago\Plan::find_by_id($_POST["data"]["id"]);
     case "subscription":
         $plan = MercadoPago\Subscription::find_by_id($_POST["data"]["id"]);
     case "invoice":
         $plan = MercadoPago\Invoice::find_by_id($_POST["data"]["id"]);
     case "point_integrartion_wh":
         // $_POST contains the information related to the notification.
  1. Once the necessary settings have been made, the notification via Webhook will have the following format:
For the event type point_integration_wh the notification format changes. Click here to consult the documentation of Mercado Pago Point.
In the case of the delivery and topic_claims_integration_wh events, we will also have some different attributes in the response. Check the table below for these features.


 "id": 12345,
 "live_mode": true,
 "type": "payment",
 "date_created": "2015-03-25T10:04:58.396-04:00",
 "user_id": 44444,
 "api_version": "v1",
 "action": "payment.created",
 "data": {
     "id": "999999999"

This indicates that payment 999999999 was created for user 44444 in production mode with API version V1 and that this event occurred on date 2016-03-25T10:04:58.396-04 :00.

idNotification ID
live_modeIndicates if the URL entered is valid.
typeType of notification received (payments, mp-connect, subscription, claim, etc)
date_createdResorce creation date
user_idVendor UserID
api_versionIndicates if it is a duplicate notification or not
actionType of notification received, indicating whether it is the update of a resource or the creation of a new
data - idID of the payment, merchant_order or claim
attempts (delivery)Number of times a notification was sent
received (delivery)Resource Creation Date
resource (delivery)Type of notification received, indicating whether this is an update to a feature or the creation of a new one
sent (delivery)Notification sent date
topic (delivery)Type of notification received
resource (claims)Type of notification received, indicating notifications related to claims made by sales
  1. If you want to receive notifications only from Webhook and not from IPN, you can add in the notification_url the parameter source_news=webhook. For example: https://www.yourserver.com/notifications?source_news=webhooks

Actions required after receiving notification

When you receive a notification on your platform, Mercado Pago waits for a response to validate that you received it correctly. For that, you must return an HTTP STATUS 200 (OK) or 201 (CREATED). If this response is not sent, it will be understood that you have not received the notification and a further attempt to send it will be made until you submit the response.

In the table below you can find the main events, deadlines and waiting time for receiving new notification attempts.

EventDeadline after the first dispatchConfirmation waiting time
Shipping-22 seconds
First try15 minutes5 seconds
Second attempt30 minutes5 seconds
Third attempt6 hours5 seconds
Fourth attempt48 hours5 seconds
Fifth attempt96 hours5 seconds

After returning the notification and confirming its receipt, you will obtain the full information of the notified resource by accessing the corresponding API endpoint:

paymenthttps://api.mercadopago.com/v1/payments/[ID]check documentation
subscription_preapprovalhttps://api.mercadopago.com/preapprovalcheck documentation
subscription_preapproval_planhttps://api.mercadopago.com/preapproval_plancheck documentation
subscription_authorized_paymenthttps://api.mercadopago.com/authorized_paymentscheck documentation
point_integration_wh-check documentation
topic_claims_integration_whhttps://api.mercadopago.com/claim_resourcecheck documentation

Also, specifically in fraud alerts, you must not deliver the order and you will need to do the cancellation through the cancellations API.

In the notification, you will receive a JSON with the following information containing the payment id to cancel.


 "description": ".....",
 "merchant_order": 4945357007,
 "payment_id": 23064274473

You can also get more order information using the Get order API.

With this information, you will be able to carry out the necessary updates to your platform, such as updating an approved payment.