How to Set Up Text-to-Pay
A plain-English guide to setting up text-to-pay — how it works, the security and consent rules, the fees, and the tools that send and track the link.
In short
Text-to-pay lets a customer pay by tapping a secure link you send to their phone by SMS. To set it up, you connect a payment processor to a texting tool, register your business phone number for A2P messaging with the carriers, build a payment or invoice link, and send it to a customer who has agreed to receive texts from you. When they tap the link they land on a hosted, encrypted checkout page and pay by card or digital wallet in a few seconds — you never touch or store the card number, so you stay out of most PCI scope. The whole appeal is speed: a link on the phone someone is already holding gets paid far faster than an emailed invoice. This guide covers exactly how it works, how to set it up securely and compliantly, the fees to expect, and the tools that do it.
Key takeaways
- Text-to-pay is a secure payment link sent by SMS — the customer taps it, pays on a hosted encrypted page, and you never see or store the card number.
- Setup has four moving parts — a payment processor, a texting tool, an A2P-registered business number, and explicit consent from the person you are texting.
- It is secure and stays out of most PCI scope because the card is entered on the processor's hosted page, not in the text itself — never ask anyone to text you a card number.
- Speed is the whole point — a pay link on the phone someone is already holding gets paid in minutes, where an emailed invoice can sit for days.
- The cleanest setups tie the pay link to your CRM so the send, the payment, and the customer record all update in one place with no manual reconciliation.
You finished the job, the customer is happy, and now you need to get paid. You could email an invoice and wait — or you could send a link to the phone that is already in their hand and be paid before you have packed up your tools. That second option is text-to-pay, and it is one of the simplest, fastest ways for a small business to collect money. This guide explains exactly what it is, how it works, how to set it up securely and legally, what it costs, and which tools do it well.
What is text-to-pay and how does it work?
Text-to-pay is a way of collecting payment by sending a customer a secure link in a text message — they tap the link, pay on a hosted encrypted checkout page in a few seconds, and the card details never travel through the text itself. It is also called pay-by-text or SMS payments, and it works for any business that needs to bill someone who is not standing in front of a card reader.
Here is the flow, step by step. You create a payment request or invoice in your payment tool, which generates a unique link tied to that exact amount and customer. That link goes out by SMS. The customer taps it, their phone opens your processor's hosted payment page pre-filled with what they owe, and they pay by card, Apple Pay, or Google Pay. The payment is encrypted end to end, both sides get a confirmation, and the money settles into your account on the processor's normal schedule. In a well-built setup, the payment is automatically marked against the right invoice and customer record with no manual reconciliation.
The reason this matters is friction. An emailed invoice asks the customer to open email, find the message, download a PDF, and set up a transfer — four chances to put it off. A text lands on the device they check dozens of times a day, and paying is a couple of taps. That is the whole point, and it is why the same invoice sent by text is paid so much faster than one sent by email. It sits naturally alongside the fundamentals in our guide on how to accept payments as a small business.
How do you set up text-to-pay?
Setting up text-to-pay has four moving parts. You need a payment processor, a texting tool to deliver the link, a business phone number registered to send business messages, and consent from the people you are going to text. Here is how they fit together.
| Step | What you do | Why it matters |
|---|---|---|
| 1. Choose a payment processor | Pick a processor (or an all-in-one platform) that generates hosted payment links | The link and its secure checkout page are the foundation of the whole system |
| 2. Connect a texting tool | Use a built-in SMS feature or connect a texting tool to your processor | This is what delivers the link to the customer's phone |
| 3. Register your number for A2P | Complete A2P 10DLC registration for your business messaging | Unregistered business texts get filtered — your pay links may never arrive |
| 4. Gather and record consent | Collect agreement to text each customer, with a clear opt-out | Business texting is governed by consent rules; this keeps you compliant |
| 5. Build your pay link or invoice | Create the payment request tied to the amount owed | Generates the unique, secure link you will send |
| 6. Send, and automate the follow-up | Text the link, and schedule reminders if unpaid | Removes the human delay that slows most collections |
Work through those in order and you have a working system. Two of them deserve a closer look because people most often get them wrong: security and the A2P registration.
Is text-to-pay secure and PCI-compliant?
Yes — when it is set up the right way, text-to-pay is secure and keeps you out of most of the compliance burden. The security rests on one principle: the card is never entered into, or sent through, the text message. The SMS only ever carries a link. The actual card number is typed into a hosted, encrypted checkout page run by a PCI-compliant processor, so the sensitive data flows directly between the customer and the processor. Your business never touches, transmits, or stores it.
That has a real practical benefit. Because you are not capturing card data on any system you control, you avoid most of the PCI DSS scope that applies to businesses running their own checkout. You typically fall under the simplest self-assessment rather than a full audit. You are still responsible for using a reputable processor and not circumventing its hosted page — but you are not building or securing a payment form yourself.
There is exactly one thing that makes text-to-pay unsafe, and it is worth stating plainly: never ask a customer to text you their card number. A card number sitting in an SMS thread is unencrypted, stored on two phones and a carrier's systems, and completely outside PCI protection. Proper text-to-pay never does this. If a tool or a person asks a customer to reply with card details, that is not text-to-pay — it is a security incident waiting to happen.
Do you need A2P registration and consent?
In the United States, two rules govern sending these messages, and both are easy to satisfy if you plan for them.
The first is A2P 10DLC registration. Any business sending application-to-person messages to customers over standard local numbers must register the business and its messaging campaigns with the mobile carriers. Text-to-pay is business messaging, so it qualifies. Registration tells the carriers who you are and what you send, which is what keeps your messages from being filtered as spam and ensures your pay links actually arrive. Most texting and all-in-one platforms guide you through it during onboarding. Skip it and your carefully built pay links may silently never reach anyone. Our companion guide, SMS marketing, goes deeper on getting business texts delivered.
The second is consent. Business texting is governed by consent rules and carrier policy, so you should only text customers who have agreed to hear from you. Gathering it is simple — a checkbox at checkout, a line on your intake form, or a customer handing you their number specifically to receive an invoice by text all count when you record them properly. Keep a record of the consent, and honour any opt-out immediately. A customer expecting an invoice they asked for sits on firmer ground than unsolicited marketing, but consent and a clear way to opt out are always the baseline.
What are the best use cases for text-to-pay?
Text-to-pay earns its keep any time the customer is not in front of a card reader. The strongest cases include:
- Field service and trades collecting payment right after finishing a job on site.
- Clinics, salons, and studios taking a deposit to hold an appointment or a balance on the day.
- Contractors invoicing for a milestone and getting paid without an email chase.
- Overdue invoices — switching a stubborn emailed invoice to a text link is often the single fastest way to recover the money.
- Failed subscription payments — a quick pay-by-text link recovers a lapsed charge before it becomes churn.
- Deposits and add-on sales where sending a full invoice would be overkill.
The common thread is speed and simplicity. Anywhere you would otherwise say "I'll email you an invoice", a pay link by text almost always gets paid sooner. If invoicing is part of your workflow, our guide on how to send invoices pairs naturally with this — text-to-pay is simply the fastest way to deliver the invoice's pay-now link.
Which tools do text-to-pay best?
Once you are past the concept, the practical question is which tools to run. Here is an honest comparison of three common approaches, including the all-in-one category.
| Tool | Best for | Strength | Watch-out |
|---|---|---|---|
| Stripe payment links + a texting tool | Businesses already on Stripe wanting flexibility | Powerful, developer-friendly payment links you can send anywhere | Two systems to connect and reconcile; the texting is a separate tool |
| Square pay-by-text | Businesses already inside the Square ecosystem | Built-in, simple, and works out of the box for Square users | Ties you to Square; less flexible outside it |
| All-in-one (e.g. GoHighLevel) | Businesses wanting the pay link tied to their CRM | Sends the link, takes payment, and logs it against the customer record automatically | Broad platform; needs proper setup to pay off |
The right pick depends on what you already have. If you live in Stripe and do not mind connecting a separate texting tool, Stripe payment links are flexible and robust. If you already run Square, its built-in pay-by-text is the path of least resistance. Both, though, leave you either bridging two systems or working inside one vendor's walls.
An all-in-one platform like GoHighLevel sits in a different spot. Instead of a payment tool that you then connect to a texting tool and a CRM, it bundles all three, so it is the one option here that sends the pay link, processes the payment, and logs it against the customer's record in a single place. That matters for the two things that actually make text-to-pay work — getting the link delivered and automating the follow-up — because the trigger, the message, and the payment status all run on the same data, with nothing to integrate or reconcile. When a customer pays, their record, their invoice, and their pipeline all update at once. The trade-off is that a platform doing this much needs to be configured properly before it earns its keep. You can see how it fits the wider picture on our web, email & ecommerce hub.
Whichever route you choose, the tool is not the system. A secure hosted link, a registered number, recorded consent, and automated follow-up are the system. Software just makes it run without you.
Putting it together
Here is the whole thing as a checklist you can act on this week:
- Choose a payment processor or all-in-one platform that generates secure hosted pay links.
- Connect a texting tool — built in, or linked to your processor — to deliver the link.
- Complete A2P 10DLC registration so your business texts actually arrive.
- Gather and record consent, with a clear opt-out on every message.
- Build the pay link or invoice tied to the exact amount owed.
- Send it, then automate reminders so no unpaid link is ever forgotten.
Do those six things and you get paid faster — not because your customers changed, but because you put the pay link on the device they are already holding and removed every step between owing and paying. That is the entire point of text-to-pay: to close the gap between finishing the work and having the money in your account.
If wiring the processor, the texting, the A2P registration, and the automated reminders together sounds like more time than you have, that is fair — each part is simple, but connecting them so they run themselves takes real hours. It is exactly the kind of system we build for clients. You can see what it costs on our pricing page, or just book a call and we will map your payment flow with you.
Frequently asked questions
What is text-to-pay?
How does text-to-pay work?
Is text-to-pay secure?
Does text-to-pay keep me out of PCI scope?
Do I need A2P 10DLC registration for text-to-pay?
What does text-to-pay cost?
What are the best use cases for text-to-pay?
Does text-to-pay actually get me paid faster?
What is a payment link?
Do I need consent to send someone a text-to-pay link?
What are the best tools for text-to-pay?
Can I automate text-to-pay reminders?
About the author

Founder, GHL Spark
Farhad is the founder of GHL Spark, where he builds and white-labels GoHighLevel SaaS platforms for agencies and SaaS operators. He writes about the parts of GoHighLevel that actually break in production — A2P registration, onboarding, support load and automation.
More from Farhad