A good payment reminder message names your business, the invoice number, the exact amount, the due date and one link to pay, all in under 160 characters. Send a short, polite set (before the due date, on the day, after it's overdue and a final notice), because most late payers forgot. Very few are refusing to pay.

This post gives you copy-paste templates for each stage. It also covers four practical points: what makes these texts transactional, why payment links get filtered, how to keep amounts accurate, and how to automate the schedule so a customer who already paid never gets chased.

Why text payment reminders at all

Email reminders land in a crowded inbox next to newsletters and receipts. A text gets read within minutes in most cases. Response rates on opted-in transactional texts are often far higher than on email, though we're giving a rough industry pattern here, not a measured figure.

The bigger point is friction. A text with a working pay link turns "I'll deal with it later" into a 30-second task on the phone that's already in their hand. That's why the templates below put the link in every message and cut everything else.

The payment reminder message templates

Swap the bracketed fields for your own data. Each template stays near or under 160 characters once filled in with typical values. Test yours with real data, because a long business name or URL can push it into a second segment.

1. Before the due date (3 days out)

Hi [Name], a friendly reminder from [Business]: invoice #[1042] for $[amount] is due [Fri, Mar 6]. Pay here: [link]. Reply STOP to opt out.

Put the opt-out line in the first text of the series. It's good practice, and carriers look for it.

2. On the due date

Hi [Name], invoice #[1042] for $[amount] from [Business] is due today. You can pay at [link]. Questions? Just reply here.

"Just reply here" matters. Some people won't pay because they have a question about a line item. A reply gives them a way to ask instead of ignoring you.

3. Overdue, gentle (3 days late)

Hi [Name], it's [Business]. Invoice #[1042] ($[amount]) was due [Mar 6] and still shows open. If you've already paid, thank you, please ignore this. Pay: [link]

The "if you've already paid" line covers you when a payment is in flight. It also keeps the tone friendly.

4. Overdue, with an offer to help (10 days late)

Hi [Name], [Business] here. Invoice #[1042] for $[amount] is now 10 days past due. If timing is a problem, reply and we can work out a plan. Pay: [link]

Offering a plan isn't soft. It's the fastest way to learn whether you're dealing with forgetfulness, cash flow or a dispute.

5. Final notice

Hi [Name], final reminder from [Business]: invoice #[1042] for $[amount] is [21] days past due. Please pay by [Mar 31] or reply to talk it through. [link]

If something really happens next, such as a late fee under your agreement or a paused service, say so plainly in one clause. Don't threaten anything you won't do, and don't hint at legal action in a text.

Two extras worth having

  • Partial payment received: "Thanks [Name], we got $[paid] toward invoice #[1042]. Remaining balance: $[balance]. Pay anytime at [link]."
  • Paid in full: "Thanks [Name], invoice #[1042] is paid in full. Receipt: [link]." This closes the loop and makes the earlier reminders feel like service rather than pressure.

Tone rules that keep it polite

  • Lead with the business name. An unknown number asking for money looks like a scam. Name yourself in the first ten words.
  • One ask per text. Pay, or reply. Don't add a promo.
  • No all caps, no exclamation stacks, no "URGENT". These read as hostile to people and as spam to carrier filters.
  • Escalate facts, not emotion. Each text adds one fact (due today, 10 days late, final date). The wording stays calm throughout.
  • Stop at the final notice. After that, a person should call or write. Five texts is plenty.

Is a payment reminder transactional or marketing?

A reminder about an invoice a customer already owes your business is generally treated as an informational, transactional message. For 10DLC, that usually means registering under an account-notification or customer-care style use case, not marketing. Picking the wrong one is a common cause of throttling, and our guide to matching your 10DLC use case to what you actually send walks through it.

Three caveats:

  1. Transactional texts still need consent. Collect the mobile number with clear permission to text about the account. Put it in your terms or invoice signup. Compliance is your responsibility, and we can't make that call for your business.
  2. Don't mix in marketing. "Pay invoice #1042, and check out our spring sale!" turns an account notification into a marketing message, both in carriers' eyes and under TCPA.
  3. Third-party debt collection is a different category. If you collect debts owed to someone else, stricter rules apply (federal debt-collection rules and carrier restrictions). These templates are for first-party invoices only.

Payment links and filtering risk

Texts that say "pay" and contain a link look a lot like phishing. That's exactly the pattern carrier filters are built to catch. Registration doesn't exempt you from content filtering. Our post on messages getting filtered after approval covers that in detail. For payment links specifically:

  • Never use a public URL shortener (bit.ly and similar). Shared shorteners are heavily abused, and filters treat them harshly.
  • Use a domain you own, ideally the same domain as your website or invoices. A branded short domain is fine if it's consistently yours.
  • Keep the link domain the same across every text. Rotating domains looks evasive.
  • Match your registration sample messages. If your registered campaign samples include a pay link, filters and reviewers have already seen the pattern.
  • Don't put sensitive data in the text. Leave out full account numbers and payment card details. In healthcare, avoid anything that reveals treatment. The link should lead to a page that requires the customer to log in or verify who they are.

Keep amounts and details accurate

A wrong amount in a payment reminder does more damage than no reminder. It creates disputes, refund requests and support load. The rules:

  • Pull the amount at send time, not schedule time. If a reminder was queued Monday and a partial payment landed Tuesday, Wednesday's text must show the new balance.
  • Check paid status before every send. The single worst reminder is "your invoice is overdue" to someone who paid yesterday.
  • Use the invoice number every time. Customers with multiple invoices need to know which one you mean.
  • Show dates in the customer's terms. "Fri, Mar 6" beats "2026-03-06".
  • Let quiet hours do their job. On Ready, a text due during the recipient's quiet hours is held and sent later, and it's charged only when it sends. Nobody gets a 6 AM money text. Campaigns, drip campaigns and automations wait up to 24 hours for the window; a one-to-one or API text is held only if the window opens within 6 hours, otherwise it is refused and must be resent; a one-to-one reply to someone who texted you in the last 24 hours goes out at any hour.

Automating the reminder schedule in Ready

We make Ready, so here's how this runs on it. There are two common setups.

Option A: drip campaign in the app

Save the five templates as reusable templates. Build a drip campaign with five steps: the first sends as soon as a customer is enrolled, then the next four wait 3, 3, 7 and 11 days. Enroll each customer 3 days before the invoice is due, so the texts land 3 days before, on the due date, and 3, 10 and 21 days after it. Draft with AI and a Spam check in Ask AI can tighten the wording before you save. The key operational rule: when an invoice is paid, take that customer out of the remaining steps, so the paid status always beats the schedule.

Option B: your billing system calls the API

If you run invoicing software or a platform, the cleanest pattern is to let your billing system decide. Each day it finds unpaid invoices hitting a reminder step and sends one text per invoice:

POST https://api.tryready.com/v1/messages
X-API-Key: <key>
Idempotency-Key: <uuid for invoice 1042, step 3>
Content-Type: application/json

{"to": "+12125550199", "body": "Hi Dana, it's Acme Plumbing. Invoice #1042 ($240.00) was due Mar 6 and still shows open. If you've already paid, thank you. Pay: https://pay.acmeplumbing.example/1042", "consent_attested": true}

Generate the Idempotency-Key per invoice and step, so a retried job never texts the same reminder twice. Opt-outs, numbers on your Ban list and known landlines are refused up front and not charged. Full request details are in the messages API docs, and the quickstart gets a key working.

If you're a platform sending reminders on behalf of many businesses, each business gets its own sub-account, numbers and 10DLC registration, so one customer's sloppy list doesn't drag down another's delivery. We cover who registers what in 10DLC for SaaS platforms.

What it costs: a worked example

Here's an example under stated assumptions. A business sends reminders on 300 invoices a month, every text is one segment, and on average each invoice gets four reminders before it's paid or closed.

  • 300 × 4 = 1,200 segments
  • Standard rate: 1,200 × $0.0075 = $9.00
  • Plus the carrier fee: 1,200 × $0.0045

Replies are billed like a sent text (the $0.0075/segment rate plus the $0.0045 carrier fee), so add those to the count. The quoted rate excludes the optional compliance surcharge: DNC/litigator scrubbing and landline validation are $0.003 extra per segment each, only when switched on, and both are off by default.

One emoji changes the math. A 150-character reminder is 1 segment in plain text. With an emoji the limit drops to 70 characters per segment (67 when split), so the same text becomes 3 segments, 3x the cost. Leave emoji out of money texts. They don't help the tone anyway.

Registration is $25 at submit for the first month ($25/mo for registration, plus $2/mo per number), and most approvals take 2 to 7 days. Your first 20 one-to-one texts are free, so use them to test your templates on your own phone before you register. To send, you add a card and get a number, which is $2 a month with the first month charged when you get it.

For the final-notice stage, some teams switch to a call. The Ready Dialer lets you click to call from the dial pad at $0.025/min, so a human conversation follows the last text instead of a sixth reminder.

The practical takeaway

Keep every text short, named and specific: business, invoice number, exact amount, date, one link from your own domain. Escalate the facts, not the tone, and stop at the final notice. Check paid status and the current balance right before each send. If you want to see how the drip campaign or API version behaves with your real invoices, create an account and send your templates to yourself first.

FAQ

How many payment reminder texts should I send?

Four to five per invoice is a sensible ceiling: before the due date, on the day, one or two overdue reminders, then a final notice. More than that tends to cause opt-outs, not payments.

What time of day should payment reminders go out?

Business hours in the recipient's time zone, typically mid-morning. On Ready, texts that fall in the recipient's quiet hours are held and sent later automatically. Campaigns, drip campaigns and automations wait up to 24 hours for the window; a one-to-one or API text is held only if the window opens within 6 hours, otherwise it is refused and must be resent; a one-to-one reply to someone who texted you in the last 24 hours goes out at any hour.

Do I need 10DLC registration just for payment reminders?

Yes, for ongoing sending from a regular local number. Unregistered traffic gets carrier-filtered. On Ready an account can send up to 500 texts a month before registering, and then it has to register.

Can I include a payment link without getting filtered?

Usually, if the link uses a domain you own, stays consistent across texts and matches your registered sample messages. Public URL shorteners are the most common cause of filtered payment texts.

Can I add a late fee warning to the reminder?

Only if the fee is in your agreement with the customer, and only as a plain statement of fact in the final notice. Keep threats and legal language out of texts entirely.