Failed is not the same as cancelled
Copy the billing system's real state into the message. Do not tell a customer that service ended if the invoice is simply open or a retry is scheduled.
Dunning SMS workflow
Failed payment SMS: examples and automated setup
Send a useful billing message when a recurring charge fails. Keep the payment system in control of account status while VoxiSMS sends the text from your business's own Android phone and mobile number.
The short answer
What a failed-payment SMS workflow should do
A failed-payment SMS is a short billing message triggered by a recurring charge or invoice failure. With VoxiSMS, the event travels through Zapier or Make and the connected Android phone sends it through its own SIM and real number.
- 1 Send a short billing message when a recurring charge or invoice fails.
- 2 Give the customer one verified route to update the payment method or ask for help.
- 3 Use the billing system as the source of truth for payment state, retry timing, and recovery.
- 4 Connect the billing event to VoxiSMS through Zapier or Make.
- 5 Send from your own Android phone, SIM, real mobile number, and active carrier plan.
Message library
Failed payment SMS examples for each billing moment
Keep each text specific enough to explain why it arrived. Replace the placeholders with current billing data, use one verified link, and stop the sequence as soon as the payment state changes.
| Moment | Trigger | Example message | Stop condition |
|---|---|---|---|
| First failure | The initial recurring charge fails | [Business]: We couldn't process your [plan] payment. Update your payment method securely: [verified link]. | Payment succeeds or the account closes |
| Action required | The payment needs customer authentication | [Business]: Your [plan] payment needs one more step. Complete it securely here: [verified link]. | Authentication and payment complete |
| Retry scheduled | The billing system schedules another attempt | [Business]: Your [amount] payment did not go through. We'll retry on [date]. Update your payment details: [verified link]. | The retry date changes or payment succeeds |
| Still unpaid | The invoice remains open after a retry | [Business]: Your [invoice or plan] is still unpaid. Use this secure link to update payment: [verified link]. Reply if you need help. | Payment succeeds or support takes over |
| Payment restored | A previously failed payment succeeds | [Business]: Thanks, your [plan] payment is now complete. No further action is needed. | Send once |
| Human help | The customer replies or a case needs review | [Business]: We can help with your payment question. Reply with a good time to contact you. Please don't send card details by text. | A team member owns the conversation |
Event selection
Let the billing event decide when to send
Stripe documents invoice.payment_failed
as a subscription event and recommends notifying the customer to update
the payment method. Its subscription webhook guide also shows why later invoice and payment events should control the rest
of the sequence.
Keep the workflow narrow
One workflow can cover the first failure. A separate workflow can confirm recovery. This makes the trigger, message, and stop condition easier to test.
The link is part of the action
Send the customer to the billing provider or your own secure account page. The SMS should never collect complete payment details.
Delivery path
From payment failure to one useful text
The billing platform remains the source of account status. The automation prepares the recipient and message. VoxiSMS hands the SMS to the selected Android phone for sending.
Two setup paths
Connect the payment event with Zapier or Make
Start in the VoxiSMS integrations hub, then choose the workflow tool that already receives your billing event.
Zapier path
Use a failed-payment trigger, then add VoxiSMS
Zapier's current Stripe integration directory lists failed-payment and failed-invoice triggers. Map that record into the recipient and message fields in the approved VoxiSMS Zapier action.
Make path
Receive the event, map the message, and send
Make documents how custom webhooks trigger scenarios. After the event arrives, map the customer fields into the VoxiSMS Make module and choose the sending phone.
Setup checklist
Build the failed-payment SMS workflow step by step
Use the mobile setup you already operate
The selected Android phone sends through the mobile plan already active on its own SIM and real number. Keep that device connected while the workflow is running.
- 1
Choose the exact billing event
Start with a failed charge, failed invoice, or equivalent event that your billing system records. Keep one event definition per workflow.
- 2
Match the customer and purpose
Pull the current mobile number, business name, plan or invoice label, and the minimum context needed to explain the message.
- 3
Create a verified payment route
Use your billing provider's secure HTTPS page. Do not ask a customer to send card or bank details by SMS or reply.
- 4
Add the VoxiSMS action
In Zapier or Make, map the recipient and message into VoxiSMS, then select the connected Android phone that should send it.
- 5
Test failure and recovery states
Confirm the message for a test failure, a successful payment, a missing phone number, and an inbound reply before switching the workflow on.
Test more than the happy path
A billing notification is only useful when it reflects the latest record. Before launch, verify the failure, recovery, and exception paths with test customers.
- The customer, amount, date, and account context come from the right record.
- The payment link opens the intended secure billing page.
- A successful payment prevents later failure reminders.
- Missing or invalid phone numbers follow a visible exception path.
- Inbound replies reach the person or system responsible for billing help.
- Test records cannot message real customers.
Keep the message tied to the billing purpose
A payment notice and a promotion serve different purposes. Keep the dunning text focused on the customer's account, use the right contact permission for that message, and honor an opt-out or wrong-number reply without adding a marketing offer.
Failed-payment SMS questions, answered
Direct answers about dunning messages, Stripe events, replies, mobile numbers, and payment recovery states.
What is a dunning SMS?
A dunning SMS is a short billing message sent after a payment fails or remains unpaid. It should identify the business, explain the required action, and point to a verified payment route without asking for sensitive payment details by text.
Can VoxiSMS send a text after a Stripe payment fails?
Yes, when the Stripe event is connected through a supported workflow such as Zapier or Make. The billing platform supplies the payment event; VoxiSMS handles the SMS action through the connected Android phone.
Do I need a new SMS number?
No. VoxiSMS sends through the real mobile number on your connected Android phone and SIM, so the message can come from a number your business already uses.
Can a customer reply to a failed-payment text?
Yes. VoxiSMS can pass inbound replies back into the connected workflow, where your team can answer or update the billing record.
Does VoxiSMS charge per message?
VoxiSMS adds no per-message fee. The connected phone sends through the mobile plan already active on its SIM.
What should happen when the payment succeeds?
Treat the billing system as the source of truth. A successful-payment event should stop pending reminders and, when useful, trigger one short confirmation that no further action is required.
Send the first payment alert from your own Android number
Install VoxiSMS on the sending phone, connect one billing event, and test the failure, reply, and successful-payment paths end to end.