Florist

Accept Crypto Payments as a Florist — Paid Before the Bouquet Leaves the Shop

Short answer: To accept crypto payments as a florist, use Payzum: show a fresh QR at the counter, and send payment links for phone, WhatsApp and delivery orders — including gift orders paid from abroad. Payments confirm in seconds, can't be charged back, and settle non-custodially to a wallet your flower shop controls.

Key takeaways

  • The payer is almost never the person holding the flowers: most of a florist's revenue is card-not-present gift orders — exactly where stolen-card fraud and "never received" disputes live. A USDC payment can't be made with a stolen card number and can't be clawed back weeks later.
  • A delivered bouquet can't be returned: by the time a dispute arrives, the roses are compost and your evidence is a doorstep photo. On-chain payments are final — no ~120-day chargeback window.
  • Your year is decided in a few days: Valentine's Day alone accounts for about 30% of holiday flower transactions. That is the week you can least afford card fees, held funds, or a risk review triggered by your own sales spike.
  • Any phone behind the counter is the terminal: a fresh QR per sale, PIN logins for seasonal staff, payment links for remote and cross-border gift orders, expiring invoices for event deposits — all settled non-custodially, with optional auto-convert to USDC/USDT.

Flower shop payments: the person paying is rarely the one holding the bouquet

A florist sells gifts. On an ordinary Tuesday, someone walks in, picks a bunch of peonies and pays at the counter. But the orders that make the year look different: a husband calling at 4 p.m. for an anniversary delivery, a daughter sending flowers to her mother in another city, a company ordering a sympathy arrangement for an employee's family, a bride booking the flowers for a wedding eight months away. The person who pays is rarely the person who receives — and often they're in a different city, sometimes a different country.

In card-network terms, every one of those orders is card-not-present, and card-not-present fraud liability sits with the merchant. Florists are a natural target: they take phone orders from strangers all day, and a large arrangement can be ordered, delivered and resold — or used to cash out a stolen card — before the real cardholder notices. The FCC has warned merchants for years about orders placed through IP Relay by callers posing as deaf or hard-of-hearing customers and paid with stolen or fake cards, with the classic red flags: "whatever you have in stock," several cards tried until one works, delivery to a third party. Any florist who has worked a phone line has heard a version of that call.

Then there's the dispute nobody can win cleanly: "never received." The cardholder didn't see the delivery — by design, it went to someone else. The recipient isn't your customer and has no reason to help. The product is perishable, so there's nothing to return and nothing to inspect. When the chargeback lands sixty or ninety days later, your whole defense is a doorstep photo and a driver's note, and a dispute fee comes off either way.

Ticket sizes make the exposure real. A bud vase at $35–$50 is noise, but delivered arrangements run $80–$250, sympathy pieces and standing sprays go higher, and a wedding or corporate event can reach thousands of dollars, paid as a deposit months before a single stem is bought. Every one of those payments carries roughly 2.6–3% in card fees — more when the order is keyed in by phone.

What it costs a flower shop to leave this unsolved

Start with the calendar. According to the Society of American Florists, Valentine's Day accounts for about 30% of holiday flower and plant transactions, with Mother's Day and Christmas at roughly 26% each. A florist's year is decided in a handful of weeks — and those are exactly the weeks the card stack hurts most.

Run the numbers on one Valentine's week. A mid-sized shop takes $55,000 in orders over four days. At ~3% blended card cost, that's about $1,650 in fees — in the same week you've paid growers and wholesalers up front, hired extra drivers and rented cooler space. Add two stolen-card phone orders at $300 each (flowers delivered, money reversed), one "never arrived" dispute on a $180 office delivery, and three dispute fees: about $2,500 gone from the busiest week of the year, plus the evenings spent answering disputes in March.

The cash-flow squeeze compounds it. Card batches take 1–3 business days to land, and when Valentine's Day falls on a weekend — as it does in 2027 — Saturday and Sunday's sales don't reach the bank until midweek. Worse, a sudden spike in volume is precisely what processor risk models are built to flag. A shop that triples its usual sales in four days can find payouts held or a rolling reserve applied right when it needs the cash for Mother's Day pre-orders.

And there's revenue you never see. The son abroad whose foreign card declines on your website. The relatives in three countries who want to send funeral flowers by tomorrow morning. The customer who'd happily pay in USDC but can't. When "local cards only" is the answer, those orders go to a national order site that keeps a large share before the order ever reaches a local shop — or they don't happen at all.

Why card rails fail a florist

None of this is bad luck — it's the design. Card payments are reversible by contract, and the dispute process asks the cardholder what happened, not the person who actually received the flowers. The network pushes card-not-present fraud liability onto the merchant, and a florist is card-not-present most of the time. The product is perishable, so it can't be returned and the evidence expires with it. And between you and your money sits an acquirer that takes a percentage of every order, holds funds in transit for days, and manages its own risk with reserves on your account when your seasonal spike looks unusual. Card rails were built for a shopper who pays and carries the goods out of the store — not for a business that delivers a perishable gift, paid by one person, to someone else, in time for a date that won't move.

How Payzum lets you accept crypto payments as a florist

Payzum is a non-custodial, crypto-only payment processor. Non-custodial means the settlement is the payment: when a customer pays, the funds route directly to a wallet your shop controls. Payzum never pools, holds, or touches the money — so there's no processor balance to freeze, no reserve to negotiate before Mother's Day, and no risk model deciding that your Valentine's spike looks suspicious.

At the counter, the Payzum POS turns any phone or tablet into the terminal. Ring up the bouquet, and the screen shows a fresh QR generated for that exact sale. The customer scans and pays from any wallet; the payment confirms on-chain in seconds — roughly 0.4 s on Solana, about 2 s on Base or Polygon across the supported networks — and it is final. Each person behind the counter, including the extra hands you bring in for February and May, works under their own PIN cashier login, with per-cashier and per-terminal analytics.

Most of your orders don't happen at the counter, and the same account covers them. Payment links you send by WhatsApp, Instagram DM, text or email close phone and social orders: the arrangement goes to the design table when the payment confirms, not when a card number read aloud clears. Payment buttons or hosted checkout — or a drop-in plugin for your existing store — handle orders on your website. Expiring invoices with overpayment detection cover wedding and event deposits, and recurring subscriptions run weekly flowers for hotels, restaurants, offices and home subscribers. Price stability is handled at the settlement layer: a stablecoin like USDC is issued fully reserved against dollar assets, so a $120 arrangement settles as $120. If a customer pays in another supported crypto, auto-convert settles it as USDC or USDT.

The money also flows out. After a holiday rush, stablecoin payouts on Polygon, Base, Arbitrum, Optimism, BNB Chain or Avalanche let you pay seasonal drivers and freelance designers in one batch, straight to their own wallets.

How it works, step by step

  1. Sign up. Create a Payzum account for the shop — no acquirer application, no terminal lease, no underwriting questionnaire about what share of your sales are "card-not-present gift orders."
  2. Connect your wallet. Point Payzum at a wallet the shop controls. Every payment settles there directly; turn on auto-convert so everything lands as USDC or USDT regardless of what the customer paid with.
  3. Set up the counter and your order channels. Open the POS on a phone or tablet at the counter, create a PIN cashier for each staff member, and save payment-link and invoice templates for delivery orders, sympathy orders, wedding deposits and corporate accounts.
  4. Take the order, then make it. At the counter, show the QR; for remote orders, send the link and start the arrangement when the payment confirms — final, non-reversible, and already in your own wallet.

Before your next peak, a short checklist gets the shop ready:

  • Publish pre-order links for Valentine's Day, Mother's Day or All Saints' two weeks early, so the rush is paid before the stems are ordered.
  • Create PIN cashiers for seasonal staff, so every sale is attributed and shift closes reconcile themselves.
  • Turn on auto-convert to USDC or USDT, so every order settles at the price you quoted.
  • Match invoice expiry to your supplier deadline for weddings and events — an unpaid deposit expires before you've committed to the flowers.
  • Prepare your driver payout batch, so the people who delivered 300 bouquets are paid the same night.

Use cases for a florist, from the counter to the chapel

The same building blocks cover every way a flower shop actually gets paid:

  • Walk-in bouquets and plants: ring up the sale on the counter tablet and show the QR. The customer pays from their wallet, confirmation lands in seconds, and the flowers leave already paid — no card fee on a $40 bunch of tulips.
  • Phone, WhatsApp and Instagram delivery orders: the customer picks an arrangement in a DM, you send a payment link, and the order goes on the delivery board when it confirms. No card number read over the phone, no card-not-present risk, and nothing for the payer to dispute after the recipient has signed for it.
  • Gift orders paid from abroad: a son in Houston sends flowers to his mother in Guadalajara for Mother's Day. He pays the link in USDC from his wallet; you see it confirm in seconds and deliver the same day — no foreign-card decline, no FX spread, no international wire for a $90 bouquet. For a florist whose customers' families live abroad, this is revenue that card rails quietly turn away.
  • Sympathy and funeral orders: urgent, emotional, and often paid by relatives in other cities or countries. Send one link per family member — or one each for the casket spray and the standing wreath — and deliver to the service already paid. See how funeral homes use the same rails for families abroad.
  • Weddings and events: send an expiring invoice for the deposit when the contract is signed and a second one for the balance 30 days out. You order the stems only when the deposit is final — so a deposit can't be disputed after the flowers are bought, cut and arranged. Wedding planners paying a whole roster of vendors can pay you the same way.
  • Corporate accounts and flower subscriptions: the hotel lobby, the restaurant's tables, the office reception — weekly arrangements billed as a monthly invoice or a recurring subscription that doesn't die on a card dispute. The same works for consumers who want fresh flowers at home every Friday.
  • The holiday rush with seasonal staff: five extra people at the counter on February 13, each with their own PIN, per-cashier sales visible in real time — and when the last van comes back, freelance drivers are paid in stablecoins in a single batch.

Payzum vs card processing for florists — side by side

What mattersCard terminal / online card processingPayzum
Cost on a $120 delivery order~2.6–3% (≈ $3–4), more if keyed in by phoneNo card-network percentage, no per-swipe fee
Stolen-card phone and web ordersLiability on you, flowers already deliveredCan't pay with someone else's card number
"Never received" disputesReversible for ~120 days + dispute fees; the evidence wiltsFinal on-chain — no chargebacks
Settlement after a weekend Valentine's1–3 business days, reserves possible on a spikeSeconds, any day of the week
Gift orders paid from abroadForeign-card declines, cross-border fees, FXPayment link, paid from any wallet
Wedding and event depositsDisputable after the stems are boughtExpiring invoice — paid or void, then final
Where funds landHeld by the acquirer in transitDirectly in a wallet your shop controls

Common objections, answered

Most of my customers don't hold crypto — why bother?

Run it alongside your card terminal, not instead of it. QR and payment links become the option where they pay off most: large phone orders from people you don't know, gift orders from customers abroad whose cards don't work on your site, event deposits you can't afford to see reversed, and the growing number of customers who already keep USDC on their phone. Everyone else pays as they always have. It's an added rail with near-zero setup cost — the hardware is the phone already on your counter.

What if a delivery really goes wrong?

Then it's handled by your guarantee, not by a bank's ruling. If an arrangement arrives damaged or late, you redeliver fresh flowers or refund from your own wallet on the terms you publish — the way good florists already do. The difference is that you decide, the same day, with the facts in front of you, instead of a card network deciding two months later with your money already pulled back.

Is the money safe if Payzum never holds it?

That's precisely what makes it safe. Because Payzum is non-custodial, there's no pooled processor balance to freeze and no reserve to withhold — payments settle straight to the shop's own wallet. The account is protected with 2FA, signed webhooks, and a full audit log.

Won't the price move between the order and the wallet?

No — quote in dollars, settle in dollars. Price arrangements in stablecoins, and auto-convert turns any other supported crypto into USDC or USDT on arrival. A $250 sympathy spray settles as $250 of stablecoins, not as a coin that might move overnight.

Frequently asked questions

How do I accept crypto payments as a florist?

Create a Payzum account, connect a wallet your shop controls, and open the POS on any phone or tablet at the counter. For walk-in sales, show the QR generated for that sale; for phone, WhatsApp or web orders, send a payment link. Funds settle to your wallet in seconds — no card terminal, no acquirer.

Can a customer charge back a flower delivery?

No. On-chain settlement is final, so a confirmed payment can't be reversed through a card network — including the "never received" disputes that hit gift deliveries. If something goes wrong, redelivery or refund is your call, under your own policy.

How can customers abroad pay for flowers delivered locally?

Send them a payment link. They pay in USDC or USDT from any wallet, wherever they live, and the payment confirms in seconds in your shop's wallet — no foreign-card declines, no international wire and no FX spread for a bouquet delivered across town.

Does accepting crypto protect my flower shop from stolen-card phone orders?

Yes, for the payments taken this way. A crypto or stablecoin payment is authorized from the payer's own wallet, not with a card number that could be stolen, and once confirmed it can't be reversed by the real cardholder weeks later.

How do I take wedding and event deposits in crypto?

Send an expiring invoice for the deposit when the contract is signed and another for the balance before the event. Overpayment detection keeps the books clean, and because each payment is final, you can order stems without the risk of a deposit being disputed later.

Can I pay seasonal delivery drivers in stablecoins?

Yes. Payzum's EVM stablecoin payouts on Polygon, Base, Arbitrum, Optimism, BNB Chain or Avalanche let you pay every driver and freelance designer in one batch after a holiday rush, straight to their own wallets.

Book a meeting for your flower shop

Tell us how your shop collects today — counter sales, delivery orders by phone and WhatsApp, gift orders from abroad, sympathy work, weddings, corporate accounts — and we'll design a non-custodial setup around it: a QR per sale with no chargebacks on the devices you already own, PIN logins for your seasonal staff, payment links for customers who pay you from abroad, and settlement in seconds to your own wallet on the networks your customers use.

Prefer a direct link? Book a payments consultation · [email protected]