Quick answer
This guide teaches you how to use the Mundpay Generic Webhook to connect your sales in real time to any external tool, such as CRMs, course platforms (LMS), WhatsApp automation systems, spreadsheets or your own APIs, ensuring complete post-sale automation.
How to Integrate Any Platform via Generic Webhook
This guide teaches you how to use the Mundpay Generic Webhook to connect your sales in real time to any external tool, such as CRMs, course platforms (LMS), WhatsApp automation systems, spreadsheets or your own APIs, ensuring complete post-sale automation.
1. What is the Mundpay Webhook and why should I use it?
The Webhook is a tool for instant notification. Whenever an event occurs in your checkout, such as an approved sale, a Pix generated or a refund, Mundpay automatically sends a "data package" (JSON payload) to a URL you registered.
Why use it? It eliminates the need to check the dashboard manually and allows you to:
- Automatically grant access to member areas and courses.
- Send immediate messages on WhatsApp, such as welcome, billing or recovery messages.
- Update data on platforms like Zapier, Make, n8n or CRMs.
1.1. Step by Step: How to Configure the Webhook in the Mundpay Dashboard
- Access the Dashboard: In the Mundpay side menu, navigate to the Integrations section.
- Add the Integration: Go to "Generic Webhook".
- Click on "Connect Integration"
- Name your integration
- Select the products from which you will receive the events
- Set the Destination URL: Paste the address of the receiving platform, such as the Webhook link generated by Zapier, Make, n8n or your own server.
- Select the Events: Choose which stages of the sale you want to monitor. We recommend selecting all to track the entire customer lifecycle.
- Save: Click on Save to activate automatic sending.
2. What is the destination URL (Endpoint) that I should register?
The destination URL is the address of your server's system or the platform that will receive Mundpay notifications, such as [https://seu-sistema.com/webhook-vendas](https://seu-sistema.com/webhook-vendas) or the link generated by your flow in Make or Zapier.
3. Table of Sale Status and Recommended Actions
Understand the meaning of each status sent in the data package to configure your automations efficiently:
Status | What does it mean? | Recommended Action in Post-Sale |
|---|---|---|
| Abandoned Cart: The customer started registration but did not complete it. | Send an email or WhatsApp cart recovery message. |
| Awaiting Payment: Boleto or Pix (Brazilian instant payment system) generated, pending settlement. | Send a reminder with the Pix copy and paste key or barcode. |
| Approved Sale: Payment confirmed successfully! | Grant access to the product or service and send a welcome message. |
| Refused: The transaction was denied by the card issuer or anti-fraud system. | Offer another payment method or contact the customer for support. |
| Refunded: The sale amount was refunded to the customer. | Block access to the product or service and cancel subscriptions. |
| Chargeback: A dispute or purchase contestation opened by the buyer. | Suspend access and activate the chargeback defense team. |
| Canceled: Order canceled due to payment failure or error. | Record the reason for conversion analysis.
|
4. How to integrate with no-code platforms, such as Zapier, Make or n8n?
If you are not a developer, you can connect systems without writing a single line of code:
- In the no-code tool, such as Make or Zapier: Create a new scenario or zap and set the initial trigger to Webhooks, such as Custom Webhook or Catch Hook.
- Copy the URL: The platform will generate an exclusive webhook link, such as
[https://hook.us1.make.com/](https://hook.us1.make.com/).... - Paste into Mundpay: Insert this URL in the Mundpay dashboard following the step-by-step guide in Section 2.
- Send a Test: Make a test sale in checkout, or generate a Pix or Boleto so Mundpay sends the data in real time and the external tool recognizes the structure of the variables.
5. Technical Structure of the Data, JSON Payload
For developers who will directly consume the API in the backend, requests are sent via the POST method with the Content-Type: application/json header.
Example of the Payload sent:
JSON
{
"event": "paid",
"data": {
"transaction_id": "tx_987654321",
"status": "paid",
"amount": 19700,
"currency": "BRL",
"payment_method": "credit_card",
"customer": {
"name": "João da Silva",
"email": "joao@email.com",
"document": "12345678900",
"phone": "+5511999999999"
},
"product": {
"id": "prod_12345",
"name": "Curso Avançado de Tráfego"
},
"tracking": {
"utm_source": "google",
"utm_campaign": "campanha_natal",
"src": "afiliado_01"
},
"created_at": "2026-08-12T14:00:00Z"
}
}
Attention (Financial Values): The
amountfield is always sent in cents. In the example above,19700represents R$ 197.00.
6. How to test my integration before going to production?
To validate the operation without affecting your official system:
- Access the free website Webhook.site.
- Copy the Unique URL generated on the page.
- Register this temporary URL in Mundpay.
- Generate a Pix or complete a test in your checkout.
- See the data arriving in real time on Webhook.site to inspect the headers and the body of the request.
![]()
If your integration is already live, use this part to check what usually slips through: duplicate event delivery and signature verification. That is where almost every silent failure lives.
Wellington VicenteGlobal Payments Specialist
7. Security Validation and Best Practices, Level 2 Support
- Security Signature, HMAC SHA-256: To ensure that the requests were indeed sent by Mundpay and prevent spoofing attacks, we send the signature in the
X-Mundpay-Signatureheader. Validate this hash in your API using your secret key. - Fast Response, Status 200: Your server should respond to Mundpay with an
HTTP 200code within 10 seconds. We recommend receiving the notification, responding200 OKimmediately and processing heavier flows, such as sending emails or consuming third-party APIs, asynchronously. - Idempotency: Always use the
transaction_idfield as a unique key in your database to avoid reprocessing or access duplication in case of automatic webhook resend attempts.
Questions or advanced schema queries? Access ourOfficial Developer Documentation.
Updated on: 12/08/2026
FAQ: Frequently asked questions on generic webhook
What is a webhook and why should I use it?
A webhook is an instant notification tool that works like this: whenever an event occurs in your Mundpay checkout (such as an approved sale, a Pix generated or a refund), the platform automatically sends a package of data in JSON to a URL you registered. This allows you to automatically unlock access to member areas, send messages on WhatsApp, update data on platforms like Zapier and Make, all without manual action.
Where do I access the Generic Webhook configuration in Mundpay?
To configure the Generic Webhook, access the Mundpay side menu and navigate to the Integrations section. There you will find the Generic Webhook option. Click Connect Integration to start. You will be asked to fill in information such as integration name, products to receive events from, destination URL and the specific events you want to monitor.
We see our customers as invited guests to a party, and we are the hosts. It is our job every day to make every important aspect of the customer experience a little bit better.
How do I set the destination URL to receive notifications?
The destination URL is the address of your server system or the platform that will receive notifications from Mundpay. It can be a custom URL like https://your-system.com/webhook-sales or the link generated by your flow in Make or Zapier. This URL must be prepared to receive POST requests in JSON. If you are testing, you can use Webhook.site to generate a temporary test URL.
What sale statuses are sent in the webhook?
Mundpay sends notifications for various sale statuses: incomplete for abandoned cart, awaiting_payment for Boleto or Pix generated, paid for approved sale, refused for rejected transaction, refunded for reversal, chargedback for dispute, and canceled for cancelled order. For each status you can configure a recommended action in your post-sale.
How do I integrate the webhook with No-Code platforms like Make or Zapier?
In No-Code platforms, create a new scenario or zap and set the initial trigger as Webhooks, choosing the Custom Webhook or Catch Hook option. The platform will generate an exclusive webhook link. Copy this URL and paste it into the Mundpay panel following the integration step-by-step. After saving, perform a test sale so the platform recognizes the structure of the data being sent.
What is the importance of the security signature in the webhook?
The HMAC SHA-256 signature is essential for security. Mundpay sends this signature in the X-Mundpay-Signature header of each request. You should validate this hash in your API using your secret key to ensure that the requests were indeed sent by Mundpay and prevent spoofing attacks. This protects your system against fraudulent data.
What is the maximum time my server has to respond to the webhook?
Your server must respond to Mundpay with an HTTP 200 code within 10 seconds. It is recommended to receive the notification, respond immediately with 200 OK, and process heavier flows asynchronously. Also, always use the transaction_id field as a unique key in your database to avoid reprocessing in case of automatic retries.
![]()
A good integration is noticeable precisely because it never shows up: the sale lands, access opens and nobody files a ticket. Follow the steps to the end, including the part that looks obvious.
Wellington VicenteGlobal Payments Specialist
In short
How to Integrate Any Platform via Generic Webhook: This guide teaches you how to use the Mundpay Generic Webhook to connect your sales in real time to any external tool, such as CRMs, course platforms (LMS), WhatsApp automation systems, spreadsheets or your own APIs, ensuring complete post-sale automation.





