- Docs
- Guides
Pay in chat with Razorpay (UPI) & Stripe
Ask for a payment right in the conversation. A teammate — or the AI assistant, once a teammate approves — sends a card like “₹1,500 — Website setup · Pay”; the customer taps Pay and pays on your own Razorpay account or Stripe account. When the money arrives the card turns Paid everywhere and you are notified. Payments in chat are included with Starter, Pro, Lifetime and Reseller accounts.
Your account, your money. Customers pay on Razorpay’s or Stripe’s own secure page, straight into your account. TalkingDot takes no cut and never sees card or bank details — only the amount, what it is for and whether it was paid. Your provider’s usual fees apply.
How it works
- Ask. In the inbox, click the Request payment button under the reply box (the wallet icon). Enter the amount, the currency, what it is for (the customer sees it) and how long the link stays valid — from 1 hour to 30 days.
- The customer pays. The chat shows a card with the amount, the description and a Pay button that opens the payment page in a new tab. With Razorpay in rupees they can pay with UPI (any UPI app, or a QR code on a computer), cards, netbanking or wallets; with Stripe, by card.
- It turns Paid. The card switches to Paid ✓ in the chat, the inbox and the mobile app. The teammate who asked gets a notification (in the bell, and as a push unless they switched off Payments received in Settings → Notifications), the conversation shows “Payment received”, the customer’s profile gets a Paid ₹1,500 event, and Reports adds it to Payments in chat.
Open requests can be cancelled from their card (Cancel request) — the link stops taking payments. A request that runs out shows Expired. If a payment still arrives after that, the request is shown as paid: money that arrived always counts.
Set up Razorpay
- Get your API keys. In the Razorpay Dashboard open Account & Settings → API keys and generate a key. Copy the Key ID and the Key secret (Razorpay shows the secret only once). Keys starting with
rzp_test_are test keys — payments are simulated;rzp_live_keys take real money and need an activated account. - Connect. In TalkingDot open Settings → Payments, paste both and click Connect & test. We check the keys with Razorpay straight away and show whether you are in live or test mode. The secret is stored encrypted and never shown again.
- Add the webhook (recommended) — see below.
- Choose your defaults on the same page: the usual currency, how long requests stay valid and, if you connected both, which provider to use.
UPI and payments in India
- Requests are Razorpay Payment Links. For rupees the payment page offers UPI next to cards, netbanking and wallets — whatever is switched on in your Razorpay account. On a phone, UPI can open the customer’s UPI app; on a computer they can scan a QR code.
- Amounts are exact: ₹1,500 is sent to Razorpay as 150000 paise. The smallest request is ₹1.
- UPI works in rupees only. Requests in US dollars, euros, pounds and other currencies need International payments switched on in your Razorpay account and are paid by card.
- In test mode Razorpay limits how many payment links a business can make, and UPI payments are simulated on Razorpay’s test page.
- TalkingDot asks Razorpay not to text or email the link (and not to send reminders) — the customer already has it in the chat.
Set up Stripe
- Connect Stripe in Settings → Integrations → Stripe (the same connection that shows the Stripe customer card — see the Stripe guide).
- Stripe appears in Settings → Payments. When both are connected, teammates pick Razorpay or Stripe on each request; set the default there.
- Add the webhook shown in Settings → Payments to Stripe under Developers → Webhooks (recommended — see below).
Webhooks: “Paid” the moment it happens
You don’t have to set anything up for requests to be marked as paid: TalkingDot checks every open request with the provider by itself — every 2 minutes in the first hour, every 10 minutes for the first day, then every 30 minutes, and once more just after it expires. A customer who comes back from the payment page also triggers a check. A webhook makes it instant.
For Razorpay: in the Dashboard open Account & Settings → Webhooks → Add new webhook and paste the Webhook URL and Secret from Settings → Payments. Tick these active events and save:
payment_link.paidpayment_link.cancelledpayment_link.expired
Every webhook is signed with that secret (the X-Razorpay-Signature header) and checked before anything changes; a wrongly signed one is refused. Settings → Payments shows when the last webhook arrived. If you connect one Razorpay account to several workspaces, add each workspace’s own URL — each one only ever changes its own requests.
What customers see
- On your website’s messenger: a compact card with the amount, the description, a Pay ₹1,500 button and “Secure payment by Razorpay”. It changes to Paid ✓, expired or cancelled on its own, without reloading. Test-mode requests say so on the card.
- On WhatsApp, Telegram, Instagram, Facebook Messenger and email: a plain message — “Payment request: ₹1,500 — Website setup. Pay here: https://rzp.io/…” — in the customer’s language. On WhatsApp the usual 24-hour reply window applies.
- After paying: the provider sends them back to a short “Thank you — your payment was received” page with your team’s name; they can close it and carry on in the chat.
- Emailed transcripts and missed-reply emails include the request as text, with its link while it is open.
The AI assistant
When AI actions are on, the AI can propose a payment request — for example when a customer asks to pay for something your help center prices. By default a teammate approves it first: the inbox shows “wants to run Payment request” with the amount and description, and nothing is sent until someone clicks Approve & run. The AI is told never to invent prices. Change this under Settings → AI → AI actions → Payments in chat: the AI can be switched off, ask a teammate (the default) or send on its own; Teammates decides who may send requests from the inbox and approve the AI’s (everyone by default, or admins only, or nobody).
Security
- Amounts are whole numbers in the currency’s smallest unit (paise, cents), checked for each provider and currency. The amount on the card always comes from what we created — never from the browser — and a payment is only marked paid when the provider confirms the full amount in the same currency. A paid request stays paid; repeated webhooks change nothing.
- The Pay button only ever links to the provider’s own
httpspage (Razorpay’srzp.io/razorpay.com, Stripe’sstripe.com). - Only teammates and the approved AI can send payment requests; a visitor typing a message can never make a payment card appear. Each card is bound to the request it belongs to.
- Keys and webhook secrets are encrypted at rest and never written to logs. Webhook signatures are compared in constant time.
- Requests are rate-limited per teammate, per conversation and per workspace, and follow the usual rules: no requests to blocked visitors or in locked conversations.
Plans
Payments in chat are included with Starter, Pro, Lifetime and Reseller accounts. On a plan without them no new requests can be sent; requests already sent keep showing whether they were paid, and paid ones are still recorded.
For developers
- REST API:
GET /api/v1/payment-requestsandGET /api/v1/payment-requests/{id}— see the REST API. - Webhooks:
payment_request.createdandpayment_request.paid— see webhook events. - MCP server: the
list_payment_requeststool reads a conversation’s requests — see the MCP guide.
Questions
Does TalkingDot charge a fee on payments?
No. The money goes straight to your Razorpay or Stripe account; only your provider’s own fees apply.
How do I refund a payment?
In your Razorpay or Stripe dashboard, as for any other payment. The card keeps showing that it was paid.
Can a customer pay part of the amount?
No — partial payments are switched off, so a request is either paid in full or still open.