Commerce
Payments, orders, and LTV
Create Razorpay payment links only after an identifiable customer choice, then sync payment outcomes into CRM.
Payment safety
Do not generate links from vague messages. A flow Buy action must identify the catalog item and price first.
Verified payment creates/updates the order, refreshes customer lifetime value, and may trigger an approved utility confirmation template and website callback.
Webhooks and website callback
Razorpay must call the configured CRM webhook using its signing secret. The CRM verifies the webhook before marking an order paid. Any website callback should be authenticated and idempotent so it can safely receive a repeated payment update.