Skip to content
Payments · Razorpay integration Beta

Payment events.
Clear customer updates.

Connect your own Razorpay merchant account to WhatsApp updates for payments received, failed attempts and processed refunds. Choose the messages your customers need and review the event behind each update.

  • Payment & refund events
  • Test & Live modes
  • Message activity
From payment event to customer updateExample workflow
  1. 01A signed Razorpay event

    A payment or refund event arrives from the merchant account connected to your project.

  2. 02Check the account and event

    Wydely checks the event before recording payment activity or evaluating a message.

  3. 03Your chosen customer update

    An enabled template or matching flow handles eligible Live events. Activity records the outcome.

Example of a configured Live workflow. Test events are recorded without sending WhatsApp messages or starting flows.
Four views, one workspace

Follow the payment from connection to message outcome.

Connection, Automations, Payments and Activity keep setup and day-to-day review in one place.

Control the connection and messages

Keep Test and Live setup separate. Choose approved utility templates with mapped payment values, or use a matching automation flow for conditions and follow-ups.

Review received payment records

Review payments received through your webhook, including the available amount, currency, reference and status. Older payments are not imported.

Understand each event’s outcome

Inspect processing, message and flow outcomes in Activity. See why an update was skipped, such as a missing customer number or unavailable template value.

Supported payment events

Three updates your customers can understand.

Choose the events that fit your workflow. A payment event is evaluated against your message settings and customer permissions before sending.

01

Payment received

Acknowledge a successfully captured payment with the available amount, currency and payment reference.

02

Payment failed

Explain an unsuccessful payment attempt and offer a way to get help. A failed attempt does not mean the order is permanently unpaid.

03

Refund processed

Share a processed refund update using the available refund reference and amount. Bank credit timing can differ from the processing time.

Connection setup

Start in Test. Choose your Live updates.

The account owner connects the merchant account. Authorized team members can review activity and manage message settings according to their project permissions.

Messages stay under your control
Connecting does not enable customer messages. A matching active automation flow takes precedence over the direct template for that event.
  1. 01

    Connect the right merchant account

    Open Integration → Razorpay in your Wydely project and start in Test mode. Enter your Razorpay Account ID to create the webhook details. API keys and your Razorpay password are not required.

  2. 02

    Add the webhook in Razorpay

    Copy Wydely’s generated webhook URL and signing secret into the matching Razorpay mode. Select payment.captured, payment.failed and refund.processed, then save and enable the webhook.

  3. 03

    Verify a test event

    Complete a test payment and check the connection in Wydely. The first valid supported event verifies the connection. Review Payments and Activity; Test mode sends no customer messages.

  4. 04

    Choose future Live messages

    Create the separate Live connection, select an approved utility template or a matching automation flow, and confirm customer permission. Enable only the updates you want to send and review their recorded outcomes.

Account & access

Review the setup for your business.

Beta availability depends on your project, account access and provider setup. Bring your payment workflow to a demo so we can review the connection and messages you need.

Review your requirements
A few useful answers

Know what to expect.

Keep payment updates, payment requests and platform billing clear.

Explore WhatsApp Payments
Does connecting Razorpay turn on customer messages?

No. Messages start disabled. Test mode records events without sending WhatsApp messages or starting flows. For Live events, configure an approved utility template or automation flow and confirm customer permission before enabling the intended messages.

Does this integration collect payments or issue refunds?

This integration receives payment and refund updates from your Razorpay merchant account. It does not initiate charges, issue refunds or create payment links. Use the separate WhatsApp Payments workspace for eligible payment requests inside conversations; it requires its own active payment configuration.

Will I see my previous Razorpay payments?

Earlier payments are not automatically imported. Payments and Activity show events received through the connected webhook. Keep the webhook enabled in Razorpay and use the last received event and Activity details when checking the connection.

What happens when customer details are missing?

Events without a usable customer phone number are recorded without sending a message. Missing template values or other sending requirements also stop the message, with the outcome shown in Activity.

Does this change my Wydely subscription or message-credit billing?

No. This connection uses your merchant account for customer payment updates. Wydely subscription payments and WCC messaging-credit purchases remain separate billing workflows.

See Wydely in action

Make your payment updates useful to the customer.

Explore Razorpay setup, supported events and a customer-message workflow with our team.