Accept crypto payments at your event venue: the business that pays the headliner long before the first ticket clears

Why an event venue's money arrives after it has already been spent

Walk the money through one show. In March you agree a date with an agent for a September headliner. The contract asks for a deposit on signature — in live music the norm is a substantial share of the fee, often half — and that money leaves before a single ticket exists. Then the spending continues: production hire, backline, extra sound and lighting, the poster and the paid social, the door and security roster, the insurance rider, sometimes flights and hotels.

Ticket sales start in April. Cash starts arriving five months before the show — and that is where a venue's payments problem actually begins, because the money you have already spent is the money your acquirer is most reluctant to hand over. Advance ticket sales are, in card-industry terms, future delivery: the cardholder has paid for something that will not be provided for months, and if the show is cancelled the liability rolls back up to the acquirer. The standard answer to that risk profile is not a refusal; it is a rate, a per-transaction ceiling, delayed settlement or a rolling reserve that holds back a slice of your takings until after the event date.

Then show night arrives and the money changes shape again. Walk-ups at the door. A bar running four deep for six hours. Cloakroom, merch, VIP tables, guest-list upgrades. A large part of it in cash, which means a float, a count, till differences, a safe and a Monday banking run. And at some point in the evening, usually before the set, a tour manager asks to be paid the balance of the fee — in a currency that is not always yours, to an agency that is not always in your country, on a Saturday when no bank is moving anything.

By Sunday lunchtime the venue owes the second half of its economy: security, bar staff, sound and light techs, riggers, cleaners, the support act, the door team, and the promoters and street-team sellers who worked on commission. Twenty to sixty people, many of them freelance, most of them expecting to be paid this week — from a bank balance that still does not contain the ticket money.

What the wrong rail costs across a season of shows

The reserve that arrives at the worst possible moment. A rolling reserve on advance ticket sales withholds cash for precisely the weeks in which the deposits, the production invoices and the marketing spend fall due. The venue is not unprofitable; it is being asked to finance its own pre-sales. Many operators cover the gap on a company card at card rates, which converts a timing problem into an interest problem.

The chargeback on a show that already happened. A ticket buyer files a dispute weeks after the night — "I didn't attend", "I don't recognise the charge", a partner querying a statement line. Card scheme rules give cardholders months to raise a dispute; the windows are laid out in network documentation such as the Visa Core Rules. By then the fee has been paid, the crew has been paid, the bar stock has been drunk, and the seat cannot be resold retroactively. It is the same structural asymmetry that hits any merchant defending disputes, except the product was consumed in one evening and there is no tracking number to produce.

The declined card at 1am. A destination club or a festival-week venue serves an audience that is structurally foreign: tourists, nomads, people three days into a trip. Their card gets declined by a fraud model that has decided a 2am charge in an unfamiliar country looks wrong, or it goes through with a cross-border fee and an FX spread on top. Either way, the queue behind them keeps moving and that round does not get bought.

The headliner's balance versus the banking calendar. A fee contracted in dollars or euros, payable to an agency abroad on the day of the show, is a wire that cannot be sent on a Saturday night, arrives in two to five days, and lands short after correspondents take their cut. So it goes out on Thursday on faith, or in cash from the office safe, or it becomes an argument in a corridor at 10:45pm.

The cost of running a cash night. Cash has no interchange, which is why the door still loves it — and it has a float, a count, two people in a back office, shrinkage, a safe, an insurance line, and a bank run on Monday morning. It also gives you no per-cashier record when the door total and the ticket scanner disagree.

The acquirer's read on nightlife. High-volume small tickets, late-night card-present sales, alcohol, advance sales, seasonality and a category with a well-known dispute rate: that combination gets priced as risk. The result is a higher rate, a reserve, or a review that lands the week you are trying to confirm a New Year's Eve headliner.

Why cards, wires and cash all fail on show night

• Cards settle in days and can be reversed for months. A venue's product is consumed in six hours and cannot be recovered, which is the worst possible fit for a rail built around reversibility.
• International wires assume time. Show night is deadline money — the artist plays at 11pm, not when SWIFT reopens on Monday — and the amount that arrives is not the amount that was sent.
• Cash solves speed by creating handling, counting, shrinkage and security costs, and by leaving no per-till record you can reconcile against the scanner at 4am.
• Local instant-payment schemes — Pix, Bizum, SPEI and their equivalents — are resident-only by design. At a festival-week venue, a large slice of the queue is not a resident of anything nearby.
• Rolling reserves are not a bug in this vertical, they are the correct response by an acquirer to future-delivery liability. You will not argue your way out of the logic; you can only stop routing that money through someone else's balance sheet.

The structural fact: a venue collects small, fast, often foreign payments in a six-hour window, plus large advance payments months early, and then pays a crowd of freelancers and one international artist immediately afterwards. Every traditional rail handles at least one of those badly.

How Payzum lets an event venue accept crypto payments

Payzum is a non-custodial crypto payment processor. Payzum never holds your money: there is no Payzum balance, no settlement batch and no rolling reserve priced against a nightlife risk score. When a customer pays, funds move on-chain from their wallet to a wallet your venue controls, and settlement is the payment. That single mechanic answers the reserve problem directly — money from a pre-sale in April is in your wallet in April, available for the deposit you owe in April, because there is no intermediary holding it against the possibility that a September show gets cancelled.

On-chain payments are also final. Once a ticket or a round at the bar confirms, no issuing bank reverses it three months later. Your refund policy, your terms and your judgement decide what happens when a customer has a complaint — not an adjudication you find out about in a chargeback notification the week after the show.

And a stablecoin is the same asset in the customer's country and in yours. A ticket paid in USDC from São Paulo, a bar round paid by a tourist from Berlin and a fee balance sent to an agency in London are all the same dollar-denominated instrument, confirming in seconds, at any hour, for cents in network fees — the general mechanics of cross-border collections applied to a business whose busiest hours are exactly when banks are closed.

The instruments, mapped to a venue's collection points

• POS with a fresh QR per sale — the door, the bar, the cloakroom, the merch table. Any phone is a terminal, so a pop-up bar, a second room or a summer terrace does not need new hardware. It is the same in-person flow as any counter, and cashier accounts with PIN let door staff, bartenders and cloakroom attendants take payment without ever touching the venue wallet — with per-cashier and per-terminal analytics for the 4am reconciliation.
• Hosted checkout — redirect, modal or inline — behind your own ticket page or event site, so an advance sale completes at 2am from another continent with nobody in the loop and lands as final money in your wallet the same night.
• Payment links and buttons — no code. The VIP table or bottle-service reservation confirmed over WhatsApp, the guest-list upgrade, the deposit that turns a "we'd like to hold the room on the 14th" into an actual booking, the artist's rider rebill, the extra hour of production a client asks for two days out.
• Invoices with an expiry and overpayment detection for the money that is negotiated rather than clicked: private hire and corporate bookings, sponsorship packages, bar-buyout deals, promoter room rentals. Put the event name and date in the reference and set the expiry to the week before the event, so the balance either lands on time or flags itself while there is still time to act.
• Recurring subscriptions for what repeats: memberships and season passes, resident-night club memberships, rehearsal-room and studio blocks, patron and "friends of the venue" programmes, monthly agreements with a resident promoter — recurring billing with on-chain finality, the mechanics of subscriptions without chargebacks.
• Mass payouts. CSV batch payouts plus EVM stablecoin payouts on Polygon, Arbitrum, Optimism, Base, BNB Chain and Avalanche: the artist's balance, support acts, sound and light techs, riggers, security, bar and door staff, cleaners, photographers and the street-team sellers on commission — one operation on Sunday morning instead of forty transfers across a week.
• REST API and signed webhooks so your ticketing or box-office system issues the ticket, updates the guest list and drops the allocation the second the payment confirms — including the sale that confirms at 11:40pm on a Saturday.

Honest scope: there is no pre-authorisation on-chain

Venues run two things on a card that stablecoins genuinely do not replicate: the open bar tab held against a stored card, and the damage deposit taken as a pre-authorisation on a private hire. Neither has an on-chain equivalent — you cannot place a hold on a wallet and you cannot force-charge it later.

So the honest design is different, not pretended-identical. A tab becomes a prepaid balance topped up at the bar, or simply pay-per-round on a QR, which is what most late-night bars do anyway. A private-hire damage deposit becomes real money paid into the venue's wallet and refunded — net of anything the signed contract allows — as a payment the venue initiates after the event. That is a stronger position than a hold, not a weaker one, provided your contract says clearly how and when it comes back. And where a card hold is genuinely the right instrument for a corporate client, keep cards for that client. This runs alongside your existing rails; it is not a demand that you rip them out.

Refunds, postponements and cancelled shows

Finality cuts both ways, and pretending otherwise would be dishonest. Because nobody is holding your money, a refund is a payment you make, from funds you already have — instant, and not dependent on an acquirer releasing a reserve. But it is also entirely yours to make: there is no scheme to arbitrate, so your published refund and postponement policy has to be clear, and you have to actually hold the ticket money when a show moves. Many venues already ring-fence pre-sale cash for exactly this reason. The difference here is that the money you are ring-fencing is genuinely in your wallet from day one, rather than sitting in an acquirer's reserve where it is neither usable nor, in an insolvency, obviously yours.

Volatility is a setting, not a risk

You price tickets in your local currency and you owe an artist a fee contracted in dollars or euros, so "I'm not holding an asset that moves between the pre-sale and the show" is the right first objection. You don't have to. Payzum accepts crypto and settles in crypto, with optional auto-conversion to a stablecoin such as USDC or USDT. The ticket sold in April is the same number of dollars when the fee balance goes out in September.

What's in scope — and what stays yours

In scope: door and cover charges, bar, cloakroom and merch, advance ticket sales through your own page, VIP tables and bottle service, private-hire and corporate booking deposits and balances, sponsorship invoices, memberships and season passes, rehearsal and studio blocks — plus the whole payout side: artist balances, support acts, crew, security, bar staff, cleaners, photographers and commission-based sellers.

Not in scope, and we don't pretend otherwise: Payzum is a payment rail. It is not a ticketing platform — no seat maps, no barcode issuance, no scanning, no access control; you keep whatever ticketing system you use and Payzum sits behind it as the way money moves. It is not escrow, not a promoter's client account, and not a payroll bureau. Your entertainment or premises licence, capacity and fire-safety limits, security ratios, age restrictions and alcohol rules, how you advertise ticket prices — US regulators have been explicit about total-price disclosure through the FTC's rulemaking on unfair or deceptive fees — performing-rights royalties on the music you play, withholding on payments to foreign performers (in the US the IRS operates central withholding agreements for touring entertainers), work permits and visas for touring crews, staff classification, insurance, VAT on tickets and tax all stay exactly where they are. The rail changes; the licence file doesn't.

What doesn't change

Payzum is crypto-only and does not settle to a bank account. Turning stablecoins into local currency for rent, PRS fees and the brewery invoice remains a separate step you take with your own exchange or off-ramp, on your own schedule. What changes is how fast confirmed money arrives, who holds it in the meantime — nobody but you — and whether the deposit you owe in April can be paid out of the tickets you sold in April.

How it works, step by step

1. Open the account and connect a wallet you control. Create a Payzum account, complete KYC, and point settlement at the venue's own wallet. There is never a Payzum-held balance — nothing to release after the event date, nothing to reserve against a future-delivery score.
2. Turn each collection point into an instrument. POS QRs for the door, each bar, the cloakroom and merch. Hosted checkout behind your ticket page. Links for VIP tables and private-hire deposits. Invoices with expiries for corporate bookings and sponsors. Subscriptions for memberships and season passes.
3. Give every staff member a PIN, not the wallet. Door staff, bartenders and cloakroom attendants collect through their own cashier accounts. Nobody handles venue funds, and the per-cashier report is what you reconcile against the scanner and the till at the end of the night.
4. Collect as final money, at the speed of a queue. Customers pay in USDC or USDT from any wallet — Solana confirms in well under a second, Base and Polygon in roughly two — and a signed webhook tells your ticketing system to issue the ticket or update the guest list immediately.
5. Run Sunday morning from the same place. One CSV settles the artist's balance, the support act, the techs, the riggers, the security firm, the bar and door crew, the cleaners and the commission sellers, across whichever of the supported networks suits each recipient.

Use cases at an event venue

Six situations where the difference shows up inside a single night, not in a year-end review.

• The pre-sale that funds the deposit. Tickets go on sale in April for a September show. The money confirms into the venue's wallet as each sale happens, so the artist's deposit and the production hire are paid out of ticket revenue that actually exists — instead of out of a company card while an acquirer holds the pre-sales until after the event date.
• The headliner's balance at 10:45pm on a Saturday. The tour manager wants the remaining fee before the set. An invoice referencing the show and date is paid from the venue's wallet in seconds, at face value, to the agency's wallet in another country — no cash envelope, no Thursday wire sent on faith, no argument in a corridor.
• The 1am round from a tourist whose card just declined. A visitor three days into a trip scans the QR at the bar and pays in USDC. No cross-border decline, no FX surcharge, no "do you have another card?" while eight people wait behind them.
• The private hire that stops being a maybe. A company wants the room on 14 December. A deposit link goes out the same afternoon and settles that evening; the balance goes out as an invoice with an expiry set to the week before. The date comes off the calendar with money behind it, and a January dispute cannot claw back a party that happened.
• The festival-week club with a foreign queue. During a major festival or high season, most of the audience banks somewhere else. Local instant-payment schemes don't serve them, their cards get flagged, and the ATM inside has been empty since midnight. A QR at the door works identically for a resident and for someone who landed this morning.
• The Sunday-morning payout run. Thirty-four people worked the night: security, bar, door, techs, riggers, cleaners, the support act and four commission sellers. One CSV batch pays all of them in stablecoins before lunch, each receiving the exact agreed amount rather than a figure reduced by transfer fees — the same mechanics as any freelance crew payout run.

Payzum vs cards, wires and cash on show night

Common objections, answered

"We already sell through a ticketing platform."

Keep it. Payzum is not a ticketing platform and does not want to be your seat map, your barcode or your scanner. It is the rail behind the money you already control directly: your own ticket page, the box office, the door, the bar, private hire, sponsorship and memberships. Plenty of venues run a third-party platform for allocated seating and take everything else themselves — that "everything else" is usually where the fees, the reserves and the disputes actually live. A REST API with signed webhooks and an integration playground means your existing system can be told the moment a payment confirms.

"My audience doesn't hold crypto."

Most of them don't, and they don't need to. This runs alongside your existing rails, not instead of them. The people it converts first are the ones your current rails serve worst: the tourist whose card declines at 1am, the festival-week visitor with no local payment method, the international artist's agency waiting on a wire, and the online buyer three time zones away whose cross-border fee costs more than the booking fee you charge. Offering it costs nothing on the nights nobody uses it, and rescues the sale every time the alternative was "sorry, cash only".

"Isn't a nightlife business too high-risk for this?"

That framing is an acquirer's framing, and it exists because acquirers carry reversal liability for your category — late-night card-present sales, alcohol, advance ticketing, seasonality. A non-custodial rail carries none of that liability, because there is no float to protect and no reversal mechanism to fund. That is why the pricing conversation is different. What it does not do is change your licensing position: your entertainment and alcohol licences, capacity limits, age checks and security obligations are unchanged, and nothing here is legal advice on them.

"What if we have to cancel a show?"

Then you refund from money you are already holding, immediately, without waiting on an acquirer to release a reserve. The trade-off is honest: there is no scheme to adjudicate, so your refund and postponement policy has to be published, clear and honoured, and pre-sale cash for a distant show should be treated as what it is — money you owe until the show happens. Most venues already work that way. This just means the money is genuinely in your wallet while you do it.