Skip to main content
New

Support WhatsApp Business Accounts (WABA) in local currencies (CLP, ARS, COP) or allow the client's own payment method

Related product area:MessengerIntegrations & Apps & API
  • October 4, 2026
  • 1 comment
  • 14 views

Juan Carlos Pd.Md

Since 2026, Meta creates new WhatsApp Business Accounts (WABAs) in Chile and other Latin American countries in local currency (CLP, ARS, COP) by default. Meta does not allow changing a WABA's currency after it is created.

Manychat can only share its USD credit line with USD WABAs. As a result, businesses like mine with a WABA in CLP get "Credit line is not set up" and cannot:
- Reply to customers from the Manychat inbox
- Send message templates or broadcasts
- Reply to contacts who did not come from a Click-to-WhatsApp ad

Since October 1, 2026, Meta charges per service message, so this blocks a core part of our daily operations. I already added my own card as payment method in Meta Business for the WABA, but Manychat still requires its own credit line.

The only solution offered by support is to delete the number from the WABA and create a new one in USD. This is very risky for us: we would lose our approved templates, our messaging limit (10,000/day), our high quality rating, and we could affect our Click-to-WhatsApp campaigns, which have strong performance.

Requests (any of these would solve it):
1. Support WABAs in local currencies (CLP, ARS, COP, etc.)
2. Allow clients to use their own payment method in Meta instead of the Manychat credit line
3. Offer an official currency migration that keeps the same WABA, templates and quality rating

This affects more and more Latin American businesses as Meta rolls out local-currency billing. Other platforms already allow paying Meta directly with the client's card.

Thank you!

1 reply

Gustavo Boregio
Forum|alt.badge.img+7
  • Community Moderator & Expert
  • October 5, 2026

Hey ​@Juan Carlos Pd.Md from experience having done that, here’s what I can tell you has happened to us when we did it with our clients:

  • Approved templates are lost, you have to create them again, and they’re usually approved quickly.
  • Messaging limit stays and is not affected
  • Quality rating stays and is not affected
  • CTWA campaigns need to be checked/updated. Ideally I suggest pausing them, migrating and then reconnecting

From what I understand there’s a limitation on Meta’s side that the solution provider (Manychat) has to be the one with the credit line, so the only viable solution for now is to ‘migrate’ and have the credit line in USD with Manychat.

It’s a scary procedure, but from my experience, it works and so far it’s been safe (for me at least).

I agree with you though, it’d be great to have more flexibility here!

Hope this helps!