If you run a payday or short-term lending operation and tried to register an SMS campaign for due-date reminders or renewal offers, you probably got one of two outcomes: an outright rejection, or an approval that still leaves a third to a half of your messages never showing up on a borrower's phone. Neither is a mistake on your end. It's how the system is built.
Here's what's actually happening at each layer, what the law requires regardless of which channel you use, and what changes when you stop routing through a carrier-registered campaign at all.
Why carriers won't register a payday lending campaign
A2P 10DLC (Application-to-Person, 10-digit long code) is the vetting system the major carriers require before a business can send SMS from a standard phone number at scale. Every campaign gets classified by industry and use case, reviewed against The Campaign Registry's content rules, and either approved, throttled, or denied.
Payday and short-term lending don't get a marginal review. They're excluded by name. Twilio's own content policy lists "payday loans, short-term high-interest loans, third-party loans" as disallowed content for toll-free and long-code registration, with a narrow carve-out for first-party loan servicing that contains no promotional language. AWS's registration guidance for lenders is more explicit still: payday loans and short-term high-interest loans are flagged as "not eligible for resubmission" once a campaign is denied on that basis. There's no appeal path built into the process. You get one shot, and the category itself is the reason for the denial, not anything about your specific message copy.
Mortgage lenders, auto lenders, and other licensed direct lenders can register campaigns for payment reminders and loan status updates. Payday and short-term high-interest lending sit in a different bucket entirely, next to debt consolidation and credit repair marketing, and carriers treat all of them the same way: not open for negotiation.
The 30-50% you do get through isn't a bug
Some lenders find an aggregator willing to push traffic through anyway, usually mischaracterized under a different industry code or squeezed through a loophole that closes the next time carriers update their filters. When that happens, delivery commonly lands in the 30-50% range, with no visibility into which messages were blocked and no dashboard that tells you why. A2P filtering happens at the carrier level, after the message leaves the aggregator, so from your side a blocked message and a delivered one look identical. You just never hear back from half your borrowers.
That's not a sending problem you can fix with better copy or a cleaner list. It's the carrier declining to forward a category of traffic it has already flagged as high-risk.
Two different rules are in play, and only one of them changes with the channel
It's worth separating two things that get conflated constantly in this space: the carrier's A2P 10DLC gate, and the federal law that governs what you're allowed to say and to whom.
A2P 10DLC is a private, carrier-enforced traffic classification system. It has nothing to do with the Telephone Consumer Protection Act (TCPA) and nothing to do with the Fair Debt Collection Practices Act (FDCPA). It's Verizon, T-Mobile, and AT&T deciding what business traffic they'll route through their own networks, and payday lending has been placed in the category they won't touch.
P2P SMS, meaning a message sent from a real handset the way a person texts a friend, isn't subject to that gate. That's the entire basis for routing through a personal device instead of a registered campaign: the traffic looks like person-to-person texting because it is person-to-person texting, from a real 10-digit number on a real carrier line.
What doesn't change is the law governing content and consent.
TCPA still governs every message you send, on any channel
The TCPA, codified at 47 U.S.C. Section 227 with implementing FCC rules, requires prior express consent before sending a non-emergency text to a wireless number, and prior express written consent for anything promotional. Statutory damages run $500 per violation, and up to $1,500 if a court finds the conduct knowing or willful, with each individual text typically counted as a separate violation. That exposure is identical whether the message routes through a registered A2P campaign or a personal phone. Switching channels changes who will carry your traffic. It does not touch what you're legally required to have before you send.
Where the FDCPA and Regulation F actually apply, and where they don't
This is the part lenders get wrong most often. The CFPB's Regulation F requires debt collectors to include a working opt-out method in every text and email, and to stop contacting a consumer through any channel they've opted out of. But Reg F implements the FDCPA, and the FDCPA's definition of "debt collector" specifically excludes a creditor collecting its own debt in its own name. If you're a payday lender texting a borrower about their own loan, under your own business name, you are typically a creditor, not a debt collector, and Reg F's text-message provisions don't directly bind you.
That changes the moment you place the debt with a third-party collector, or collect under a name that suggests a different business is involved. At that point Reg F's opt-out and communication rules apply in full. Some states also extend debt-collection-style protections to first-party creditors through their own unfair-practices statutes, so "Reg F doesn't apply" is not the same as "nothing applies." TCPA consent and opt-out obligations apply either way, regardless of whether you're collecting under your own name or someone else's.
State usury and licensing rules ride along no matter what
Switching how you send a text doesn't touch state lending law. Eighteen states and the District of Columbia have effectively banned high-cost payday lending through usury rate caps, most commonly a 36% APR ceiling, while a separate group of states permit it under licensing regimes with their own disclosure and contact requirements. The current state-by-state breakdown is maintained by the National Conference of State Legislatures. If your loan product isn't legal or licensed in a borrower's state, no SMS channel makes that fact go away, and no SMS channel is the thing that gets checked when it becomes a problem.
What changes when the message comes from a real phone
Android Texter routes outbound SMS through a phone the operator owns, using the device's own carrier line instead of an aggregator's registered campaign. There's no TCR brand registration, no campaign classification to get flagged under "high-risk financial services," and no A2P filter deciding whether your due-date reminder is worth delivering. Delivery approximates whatever your own phone's normal SMS delivery rate is, because the message is, functionally, a normal text.
What it doesn't do is create any TCPA or state-law exemption. Consent capture, recordkeeping, and honoring opt-outs are still entirely the operator's responsibility, exactly as they'd be with any other channel. Android Texter suppresses replies of STOP, UNSUBSCRIBE, CANCEL, END, and QUIT automatically, which covers the mechanical side of opt-out handling, but it doesn't advise on whether a given message is compliant and doesn't represent that using it reduces your exposure under the TCPA. The law is the same law. The channel is just one that a carrier-vetting process doesn't get a vote on.
Building a payday SMS program that holds up
A few things worth doing regardless of which channel carries your traffic:
- Capture and timestamp consent at the point the borrower signs the loan agreement, and keep a record of exactly what they agreed to (transactional reminders versus marketing are different consent standards).
- Separate transactional messages (payment due, payment received, renewal deadline) from anything promotional, since promotional content carries the higher written-consent bar under TCPA.
- Build a working opt-out into every message thread, even if you've concluded Reg F doesn't technically apply to you. A borrower who texts STOP and keeps getting messages is a TCPA claim waiting to happen, independent of debt-collector status.
- Confirm your loan product is licensed in the borrower's state before you send anything, not after a complaint arrives.
- If you ever place an account with a third-party collector, treat every message from that point forward as subject to full Reg F rules, not just the ones you were already following.
Frequently Asked Questions
Can payday lenders use SMS at all without breaking carrier rules?
Yes, but not through a standard A2P 10DLC campaign, since carriers classify payday and short-term high-interest lending as ineligible content. Lenders either route through a personal-device P2P channel like Android Texter, which isn't subject to that gate, or limit themselves to the narrow first-party, non-promotional exceptions some aggregators allow.
Does Regulation F apply to a payday lender texting its own borrowers?
Usually not directly. Reg F implements the FDCPA, and a creditor collecting its own debt under its own name isn't a "debt collector" under that definition. It applies once the debt is placed with a third-party collector or collected under a different name. TCPA consent and opt-out rules apply to you either way.
Why did my SMS campaign get denied instead of just throttled?
Most aggregators, including Twilio and AWS End User Messaging, classify payday loans and short-term high-interest lending as high-risk financial content that's not eligible for resubmission. The denial is category-based, not content-based, so rewriting your message copy won't change the outcome.
If I use a P2P channel, do I still need borrower consent?
Yes. TCPA consent requirements apply to every SMS sent to a wireless number regardless of the sending channel. Routing outside A2P 10DLC removes the carrier's campaign gate, not the underlying federal or state law governing what you can send and to whom.
What counts as an opt-out I have to honor?
STOP, UNSUBSCRIBE, CANCEL, END, and QUIT are the standard keywords carriers and the CTIA treat as unambiguous opt-out requests. Once a borrower sends one, you need to stop texting that number, and continuing to send after a stop request is one of the more common TCPA claims lenders face.
If your due-date reminders and renewal notices are dying somewhere between your platform and a borrower's phone, the carrier gate is very likely the reason, not your message content or your list quality. Android Texter routes that traffic through a real phone instead of a registered campaign, so it isn't subject to the 10DLC classification that payday lending sits outside of. It doesn't touch your TCPA obligations, which stay exactly where they are today: on you, documented, and enforced the same way regardless of channel.