A customer’s phone number collected at the register usually isn’t enough to support marketing texts. Under FCC rules, autodialed or prerecorded sales texts need prior express written consent, and a number typed into a card terminal rarely meets that standard. California adds a second problem: Civil Code section 1747.08 bars asking a credit card customer for a phone number and recording it. A retailer facing either claim usually has defenses, if it can show how and when each number was collected.
Is a phone number given at checkout consent to marketing texts?
A number given at checkout is rarely written consent to marketing texts. Section 64.1200(f)(9) defines prior express written consent as “an agreement, in writing, bearing the signature of the person called” that authorizes advertisements or telemarketing messages to a specific number.
Section 64.1200(f)(9)(i) adds a disclosure requirement to the written agreement. The consumer must be told that signing authorizes telemarketing using an autodialer or prerecorded voice. The consumer must also be told that agreeing isn’t “a condition of purchasing any property, goods, or services.” A cashier’s spoken question and a number entered on a keypad don’t supply either disclosure.
Written consent matters only for some texts. Section 64.1200(a)(2) requires it for telemarketing sent with “an automatic telephone dialing system or an artificial or prerecorded voice.” After Facebook v. Duguid, many retail texting platforms aren’t autodialers in the narrow sense the Supreme Court adopted. A Do Not Call claim doesn’t depend on the dialing technology. Checkout numbers often belong to people on the national registry.
Why does California restrict asking for phone numbers during card payments?
California’s Song-Beverly Credit Card Act limits what a merchant can ask a card customer. Civil Code section 1747.08(a) bars a business that accepts credit cards from asking the cardholder to provide personal identification information that the business “writes, causes to be written, or otherwise records upon the credit card transaction form or otherwise.”
A phone number falls squarely within the statute. Section 1747.08(b) defines personal identification information as “information concerning the cardholder, other than information set forth on the credit card, and including, but not limited to, the cardholder’s address and telephone number.”
The California Supreme Court reads the statute broadly. In Pineda v. Williams-Sonoma Stores, Inc. (2011), the court held that even a ZIP code is personal identification information, and that “requesting and recording a cardholder’s ZIP Code, without more, violates the Credit Card Act.” If a ZIP code is covered, a full phone number is covered too.
Does it help if the customer gives the number voluntarily?
Calling the request optional doesn’t solve the Song-Beverly problem, because section 1747.08(a) bars both requesting and requiring the information. Pineda quoted an earlier decision explaining that the 1991 amendment “prevents a retailer from making an end-run around the law by claiming the customer furnished personal identification data ‘voluntarily.’”
The legislative purpose points straight at marketing lists. The Pineda opinion describes retailers that collect the information “to build mailing and telephone lists which they can subsequently use for their own in-house marketing efforts.” A checkout prompt that feeds a text marketing list is the practice the statute was written to stop.
Song-Beverly has exceptions, but they’re narrow. Section 1747.08(c)(4) allows the information when it’s “required for a special purpose incidental but related to the individual credit card transaction,” such as shipping or delivery. A delivery phone number is fine. Using that number later for promotions invites both a Song-Beverly argument and a TCPA claim.
What penalties apply under Song-Beverly?
Song-Beverly penalties are capped per violation. Section 1747.08(e) provides “a civil penalty not to exceed two hundred fifty dollars ($250) for the first violation and one thousand dollars ($1,000) for each subsequent violation.” The cardholder, the Attorney General, or a district attorney or city attorney can sue to collect them.
The amounts are maximums, not fixed awards. The Pineda court noted that the statute “does not mandate fixed penalties” and that the amount “rests within the sound discretion of the trial court.” Class actions still make the exposure real, because a chain’s register prompt repeats with every card transaction.
Section 1747.08(e) also contains a defense worth building toward. No penalty applies if the business shows “the violation was not intentional and resulted from a bona fide error made notwithstanding the defendant’s maintenance of procedures reasonably adopted to avoid that error.” Written register procedures and cashier training are the records that support that defense.
| Checkout practice | TCPA risk | Song-Beverly risk | Safer alternative |
|---|---|---|---|
| Cashier asks for a phone number while the card is being run | Number isn’t written consent for marketing texts | High: request and recording during a card transaction | Don’t ask during the card transaction |
| Card terminal prompts for a phone number for rewards | Weak consent record unless the screen carries the required disclosure | High if tied to the card payment | Separate sign-up with a written disclosure |
| Customer texts a keyword to join a list | Strong record if the confirmation text carries the disclosures | Low, because it’s outside the card transaction | Keep a log of each opt-in |
| Phone number taken for delivery, then used for promotions | Number given for delivery doesn’t support marketing texts | Exception covers delivery only | Separate consent before any promotion |
How can a retailer build a text list without these problems?
A text list built outside the card transaction avoids most of the risk. Keyword opt-ins, website forms, and signage with a short code let customers sign up on their own phones. Those methods also create a time-stamped record of each opt-in, which is the evidence a defendant needs when a consent dispute reaches court.
Written consent records are worth the extra step. Section 64.1200(f)(9)(ii) says a signature “shall include an electronic or digital form of signature” recognized under federal or state law. A reply text confirming the sign-up, after a message carrying the required disclosures, is the common method. Checkout staff shouldn’t collect numbers for the list at all, because their prompt is what a Song-Beverly plaintiff will point to.
Do Not Call rules still apply to customers who buy. Section 64.1200(f)(5) recognizes an established business relationship for 18 months after a purchase. That relationship only answers a Do Not Call claim. It doesn’t supply written consent for autodialed or prerecorded marketing.
What should a retailer do after a TCPA or Song-Beverly claim?
The first priority is to keep the records showing how each number was collected:
- Put a litigation hold on text logs, texting platform data, point-of-sale prompt settings, and the opt-in records for the numbers involved.
- Pull the opt-out logs and internal do-not-call lists, with the date each request arrived.
- Pull the National Do Not Call Registry scrub records and the registry version dates used for each campaign.
- Collect the texting vendor contracts, register screen images, cashier training materials, and message templates.
- Talk to a lawyer before responding to the demand letter, contacting the customer, or offering anything to settle.
Retailers reviewing their options can see how the firm approaches defending TCPA class actions involving retail text programs. The firm’s post on prior express written consent covers the disclosure requirements in more depth. The post on web form consent covers online sign-ups, and the post on text-to-join programs covers keyword opt-ins.
Questions retailers ask about checkout phone numbers
Can a store ask for a phone number if the customer pays cash?
Song-Beverly applies to credit card transactions, so a cash sale doesn’t raise the same statutory issue. The TCPA still applies to any marketing texts sent later. A cash customer who gives a number to a cashier hasn’t signed a written agreement, so the store needs a separate written consent before sending autodialed or prerecorded promotions.
Can a store ask for a phone number after the payment is complete?
Timing matters, but it isn’t a safe harbor on its own. A request made after the card transaction, with no link to the payment, is easier to defend under Song-Beverly. It still doesn’t create written consent under the TCPA. The cleaner approach is a separate opt-in the customer completes on their own phone.
Can a cashier check a customer’s ID during a card payment?
Section 1747.08(d) lets a business require “reasonable forms of positive identification,” such as a driver’s license, before accepting a card. The catch is recording. The statute allows the check only if none of the information on the ID is written or recorded. A cashier who types details from the license into the register loses that protection.
If your company is facing a checkout text claim
If your company is accused of texting customers whose numbers were collected at the register, the register prompt and the opt-in records usually decide the case. Rosenberger + Kawabata represents businesses defending TCPA lawsuits and class actions through its business litigation practice, including claims involving marketing texts to phone numbers collected at checkout. Contact Rosenberger + Kawabata online for a confidential consultation, or call (310) 894-6921.
Sources
47 C.F.R. section 64.1200 (prior express written consent, telemarketing consent, established business relationship).
Civil Code section 1747.08 (Song-Beverly Credit Card Act limits on personal identification information).
Pineda v. Williams-Sonoma Stores, Inc., 51 Cal.4th 524 (2011) (ZIP code is personal identification information under section 1747.08).
Facebook, Inc. v. Duguid, 592 U.S. 395 (2021) (autodialer definition).
47 U.S.C. section 227 (TCPA private rights of action and damages).
This post is general information about the Telephone Consumer Protection Act and related laws as of November 19, 2026. It is not legal advice, and reading it does not create an attorney-client relationship. Courts and the FCC change the rules in this area often, and the outcome of any claim depends on its facts. Past results do not guarantee future outcomes.