## Overview

The charge is the heart of the module. You create a charge with an amount, a description and line
items, pick the method (**PIX**, **boleto** or **card** via hosted checkout) and send it right in the
conversation. The customer receives a payment card in the window itself — with the PIX QR code and
copy-and-paste string, the boleto barcode line, or the checkout link — and the status updates when
the gateway confirms.

There are three ways to start a charge: **one-off** (type the amounts), **from the catalog** (pick
ready-made products) or **from a deal** in the CRM (reuse the amount already recorded).

## Prerequisites

- A **connected**, valid gateway (see *Connect a gateway*).
- To charge from the catalog, the **Catalog** module enabled with products registered.
- To charge from a deal, the **CRM** module enabled and a deal with an amount.
- A contact with minimum data (name and, ideally, email and phone) for the gateway customer.

## Step by step

1. In a conversation, open the **create charge** action (or create one from the Payments area).
2. Choose the amount source:
   - **One-off**: enter amount, description and, optionally, line items.
   - **Catalog**: select products; the amount is summed automatically.
   - **Deal**: select a CRM deal; the amount is reused.
3. Select the **payment method**: PIX, boleto or card (hosted checkout).
4. (Optional) Apply a **discount** or adjust the value — see *Discounts and value adjustment*.
5. Set the **due date**, when applicable.
6. Create the charge. The platform generates the PIX (QR + copy-and-paste), the boleto (barcode line)
   or the checkout link, depending on the method.
7. **Send it in the conversation**: the payment card appears for the customer in the same window.
8. Watch the status move from pending to paid automatically once the gateway confirms.

## Settings & options

- **Methods**: PIX (QR code + copy-and-paste), boleto (barcode line/PDF) and card via **hosted
  checkout** — the platform never asks for the card number.
- **Line items**: describe each product/service with quantity and amount; the total is the sum of the
  lines.
- **Due date**: deadline for PIX/boleto.
- **Mark as paid manually**: record payments received off-platform (where the gateway supports it) to
  keep the history consistent.
- **Resend**: you can resend the payment card in the conversation at any time.

## Use cases

- Close a sale on WhatsApp and send the PIX right away.
- Build a charge with several items from the catalog.
- Charge a deal won in the CRM without retyping the amount.
- Let the customer choose between PIX and card.

## Tips, limits & best practices

- Amounts are in major units (R$ 49.90 = `49.90`); the total is the sum of price × quantity across
  the lines — never divide by 100.
- The **card** always goes through the gateway's hosted checkout: zero card data on the platform.
- Confirm the customer's name and contact before creating — the gateway uses that data to identify
  the payer.
- Don't trust the "success" screen: the real status arrives via the **webhook**.

## Troubleshooting

- **Error creating the charge**: check that the gateway is connected and the contact has the minimum
  data.
- **Customer didn't get the PIX**: resend the payment card in the conversation.
- **Paid but still pending**: review the webhook setup (see *Refunds, webhooks and reports*).
- **Method unavailable** (e.g., card): it may be a limitation of the chosen gateway — check the
  capability matrix in *Connect a gateway*.

## See also

- [Payments overview](/hc/ajuda/articles/payments-overview-en)
- [Connect a gateway: Asaas and Mercado Pago](/hc/ajuda/articles/payments-conectar-gateway-en)
- [Discounts and value adjustment](/hc/ajuda/articles/payments-descontos-en)
- [Subscriptions and recurring plans](/hc/ajuda/articles/payments-assinaturas-planos-en)
- [Refunds, webhooks and reports](/hc/ajuda/articles/payments-reembolsos-webhooks-relatorios-en)