How to accept crypto payments as a wedding planner — deposits, balances and vendor payouts in USDC

Why wedding and event planners get paid on the hardest schedule in services

Almost every other service business is paid close to the moment it delivers. A restaurant is paid at the table. A clinic is paid at the counter. A planner is paid across a calendar that can stretch two years — and the largest single payment usually arrives while the service is still entirely in the future.

The scale is not small. The Knot Worldwide's 2026 Real Weddings Study puts the average US wedding at $34,000 in 2025, with roughly two million couples marrying and an average of thirteen vendors hired per event, inside a $100 billion industry. A full-service planner sits in the middle of that: taking money in from the couple on one side, pushing it out to thirteen suppliers on the other, and carrying the timing gap between the two.

Now add distance. Destination weddings put the couple in one country, the planner in a second, and half the vendor list in a third. Corporate and conference producers have the same shape with different names: a sponsor in Frankfurt, a production company in Mexico City, an AV crew invoiced in local currency, and a client procurement department that pays on its own calendar.

Each of those legs is a payment problem:

• The booking retainer. Often 20–50% of the fee, paid a year or more before the date. It is the payment that reserves your calendar and stops you taking another couple for the same weekend.
• Milestone instalments. Tied to venue confirmation, catering tasting, final headcount. Chasing them is unpaid admin work.
• The final balance. Due days before the event, exactly when nobody has time to sort out a rejected transfer.
• Day-of extras. An extra hour of the band, a late-night taco cart, a second shuttle run, a bar extension agreed at 11pm by a father-of-the-bride who wants to pay right now.
• Vendor payouts. Thirteen suppliers, several of them abroad, most of them wanting to be paid immediately after the event.

Traditional payment rails handle exactly none of those five well when the parties sit in different countries.

What a reversed payment or a delayed transfer actually costs

Start with the reversal. A card payment for a service is disputable long after the service is delivered — the card networks' own rules give cardholders a dispute window measured in months, not days, and the merchant carries the burden of proof (see Visa's public Core Rules and Product and Service Rules). For a planner that means the sequence every experienced vendor in this industry has heard about: the wedding happens, the photos are delivered, everybody is happy — and six weeks later the acquirer pulls a five-figure amount back out of the account, because a card was disputed, a family member "didn't recognise the charge", or somebody decided after the fact that a non-refundable deposit ought to be refundable.

You will probably win some of those cases. Winning costs you a documentation pack, a contract, a signed change order, timestamped correspondence and several unbillable hours — and you will not win all of them. It is the reason so many wedding suppliers stopped accepting cards for large balances and went back to transfers and cheques, trading a chargeback problem for a slowness problem.

Now the transfer side. An international wire from the couple's bank to yours takes days, passes through correspondent banks that deduct fees you cannot see in advance, and arrives at a converted amount nobody agreed to. Large first-time cross-border payments to an unfamiliar beneficiary routinely trigger fraud reviews and holds — precisely the profile of a wedding deposit. Meanwhile:

• Your calendar is exposed. Until the retainer lands, the date is not really booked. If a transfer sits in review for a week, you are either turning away other business on a promise or risking a double booking.
• Your margin leaks. Cross-border card fees plus FX spread on a $34,000 event is real money — and on a planner's percentage fee, the spread can be a meaningful slice of the profit on the job.
• Your cash flow inverts. Suppliers want paying within days of the event. If the final balance is still clearing, you are financing your own client out of working capital.
• Your risk profile worries acquirers. A business that takes large payments many months before delivery is, in acquiring language, "delayed delivery" exposure. That is how you end up with rolling reserves, volume caps or a sudden request for financials.

None of this is about crypto yet. It is about the structural mismatch between how planners work and how card and bank rails are built.

Why cards and international wires fail in this vertical specifically

Three structural reasons, and they are worth naming precisely because they explain why "shop around for a better processor" rarely fixes it.

Reversibility is a feature of cards, not a bug. The card system is designed to let a consumer undo a payment. That is genuinely good for consumers buying goods online. It is punishing for a business whose product is a one-off, non-recoverable, date-specific service. You cannot repossess a wedding. The service is consumed the moment it is delivered, so a dispute after the fact is a pure loss, not a returned item.

Acquirers price the future, not your track record. When a processor sees deposits collected twelve months before delivery, it is looking at what happens if you close down before the events happen — it would be on the hook for refunds. So it protects itself with reserves and holds. A ten-year-old planning studio with a spotless record still gets treated like an airline seat sold in advance.

Correspondent banking has no idea who you are. An international wire is a chain of institutions, each applying its own screening, fees and cut-off times. Nobody in that chain knows this is a wedding deposit with a hard date attached. The transfer moves at the speed of the slowest, most cautious link.

Stablecoins remove all three at once, not because they are clever, but because they are a different mechanism: the payment is a settled transfer, it has no issuer to reverse it, and it does not route through a chain of intermediaries.

How Payzum lets a wedding planner accept crypto payments

Payzum is a non-custodial crypto payment processor. The distinction matters more here than in most verticals, so it is worth being blunt about it: Payzum never holds your money. There is no Payzum balance, no payout schedule, no withdrawal request. When a couple pays, the funds move on-chain from their wallet to a wallet you control. Settlement is the payment.

For a planner, that removes the two things that make this vertical uncomfortable for processors. There is no float sitting with an intermediary for months, and there is no intermediary that can decide to hold a reserve against your future events.

Be precise about which payments this covers

This is not escrow and it is not a client-money account. Payzum does not hold funds on behalf of a couple pending an event, and it does not intermediate between you and your vendors. What it does is let you get paid for what you invoice and pay out what you owe. In practice, for a planning business, that is:

• Booking retainers and design fees — the payment that secures the date.
• Milestone instalments — 30/30/40 style schedules, or whatever your contract says.
• Final balances — including the pass-through budget when your contract has you paying suppliers on the couple's behalf.
• Day-of and on-site additions — bar extensions, overtime, extra transport, upgrades agreed at the venue.
• Retainers for corporate and conference work — sponsor invoices, production fees, per-event coordination.
• Vendor and freelancer payouts — photographers, videographers, florists, DJs, coordinators, stylists, drivers.

The instruments that cover them

Everything above maps onto product you can configure in an afternoon, with no development work:

• Payment links and buttons. No-code. One link per milestone, sent by email or WhatsApp with the amount already set. The couple opens it, pays, done.
• Invoices with expiry and overpayment detection. The right instrument for retainers and balances: the invoice has a deadline, and if the amount received does not match, the system flags it instead of leaving you to reconcile by hand.
• Hosted checkout (redirect, modal or inline) if you sell packages, planning intensives or ticketed events from your own site.
• Recurring subscriptions for monthly planning retainers and month-by-month payment plans — and unlike card subscriptions, they cannot die to a dispute mid-schedule.
• POS with a fresh QR per sale. On the event day, any phone at the welcome desk becomes a terminal. Cashier accounts with PIN mean your on-site coordinator can take a payment without touching your wallet, and per-cashier analytics show you who took what.
• Mass payouts. CSV batch payouts in stablecoins on Polygon, Arbitrum, Optimism, Base, BNB Chain and Avalanche — the vendor list paid in one operation.

Volatility is a decision, not a risk you are forced to take

The objection every planner raises first: "I quoted $34,000, I am not accepting something that might be worth $30,000 next week." Correct — and you do not have to. Payzum accepts crypto and settles in crypto, with optional auto-conversion to a stablecoin such as USDC or USDT. A stablecoin is designed to track the dollar, so a $12,000 retainer received in USDC is $12,000 of USDC in your wallet, whether the wedding is in six weeks or sixteen months.

Payzum is crypto-only: it does not settle to a bank account. Converting stablecoins to local currency, and when, is a separate decision you make with whatever exchange or off-ramp you already use. Some planners hold the whole event budget in USDC until they pay suppliers in USDC, and never touch fiat for that job at all.

What does not change

Being paid in stablecoins does not rewrite your contract. Your cancellation terms, your refund ladder, your force-majeure clause and your change-order process are exactly as they were — and they matter more, not less, because an on-chain payment is final. If you owe a refund under your contract, you send a refund; you decide that, not a card issuer. The same is true of invoicing, bookkeeping and tax: a payment received in USDC is revenue, recorded like any other, on whatever basis your accountant already uses.

How it works, step by step

1. Create your account and connect a wallet you control. Complete KYC in the dashboard and set the destination wallet — yours, not Payzum's. Turn on auto-conversion to USDC or USDT if you want every incoming payment pinned to the dollar. Enable 2FA while you are there.
2. Build the payment schedule for the event. Create an invoice or a payment link per milestone, each with its own amount, reference and expiry — for example: 30% retainer on signature, 30% at venue confirmation, 40% fourteen days before the date. Send them the same way you already send your contract.
3. Get paid and see it confirm. The couple pays from their wallet or exchange on whichever supported network they use — Solana confirms in under a second, Base and Polygon in roughly two. The funds land in your wallet; the dashboard marks the milestone paid; a signed webhook can push the event straight into your CRM or planning tool so the status updates itself.
4. Take the day-of extras at the venue. Open the POS on a phone or tablet at the welcome desk, enter the amount, show the QR. A fresh QR per sale means no reused address and no ambiguity about which payment was which. Give your on-site coordinator a PIN-protected cashier account rather than access to your wallet.
5. Pay the vendor list the morning after. Export or build a CSV — supplier, network, address, amount — and run it as a single batch payout in stablecoins. Thirteen vendors, one operation, each of them paid in minutes instead of waiting on international transfers.

Use cases in a wedding and event planning business

Four scenarios that show where this actually earns its place, rather than being a novelty payment option on the website.

• The destination wedding retainer that has to clear this week. A couple in Berlin books a planner in Tulum for a March date. The venue holds the date for seven days. A SEPA-to-Mexico wire is a four-day question mark with an unknown arrival amount; a card payment leaves a five-figure reversible charge hanging over the job for months. Instead the planner sends an invoice for €12,000 in USDC with a 72-hour expiry. It is paid the same evening, converted and settled to the planner's wallet, and the venue deposit goes out the next morning. The date is locked before the option lapses.
• The vendor batch the day after the event. Sunday morning after a Saturday wedding: photographer, videographer, second shooter, florist, band, DJ, hair and make-up team, two drivers and the on-site coordinator. Some are local, some flew in, three invoice in a different currency. One CSV, one batch, everyone paid in stablecoins on a cheap network before the planner has finished breakfast. Suppliers who get paid that fast become suppliers who prioritise your events.
• The bar extension at 11pm. The father of the groom wants two more hours of open bar and wants to settle it there and then. The coordinator opens the POS on her phone, enters the amount, and he scans the QR. Payment confirmed in seconds, logged against her cashier account, no terminal, no card, and no chance of that particular charge being disputed on Monday. This is the same in-person flow a restaurant or venue uses, applied to on-site upselling.
• The corporate event producer with international sponsors. A three-day conference with sponsors in four countries, each on a different procurement cycle. Every sponsor gets its own payment link with a reference and a deadline; the producer sees exactly which ones have settled without reconciling four bank statements. Production crews in the host country are paid from the same balance the week of the build.

Payzum vs cards and international wires for planner payments

Common objections, answered

"My couples don't hold crypto."

Most will not, and this is not a replacement for how you already get paid — it is an additional rail you turn on for the clients who need it. In practice the ones who need it are exactly the ones causing you the most friction today: the couple in another country whose bank blocks the transfer, the expat client paid in dollars but living somewhere with capital controls, the sponsor whose treasury already holds USDC. You keep your existing methods for everyone else. One well-placed option on the invoice is enough.

"What if the value moves between the retainer and the wedding?"

Turn on auto-conversion to USDC or USDT and the question mostly disappears: the retainer is received as dollars-denominated stablecoin and stays that way. A stablecoin issuer's own reserve and redemption model is worth reading before you pick one — Circle publishes its reserve reporting for USDC — but the working reality for a planner is simple: you quoted in dollars, you hold dollars-denominated value, and you decide separately when and whether to convert to local currency.

"An irreversible payment sounds risky for my client. Is that a hard sell?"

Sell it as what it is: the payment is final, so your contract is what governs refunds — not an anonymous dispute process. Good planners already have clear cancellation ladders and change-order procedures. Say so in writing, be explicit about what is refundable and when, and most couples find a named human with a written policy more reassuring than a chargeback form. Where the relationship needs a neutral third party holding funds — large pass-through budgets, for instance — use a proper escrow arrangement with your lawyer. Payzum is a payment processor, not an escrow agent, and we will tell you that on the call.

"Who actually controls the wallet?"

You do. Payments settle to a wallet whose keys you hold, which is the entire point of a non-custodial processor: there is no Payzum balance to freeze, delay or apply a reserve to. That also means wallet security is your responsibility. Use a hardware wallet or a multi-signature setup for the business wallet, keep 2FA on the dashboard, restrict cashier accounts to PIN-level access, and use the audit log to see who did what.

"We already take cards through a booking platform."

Keep it. Cards are convenient for small, low-risk payments and plenty of couples want the points. The pattern that works is to route by size and distance: small local payments on the existing rail, and large cross-border retainers and final balances — the ones that hurt when they reverse or arrive short — on stablecoins. Many merchants find the same split works for reducing chargeback exposure generally, and the fee difference on a $34,000 event is not a rounding error.