%202%20(2).png){kind=avatar}
The sale is already made. A customer said yes to a custom setting and owes a deposit. A repair is polished and sitting on the will-call shelf. A longtime client texted back about a bracelet and wants it shipped. The only thing left is the money, and the customer is not standing in your store.
For those moments, the best way for a jewelry store to collect payment over text message is text-to-pay: a secure payment link sent inside the conversation the customer already has with your store, from a clienteling platform like Clientbook that records the payment on that client's conversation. It beats an emailed invoice because it lands where the customer actually replies, and it beats a phone payment because nobody reads a card number out loud.
It is not a new channel or an app to download: the link travels through a conversation that already exists, from a number the customer recognizes, and no card details ever appear in the thread. Here is how it works, step by step.
How Text-to-Pay Works, Step by Step
The steps below follow the flow in Clientbook, where payment requests live inside the messaging inbox next to the client's profile; other platforms differ in the details.
Step 1: Start from the client's existing conversation
Open the message thread with the client, the one where you discussed the ring or the repair. In the Clientbook mobile app, the payment request starts from a dollar sign icon beside the message box; the desktop dashboard offers the same option. There is no separate invoicing screen to switch to.
Step 2: Enter the amount and what it is for
Type the total and a short description: the deposit on a custom setting, the balance on a repair. You can list several items on one request. Then decide whether the link should expire. By default a Clientbook payment link never expires, but you can set it to lapse at end of day, end of tomorrow, end of month, or on a custom date, useful for a deposit that holds a piece. Preview the request and create the link.
Step 3: Send it as an ordinary text
The link drops into the message box and you send it like any other text. The wording around it is a template your store controls: in Clientbook, an admin sets the store name shown on the request, the message that goes out with a new link, and the reminder wording, under Setup, Payment Links, Payment Settings. Multi-location stores should check that name before the first link goes out.
Step 4: What the customer sees
A text from your store's number with a short message and a link. Tapping it opens a payment page in her browser with your store's name and logo, the amount, and the description you entered. She enters her card details on that page, the same pattern as any online checkout, and taps to pay. No app to install, no account to create, nothing about the card typed into the thread. If she has a question, she replies to the same text and a person she knows answers.
Step 5: Confirmation and follow-up
Every update to the request appears as a note inside the client's message thread, so anyone on the team can see whether the link has been sent, paid, canceled, or refunded. The Today page on the dashboard and in the mobile app lists recent requests. The detailed history of each action is on View All Payments on the dashboard, and under View All in the mobile Payments section. If a link sits unpaid, open the request and use Send Reminder to edit and send a pre-written nudge.
Step 6: Where the payment lands
Because the request was created from the client's conversation, the record is attached to the client from the start. In Clientbook's Payment Requests Report, every link shows when it was sent, which associate sent it, which client it went to, the amount, its status, and when it was paid; you can filter by associate or status and export the payment links or bank transactions for reconciliation. A Time to Pay report tracks average time to pay. Purchase history is a separate record: in a clienteling platform connected to your point of sale, including Clientbook, it is fed by the POS, so you ring the sale up as usual and it appears on the client's profile like an in-store sale. The link records how the money arrived; the POS sale records what was bought. See which jewelry store POS systems Clientbook works with.
Five Jewelry Use Cases, With a Text for Each
When the customer is at your counter, take the payment in person. The link earns its keep in the gaps between visits, and jewelry has more of those than most retail. Each example below is a text a jeweler could send as written.
1. Special-order deposits
At many independent stores the deposit workflow still lives on paper; ask a jeweler how they track it and the answer is usually pen, paper, and a job envelope. With text-to-pay, the deposit request follows the approved design in the same thread. Send it the moment the design is approved.
Example text: {first name}, so glad you love the setting. Here is the link for the {amount} deposit so we can get your stone into production this week: {payment link}. Reply here with any questions. {store name}
2. Repair balances
Your ring is ready may be the most common text a jewelry store sends. Add the balance and pickup stops being a checkout. Send it when the repair clears quality control.
Example text: {first name}, your ring is polished and ready for pickup at {store name}. The balance is {amount}. Here is a link if you would like to take care of it before you come in: {payment link}
3. Shipping requests
When a client asks you to ship a piece, the payment and the shipping address belong in the same thread. Send it before the order goes to the packing table.
Example text: {first name}, happy to ship the pendant to you. Here is the link for the balance plus insured shipping: {payment link}. I will text you to confirm the address once it comes through. {store name}
4. Layaway installments
Layaway means collecting from the same customer month after month; without a link, that is a phone call or an installment that quietly slides. Send it a few days before each one is due.
Example text: {first name}, this month's layaway installment on your tennis bracelet is due Friday. Here is the link whenever you are ready: {payment link}. Thank you for letting {store name} hold it for you.
5. Remote purchases for out-of-town clients
Every established store has customers who moved away; we do not live in the area anymore, but we would love to keep buying from you. An associate shares a few pieces using brand catalog images sent by text, the client picks a favorite, and the link closes the sale in the same thread. The better your team gets at tracking what customers like and sending relevant suggestions, the more often this close happens.
Example text: {first name}, here is the link for the sapphire studs we talked about: {payment link}. Once it comes through I will have them insured and on their way, and I will text you the tracking number. {store name}
Why the Conversation Channel Converts
The case for collecting payment by text is the case for texting at all: it is the channel customers already answer. At Wilson Diamonds, image texts sent after first visits reached a 98 percent read rate and over 71 percent response rate. A payment link lands in the thread where the customer said yes a few minutes ago, and every extra step between the yes and the payment gives second thoughts room to grow. It is the same reason conversations are where appointments and event RSVPs get confirmed: the reply is one tap away from the ask.
Built for jewelry payment moments, not generic invoices
Jewelry text-to-pay is rarely a cart checkout. It is a deposit that holds a semi-mount, a balance due when a repair is ready, a special order that should not wait for another store visit, or a shipped piece paid before it leaves the safe. The useful system starts from the same client conversation where the associate already discussed the piece, keeps the payment on that client profile, and lets the associate set an expiration when the money is what holds inventory.
In Clientbook, payment requests start from the dollar sign in the message thread. Links never expire by default, and optional expirations cover end of day, end of tomorrow, end of month, or a custom date. Set the expiration before you create the link. It cannot be changed after the link is sent. If the date is wrong, cancel that link and send a new one. Whoever is working the request can cancel the link, mark it paid if the client settled another way, and send a reminder while the link is still open. Associates can send the original payment request from the thread. Payment settings, including the store name and the message templates, stay with an admin. None of that requires reading a card number aloud or sending the client to a separate billing portal with a different login.
Stores evaluating text-to-pay for jewelry should ask workflow questions first: does the link live on the client record, can deposits and balances reuse the same thread, and does the associate see status without leaving messaging? Pricing and merchant-account questions are a separate conversation with your payments provider and with Clientbook sales. This page stays on the jewelry workflow.
Security and Compliance in Plain Language
Customers will ask whether paying by text is safe, and the store carries the risk if a remote payment turns out to be fraudulent.
Never accept card numbers in a text, a DM, or a photo. Not typed into the thread, not read aloud and keyed in later, not as a picture of the card. A customer offering to text a card number is your cue to send a link.
The hosted payment page is what handles the card data. Your associates send a link and watch a status; the sensitive part happens on a page built for it.
Send from the number the customer already texts with. A request in the thread where she just approved a design reads as the natural next step; the same link from an unknown number reads like a scam. Keep every request inside a real conversation, for an amount the customer expects.
Keep the records attached to the client. The request, its status, the associate who sent it, and the export you reconcile against the bank should all trace back to one client profile.
Verify identity on remote orders from people you have not met. Screening on the payment side helps, but the store is responsible for confirming the person paying is the cardholder. Ask a new remote client for a photo of themselves holding their ID, and for a high-value order, add a live video call.
Set an approval rule for high-value remote orders. New client plus high value plus shipping plus urgency should trigger a second-person review before the piece leaves the store, however legitimate the conversation feels.
PCI DSS is the card industry's security standard for any business that stores, processes, or transmits card data, or can affect its security. For payments taken by text, the simplest way to keep your exposure small is to never touch card numbers at all. A hosted payment page makes that possible: the customer types her card into a page run by a PCI-compliant payment provider, and your associates never see, store, or text the number. It shrinks your PCI responsibilities for that channel, but it does not remove them. Ask any text-to-pay provider you evaluate for its PCI Attestation of Compliance and which PCI requirements it handles for you. If a customer texts a card number anyway, delete the message, do not quote it in your reply, and send a payment link instead.
One fraud signal hides in plain sight in the payment record. Several failed payment attempts followed by one that clears, on a high-value order from someone with no history at your store, is not a customer fumbling an expired card. It is card testing: someone cycling stolen numbers until one works. If the tool you collect payments through shows failed attempts, treat a run of declines as a stop sign, hold the order, and verify by another channel. What that looked like at two real stores is in our guide to fighting jewelry store fraud when scammers know how to use AI.
The Text-to-Pay Checklist for Jewelry Stores
Here is the checklist Clientbook recommends for any jewelry store collecting payments over text message, whichever platform you use:
- Send every payment request from inside the client's existing conversation, from the store number she knows.
- Put the amount and the reason in the message: the deposit on the setting, the balance on the repair.
- Never accept a card number by text, DM, photo, or phone. The hosted payment page is the only place card details go.
- Put your store name and logo on the payment page so it looks like you.
- Set an expiration on links tied to a deadline, such as a deposit that holds a piece.
- Send a reminder on unpaid links after a few days, from the same thread, in your own words.
- Mark a request as paid if the customer settles another way, and cancel links no longer needed, so the report matches reality.
- Ring the sale in your POS so purchase history stays complete and the associate gets credit.
- Reconcile exported payment links and bank transactions against your books every month.
- Verify identity on remote orders from new clients, require a second-person review on high-value shipped orders, and treat a run of declines followed by a success as a fraud signal.
What to Look for in a Text-to-Pay Tool
The payment feature is the easy part to demo. The differences are where the payment lives and what happens after it goes through: whether the request starts inside the conversation, whether it attaches to the client record with the sender recorded, whether it handles deposits, one-off installment amounts, expirations, reminders, cancel, mark as paid, and export, and whether it sits next to wishlists, preferences, and purchase history. See what to look for when choosing a CRM for your jewelry business.
If you are weighing platforms that bundle texting and payments, see the best all-in-one texting, reviews, and payments platform for jewelry stores. For where text-to-pay sits in the broader store stack, there is the technology successful jewelry stores are using in 2026.
Goodman and Sons covered a year's worth of Clientbook cost within the first month. The Goodman and Sons case study attributes that to follow-up on clients the store already had: faster replies, and associates who could see each other's conversations. It is not a text-to-pay result. Text-to-pay is a later step in that same client thread. The deposit or the balance still goes out from the conversation the customer already answers.
Frequently Asked Questions
Is it safe for customers to pay by text?
Yes, when the store follows the practices above. The link arrives from the store's known number inside an existing conversation, the customer enters her card details on a hosted payment page rather than in the chat, and no card number is ever typed into a message. The store's side is to never ask for card numbers by text and to verify identity on remote orders from new clients.
Is a payment link the same as an invoice?
No. An invoice is a formal bill, usually a document with terms and a due date, often sent by email, and it suits trade accounts and wholesale. A payment link is a request for a specific amount, sent in the conversation where the customer just said yes, and paid on her phone. Many invoices now include a pay link; the difference is where it arrives and how many steps sit between the request and the payment. For deposits, repairs, special orders, and remote sales, the link removes steps because it arrives in the thread she is already reading. Ring the sale in your POS either way so the record stays complete.
Is text-to-pay PCI compliant?
PCI compliance applies to businesses rather than to a payment method. Text-to-pay can fit within a PCI-compliant setup when card details are entered on a hosted payment page from a PCI-compliant provider instead of being typed into the thread, so they do not need to pass through the text thread or your associates' hands. Your part is to keep card numbers out of texts, DMs, and photos, to confirm your provider's PCI compliance and review it every year, and to complete whatever annual PCI validation your payment processor asks of you. In-store card terminals are a separate part of your PCI picture.
Does the payment show in the customer's purchase history?
The payment request and its status attach to the client's conversation and appear in the payments report with the client's name, the associate, the amount, and the paid date. Purchase history itself is fed by your point of sale, so ring the sale up in the POS as usual; with a connected POS, it then appears on the client's profile like any in-store sale.
Can a jewelry store take a deposit for a special order or repair by text?
Yes, and it is one of the most common uses. Enter the deposit amount and a description, set an expiration if the deposit holds a piece for a limited time, and send it in the thread where the customer approved the work.
Do customers need to download an app to pay by text?
No. The link opens a payment page in the phone's browser, with no app to install and no account to create.
What if the customer pays in the store after I already sent the link?
Mark the payment request as paid so the record matches what happened, or cancel it if it is no longer needed. Either way, ring the sale in the POS so purchase history and associate credit stay complete.
Close the Sale Where the Conversation Already Happens
The best way to collect payments over text message is not really about payments. It is about refusing to move a ready customer to a colder channel at the exact moment she is ready. A payment link inside a warm conversation closes deposits, repair pickups, shipping requests, layaway installments, and remote sales without asking anyone to drive, call, or wait.
Book a demo at clientbook.com/demo and ask to see a payment request sent inside a real client conversation.
Related reading:
Tools That Let Jewelry Associates Share Brand Catalog Images via Text
Appointments and Events: How Jewelers Increase Conversion and Revenue
