Treat payment-state lookup and payment-event notifications as separate tasks. Configure the actual merchant event and customer phone before attempting a WhatsApp update; a payment is not proof of messaging consent.
WhatsApp CRM and Marketing start on Growth: US$12/month · ₹999/month in India. AI credit, purchased team seats and Meta/provider message charges are separate. Email and Store remain admin-only beta; Commerce is not a new purchasable plan.
The Razorpay adapter uses merchant key credentials to read recent payments. It fetches a limited set of 20 and filters supported payment/order identifiers, email or contact; a missing match does not prove that a payment failed.
Report the returned payment state, not a promise of settlement or a completed refund. This adapter does not charge a customer, create merchant payment links or execute refunds. Repli subscription checkout is unrelated to the merchant workflow.
A compatible supplied payload can be processed by the generic WhatsApp inbound receiver. Its optional shared-secret check is not raw-body Razorpay HMAC verification. Authenticate the source in a verified bridge and map the relevant payment event and recipient.
The Email workspace has a separate Razorpay event-template path and remains private beta. That path is not evidence of one-click WhatsApp notifications. Verify receipt, matching, consent and appropriate templates independently; do not treat a received event as a delivered message.
Identify the merchant event and verify its signature in an appropriate bridge.
Map the actual phone, payment identifier and state; limit stored payload details.
Review consent and approved-template eligibility, then verify the dispatch result separately.
The generic WhatsApp receiver does not establish Razorpay raw-body HMAC validation. A configured shared secret is not equivalent; authenticate your merchant bridge separately.
No customer message, provider connection or notification delivery was performed in this audit. Source behavior and aggregate configuration records do not prove current end-to-end operation.
WhatsApp CRM and Marketing start on Growth: US$12/month · ₹999/month in India. AI credit, purchased team seats and Meta/provider message charges are separate. Email and Store remain admin-only beta; Commerce is not a new purchasable plan.
WhatsApp Business Platform pricing — Delivered-message billing depends on recipient market and category; consult the current rate card and account invoice.
Cloud API getting started — Account and number prerequisites; Meta controls availability and approval.
WhatsApp Business Messaging Policy — Consent, acceptable use and messaging restrictions still apply.