# MD for: https://www.mercadopago.com.mx/developers/es/docs/checkout-pro/additional-content/notifications/ipn.md

\# IPN Instant Payment Notification (IPN) is a mechanism that allows your application to receive notifications from Mercado Pago informing about the status of a specific payment, chargeback, or \`merchant\_order\`, through an \`HTTP POST\` call to report on your transactions. > WARNING > > Important > > IPN notifications will be discontinued. Additionally, despite receiving the \`x-Signature\` header, they do not allow validation through the secret key to confirm they were sent by Mercado Pago. If you wish to perform this origin validation, we recommend migrating to \[Webhooks notifications\](https://www.mercadopago.com.mx/developers/en/docs/your-integrations/notifications/webhooks), which now also send the \`merchant\_order\` and \`chargebacks\` topics. IPN notifications can be configured in two ways: | Configuration mode | Description | |---|---| | \[Description configuration through Your integrations\](https://www.mercadopago.com.mx/developers/en/docs/your-integrations/notifications/ipn#bookmark\_configuration\_through\_your\_integrations) | Only \*\*one notification URL\*\* can be configured per account (depending on the application, more than one application can use this URL). | | \[Configuration during the creation of a payment, preference or order\](https://www.mercadopago.com.mx/developers/en/docs/your-integrations/notifications/ipn#bookmark\_configuration\_during\_payment\_creation) | This can be done using the \`notification\_url\` field. The URL can be different for each object. | In this documentation, we will explain the necessary configurations for receiving IPN notifications, as well as the required actions to ensure that Mercado Pago validates that the messages were properly received. ## Configuration through Your integrations Configure notifications directly in Your integrations efficiently and securely. ### Specify URLs and configure events To configure IPN notifications via Your integrations, it is necessary to specify the URLs where they will be received and specify the events for which you wish to receive notifications. > WARNING > > Important > > When configuring IPN notifications via Your integrations, you are setting up the URL and Events for \*\*all applications within your Mercado Pago account\*\*. To configure URLs and events, follow these steps: 1\. Access \[Your integrations\](https://www.mercadopago.com.mx/developers/panel/app) and select the application to enable notifications for your account. If you haven't created an application yet, access the \[Developer Dashboard documentation\](https://www.mercadopago.com.mx/developers/en/docs/your-integrations/dashboard) and follow the instructions to do so. 2\. In the left menu, click on \*\*IPN\*\* and configure the \*\*production URL\*\* that will be used to receive notifications. Keep in mind that you can also experiment and test whether the indicated URL is correctly receiving notifications, allowing you to verify the request, server response, and event description. !\[ipn\](https://www.mercadopago.com.mx/images/dashboard/ipn\_es\_v1.png) > NOTE > > Note > > If you need to identify multiple accounts, you can add the parameter \`?cliente=(sellersname)\` to the endpoint URL to identify the sellers. 3\. Select the \*\*events\*\* from which you want to receive notifications in JSON format via an HTTP POST to the URL specified earlier. An event can be any type of update on the reported object, including status changes or attributes. Refer to the table below to see the events that can be configured, considering the integrated Mercado Pago solution and its business specifics. | Events| Name in Your integrations | Topic | Associated products | |---|---|---|---| | Creation and update of payments | Payments | \`payment\` | \[Checkout API\](https://www.mercadopago.com.mx/developers/en/docs/checkout-api-payments/overview) (\*\*legacy\*\*)  
\[Checkout Pro\](https://www.mercadopago.com.mx/developers/en/docs/checkout-pro/overview)  
\[Checkout Bricks\](https://www.mercadopago.com.mx/developers/en/docs/checkout-bricks/overview)  
\[Subscriptions\](https://www.mercadopago.com.mx/developers/en/docs/subscriptions/overview)  
\[Mercado Pago Point\](https://www.mercadopago.com.mx/developers/en/docs/mp-point-legacy/overview) (\*\*legacy\*\*)  
\[Wallet Connect\](https://www.mercadopago.com.mx/developers/en/docs/wallet-connect/landing) | | Completion, cancellation or error processing payment attempts on Mercado Pago Point devices. | Point Integrations | \`point\_integration\_ipn\` | \[Mercado Pago Point\](https://www.mercadopago.com.mx/developers/en/docs/mp-point-legacy/overview) (\*\*legacy\*\*) | | Fraud alerts after processing an order | Fraud alerts | \`delivery\_cancellation\` | \[Checkout API\](https://www.mercadopago.com.mx/developers/en/docs/checkout-api-payments/overview) (\*\*legacy\*\*)  
\[Checkout Pro\](https://www.mercadopago.com.mx/developers/en/docs/checkout-pro/overview) | | Creation, closure, or expiration of commercial orders | Commercial orders | \`merchant\_order\` | \[Checkout Pro\](https://www.mercadopago.com.mx/developers/en/docs/checkout-pro/overview) | | Opening of chargebacks, status changes, and modifications related to the release of funds | Chargebacks | \`chargebacks\` | \[Checkout Pro\](https://www.mercadopago.com.mx/developers/en/docs/checkout-pro/overview)  
\[Checkout API\](https://www.mercadopago.com.mx/developers/en/docs/checkout-api-payments/overview) (\*\*legacy\*\*)  
\[Checkout Bricks\](https://www.mercadopago.com.mx/developers/en/docs/checkout-bricks/overview) | > WARNING > > Important > > If you have any questions about the topics to activate or the events that will be notified, consult the documentation \[Additional information about notifications\](https://www.mercadopago.com.mx/developers/en/docs/your-integrations/notifications/additional-info). 4\. Finally, click on \*\*Save\*\*. ## Configuration during payment creation During the process of creating a payment, preference or order, it's possible to configure the notification URL more specifically for each payment using the \`notification\_url\` field and implementing the necessary notification receiver. > WARNING > > Important > > It's not possible to configure notifications for the \`point\_integration\_wh\` topic using this method. To activate these topics, use \[Your integrations settings\](https://www.mercadopago.com.mx/developers/en/docs/your-integrations/notifications/ipn#bookmark\_configuration\_through\_your\_integrations). Next, we explain how to do this with the help of the SDKs. 1\. In the \`notification\_url\` field, specify the URL where notifications will be received, as shown in the example below. To receive notifications exclusively via Webhooks and not via IPN, you can add the parameter \`source\_news=ipn\` to the \`notification\_url\`. For example: \`https://www.yourserver.com/notifications?source\_news=ipn\`. > WARNING > > Do not use local domains in the \`notification\_url\` value, such as 'localhost/' or '127.0.0.1' with or without a specified port. We recommend using a server with a named domain (DNS) or an externally accessible development IP so that Mercado Pago can send notifications correctly. 

* [csharp ](#editor%5F5)
* [curl ](#editor%5F7)
* [java ](#editor%5F3)
* [node ](#editor%5F2)
* [php ](#editor%5F1)
* [python ](#editor%5F6)
* [ruby ](#editor%5F4)
php node java ruby csharp python curl 

```
<?php
  require_once 'vendor/autoload.php';

  MercadoPago\SDK::setAccessToken("YOUR_ACCESS_TOKEN");

  $payment = new MercadoPago\Payment();
  $payment->transaction_amount = (float)$_POST['transactionAmount'];
  $payment->token = $_POST['token'];
  $payment->description = $_POST['description'];
  $payment->installments = (int)$_POST['installments'];
  $payment->payment_method_id = $_POST['paymentMethodId'];
  $payment->issuer_id = (int)$_POST['issuer'];
  $payment->notification_url = `http://requestbin.fullcontact.com/1ogudgk1`;
  ...
  $response = array(
  'status' => $payment->status,
  'status_detail' => $payment->status_detail,
  'id' => $payment->id
  );
  echo json_encode($response);

?>
```

Copiar 

```
var mercadopago = require('mercadopago');
mercadopago.configurations.setAccessToken("YOUR_ACCESS_TOKEN");

var payment_data = {
 transaction_amount: Number(req.body.transactionAmount),
 token: req.body.token,
 description: req.body.description,
 installments: Number(req.body.installments),
 payment_method_id: req.body.paymentMethodId,
 issuer_id: req.body.issuer,
 notification_url: "http://requestbin.fullcontact.com/1ogudgk1",
 payer: {
  email: req.body.email,
  identification: {
  number: req.body.docNumber
  }
 }
};

mercadopago.payment.save(payment_data)
 .then(function(response) {
  res.status(response.status).json({
  status: response.body.status,
  status_detail: response.body.status_detail,
  id: response.body.id
≈ });
 })
 .catch(function(error) {
  res.status(response.status).send(error);
 });
```

Copiar 

```
MercadoPago.SDK.setAccessToken("YOUR_ACCESS_TOKEN");

Payment payment = new Payment();
payment.setTransactionAmount(Float.valueOf(request.getParameter("transactionAmount")))
  .setToken(request.getParameter("token"))
  .setDescription(request.getParameter("description"))
  .setInstallments(Integer.valueOf(request.getParameter("installments")))
  .setPaymentMethodId(request.getParameter("paymentMethodId"))
  .setNotificationUrl("http://requestbin.fullcontact.com/1ogudgk1");

Identification identification = new Identification(); 
identification.setNumber(request.getParameter("docNumber"));

Payer payer = new Payer();
payer.setEmail(request.getParameter("email"))
  .setIdentification(identification);
  
payment.setPayer(payer);

payment.save();

System.out.println(payment.getStatus());
```

Copiar 

```
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: {
  number: params[:docNumber]
  }
 }
}

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

puts payment
```

Copiar 

```
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
  {
  Number = Request["docNumber"],
  },
  },
};

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

Console.WriteLine(payment.Status);
```

Copiar 

```
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": {
  "number": request.POST.get("number")
  }
  }
}

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

print(payment)
```

Copiar 

```
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@testuser.com"

  }
  }'
```

Copiar 

2\. Implement the notification receiver using the following code as an example: \`\`\`php <?php MercadoPago\\SDK::setAccessToken("ENV\_ACCESS\_TOKEN"); $merchant\_order = null; switch($\_GET\["topic"\]) { case "payment": $payment = MercadoPago\\Payment::find\_by\_id($\_GET\["id"\]); // Get the payment and the corresponding merchant\_order reported by the IPN. $merchant\_order = MercadoPago\\MerchantOrder::find\_by\_id($payment->order->id); break; case "merchant\_order": $merchant\_order = MercadoPago\\MerchantOrder::find\_by\_id($\_GET\["id"\]); break; } $paid\_amount = 0; foreach ($merchant\_order->payments as $payment) { if ($payment\['status'\] == 'approved'){ $paid\_amount += $payment\['transaction\_amount'\]; } } // If the payment's transaction amount is equal (or bigger) than the merchant\_order's amount you can release your items if($paid\_amount >= $merchant\_order->total\_amount){ if (count($merchant\_order->shipments)>0) { // The merchant\_order has shipments if($merchant\_order->shipments\[0\]->status == "ready\_to\_ship") { print\_r("Totally paid. Print the label and release your item."); } } else { // The merchant\_order don't has any shipments print\_r("Totally paid. Release your item."); } } else { print\_r("Not paid yet. Do not release your item."); } ?> \`\`\` 3\. Once the configurations are done, Mercado Pago will notify that URL with two parameters every time a resource is created or updated. For example, if you set up the URL \`https://www.yoursite.com/notifications\`, you will receive payment notifications like this: \`https://www.yoursite.com/notifications?topic=payment&id=123456789\`. | Field | Description | | --- | --- | | \`topic\` | Identifies what the resource is, which could be \`payment\`, \`chargebacks\`, \`merchant\_order \` o \`point\_integration\_ipn\`. | | \`id\` | It is a unique identifier of the notified resource. | ## Necessary actions after receiving a notification When you receive a notification on your platform, Mercado Pago expects a response to validate that you received it correctly. To do this, you need to return an \`HTTP STATUS 200 (OK)\` or \`201 (CREATED)\` status. The \*\*waiting time\*\* for that confirmation is \*\*22 seconds\*\*. If this confirmation is not sent, the system will understand that the notification was not received and will \*\*retry sending every 15 minutes\*\* until a response is received. After the third attempt, the interval will be extended, but the attempts will continue. After responding to the notification and confirming its receipt, you can obtain the complete information of the notified resource by making a request to the corresponding API endpoint. To identify which endpoint to use, check the table below: | Topic | URL | Documentation | | --- | --- | --- | | payment | \`https://api.mercadopago.com/v1/payments/\[ID\]\` | \[Get payment\](https://www.mercadopago.com.mx/developers/en/reference/online-payments/checkout-api-payments/get-payment/get) | | point\_integration\_ipn| \`https://api.mercadopago.com/point/integration-api/payment-intents/{paymentintentid}\` | \[Search payment intent\](https://www.mercadopago.com.mx/developers/en/reference/integrations\_api/\_point\_integration-api\_payment-intents\_paymentintentid/get) | | merchant\_orders | \`https://api.mercadopago.com/merchant\_orders/\[ID\]\` | \[Get merchant order for Checkout Pro\](https://www.mercadopago.com.mx/developers/en/reference/online-payments/checkout-pro/merchant\_orders/get-merchant-order/get) or for \[QR Code (deprecated)\]() | | chargebacks | \`https://api.mercadopago.com/v1/chargebacks/\[ID\]\` | \[Get chargeback\](https://www.mercadopago.com.mx/developers/en/reference/online-payments/checkout-pro/get-chargeback/get) | With this information, you will be able to make the necessary updates to your platform, such as updating an approved payment.