Sellium · WhatsApp payments

Collecting payments on WhatsApp:the payment link, right in the conversation

The sale closes in the chat and then the payment goes somewhere else: a message with bank details, a link someone builds by hand, a receipt nobody reconciles. An AI agent generates the payment link in the same conversation, confirms when the money comes in and records it in your ERP and CRM. Here is how it works, when it makes sense and when it does not.

The short answer

How do you collect a payment on WhatsApp without leaving the conversation?

To collect a payment on WhatsApp without leaving the conversation, an AI agent generates a payment link from your gateway (Mercado Pago, Stripe or the one you already use) for the exact order amount and sends it in the same chat. The customer pays on the gateway's secure page, the gateway reports the approved payment instantly and the agent confirms it and marks the order as paid in the ERP and the CRM.

Card details never go through the chat: the agent does not ask for them or receive them. Collecting in the conversation works for cash sales, deposits and reservations. For B2B customers on credit terms, the link is the exception: there the agent works with each customer's balance and payment terms.

The problem

What you lose when payment leaves the chat

A sales conversation on WhatsApp usually ends well: the customer confirms the order, accepts the price and asks how to pay. That is where a second process starts, almost always manual, and where sales that were already closed go cold.

Every step outside the chat is a chance for the customer to put it off. And in a purchase that is not urgent, what gets put off often never comes back.

  • Bank details by message: the customer transfers when they can, sends the receipt as a photo and someone has to find it in the bank statement.
  • Links built by hand: a rep logs into the gateway dashboard, copies the amount and pastes it, with the risk of getting the amount or the order wrong.
  • Payments nobody owns: the money comes in but nobody says so, the order stays pending and the customer asks twice whether it went through.
  • Manual reconciliation: finance matches payments to orders in a spreadsheet, days later.
  • After-hours sales: the customer decides at night and has nobody to ask for the link.
The gateways

Mercado Pago, Stripe or the gateway you already use

The agent does not replace your payment gateway: it uses it. It connects through the gateway's official API, creates the charge with the amount and the order reference, and listens for the payment status notification.

Which gateway fits depends on the country where you invoice and the payment methods your customers use. The mechanics are the same across all of them, and the table sums up how they work in the two most common ones.

GatewayHow it creates the chargeHow it reports the paymentHow it reconciles
Mercado PagoCreates a Checkout Pro payment preference with the details and the amount; the response includes the link the agent sends on WhatsAppA webhook notification every time the payment is created or changes status: approved, pending or rejectedThe external reference (your order number) travels with the payment
StripeCreates a Payment Link through the API with the products and the priceThe checkout.session.completed event when the customer completes the paymentAn order or customer reference that comes back in that event
The one you already useIf your gateway has a payments API, as MODO, Getnet or dLocal do, the flow is the sameA webhook or a payment status queryDefined during process mapping, before the quote

Mechanics per the Mercado Pago and Stripe developer documentation. Payment methods, installments and availability depend on your account and your country.

Native WhatsApp payments: WhatsApp has in-app payments only in a few countries, such as India and Brazil, according to Meta's documentation. Where they are not available, which is most of Latin America, the payment link is the way to go: it works with your gateway and the customer pays with a method they already know.

After the payment

Payment confirmation and reconciliation in the ERP and the CRM

Collecting does not end when the customer pays: it ends when the payment is matched to the right order. That is why every link carries the order reference, and the gateway's notification comes back with it.

With that reference, the agent does what a person checking the dashboard would do: confirms with the customer, releases the order and records the payment where finance will look for it. How the order gets into your system is covered in selling on WhatsApp with your ERP.

  • For the customer: a message with the confirmed payment, the order number and the delivery date, in the same conversation.
  • In the ERP: the order moves to paid and is ready to pick or invoice, with the gateway's transaction ID.
  • In the CRM: the opportunity closes as won and the payment lands on the customer record in Salesforce.
  • Pending or declined payment: the agent lets the customer know, offers another method or a new link and, if the customer goes quiet, follows up with an approved template.
  • For finance: the gateway's reports match the orders through the same reference, with no side spreadsheets.
When it fits and when it doesn't

When collecting on WhatsApp makes sense and when it doesn't

A payment link handles cash sales very well. In B2B sales on credit terms, though, most orders are not paid on the spot, and forcing a link there adds friction instead of removing it.

SituationPayment link in the chat?What the agent does
Cash sale to a new or retail customerYesSends the link for the total and confirms payment before releasing the order
Deposit or reservation: a machine, an appointment, goods set asideYesCollects the deposit and records the reservation with its expiration
B2B customer on credit terms with available creditUsually notChecks the balance and credit limit, enters the order on the agreed terms and does not ask for payment
B2B customer with an overdue balance or over the credit limitDepends on your policyReports the balance and, if your rule allows it, offers to settle it with a link or hands the case to collections
Bank transferNot neededShares your company's account details and records the receipt the customer sends so finance can apply it
Sale with financing that needs approvalNoHands off to the person who approves financing, with the full conversation

The rules per customer and per payment term are defined during process mapping, with your sales and finance teams.

Security

Security: the agent never asks for card details

The rule is simple: the card goes into the gateway, never into the chat. The agent sends a link to the Mercado Pago or Stripe payment page, and that is where the customer enters their details. Neither the agent nor your CRM ever sees the card number.

Beyond being good practice, it is what WhatsApp's business messaging policy asks for: do not request full payment card numbers, financial account numbers or ID numbers in the chat. And the gateways meet the PCI DSS security standard: Stripe, for example, is certified as a PCI Service Provider Level 1.

  • Fixed amount: each link is generated for one order and one amount; if the order changes, the agent generates a new one.
  • Links that expire: the link can be set to expire, so no old link is left floating around.
  • Verified source: gateway notifications are validated with their signature before anything is marked as paid.
  • Audit trail: every link, payment and message is recorded in the CRM, with date and owner.
Step by step

How an AI agent collects payment on WhatsApp, from order to recorded payment

Payment is the last step of the same conversation in which the customer asked, got a quote and ordered.

1

Closes the order

Confirms products, quantities, price and delivery against your price list and your inventory, before talking about payment.

2

Picks how to collect

Based on the customer and your rule: payment link, deposit, bank transfer or credit terms. On credit terms there is no link.

3

Generates the link

Creates the charge in your gateway for the exact amount with the order reference, and sends it in the same chat.

4

Listens for confirmation

The gateway reports by webhook when the payment is approved, pending or declined.

5

Confirms and records

Lets the customer know, marks the order as paid in the ERP and closes the opportunity in Salesforce.

6

Follows up on what's pending

If the payment does not come in, offers another method or writes again with an approved template, and hands special cases to a person.

Benchmarks

Public data on payment friction

Published figures to size how much each extra step at payment weighs. None of them is a Sellium result.

~70%

Of online shopping carts are abandoned before payment, on average

Source: Baymard Institute (2025)

19%

Of shoppers who abandoned a purchase at checkout did not trust the site with their card details

Source: Baymard Institute (2025)

18%

Of shoppers who abandoned a purchase at checkout did so because the process was too long or complicated

Source: Baymard Institute (2025)

1,000

Free service messages per number per month: they include the link and the confirmation the agent sends within the 24-hour window

Source: Meta for Developers (2026)

Caveats: Baymard's figures come from e-commerce studies (the abandonment reasons come from a survey of US online shoppers), not from WhatsApp or B2B sales; they are used as a reference for how much payment friction weighs. Meta updates its rates several times a year: check the current one in its documentation.

Frequently asked questions

Frequently asked questions about collecting payments on WhatsApp

What sales and finance teams ask before sending their first payment link on WhatsApp.

Can you collect payments on WhatsApp?

Yes. The most common way is to send a payment link from a gateway like Mercado Pago or Stripe in the same conversation: the customer pays on the gateway's secure page and the business gets the confirmation instantly. In-app WhatsApp payments exist only in a few countries, such as India and Brazil.

How do you send a Mercado Pago payment link on WhatsApp?

With the Mercado Pago API you create a payment preference with the order details and amount, and the response includes the link. Sellium does it on its own, on the spot, with the order reference, and sends it in the chat; when Mercado Pago reports the payment as approved, it confirms with the customer and records it.

Is it safe to pay with a link sent on WhatsApp?

Yes, as long as the link leads to the gateway's page and comes from the company's official number. The customer enters the card on Mercado Pago or Stripe, not in the chat, and the agent never asks for those details. It is best if each link is for a fixed amount and expires, so no old link keeps circulating.

How do I know the customer paid?

The gateway reports by webhook as soon as the payment changes status, and the agent updates the order and the CRM without anyone checking the dashboard. If the customer sends a screenshot of the receipt, the confirmation that counts is still the gateway's.

Does it work for customers on credit terms?

Usually it is not needed: a B2B customer on credit terms buys on the agreed terms and pays against the invoice. There the agent checks the balance and available credit before entering the order, and the payment link is kept for cash sales, deposits or settling an overdue balance if your policy allows it.

How much does it cost to collect payments on WhatsApp with Sellium?

Sellium is priced in two parts: an initial implementation quoted for each company, which includes the integration with your gateway, your ERP and your CRM, and a monthly subscription with expandable AI credits, with no lock-in. You pay for WhatsApp messages directly to Meta, on your own account and with no markup from us, and the fees on each payment are your gateway's. For your case, request a quote.

See how Sellium would collect in your conversations

Tell us which gateway you use, which ERP you run and how your sales split between cash and credit terms. We will show you the full flow, from confirmed order to recorded payment.