ConversaLabs Help Center
en
Language
pt_BR Portuguese (Brazil) en English es Spanish

Payments overview

Open in
View as Markdown Open in ChatGPT Open in Claude
Conversa Labs

Conversa Labs

Last updated on Jun 27, 2026

Overview

The Payments module turns ConversaLabs into a billing counter inside the conversation itself. You connect a gateway (Asaas or Mercado Pago), create one-off, recurring or deal-based charges, and send the payment link right in the chat — with PIX (QR code + copy-and-paste), boleto and card (hosted checkout).

Everything happens without leaving the platform: the customer receives the charge in the same window where they talk to you, pays, and the status updates automatically when the gateway confirms the payment. You don't have to log into your bank's panel to follow up — ConversaLabs reflects paid, overdue, refunded and canceled in real time.

Prerequisites

  • The Payments module must be enabled for your account. It is optional and off by default — ask an administrator or the platform operator to turn it on.
  • An active account on a supported gateway: Asaas or Mercado Pago.
  • Administrator permission to connect the gateway and configure webhooks.
  • To charge from the CRM or the Calendar, those modules must also be enabled.

Step by step

  1. Make sure the Payments module is enabled for the account.
  2. Connect a gateway (Asaas or Mercado Pago) with your credentials and environment — see Connect a gateway.
  3. Create your first charge (one-off, from the catalog or from a deal) and send it in the chat.
  4. Track the charge status: pending, awaiting payment, paid, overdue or refunded.
  5. For recurring revenue, set up subscriptions and plans.
  6. Follow results in the reports (revenue, average ticket, MRR and churn).

Settings & options

  • Gateways: connect one or more gateways; each connection has its own environment (production or sandbox) and credentials.
  • Payment methods: PIX, boleto and card via hosted checkout. The availability of each method depends on the chosen gateway.
  • Charges: one-off, with line items, discounts and value adjustment.
  • Subscriptions and plans: recurring billing delegated to the gateway and mirrored on the platform.
  • Refunds: full or partial, depending on the gateway.
  • Reports: revenue by status, by gateway and by currency, average ticket, MRR and churn.

Use cases

  • Close a sale on WhatsApp and send the PIX right away, with QR code and copy-and-paste.
  • Charge a service from a deal won in the CRM, without retyping amounts.
  • Create a monthly subscription for a recurring customer.
  • Apply a one-time discount to a charge before sending it.
  • Require prepayment for a Calendar booking (paid scheduling).

Tips, limits & best practices

  • The module only works with hosted checkout — the platform never captures card data, which keeps you out of PCI scope.
  • Amounts are handled in major units (reais, not cents): R$ 49.90 is 49.90.
  • The webhook is the source of truth for status: trust it, not the checkout "success" screen.
  • Keep gateway credentials current; expired tokens stop new charges.

Troubleshooting

  • I don't see Payments in the menu: the module isn't enabled for your account or profile — talk to an administrator.
  • I can't create a charge: check that a gateway is connected and valid.
  • Status won't update: review the webhook setup in Refunds, webhooks and reports.

See also