Every Razorpay payment, followed by a call
Add a Razorpay webhook with the URL LumaKol gives you. Each captured payment from your Payment Pages, Payment Links or Payment Buttons becomes a lead with what they paid for, so a caller can welcome, onboard or upsell them.
- Only captured payments
- Amount and purpose in the note
- Each payment added once
Razorpay at a glance
- How leads get in
- A Razorpay webhook posts payment events to the private URL on your LumaKol source. There is no Razorpay API key to copy anywhere.
- How fast
- As Razorpay sends the event. For payment.captured that is the moment the payment is captured.
- Repeats and retries
- Each payment ID is added once. Ticking both payment.captured and order.paid does not double a buyer, because both events carry the same payment.
- Where you set it up
- Razorpay Dashboard → Accounts & Settings → Webhooks → Add New Webhook.
Who it’s for
Coaching institutes and course sellers collecting fees or registration amounts, event and workshop organisers, consultants taking booking fees, and brands selling through Razorpay payment pages. A call soon after payment confirms the batch or slot, answers questions and opens the door to the next purchase.
- Paid for a demo class or a registration? The counsellor confirms the batch and talks about the full course.
- Failed and pending payments are ignored; only payments that went through become leads.
- Fields you add to a Payment Page, such as name, city or course, are saved on the lead or in its note.
How to connect it
- 1
Add Razorpay as a lead source
In LumaKol, go to Integrations → Lead sources, choose Add source, then Razorpay, and copy the webhook URL.
- 2
Add a webhook in Razorpay
In the Razorpay Dashboard, open Accounts & Settings → Webhooks, click Add New Webhook and paste the URL. The secret can be any value.
- 3
Pick the events
Tick payment.captured, plus payment_link.paid or order.paid if you use Payment Links or orders, then create the webhook.
- 4
Make a small test payment
Pay a small amount through your own Payment Page or Link. It appears under the source’s Activity as New lead, and the lead’s note shows the amount and the payment ID.
How a Razorpay payment becomes a lead
| What Razorpay sends | Where it lands in LumaKol |
|---|---|
| A payment note called name, full_name or customer_name, or the customer on a Payment Link | Name |
| The contact number entered at checkout, else a phone, mobile or contact note, else the Payment Link’s customer | Phone |
| The email entered at checkout, else an email note, else the Payment Link’s customer | |
| A payment note called company | Company |
| A payment note called city | City |
| Amount, currency and payment ID | A “Paid” line in the note, with the currency’s own sign and the payment ID |
| The payment’s description | A “For:” line in the note |
| Any other payment notes, such as a course or batch field | One “Field: value” line each in the note |
Only payment.captured, order.paid and payment_link.paid create leads. Every other event is answered and logged as Test, so Razorpay stops retrying it and no lead is made.
After the lead arrives
Other Razorpay events, such as failed or authorised-only payments, are acknowledged and logged as Test, never as leads. A buyer who is already a lead, for example a student who enquired last week, gets the payment as a note on their existing lead, so their counsellor sees it straight away.
Common Razorpay problems, and the fix
A payment shows as Test instead of a lead
Only captured or paid payments become leads. A failed payment, a payment that was authorised but never captured, or any other event you ticked is logged as Test. If your Razorpay account does not capture payments automatically, the lead arrives when you capture the payment.
Buyers arrive without a name
LumaKol takes the name from a payment note called name, full_name or customer_name, or from the customer on a Payment Link. When a payment carries neither, the lead is named after its phone number; rename it after the first call.
Nothing arrives at all
Check that the webhook is active in Razorpay, that its URL is the one on the source, and that the source is not paused: a paused source turns deliveries away until you press Resume. Razorpay keeps separate webhooks for Test mode and Live mode, so add the URL in the mode you take payments in.
A regular customer paid again
That is expected to be a note, not a new lead. The payment is added to the lead that already has the number, marked as an enquiry again via your source, and the lead moves up the list so the caller sees both payments.
Questions about Razorpay
Which Razorpay events should I tick?+
payment.captured covers Payment Pages and Payment Buttons. Add payment_link.paid for Payment Links and order.paid if you create orders. Other events are logged as Test and never become leads.
Why does a lead have no name?+
Razorpay sends a name only when your Payment Page has a name field or the Payment Link was made for a customer. Add a Name field to the page and every buyer arrives with one.
Can I try it with Razorpay’s Test mode?+
Yes. Add the same LumaKol URL as a webhook in Test mode and make a test payment. LumaKol treats it like any other payment and creates a real lead, so delete that lead afterwards or test with a separate source.
Will a payment be added twice if Razorpay sends it again?+
No. Each payment ID is added once, however many times Razorpay sends it, and a buyer whose number is already a lead gets a note instead.
Do I copy the webhook secret into LumaKol?+
No. Razorpay asks for a secret, but it can be any value; the private URL is what links the webhook to your workspace. Keep the URL private, and use Change URL if it leaks.
Step-by-step setup guide
Related integrations
All integrationsప్రతి కాల్ను నమోదు చేసే CRM ను మీ టీమ్కు ఇవ్వండి
మీ వర్క్స్పేస్ సెటప్ చేసి అదే రోజు కాల్లను నమోదు చేయడం ప్రారంభించండి.
- కార్డ్ అవసరం లేదు
- కాల్ చేయని 3 అడ్మిన్ల వరకు ఉచితం
- మీ సొంత SIM నుంచే కాల్లు