Direct answerMundpay talks to the seller's stack in two ways. Part of the toolset is native inside the platform, such as the integrated members area, the Meta Pixel per product, and UTM reports by country. What isn't native connects through webhooks and API, which send the sale event to virtually any external system. The names in the title (Nottaz, Hotzap, SMS, Funnels) are examples of categories of tool that connect to the gateway: members area, WhatsApp automation, SMS, and funnel builders. Since the list of connectors changes over time, confirm current availability with the Help Center or support.

Why Do Integrations Define the Productivity of Your Operation?

Every digital sale triggers a sequence of tasks after payment is approved: releasing product access, sending the welcome email or message, logging the lead in your database, marking the conversion in the ad manager. If every one of these tasks depends on you doing something by hand, the operation doesn't scale, it jams.

This is where integration stops being a technical detail and becomes a productivity lever. When the gateway notifies the other tools on its own, the buyer gets access in seconds, the relationship automation starts at the right moment, and your team stops running a spreadsheet. Human effort concentrates on what generates revenue, not on copying data from one system to another.

That's why the right question when choosing where to process payment isn't just about fees. It's about how many tools in your stack that gateway can talk to, and how easily. A poorly connected gateway costs you dearly in time, even with the lowest fee on the market.

Which Tool Categories Does a Seller Usually Connect?

Before talking about names, it's worth mapping the functions. Most digital product operations connect five types of tool around the checkout:

  • Members area: where the course, access, or content is hosted and delivered, with tools like Nottaz. It's what the buyer receives as soon as they pay.
  • WhatsApp automation: sending confirmation messages, access notifications, and recovery, with tools like Hotzap. It's the channel with the highest open rate in Brazil.
  • SMS: sending short messages for confirmation, boleto notice, or cart recovery, useful as a redundant channel to WhatsApp and email.
  • Funnel builders: sales, upsell, and thank-you pages, with tools like Funnels, which organize the journey before and after checkout.
  • Pixel and analytics: conversion tracking in the ad manager and reading traffic source, to know which campaign is actually selling.

Notice that the names mentioned are examples within each category, not a closed list. What matters is the function: each operation picks the brand it prefers within each type, and the next question is how the gateway connects to it.

How Does Mundpay Connect Each Category: Native or Webhooks and API?

Mundpay solves these connections in two layers, and understanding the difference avoids frustration when setting up your operation.

Native layer. Some functions already come inside the platform, no external tool needed. The integrated members area delivers course access within the same system that processed the payment. The Meta Pixel integrated per product marks the conversion in the ad manager with no workaround. And the UTM reports by country show the sale's origin without depending on a separate analytics tool. In the same native block are the Secret Order Bump and the one-click upsell, which act on the ticket inside the checkout.

Webhooks and API layer. For everything outside the native set, Mundpay offers webhooks and API integrations. The webhook is an automatic notification: when a sale is approved, the platform sends the order data to a URL you define, and the destination tool reacts instantly, whether it's a WhatsApp automation, an SMS send, or a funnel builder. The API allows the reverse path and scheduled reading of data. In practice, this layer is what lets you connect tools that don't have a ready-made connector.

In other words: the members area, the pixel, and the UTM you handle inside Mundpay; WhatsApp, SMS, and the funnel you connect by webhook. This combination is what makes the platform talk to the real stack of whoever is selling, and it's also what backs the consolidated-cost argument that comes up in the review of whether Mundpay is worth it.

Users spend most of their time on other sites. This means that users prefer your site to work the same way as all the other sites they already know.

Jakob Nielsen Source: Nielsen Norman Group.

What Do You Do When There's No Native Integration?

Not every tool on the market will have a ready-made connect button, and that's not a blocker. When there's no native connector for the specific brand you use, the path is the webhook. The general steps are simple:

  • Identify the event that matters. In most cases it's "sale approved," but it could be refund, chargeback, or subscription canceled, depending on what the destination tool needs to know.
  • Point the webhook to the destination. The external tool, or an orchestrator in between, receives the data and executes the action: releasing access, sending a message, logging the contact.
  • Test with one real, low-value sale. Before scaling, confirm the event arrives in the expected format and that the action happens. It's cheaper to fix with one transaction than with a hundred.

Honesty protects your operation here: since the details of each integration can change, don't assume a tool connects one way just because a similar one connects that way. Confirm the event format and the connection route before designing the entire flow on top of an assumption.

How Do You Confirm What's Available Today?

The list of native connectors evolves, and an integration that didn't exist yesterday may exist tomorrow, or change format. That's why the reliable source is never an article, it's the official, up-to-date channel. Before finalizing your operation's architecture:

  • Check Mundpay's Help Center to see integration documentation and the webhook and API walkthrough.
  • Talk to technical support through the Help Me page when you need to confirm a specific tool or ask for the exact format of the event sent.
  • Cross-check this with the payments and fees structure to know the total cost of the operation, not just the integrations.

Confirming before you build saves rework. A quick question to support is worth more than an entire flow built on top of an integration that needs to be done a different way.

In Short: Mundpay's Integrations

  • Mundpay connects the seller's stack in two layers: native features inside the platform and external integrations through webhooks and API.
  • Native features include the integrated members area, the Meta Pixel per product, and UTM reports by country, plus the Secret Order Bump and the one-click upsell.
  • The names Nottaz, Hotzap, SMS, and Funnels represent tool categories (members area, WhatsApp automation, SMS, and funnel builder), not confirmed native integrations.
  • When there's no native connector, the webhook sends the sale event to virtually any external system, and the API allows scheduled reads and actions.
  • Since the list of connectors changes, current availability should be confirmed with the Help Center or technical support before setting up the operation.

FAQ: Frequently asked questions on Mundpay integrations and tools

Which tools does Mundpay integrate with?

Mundpay connects the tool categories a digital sales operation usually needs: member area like Nottaz, WhatsApp automation like Hotzap, SMS dispatch, funnel builders like Funnels, and tracking. Some of this is native to the platform, like built-in member area, Meta Pixel per product, and UTM reports by country. What is not native can connect via webhooks and API. To confirm availability and details for a specific tool, check the Help Center or contact support.

Does Mundpay have native integration with Nottaz, Hotzap, or Funnels?

Nottaz, Hotzap, and Funnels are examples of categories sellers connect to a gateway: member area, WhatsApp automation, and funnel builder respectively. The way each one connects can change over time, so don't treat any as official native integration without checking. When there is no native connector, the standard path is webhooks and API, which let you send the sale event to almost any system. The practical recommendation is check current availability on the Help Center or with support before building your operation.

Demonstrate to people that you can help them by actually helping them.

Frank Kern Source: the author's material on Intent-Based Branding.

How do webhooks and Mundpay API work?

Webhook is an automatic alert: when an event happens, like an approved sale or a refund, Mundpay sends that data to a URL you define, and the destination tool reacts right away. API lets you do the reverse and read information on schedule. Together, webhooks and API make it possible to connect tools with no native integration, unlocking product delivery, message dispatch, or spreadsheet logging without manual work.

Does Mundpay have its own member area?

Yes. Built-in member area is a native Mundpay feature, letting you deliver course access within the same platform that processes payment, without relying on external tools just to host content. This cuts the number of subscriptions on your stack and shrinks the places where integration can fail. Still, if you prefer an external member area, you can connect it via webhooks and API.

How do you confirm if an integration is available at Mundpay today?

The list of native connectors and integration details evolve, so the trustworthy source is always Mundpay Help Center or direct contact with support. Before locking your operation's architecture, confirm whether the tool you use has a native connector or will be linked via webhooks and API, and ask for the event format sent. This way you avoid building a flow on integration assumptions that maybe need another approach.

How do you test a webhook before activating it in production?

The safe path is to run a test sale with low value, not zero, because some antifraud systems block penny transactions. Point the webhook to your target and monitor whether the event arrives in the expected format and whether the action happens right. Check the webhook log on the Help Center and confirm delivery status from Mundpay. If it fails, the log shows the error and returns from the destination tool. Once you confirm with a sale, confidence to turn it live at scale is much higher. If you don't want real money, ask support for a test environment or simulated transaction.

What is the time between sale approval and webhook dispatch?

The webhook fires practically in real time, in seconds after sale approval. In practice, when the buyer sees the success page, the event already left Mundpay and reached the destination tool. There is no purposeful delay in the architecture. Delays usually come from two sides: either the destination tool takes time to process the data (server slowness on their end), or there is connectivity trouble when the webhook tries to deliver. The Help Center offers logs that let you trace when Mundpay sent the event and whether the tool confirmed receipt. If the delay is not Mundpay's fault, support can help investigate the other side.