payment_configuration_update webhook reference | Developer Documentation

Check payment confirmation after sending a WhatsApp link

When you send an external checkout link through ChatArchitect, the payment happens on the payment service's website. ChatArchitect does not provide native WhatsApp payments. Use the external service's transaction result to decide whether an order has been paid.

Keep the two records separate

Message delivery statuses such as delivered or read do not establish a transaction result. The ChatArchitect Quick Start documents message and message-event callbacks; it does not define a payment-confirmation payload.

Verify an order

1. Find the order and the checkout link your team sent. Record the payment-service reference, rather than identifying a transaction only by the text of a WhatsApp message.
2. Open that reference in the payment service and check its current result using that service's terminology and instructions.
3. If the CRM shows a different result, identify the connection responsible for updating it. Check that connection's mapping, credentials and processing record with its administrator.
4. When a result is unclear, resolve it with the payment service before sending another request for the same order.

For developers

A payment-service webhook and a ChatArchitect message webhook have separate sources and contracts. Implement transaction processing from the payment service's documented contract. Use ChatArchitect webhooks for the messaging events documented for your connection.

The imported Meta event named payment_configuration_update concerns native payment configuration. It is not a ChatArchitect checkout result or proof that a customer paid.