WhatsApp, ERP and payment integration: what it costs in 2026

Almost every system request ends with the same line: "and it needs to talk to WhatsApp, the ERP and payments." Fair enough. A system that doesn't share data with the rest of the company becomes one more screen for someone to copy and paste into.

The problem is that integration usually shows up in the quote as a single line, with no price of its own. And it has two very different costs: building it, paid once, and using it, which arrives every month on the bill from Meta, the gateway or the ERP. In this guide I split the two, with the official 2026 rates, so you can ask for a quote knowing what you're buying.

Why integration weighs so much

MuleSoft, Salesforce's integration company, surveyed more than 1,050 IT leaders for its 2025 connectivity report. The average company uses 897 apps, and only 29% of them are integrated. According to the same study, IT teams spend 39% of their time building custom integrations.

Those numbers come from large companies, but the picture holds for small and midsize ones. The difference is scale: instead of 897 apps, there are five or six. The ERP, the finance spreadsheet, the sales team's WhatsApp, the gateway that takes card payments. Each one holds a piece of the customer, and someone on the team bridges them by hand.

Integrating means taking that person out of the middle. And the cost of doing it depends on how many bridges exist, how many times a day data crosses them and how each vendor charges for usage.

WhatsApp: Meta charges per message, with new rules in October

The official WhatsApp integration runs through the WhatsApp Business Platform, Meta's API. It's not the WhatsApp Business app on your phone. It's what lets the system send order confirmations, appointment reminders, access codes and boletos without anyone typing.

Since July 1, 2025, Meta has charged per delivered message, according to its official pricing documentation. Messages a customer sends to the business are free. The ones the business sends fall into categories:

• Marketing: promotions, news, cart recovery. The most expensive.
• Utility: order confirmation, delivery notice, payment reminder.
• Authentication: a code to log in or confirm a transaction.
• Service: free-form replies within 24 hours after the customer wrote.

The change that hits the budget came on October 1, 2026. Meta started charging again for service messages, which had been free since November 2024. Now each number gets 1,000 free service messages per month, with no rollover to the next month. Utility messages sent inside the 24-hour window, which were also free, started being billed on the same date.

In its own documentation, Meta cites the utility and authentication rate for users in Brazil: about 0.68 US cents per message. Since July 2026, billing for Brazilian accounts can be in reais, issued by Facebook Brasil. And Meta warns it may change prices on the first day of each quarter, meaning up to four times a year.

One rule helps advertisers: when a customer arrives through a click-to-WhatsApp ad, a window of up to 7 days opens in which messages are free.

What this means if you're commissioning the system:

1. The flow sets the bill. An appointment reminder is utility. A "come back and finish your purchase" is marketing. The same integration can cost little or a lot, depending on what it triggers.
2. Service volume now has a price. If your company answers thousands of conversations a month, the bill that used to be zero isn't anymore.
3. Someone needs a card on file with Meta. A company with no payment method by September 30, 2026 risks having its messages cut off.

If the idea is a bot answering on WhatsApp, the AI cost adds to Meta's. I broke that math down in the article on what an AI agent for customer service costs.

Payments: fees per transaction, not per month

With a payment gateway, the integration itself is the predictable part. The cost that grows with the business is the fee on each sale. For an official reference, see Stripe's pricing in Brazil:

• Domestic card: 3.99% plus R$0.39 per transaction.
• International card: an extra 2% on the amount.
• Boleto: R$3.45 per paid boleto.
• Pix: 1.19% per paid Pix, invite-only for now.
• Monthly fee: none.

Other gateways charge different amounts, and some negotiate the fee based on volume. The point is the logic: in a system that sells R$100k a month by card, each percentage point of fee is worth R$1k a month. Choosing a gateway by integration price instead of fee is saving in the wrong place.

When deciding, ask:

• Which payment method do your customers use most: card, Pix or boleto?
• Will the system bill a monthly subscription or one-off sales?
• How many days until the money lands in your account?
• Does the gateway notify the system when a payment is approved, refunded or disputed?

That last question sounds technical, but it's what keeps a customer from paying while the order still says "pending."

ERP: the API limit shapes the design

The ERP integration is usually the most work, because that's where inventory, invoices, customers and finance live. Here the cost comes less from fees and more from what the ERP's API lets you do.

A concrete example: the Bling documentation, an ERP popular with small businesses, limits its API to 3 requests per second and 120,000 per day, per account. Past that, further requests aren't processed. Too many errors in a row block the system's address for 10 minutes, and anyone who keeps trying can be blocked indefinitely.

For a store with 200 products, that's plenty. For a system that syncs 30,000 inventory items several times a day, it changes the project: the integration needs a queue, updates for only what changed and automatic retries when the limit is hit. That's build work, and it goes into the price.

Before the quote, find out three things about your ERP:

1. Does it have a documented API open on your plan?
2. Which data can it read and which can it write?
3. What are the usage limits?

If the ERP has no API, the integration turns into file exchange or another workaround, and the cost goes up. Sometimes the honest answer is that the spreadsheet bridging things today is already the system you're missing. The guide on turning spreadsheets into a system shows where to start.

What drives the build cost up

The cost of building an integration doesn't depend on the vendor's brand. It depends on what it has to do:

• Direction: only sending data is simpler than sending and receiving.
• Frequency: real time costs more than once an hour.
• Volume: thousands of records a day call for a queue and rate limiting.
• Rules: what happens when the ERP's inventory and the system's don't match?
• Failures: what happens when WhatsApp, the gateway or the ERP goes down for an hour?

That last question is what separates an integration from a demo. Every API goes down, changes versions or changes prices. A well-built integration logs the error, retries and alerts someone. A poorly built one loses the order in silence.

How much this weighs on the system's total price is in our guide on what a custom web system costs.

How we do it at the Studio

At the Studio, the price is fixed after discovery, and the deadline is written into the contract. That's why it pays to come to that conversation with your list of integrations in hand: each bridge, what it sends, what it receives and what the vendor charges for usage.

The Meta, gateway and ERP accounts stay in the client's name, as do the code, files and access. The team that builds it is our in-house dev team. And every system we deliver ships with an AI agent that runs every day, flags failures, suggests improvements and checks that the data makes sense. In an integration, it's the one that notices when orders stopped coming in from the gateway or when the ERP's inventory no longer matches the system's.

One example of scale: LCX, a travel company operating in more than 10 South American countries, replaced one system per country with a single system, live in 29 days.

If your system needs to talk to WhatsApp, an ERP or payments, the next step is discovery for our custom system and SaaS development service, with every integration in the scope and the price.