> ## Documentation Index > Fetch the complete documentation index at: https://www.vobiz.ai/docs/llms.txt > Use this file to discover all available pages before exploring further. # Polite Payment Reminder SMS: Samples and How to Send > Polite payment reminder SMS samples for every stage, in English and Hindi, plus a send schedule, India DLT rules, and how to send them without spam complaints. *November 3, 2026 · By [Piyush Sahoo](https://www.linkedin.com/in/piyush-s713/)* A polite payment reminder SMS names your business, states the amount and due date, and gives one easy way to pay, all within 160 characters and with no pressure words. Send the first one before the due date and firm up slowly. In India, register the exact wording on DLT first. This guide gives you samples you can adapt, a schedule, and the Indian rules that decide whether your message arrives at all. > [!NOTE] > > **Key takeaways** > > * **Politeness is mostly facts.** A clear amount, reference, and date let you stay kind without sounding vague. > * **Most reminders in India fit the service category**, on our reading of TRAI's definitions. One discount line can turn a reminder into a promotional message. > * **Small characters change the bill.** The ₹ sign or a Devanagari word moves a message to a smaller segment size, so write Rs or use Hindi in Latin letters when length matters. > * **Send between 10:00 and 19:00 IST.** That range sits inside every window we could find, including the lender contact window in RBI's directions effective January 2027. > * **Your link and callback number must be registered too.** Since TRAI's 2025 direction, unregistered values in a template can stop the message. ## What makes a payment reminder SMS polite? A polite reminder assumes the best while still being exact. Most people who get one haven't refused to pay. They may have missed the date, be waiting for a salary, or have paid an hour ago. ![An example reminder from sender header AB-ACMEIN-S with six numbered parts: the sender header, the name and business, the amount and reference, the date, one way to pay, and a thank-you that covers people who already paid.](https://mintcdn.com/vobizai/p1DwoESAipLb1g-q/images/blog/payment-reminder-sms/reminder-anatomy-light.svg?fit=max\&auto=format\&n=p1DwoESAipLb1g-q\&q=85\&s=6af341c9eb43bb653f86fccb84534f81) Being polite doesn't mean being unclear. Avoid both extremes, the message too soft to act on and the one that picks a fight. These swaps keep you in the middle: | Instead of | Write | Why it works | | - | - | - | | You failed to pay | We have not seen your payment yet | It states what you know, not what they did | | URGENT!!! | Please pay by 20 Nov | A date creates urgency without shouting | | Final warning | This is our last reminder before \[next step] | It explains what happens next | | Legal action will follow | Name a step only if your contract allows it and you will take it | Empty threats damage trust | | Why haven't you paid? | Something wrong? Call us on \[helpline] | It invites a conversation | | Please do the needful | Please pay Rs 4500 using this link | It says exactly what you want | Also leave out anything private. A text can appear on a locked screen or on a shared family phone, so skip words such as defaulter, and don't mention other people. ## Polite payment reminder SMS samples by stage Replace the words in brackets with your own details. Character counts use short example values: a five-letter name, a four-letter business, Rs 4500, invoice INV2291, a date like 20 Nov, a 10-digit helpline, a 24-character link, and five characters for any other bracket. Count again with your longest real values. Every sample stays inside one GSM-7 segment at those lengths. | Stage | Sample | Characters | | - | - | - | | **3 days before** | Hi \[name], a note from \[business]: Rs \[amount] for invoice \[invoice] falls due on \[date]. You can pay at \[link]. Already paid? Thank you. | 142 | | **Due day** | Hi \[name], your \[business] payment of Rs \[amount] is due today. It takes a minute to pay here: \[link]. Thank you. | 120 | | **3 days late** | Hi \[name], we have not seen Rs \[amount] for invoice \[invoice] yet. It may have slipped by, so here is the link again: \[link]. Thanks, \[business] | 149 | | **7 days late** | Hi \[name], Rs \[amount] on invoice \[invoice] is 7 days past due. Please pay by \[new date]: \[link]. Something wrong? Call \[helpline]. \[business] | 143 | | **14 days late** | Hi \[name], if paying Rs \[amount] in full is hard right now, we would like to help. Call \[helpline] to discuss part payment or a new date. \[business] | 137 | | **30 days late** | Hi \[name], Rs \[amount] on invoice \[invoice] is unpaid. Please pay by \[new date] to keep your service active: \[link]. To talk, call \[helpline]. \[business] | 154 | | **After payment** | Thank you, \[name]. We received Rs \[amount] for invoice \[invoice] on \[date]. Your receipt: \[link]. \[business] | 113 | The 14-day message adds help instead of pressure. Only send the 30-day wording if service really will stop on that date. Avoid "reply to this message" in Indian samples. Indian business SMS goes out from a [registered sender header rather than a phone number](https://www.vobiz.ai/docs/sms/compliance/india-dlt.md), so give a link or a callback number instead. ## Samples for your type of business Adjust the first reminder to match how your customer thinks about the payment. | Business | Sample | Characters | | - | - | - | | **Loan or EMI** | Dear \[name], your \[lender] EMI of Rs \[amount] (loan ending \[last 4 digits]) is due on \[date]. Please keep funds ready or pay here: \[link] | 135 | | **Subscription on autopay** | Hi \[name], your \[plan] plan renews on \[date] for Rs \[amount] through autopay. You need not do anything. To change it, visit \[link]. \[business] | 148 | | **School or coaching fees** | Dear parent, term fee of Rs \[amount] for student ID \[ID] is due on \[date]. Pay at \[link] or the school office. Thank you, \[school] | 141 | | **Housing society** | Hi \[name], maintenance of Rs \[amount] for flat \[flat] is due by \[date]. You can pay here: \[link]. Thank you, \[society] | 125 | | **B2B invoice** | Hi \[name], invoice \[invoice] for Rs \[amount] from \[business] fell due on \[date]. Could you confirm a payment date? Call \[helpline] or see \[link] | 149 | | **Clinic, gym, or freelancer** | Hi \[name], a small reminder from \[business]: Rs \[amount] for your \[service] is open. You can settle it this week here: \[link]. Thank you. | 140 | ## Can you send a payment reminder in Hindi? Yes, but the script you choose changes the length limit. In [Vobiz's segment rules](https://www.vobiz.ai/docs/sms/channels/sms.md#segments-and-encoding), a GSM-7 message fits 160 characters. A UCS-2 message fits only 70, and 67 per segment once it splits. A single character outside the [GSM 7-bit alphabet](https://en.wikipedia.org/wiki/GSM_03.38) moves the whole text to UCS-2. Devanagari falls outside it, and so does the ₹ sign. These two samples say the same thing: * **Hindi in Latin letters:** Namaste \[name], \[business] ka Rs \[amount] ka bhugtan \[date] tak baaki hai. Yahan pay karein: \[link]. Dhanyavaad. * **Hindi in Devanagari:** नमस्ते \[name], \[business] का Rs \[amount] का भुगतान \[date] तक बाकी है। यहां भुगतान करें: \[link] धन्यवाद। ![Chart of four versions of one reminder. English with Rs at 111 characters and Hindi in Latin letters at 119 characters use one GSM-7 segment. English with the rupee sign at 109 characters and Hindi in Devanagari at 110 characters use two UCS-2 segments.](https://mintcdn.com/vobizai/p1DwoESAipLb1g-q/images/blog/payment-reminder-sms/sms-segments-light.svg?fit=max\&auto=format\&n=p1DwoESAipLb1g-q\&q=85\&s=2d7dd6d4189cd7f2a73267feb5a68066) Don't choose on cost alone. If your customers read Devanagari more easily than Latin letters, two segments may be money well spent. Run one group on each version and compare how many of them pay. ## When should you send each reminder? Start before the due date, since a reminder at that point feels like a service. Then widen the gaps as time passes. [Razorpay](https://razorpay.com/blog/automated-payment-reminders) suggests a similar pattern of 3 days before, the due date, then 3, 7, 14, and 30 days after. ![Suggested schedule of six reminders with rising firmness: friendly note at day minus 3, light nudge on the due day, benefit of the doubt at day 3, clear ask at day 7, offer of help at day 14, and a firm dated message at day 30. Remove anyone who pays, disputes the amount, or calls before the next send.](https://mintcdn.com/vobizai/p1DwoESAipLb1g-q/images/blog/payment-reminder-sms/reminder-schedule-light.svg?fit=max\&auto=format\&n=p1DwoESAipLb1g-q\&q=85\&s=ce705fb0a410c0cdabb2e4e1738ae948) The stop rule matters as much as the schedule. Nothing feels less polite than a late notice for a bill someone settled yesterday, so update your list on the morning of each send. ### What time of day works best? We suggest 10:00 to 19:00 IST. No single published window covers every sender, so we chose the range that fits inside all of those we could read: ![24-hour chart. The lender contact window in RBI's directions effective January 2027 runs 08:00 to 19:00. TRAI's 2018 regulations keep time bands outside 10:00 to 21:00 off by default. The suggested reminder window of 10:00 to 19:00 sits inside both.](https://mintcdn.com/vobizai/vn3KxdUq6H3224WW/images/blog/payment-reminder-sms/sending-window-light.svg?fit=max\&auto=format\&n=vn3KxdUq6H3224WW\&q=85\&s=5c8db382a7f8e311e4e2eb5e24717142) The promotional hours come from the default time bands in [TRAI's 2018 regulations](https://trai.gov.in/sites/default/files/2025-01/RegulationUcc19072018.pdf), which keep the bands before 10:00 and after 21:00 off unless the customer switches them on. Ask your DLT provider how this applies to your messages. TRAI's [Third Amendment](https://www.trai.gov.in/sites/default/files/2026-09/Regulation_18092026.pdf) says transactional and service messages aren't blocked during any time band, but a reminder isn't urgent enough to wake anyone. If you also text customers in the United States, [FCC rules under the TCPA](https://www.law.cornell.edu/cfr/text/47/64.1200) limit telephone solicitations, which include marketing messages, to the hours from 8 AM to 9 PM, local to whoever receives it. ## What do India's SMS rules mean for your reminder? TRAI's rules decide whether your message reaches anyone. They apply to the words you write as much as to the system that sends them. They change often, so confirm the current text and take legal advice for your own case. ### Which category does a payment reminder fall into? TRAI's [2025 amendment](https://www.trai.gov.in/sites/default/files/2025-02/Regulation_12022025.pdf) defines each category. It doesn't name payment reminders, so the map below is our reading of it, and your DLT provider makes the final call on your template. ![Decision map. A message with any offer, upsell, or discount is promotional, suffix P. A confirmation within 30 minutes of a transaction the customer started is transactional, suffix T. A message about a product or service the customer already has is a service message, suffix S, where most payment reminders fall. Anything else needs explicit consent first.](https://mintcdn.com/vobizai/p1DwoESAipLb1g-q/images/blog/payment-reminder-sms/dlt-category-map-light.svg?fit=max\&auto=format\&n=p1DwoESAipLb1g-q\&q=85\&s=29524fe24dd0c089fc80b372e4082578) Three consequences follow for what you write: * **Keep offers out.** The amendment treats any message that mixes promotional content with service or transactional content as promotional. "Pay today and get 10% off your next plan" could put your reminder in the wrong category. Register that as a separate promotional template. * **Customers see the category.** [TRAI's press note](https://trai.gov.in/sites/default/files/2025-02/PR_No.11of2025.pdf) says headers carry a suffix of -P, -S, -T, or -G. A reminder that arrives with -P looks like marketing. * **The customer relationship carries the consent.** [Service messages to your own customer](https://www.trai.gov.in/sites/default/files/2025-02/Regulation_12022025.pdf) don't need explicit consent, but [that inferred consent lasts](https://trai.gov.in/sites/default/files/2025-02/PR_No.11of2025.pdf) only as long as the contract. Once the contract ends, stop sending service messages unless the person agrees to them. TRAI's [Third Amendment, announced on 18 September 2026](https://www.trai.gov.in/sites/default/files/2026-09/PR_No119of2026.pdf), keeps this structure and [narrows the wording](https://www.medianama.com/wp-content/uploads/2026/09/trai-amendments-unsolicited-communications.pdf) to a product or service the customer has procured. Its parts start 30 to 90 days after Gazette publication, and we couldn't confirm that date. The same text says these regulations don't remove your duties under the Digital Personal Data Protection Act, 2023. ### What must be registered before you send? Everything repeatable goes on a DLT portal first, and [Vobiz's DLT registration guide](https://www.vobiz.ai/docs/best-practices/dlt-registration.md) walks through it: | Item | Example | What to watch | | - | - | - | | **Your business** | Principal Entity ID | One registration for your organisation | | **Sender header** | ACMEIN | [Six characters](https://www.vobiz.ai/docs/sms/compliance/india-dlt.md), registered for the right category | | **Message wording** | Each sample above | Sent text must match the template, or [operators reject it](https://www.vobiz.ai/docs/sms/compliance/india-dlt.md) | | **Payment link** | Your own domain | [TRAI told providers](https://www.pib.gov.in/PressReleasePage.aspx?PRID=2058943\®=48\&lang=2) to block links that aren't whitelisted | | **Callback number** | Your helpline | Must match a number registered for the template variable | So plan one template for each stage and business type. A last-minute edit to the wording means fresh approval before you can send it. ### How do variable tags affect your samples? TRAI's [November 2025 direction](https://trai.gov.in/sites/default/files/2025-11/Directions_18112025_0.PDF) requires each changing part of a template to carry a tag. After a 60-day logging period, messages that fail the check are rejected outright. We couldn't confirm when each provider's clock began, so treat this as live. Count your variables as well. The same direction recalls TRAI's earlier limit of two variables per template, a third in exigencies, and more than three only in special circumstances on a request with reasons. Most samples here use more than that. Write your business name as fixed text, ask your provider how many it will approve, and drop the name or reference if it holds you to three. The brackets in our samples map to tags like this: | Bracket | Tag | Rule from TRAI's annexure | What it means for you | | - | - | - | - | | \[amount] | `#numeric#` | Digits only | Send 4500, not 4,500 or 4500.00 | | \[invoice] | `#alphanumeric#` | Letters and numbers, up to 40 characters | Keep references plain and short | | \[link] | `#url#` | Must match a registered link | A public shortener won't help you here | | \[helpline] | `#cbn#` | Must match a registered number | Register each helpline you use | Test a real example of each value with your provider, especially names with spaces and dates. Ask about short links too. TRAI's annexure lists short URLs among the types you can register, while [Zoho's help forum](https://help.zoho.com/portal/ar/community/topic/stay-in-the-know-important-trai-mandate-on-url-whitelisting-for-indian-crm-customers) says public short links such as bitly aren't approved. ### What happens if customers complain? Too many reminders can become a compliance problem. Under the [2025 changes](https://trai.gov.in/sites/default/files/2025-02/PR_No.11of2025.pdf), action starts at complaints against a sender from 5 people in 10 days. A first violation bars outgoing services on all the sender's telecom resources for 15 days. Later violations mean one year of disconnection and blacklisting. Once it takes effect, [TRAI's Third Amendment](https://www.trai.gov.in/sites/default/files/2026-09/PR_No119of2026.pdf) adds a lower trigger of 3 complaints in 10 days when the operator's AI system has also flagged the sender's number. See [Vobiz's UCC page](https://www.vobiz.ai/docs/compliance/india/ucc.md) for how complaints work on your account. ## How do the rules change for your business? Use this table to find the extra check that applies to you. | If you are | Do this | Why | | - | - | - | | **A bank, NBFC, or other RBI-regulated lender** | Have compliance approve every template, and send within 08:00 to 19:00 | See the lender rules below | | **On autopay or e-mandate** | Say no action is needed, and don't send a pay link alongside | The customer may pay twice | | **A micro or small supplier chasing a business** | Quote the invoice and acceptance date, and keep the tone neutral | The law gives you rights, so you don't need threats | | **A school, clinic, or society** | Use an ID in place of a child's or patient's name | Anyone holding the phone can read the message | | **Any other business** | Follow the schedule and the category map | The general rules apply | **Lenders.** RBI's [August 2026 directions](https://www.rbi.org.in/Scripts/BS_PressReleaseDisplay.aspx?prid=63305) take effect on 1 January 2027 for banks, NBFCs, and other regulated entities. The [commercial bank](https://www.rbi.org.in/scripts/NotificationUser.aspx?Id=13665\&Mode=0) and [NBFC](https://www.rbi.org.in/scripts/NotificationUser.aspx?Id=13672\&Mode=0) texts allow contact only from 08:00 to 19:00, unless the borrower asks otherwise. They class excessive messaging, messaging outside those hours, and misleading statements about the consequences of non-payment as harsh practices. They also say all recovery-related communications must carry the grievance officer's name, email, phone, and address. Those details won't fit a short SMS, so ask your compliance team now how they want this handled. **Autopay.** RBI's [E-mandate Framework, 2026](https://www.rbi.org.in/Scripts/NotificationUser.aspx?Id=13374) makes the issuer send a notice at least 24 hours before a recurring debit on a card, prepaid instrument, or UPI. Your own message is a courtesy on top of that notice, so don't ask the customer to pay by hand. **Small suppliers.** The [MSME ministry's summary](https://www.dcmsme.gov.in/publications/LegalFramework.pdf) says a buyer who doesn't pay a micro or small enterprise within 45 days of acceptance owes compound interest at three times the RBI bank rate. It also describes the state councils that handle these disputes. Save that for a formal letter, and keep your SMS friendly. ## Should you use SMS, WhatsApp, or a call? Start with SMS for scheduled reminders, then change channels as the amount and the delay grow. Our guidance: | Situation | Best first choice | Reason | | - | - | - | | Routine due-date reminder | SMS | It works on any phone and needs no app | | Customer already talks to you on WhatsApp | [WhatsApp template](https://www.vobiz.ai/docs/whatsapp/messaging/templates.md) | It has room for detail and sits in an ongoing thread | | Several SMS with no payment | [Reminder call](https://www.vobiz.ai/docs/solutions/automated-outbound-calling.md) | A voice call can route the customer to a person | | Dispute or hardship | A person on the phone | Automation can't settle a disagreement | Calls carry their own [number series rules](https://www.vobiz.ai/docs/compliance/india/calling-regulations.md), so check those before you add voice. Lenders can read [how Vobiz supports EMI reminder calls](https://www.vobiz.ai/docs/solutions/finance-fintech.md). ## How do you send payment reminders step by step? 1. **List your scenarios.** Pick the stages and business types you need from the samples above. 2. **Register everything.** Complete your business, header, templates, links, and callback numbers on a DLT portal. Allow time for approval. 3. **Prepare a clean list.** Pull unpaid invoices on the morning of the send, with the name, amount, reference, date, and link in separate columns. 4. **Preview a few messages.** Check the wording against your template, then check the length with your longest values. 5. **Send a small group first.** Use your own numbers to confirm the text and link work. 6. **Send inside your window.** Keep to 10:00 to 19:00 IST, and remove anyone who has paid. 7. **Measure payments.** Track how many customers pay within three days of each stage, using your own billing records. Judge results by money received, not by read rates. Some guides quote 98% open rates, but we couldn't trace that figure to an original measurement. SMS also doesn't report opens in the way email can, so your payment records are the honest test. ## How Vobiz handles payment reminder SMS The [Vobiz Messaging API and console](https://www.vobiz.ai/docs/sms/overview.md) cover sending, tracking, and opt-outs. You don't need code for a monthly run, because the console offers the same flow under **SMS & RCS → Broadcasts**. * **Bulk reminders.** A [broadcast](https://www.vobiz.ai/docs/sms/broadcasts.md) takes a CSV or XLSX file of up to 10,000 recipients, and each extra column becomes a variable in your message. Set the send rate from 1 to 50 messages per second. * **Preview before launch.** The preview shows rendered samples, segment counts, the encoding, and any missing variables. * **Scheduling.** Launch now or at a set time. Enter the time with care, since 10:00 IST is 04:30 UTC. A launched broadcast can't be edited, but you can pause or cancel it. Build the list close to the send so that it stays current. * **India DLT.** Add your [entity, header, and template IDs](https://www.vobiz.ai/docs/sms/compliance/india-dlt.md) to the broadcast, and every message carries them. Vobiz records these IDs, and the operators check each message against your registration. Contact [support@vobiz.ai](mailto:support@vobiz.ai) to enable your header as a sender. * **Opt-outs.** Every send is checked against your [opt-out list](https://www.vobiz.ai/docs/sms/opt-outs.md). Add requests that reach you by phone or email as manual entries. * **Results.** You can track each recipient's status and export a CSV of results to match against your billing records. Developers can receive delivery events through [webhooks (callbacks)](https://www.vobiz.ai/docs/sms/webhooks.md). * **One-off reminders.** Developers can [send a single message](https://www.vobiz.ai/docs/sms/api/messages/send-message.md) tied to one invoice, hold it with `scheduledAt`, and use `idempotencyKey` so a retry doesn't text a customer twice. * **Cost.** SMS is billed per segment. Use [cost preview](https://www.vobiz.ai/docs/sms/api/messages/cost-preview.md) to see the count and price without sending anything, and find current rates on the [Vobiz pricing page](https://www.vobiz.ai/pricing/). Launching a broadcast sends real messages to every pending recipient and bills your account. Run it only with your own credentials, on a list you're entitled to message, after you confirm the wording and numbers. ## Frequently asked questions > [accordion] How do I politely remind someone to pay by SMS? > > Name your business, state the amount and reference, give the due date, and add one payment link. Thank the customer, and allow for the chance that they already paid. Leave out capital letters, exclamation marks, and guesses about why the money hasn't arrived. > [accordion] What is a polite way to say a payment is overdue? > > State what you can see rather than what they did. Saying we have not seen Rs 4500 for invoice INV2291 yet is factual, and it leaves room for a bank delay or a missed message. Then give the link and a number to call. > [accordion] Is a payment reminder SMS transactional or promotional in India? > > Usually neither. We read a due-date reminder to an existing customer as a service message under TRAI's definitions. A receipt within 30 minutes of payment can be transactional. Any offer in the text makes it promotional. Your DLT provider confirms the category. > [accordion] Do I need DLT registration to send payment reminders in India? > > Yes, for commercial SMS. You register your business, a sender header, and the exact wording on a DLT portal, along with links and callback numbers. Operators reject messages that don't match a registered template. > [accordion] What time should I send a payment reminder SMS? > > We suggest 10:00 to 19:00 IST. That range sits inside the 08:00 to 19:00 lender contact window in RBI's directions effective January 2027, and inside the default time bands for promotional messages in TRAI's regulations. Test within it using your own payment data. > [accordion] How many payment reminders are too many? > > We found no rule that sets a number. RBI's directions effective January 2027 bar excessive messaging by lenders without defining it. We suggest up to six messages per unpaid invoice, spaced days apart, stopping when the customer pays, disputes the amount, or calls you. ## Further reading on Vobiz * [India DLT for SMS](https://www.vobiz.ai/docs/sms/compliance/india-dlt.md) · [DLT entity registration](https://www.vobiz.ai/docs/best-practices/dlt-registration.md) · [UCC and NDNC compliance](https://www.vobiz.ai/docs/compliance/india/ucc.md) * [SMS broadcasts](https://www.vobiz.ai/docs/sms/broadcasts.md) · [Segments and encoding](https://www.vobiz.ai/docs/sms/channels/sms.md#segments-and-encoding) · [Opt-outs](https://www.vobiz.ai/docs/sms/opt-outs.md) * [Automated outbound calling](https://www.vobiz.ai/docs/solutions/automated-outbound-calling.md) · [WhatsApp message templates](https://www.vobiz.ai/docs/whatsapp/messaging/templates.md) ## Sources **Indian regulators and government** * TRAI, [Telecom Commercial Communications Customer Preference Regulations, 2018](https://trai.gov.in/sites/default/files/2025-01/RegulationUcc19072018.pdf), July 2018. * TRAI, [Telecom Commercial Communications Customer Preference (Second Amendment) Regulations, 2025](https://www.trai.gov.in/sites/default/files/2025-02/Regulation_12022025.pdf), February 2025. * TRAI, [Press release 11/2025 on the TCCCPR amendments](https://trai.gov.in/sites/default/files/2025-02/PR_No.11of2025.pdf), February 2025. * TRAI, [Press release 119/2026 on the Third Amendment](https://www.trai.gov.in/sites/default/files/2026-09/PR_No119of2026.pdf), 18 September 2026. * TRAI, [Third Amendment Regulations, 2026](https://www.trai.gov.in/sites/default/files/2026-09/Regulation_18092026.pdf), 18 September 2026. * TRAI, [Third Amendment Regulations, 2026 (copy hosted by MediaNama)](https://www.medianama.com/wp-content/uploads/2026/09/trai-amendments-unsolicited-communications.pdf), 18 September 2026. * TRAI, [Direction on pre-tagging of variables in SMS content templates](https://trai.gov.in/sites/default/files/2025-11/Directions_18112025_0.PDF), 18 November 2025. * PIB, [TRAI mandates whitelisted URLs, APKs, or OTT links for SMS traffic](https://www.pib.gov.in/PressReleasePage.aspx?PRID=2058943\®=48\&lang=2), September 2024. * RBI, [Press release on conduct in loan recovery and recovery agents](https://www.rbi.org.in/Scripts/BS_PressReleaseDisplay.aspx?prid=63305), 6 August 2026. * RBI, [Commercial Banks, Responsible Business Conduct, Fourth Amendment Directions, 2026](https://www.rbi.org.in/scripts/NotificationUser.aspx?Id=13665\&Mode=0), 6 August 2026. * RBI, [NBFCs, Responsible Business Conduct, Third Amendment Directions, 2026](https://www.rbi.org.in/scripts/NotificationUser.aspx?Id=13672\&Mode=0), 6 August 2026. * RBI, [Digital Payments, E-mandate Framework, 2026](https://www.rbi.org.in/Scripts/NotificationUser.aspx?Id=13374), 21 April 2026. * Development Commissioner (MSME), [Delayed payments under the MSMED Act, 2006](https://www.dcmsme.gov.in/publications/LegalFramework.pdf), undated summary. **Reference** * Wikipedia, ["GSM 03.38"](https://en.wikipedia.org/wiki/GSM_03.38). * Legal Information Institute, [47 CFR 64.1200](https://www.law.cornell.edu/cfr/text/47/64.1200). **Vendor guides** * Zoho, [Important TRAI mandate on URL whitelisting](https://help.zoho.com/portal/ar/community/topic/stay-in-the-know-important-trai-mandate-on-url-whitelisting-for-indian-crm-customers). * Razorpay, [Automated payment reminders](https://razorpay.com/blog/automated-payment-reminders). > [card] [Send your first reminder on Vobiz](https://www.vobiz.ai/docs/sms/quickstart.md) > > Set up the Vobiz Messaging API and send your first SMS. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.