Illustrative example · Florist
How a florist could accept crypto for walk-ins and phone orders
An illustrative walk-through of a small flower shop with counter sales and phoned-in delivery orders, where a QR for each and seasonal peaks shape the setup.
This is a composed educational scenario built to show how the pieces fit for this kind of business. It does not describe a real CryptoLic customer, and it promises no particular result. Any figures are illustrative. We do this instead of testimonials so nothing here can be mistaken for a real endorsement.
Picture a small flower shop with walk-in counter sales and a steady stream of phoned-in delivery orders, plus sharp seasonal peaks around holidays. Some orders are paid in person, others need to be paid remotely before delivery.
This example follows how such a shop might take crypto for both. Figures are illustrative and used to show the decision, not to predict a result for a real shop.
At a glance
| Business | Small florist, counter and delivery |
|---|---|
| Typical ticket | $25 to $150 (illustrative) |
| Current methods | Cards and cash, card-over-phone |
| Goal | Cover in-person and remote orders, survive holiday peaks |
| Equipment added | None; counter tablet plus payment links |
How they take payment today
Cards and cash at the counter, and card-over-the-phone for delivery orders. Phone card entry is clunky and carries dispute risk, and card fees climb during holiday peaks.
The pain points that started the question
- Awkward, dispute-prone card-over-phone for delivery orders.
- Card fees that spike during holiday volume.
- A wish for a clean way to collect before a delivery goes out.
Why crypto came up
A payment link sent for a phone order lets the customer pay cleanly before delivery, with no card read aloud and no chargeback risk. At the counter, a QR handles walk-ins. One tool covers both.
The initial concerns
- "Remote orders?" A payment link sent by text or email, paid before delivery.
- "Holiday rush?" Lightning keeps counter checkout quick.
- "Do we hold Bitcoin?" No. Auto-conversion to dollars.
How they researched it
The owner took the readiness quiz, read the QR-checkout explainer for the counter flow, and reviewed the Payment Solutions Center for a tool that offers both a counter QR and a shareable payment link.
The decisions they landed on
- Method: Lightning at the counter, either rail via link for delivery orders.
- Custody: a processor with dollar settlement.
- Remote orders: a payment link paid before delivery dispatch.
- Rule: deliveries leave only after payment confirms.
The implementation, step by step
- Chose a processor offering both a counter QR and shareable links.
- Set up the counter QR on the existing tablet.
- Created a link template for phone delivery orders.
- Set a confirmed-before-dispatch rule for deliveries.
Equipment and costs
No new hardware. The cost was the per-sale conversion fee, weighed against card and phone-card fees, especially at peak. Illustrative and service-dependent.
Lessons worth keeping
- Payment links made phone delivery orders cleaner than card-over-phone.
- Confirmed-before-dispatch removed the remote-order risk.
- Lightning kept the counter fast during holiday peaks.
Common misconceptions and pitfalls
- Pitfall: dispatching a delivery before the payment confirms.
- Pitfall: a static counter code for varied bouquet prices.
- Misconception: crypto only works in person; a link handles remote orders.
Recommended next steps for a similar shop
- Take the readiness quiz with counter and delivery orders in mind.
- Read the QR-checkout explainer.
- Find a QR-plus-link processor in the Payment Solutions Center.
- Set a confirmed-before-dispatch rule for deliveries.
The CryptoLic resources used in this example
- Merchant Readiness Quiz
- QR codes and the crypto checkout flow
- Payment Solutions Center
- Crypto Payment Card Builder
This example is a starting point, not a prescription. To see how it maps to your own ticket sizes and setup, take the readiness quiz for a plan built around your business.
More examples