Black Friday: From Payment Link Sent to Payment Confirmed

Key takeaways

A link sent is not a sale; only a payment confirmed at the source (gateway, bank, or card terminal) counts as revenue.
Separate pending payments by reason: indecision, technical error, delivery question, or lack of trust call for different answers.
Never ask for the full card number, password, or authentication code over WhatsApp; offer another payment method.
According to Reclame Aqui (Brazil's consumer complaints site, 2025), there were more than 400 scam alerts during Black Friday; customers distrust links, and the message needs to reduce that.
Stop all reminders the moment the payment is confirmed and record the sale value in the CRM.

Why is a link sent not a sale?

Because the link only opens the possibility of paying; the sale exists when the money is confirmed by the payment source. Teams that mark "sold" when sending the link inflate Friday's result and discover the hole in Monday's reconciliation.

November's volume makes the mistake expensive. According to Confi Neotrust (2025), Black Friday closed with 21.5 million orders in Brazilian e-commerce, 16.5% more than in 2024, with a falling average order value. More and smaller orders: every pending manual confirmation becomes a queue.

Decision rule: if the sale does not show as paid at the source, it is a pending payment, not revenue. If it shows as paid, it is an order, and the next contact is post-sale, described in post-Black Friday: from order to relationship.

What are the three statuses the team needs to separate?

The three statuses are proposal sent, payment pending, and payment confirmed. Each has an owner, a deadline, and an action; no conversation sits in a limbo called "negotiating."

Status	What it means	Team action	Deadline to act
Proposal sent	Customer received the link, with no click or no reply	Follow-up by pending issue (question, delivery time, decision)	2 to 6 h, within the 24-hour window
Payment pending	Customer tried to pay and did not complete it, or chose boleto (Brazilian bank slip) or Pix (Brazil's instant payment system) and did not pay	Ask at which step the error happened; offer an alternative method	Within 1 h of the report
Payment confirmed	Payment source shows approved	Record the value, stop reminders, send order confirmation	Immediate

Decision rule: if the customer did not reply at all after the link, treat it as proposal sent and use the cadence from follow-up without pressuring. If they wrote "it gave an error," treat it as payment pending and reply within 1 hour: a technical error goes cold faster than indecision.

How to send the right link the first time

The right link has the agreed price, visible conditions, and a clear expiration, and goes to a customer who has already chosen the item. Checklist before sending:

Same price as the advertised offer. Under art. 30 of the Brazilian Consumer Protection Code (CDC, Law 8.078/1990), the offer binds the seller. A link with a value different from the ad is a guaranteed pending payment.
Total price, shipping, and delivery time written in the message, as required by Decree 7.962/2013 (Brazil's e-commerce decree).
Expiration of the link and of the offer with real date and time.
Company name visible in the link's domain. With more than 400 scam alerts recorded by Reclame Aqui (2025), a shortened link with no identification is a legitimate reason not to pay.
Item and variant confirmed ("blue T-shirt, size M, 2 units") before generating the link.
Conversation source recorded in the CRM, to know which ad brought the person who paid.

If the offer is still not clear enough to fit in a message with a total price, the problem comes before the link; see how to build a clear offer on WhatsApp.

What to do when the customer says there was an error?

Ask at which step the error happened and offer an alternative path; do not ask for card data to "try it from here." The rule protects the customer and the company.

If the error was on the payment page (link does not open, blank page): resend the link and ask them to try another browser. If it persists, generate a new link.
If the error was in card approval (declined, limit): offer Pix or another card. Do not ask the reason for the decline; the customer rarely knows and feels exposed.
If the customer chose boleto or Pix and did not pay: confirm the expiration and ask whether they prefer another method. A boleto on Black Friday has a high chance of expiring unpaid.
If the customer asks to pay "off the books" (transfer to a personal account): decline and explain that only official methods count. This prevents scams against both sides.

Never ask for the full card number, security code, password, or authentication code over WhatsApp. If the customer sends it on their own, delete the message and guide them to use the link.

How to reconcile and close the pending payment

Reconciling is checking, at the payment source, that the money came in, and only then changing the status to confirmed. A screenshot is not reconciliation. Four-step flow:

The payment source (gateway, bank, card terminal, or checkout platform) shows the payment approved.
The team records the sale value in the CRM, in the customer's conversation. In a CRM with attribution, such as RASTRO, this record is what links the sale to the originating ad and sends it to Meta through the Conversions API, with duplicate control.
All payment reminders stop. If there is an automated cadence, it must be interrupted by the sale record, not by someone remembering to switch it off.
The customer receives a confirmation with item, value, delivery time, and tracking channel.

Decision rule: if the payment was confirmed but the source is not available, record the sale without a source. Do not attribute it to an ad by guesswork; the dashboard shows "no source" and the number stays honest. That send to Meta runs through the Conversions API for WhatsApp sales.

Hypothetical example: 50 links sent

The numbers below are hypothetical and show the reasoning, not an expected result.

Base. 50 links sent on Friday; 12 paid by the end of the day. Immediate conversion = 12 ÷ 50 = 24%.
Classification of the 38 pending. 14 with no reply (proposal sent), 10 with a reported error, 8 with an unpaid boleto or Pix, 6 with a delivery-time question.
Action by group. Reported error: reply within 1 hour with Pix as an alternative, 6 pay. Boleto/Pix: expiration reminder, 3 pay. Delivery-time question: reply with the real delivery time, 3 pay. No reply: two-touch cadence, 3 pay.
Result. 12 + 6 + 3 + 3 + 3 = 27 paid. Final conversion = 27 ÷ 50 = 54%.
Revenue. 27 × average order value of R$ 150 = R$ 4,050, versus R$ 1,800 if the team had stopped at the initial 12.
Reading. The "reported error" group converted 6 ÷ 10 = 60% with one simple action; start there.

Common mistakes when recovering payments

Resending the same link without asking anything. If the problem is price, trust, or a technical error, the second link lands in the same place.
Marking as sold on a click or a screenshot. Friday's dashboard shows revenue that does not exist and Monday's reconciliation brings the number down.
Asking for card data to "speed things up." It exposes the customer, violates security best practices, and if it leaks, the company is liable.
Giving an extra discount to whoever "got an error." The discount teaches the next person to report an error to get a reduction.
Continuing to remind people who already paid. Under art. 49 of the CDC, anyone who bought through WhatsApp has 7 days to withdraw; an improper charge is the last push they needed.

What to measure from link to payment

Measure four indicators with the same base of links, excluding test and duplicate links. The ranges are practical references, not benchmarks.

Link-to-payment conversion = confirmed payments ÷ links sent, in a fixed 72-hour window. Below 20%, review the link checklist before blaming the customer.
Time to confirmation = hours between sending the link and confirmation at the source. If the median exceeds 24 hours, the link is being sent too early, before the customer decides.
Pending by reason = pending for each reason ÷ total pending. If "technical error" exceeds 30%, the problem is the checkout, not customer service.
Improper charge rate = reminders sent to people who already paid ÷ confirmed payments. Any value above zero indicates a failure in stopping the reminders.

These numbers feed the owner's dashboard; what the owner should look at is in Black Friday dashboard: what the business owner should watch.

Frequently asked questions

Sources

Should I resend the payment link several times?

No. Resend it once if the customer reported that the link did not open. Beyond that, find the barrier first: ask at which step they stopped and offer another payment method. Repeating the link does not solve price, trust, a card error, or a purchase that was already paid another way.

Does a receipt sent by the customer count as payment?

Not as confirmation. Thank them, say you will check, and only change the status when the payment source shows the value approved. Receipts can be for a scheduled payment, for another order, or edited. The check takes minutes and prevents releasing an order with no money in the till.

Can I chase a customer who chose boleto and did not pay?

You can remind them of the expiration, within WhatsApp's window and opt-in rules, and offer Pix as an alternative. One objective reminder with the due date is enough. If the boleto expired with no reply, release the stock and close the pending payment.

Does the CRM confirm the payment by itself?

It depends on the integration between the CRM and the payment method, which varies by tool. Without integration, someone on the team checks at the source and records the value manually. What matters is that the record exists in the customer's conversation, stops the reminders, and carries the source when it is available.