Laundry payments: confirm the service as well as the charge

A well-managed payment journey begins before the charge and ends after activation. Customers need the full price, a recognizable machine selection and a clear response. Operators need to connect financial events to equipment events without confusing “paid” with “service delivered”. PIX, cards and other supported payment methods should follow the same principle.

Assign a reference to each attempt

Link the site, machine, service, amount and time to a purchase reference. Do not identify transactions by the customer’s address or amount alone: two people may buy identical cycles simultaneously. Retain the payment provider’s identifier and the server-confirmed result. An on-screen success message or a customer-supplied receipt does not replace verification.

Plan for delayed confirmation

A PIX confirmation may arrive after the customer leaves the screen. A card connection failure can leave its result uncertain. Check the transaction status before creating a second charge. Provider notifications may be delivered repeatedly; processing should recognize the same reference and prevent one payment from activating two services. Validate the actual mechanism with the chosen integration.

Treat activation as a separate stage

After approval, verify that the machine is still available and track the cycle start. If it does not respond, explain that the operation is being checked and provide support with the reference already attached. Repeating a command without knowing its earlier result can be as problematic as repeating the payment. Agree on waiting limits and recovery procedures with the technical team.

Reconcile payment and fulfillment

At the end of the period, compare approved payments, started services, cancellations and refunds. Distinguish provider fees, gross value and net value because they answer different questions. Review unresolved items by site and equipment rather than simply adding revenue. Every approved payment without a matching cycle should enter an investigation queue with an owner and a deadline.

Implementation checklist

• Display the price and machine before confirmation.
• Record financial and operational references.
• Test duplicate notifications and delayed responses.
• Review charges without confirmed services every day.