Designing a safer payment flow for WhatsApp orders
Verified payment events belong on the order record. The payment-link service is implemented, while desktop link creation remains in progress.
Field notes · Built by Arche Axon
A manual payment flow can involve an agent sharing an amount or till number, a customer paying, then the team checking a receipt before changing the order status. Each handoff can introduce a mismatch when the order and payment live in separate records.
What breaks in the manual chain
- Pasting a stale till number can send money to the wrong account, unnoticed for days.
- Typos in amounts: the customer pays 2,500 for a 5,200 order and the discrepancy surfaces at stock-take.
- Screenshot verification: no record of which payment belongs to which order except a human matching amounts.
- Refunds become negotiations because there is no payment record tied to the order.
What 'inside the chat' should mean
A reliable payment request should be tied to an order and carry its amount and reference. Once a provider confirms settlement, a verified event should update that order. Vendale's payment-link service supports this provider flow, but the desktop link-creation workflow is still in progress, so the full loop is not available in the current desktop release.
The honest caveat
Payment rails differ by provider and country, and settlement times are what they are. A CRM does not owe you magic money. It owes you linkage: order to payment request to confirmation, recorded without a human retyping anything.