Agency Ops9 min read

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.

Farhad, founder of GHL Spark
Farhad · Founder, GHL Spark
Cover illustration — four ascending teal bars on a dark green background, marked GHL Spark, Agency Ops

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.

StepWhat you doWhy it matters
1. Choose a payment processorPick a processor (or an all-in-one platform) that generates hosted payment linksThe link and its secure checkout page are the foundation of the whole system
2. Connect a texting toolUse a built-in SMS feature or connect a texting tool to your processorThis is what delivers the link to the customer's phone
3. Register your number for A2PComplete A2P 10DLC registration for your business messagingUnregistered business texts get filtered — your pay links may never arrive
4. Gather and record consentCollect agreement to text each customer, with a clear opt-outBusiness texting is governed by consent rules; this keeps you compliant
5. Build your pay link or invoiceCreate the payment request tied to the amount owedGenerates the unique, secure link you will send
6. Send, and automate the follow-upText the link, and schedule reminders if unpaidRemoves 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.

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.

ToolBest forStrengthWatch-out
Stripe payment links + a texting toolBusinesses already on Stripe wanting flexibilityPowerful, developer-friendly payment links you can send anywhereTwo systems to connect and reconcile; the texting is a separate tool
Square pay-by-textBusinesses already inside the Square ecosystemBuilt-in, simple, and works out of the box for Square usersTies you to Square; less flexible outside it
All-in-one (e.g. GoHighLevel)Businesses wanting the pay link tied to their CRMSends the link, takes payment, and logs it against the customer record automaticallyBroad 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:

  1. Choose a payment processor or all-in-one platform that generates secure hosted pay links.
  2. Connect a texting tool — built in, or linked to your processor — to deliver the link.
  3. Complete A2P 10DLC registration so your business texts actually arrive.
  4. Gather and record consent, with a clear opt-out on every message.
  5. Build the pay link or invoice tied to the exact amount owed.
  6. 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?
Text-to-pay, sometimes called pay-by-text or SMS payments, is a way of collecting payment by sending a customer a secure link in a text message. The customer taps the link, lands on a hosted checkout or invoice page, and pays by card, Apple Pay, or Google Pay in a few taps. The text itself never contains card details — it only carries a link to a secure, encrypted payment page run by your payment processor. It is popular with service businesses, contractors, clinics, and anyone who bills a customer who is not sitting in front of a card machine, because almost everyone opens a text within minutes.
How does text-to-pay work?
You create a payment request or invoice in your payment tool, which generates a unique, secure link tied to that specific amount and customer. That link is sent to the customer's mobile number by SMS. When they tap it, their phone opens the processor's hosted payment page, pre-filled with what they owe. They enter their card or use a saved digital wallet, the payment is processed and encrypted end to end, and both you and the customer get a confirmation. The money settles into your account on the processor's normal schedule, and in a good setup the payment is automatically marked against the right invoice and customer record.
Is text-to-pay secure?
Yes, when it is set up correctly. The security comes from the fact that the card is never entered into or sent through the text message. The SMS only carries a link; the actual card details are typed into a hosted, encrypted checkout page operated by a PCI-compliant payment processor. That means the sensitive data flows directly between the customer and the processor, and your business never touches or stores it. The one rule that makes it unsafe is asking a customer to text you their card number in plain text — never do that. A proper text-to-pay link keeps the card entirely inside the processor's secure environment.
Does text-to-pay keep me out of PCI scope?
Largely, yes. Because the customer enters their card on the processor's hosted payment page rather than on any system you control, you avoid handling, transmitting, or storing raw card data yourself — which removes most of the PCI DSS burden. You typically fall under the simplest self-assessment questionnaire rather than the full audit that applies to businesses that capture cards directly. You are still responsible for using a compliant processor and not circumventing the hosted page, but you are not building or securing a checkout of your own. This is one of the main practical reasons hosted pay-by-text links are preferred over any home-grown approach.
Do I need A2P 10DLC registration for text-to-pay?
In the United States, yes. Any business sending application-to-person (A2P) messages to customers over standard local (10-digit long code, or 10DLC) numbers must register the business and its messaging campaigns with the carriers. Text-to-pay messages are business messaging, so they fall under this. Registration tells the carriers who you are and what you send, which improves deliverability and keeps your messages from being filtered as spam. Most texting and all-in-one platforms walk you through this registration during setup. Skipping it means your pay links may simply never arrive. Our guide on the topic explains the process in more detail.
What does text-to-pay cost?
There are usually two layers of cost. The first is the payment processing fee — a percentage of each transaction plus a small fixed amount, which is the standard card-processing rate charged by your processor. The second is the messaging cost — a small per-segment fee for each SMS sent, plus any monthly platform or phone-number fee from your texting tool, and one-off A2P registration fees. For most small businesses the messaging costs are minor next to the processing fees. An all-in-one platform often folds the texting and payment features into one subscription, which can simplify the maths compared with stitching separate tools together.
What are the best use cases for text-to-pay?
Text-to-pay shines whenever the customer is not in front of a card reader. Common cases include field-service and trade businesses collecting payment after a job, clinics and salons taking deposits or balances, contractors invoicing for milestones, gyms and subscriptions recovering a failed payment, and any business chasing an overdue invoice. It is also excellent for deposits that hold an appointment, and for quick top-ups or add-on sales where sending a full invoice would be overkill. Anywhere you would otherwise say "I'll email you an invoice", a pay-by-text link almost always gets paid faster.
Does text-to-pay actually get me paid faster?
In practice, yes — and this is its main advantage. Text messages are opened within minutes by the vast majority of recipients, where emailed invoices can sit unread for days. Because the pay link lands on the phone the customer is already holding and the payment takes only a few taps, the friction between "you owe this" and "it is paid" is as low as it gets. Removing steps — no logging into email, no downloading a PDF, no setting up a manual transfer — is what compresses the payment timeline. For many businesses, switching an overdue invoice from email to text is the single fastest way to recover the money.
What is a payment link?
A payment link is a unique web address that opens a secure, pre-filled checkout page for a specific amount. Instead of building a checkout, you generate a link tied to a product, service, or invoice, and the customer pays by opening it. Payment links can be sent by text, email, chat, or embedded anywhere, and the payment is processed on the provider's hosted page. Text-to-pay is simply a payment link delivered by SMS. The link is what makes the whole thing secure and low-effort — it carries the customer straight into a compliant checkout without any card details ever travelling through the message.
Do I need consent to send someone a text-to-pay link?
Yes. Sending business text messages is governed by consent rules — in the US, the TCPA — and by carrier policy, so you should only text customers who have agreed to receive messages from you. In practice, consent is straightforward to gather: a checkbox at checkout, a line on your intake form, or a customer giving you their number to receive an invoice by text all count when properly recorded. You should keep a record of that consent and honour opt-outs immediately. Transactional messages like sending an invoice a customer expects sit on firmer ground than marketing, but consent and clear opt-out are still the baseline.
What are the best tools for text-to-pay?
It depends on what you already run. If you use a processor like Stripe, you can create payment links and send them through a separate texting tool — flexible, but two systems to connect and reconcile. Square offers built-in pay-by-text for businesses already on Square, which is simple if you live in that ecosystem. An all-in-one platform such as GoHighLevel bundles the SMS, the payment link, and the CRM together, so the send and the payment log against the same customer record automatically. The right choice comes down to whether you want to assemble tools yourself or have them arrive connected.
Can I automate text-to-pay reminders?
Yes, and this is where it becomes genuinely powerful. Rather than manually sending each link, you can trigger a pay-by-text message automatically when an invoice is created, when a job is marked complete, or when a payment fails, and schedule polite reminders if the link is not paid within a set time. Automating the sends and the follow-ups removes the human step that usually causes delay, and it means no invoice is ever forgotten. Platforms that combine texting, payments, and a CRM handle this natively, because the trigger, the message, and the payment status all live on the same data.

About the author

Farhad, founder of GHL Spark

Farhad

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

Want this handled for you?

We set up, configure and white-label your GoHighLevel SaaS — so you can sell it instead of building it.

Fixed quote · No lock-in · Launch-ready in ~7 days