How SMS Mobile Payments Work: A Guide to Accepting Payments by Text
See how SMS mobile payments work in a medical practice, what a payment provider charges, and which consent rules apply before your first text goes...
6 min read
Alvin Amoroso : Published Updated
A $40 co-pay costs more to chase than it returns. Print the statement, stamp it, mail it, wait, mail it again.
Two stamps at $0.78 each, plus the paper and the staff minutes, against $40. Most billing leads know the math and keep sending anyway.
Text to pay replaces that cycle with a link. The patient taps, pays, and the balance clears the same afternoon.
Our position is that the speed is the obvious part, and the security design is the part worth understanding. Where the card number goes decides what you have to prove at audit.
What follows: how the flow works, what it saves, how card data is protected, and how to choose a provider.
Four steps, plus one piece of plumbing that does the real work.
Something marks a balance as owed. A visit closes, a claim adjudicates, or a statement posts.
The trigger decides the timing. Practices tracking payment ROI in Elation Health fire the request when the clinical note is signed. The ask lands while the visit is fresh.
A short text carries the amount and a link. It names the practice and the balance, and nothing else. Keep clinical detail out. Standard SMS is not encrypted, and a diagnosis on a lock screen is a disclosure.
The link opens a page hosted by the payment processor, not by the practice. The patient types the card number there. No account, no password. That single difference is why text-to-pay collects where a portal does not.
A receipt lands in the same thread. The balance posts back to the chart, so nobody reconciles it by hand on Friday.
A gateway passes the card to the processor. Card details are stored there, and a token comes back. A token is a stand-in string. It maps to the real card only inside the processor's vault. A copy taken from your system buys an attacker nothing.
That token is what lets a patient pay a second balance without retyping a card. The practice stores the token and never the number.
Pay by text and text to pay describe the same flow. The term changes by industry; the mechanics do not.
The payment does not happen inside the message. SMS carries a link, and the transaction happens on a web page. Carrier billing, where a charge lands on a phone bill, is a different thing entirely. It has no place in healthcare billing.

Paying takes one tap and about 30 seconds. Compare that with finding a portal password, or writing a check and buying a stamp.
A mailed statement takes days to arrive and days to come back. A text arrives in seconds, and most payments land the same day.
Balances get harder to collect as they age, which is why the first ask should go out early. An automated series beats a single statement and a hope.
A billing question arrives in the same thread as the request. Staff answer in writing instead of playing voicemail tag over $40.
This is the overstated one. Our own pages have carried a 98% open rate for years, with no source behind it. We are not repeating it here.
What holds up is simpler. A text arrives on a device the patient already has, with no login between them and the payment page.
A First-Class Forever stamp is $0.78, and a statement cycle usually needs two. Count the paper, the envelope, and the staff minutes on top.
The practice never receives the card number, so the risk sits with the processor that is built to hold it.
The sequence runs itself and stops when payment posts. Staff work the replies that need a person, not the list.
Most vendor pages stop at the words PCI compliant. A useful overview of text-to-pay security and tokenization says who holds the card number. It also says what that does to your audit.
If the payment page is hosted by a validated processor, card data never touches your network. You store a token and a receipt. That is the whole security design. Everything else follows from it.
PCI DSS v4.0.1 is the standard in force. Version 3.2.1 retired on March 31, 2024, and the 51 future-dated requirements became mandatory on March 31, 2025.
A practice that never receives, sends, or stores card data usually validates on SAQ A, the shortest self-assessment. Your acquiring bank confirms which one applies to you.
That scope reduction is the real saving. It is fewer controls to run and a shorter questionnaire, not a faster checkout.
Billing is a payment activity under treatment, payment, and health care operations. Texting a patient about a balance is permitted. Keep clinical detail out of the message.
On TCPA, a payment request to an existing patient about their own bill is transactional rather than marketing. In January 2025, the Eleventh Circuit vacated the FCC's one-to-one consent rule. Guidance written in 2024 about preparing for it is out of date.
Honor opt-outs across every location on the first request. One STOP should stop all of them.
Any business billing small amounts to many people gains. Patient payments gain most, because the balance arrives weeks after the service.
A restaurant collects at the table. A clinic bills after the claim clears. By then the visit is a memory and the statement is junk mail.
Small practices feel it hardest. A text-to-pay guide for Practice Fusion users covers co-pay requests before the visit and balance requests straight after it.
Setup is mostly decisions, not configuration. Make them before the first send.
Enterprise groups face a sixth. Teams deploying text to pay across GE Centricity sites set the rules centrally. Pilot two or three locations before the network sees it.
Four questions separate the real options. Ask them before the demo, because the answers are usually yes or no.
Curogram Highlight: What to Ask Any VendorDoes the balance come from the chart, or does somebody type it? Curogram's Text to Pay pulls the amount from the EMR, so the figure in the text matches the ledger. Does the patient need an account? With Curogram's text to pay, the link opens a secure page with no login and no app. The practice can attach the bill or the explanation of benefits. Does a reply reach a person? Two-way texting routes billing questions to the billing team in the same thread. Curogram is HIPAA-compliant and SOC 2 Type II certified. |
Three shifts are already underway, and none of them is speculative.
Digital wallets are becoming the default tap on a hosted payment page, which removes card entry from the flow altogether. Payment plans are moving from a phone call to a link. A $600 balance becomes six texts instead of a collections referral.
Good-faith estimates under the No Surprises Act have made patients expect a number before the visit. A request that quotes an estimate they already saw gets paid more readily than one that surprises them.
Text-to-pay works because it removes steps. No stamp, no portal password, no check in a drawer.
The security design is the part worth repeating to a nervous board. Card data goes to a validated processor and a token comes back. The practice stores a string that is useless to a thief.
That design is also what usually keeps a practice on SAQ A, the shortest PCI self-assessment. Ask your acquirer to confirm it in writing.
Start with one decision rather than a project. Pick the trigger, write one message, and send it for a month. Then compare what came back against a stack of $0.78 stamps.
See a payment request built from a real balance, with the patient's side on a phone. Book a Curogram demo.
See how SMS mobile payments work in a medical practice, what a payment provider charges, and which consent rules apply before your first text goes...
A practical 2026 guide to healthcare payment technology: what the tools do, which layers matter, and how to roll out without jamming up your front...
Where billing money actually leaks, why denials get blamed for front-desk errors, and the 7 fixes that move days in A/R. With 2026 MGMA and Experian...