You run a workshop on a Saturday morning and a panel discussion the following Tuesday. Both sell tickets for stablecoins. A week later someone emails asking for a refund because they booked the wrong date, and you realise the payments all landed in the same wallet. You have no idea which transaction belongs to which event.
This happens more often than most organisers expect. When you run events regularly, the simplest mistake is reusing the same payment address or link for everything. It works until you need to issue a refund, split revenue with a co-host, or explain your income to an accountant who wants line items, not a single mixed pile.
Why a shared wallet becomes a problem
A single wallet feels efficient at first. You set it up once, share the address, and every payment arrives in the same place. But as soon as you run more than one event in a month, the transactions blur together.
Someone pays for a ticket and writes "workshop" in a message field you never check. Another buyer sends exactly the same amount for the panel. The blockchain shows two identical payments with no context. If one person asks for a refund, you have to guess which transaction was theirs, or ask them to send a screenshot of the payment, which not everyone keeps.
Co-hosts complicate things further. If you agreed to split ticket sales fifty-fifty, you need to separate the revenue for that event from everything else. If the money sits in a shared wallet alongside income from three other events, you end up doing manual accounting every time, cross-referencing timestamps and amounts in a spreadsheet.
Tax records get messier still. Most countries expect you to report business income event by event, or at least category by category. A single wallet with dozens of incoming payments offers no structure. You either reconstruct the history by hand or hand your accountant a transaction export and a shrug.
One payment link per event
The cleanest solution is to create a new payment link for each event. On Anyza Events you set up an event page, add ticket types, and the system generates a unique payment link tied to that event alone. Every payment that comes through that link is tagged, timestamped and recorded against the right occasion.
When someone buys a ticket, the money goes straight to your wallet, not to a platform account. Anyza never holds your funds. But the payment link itself acts as a filter: it tells you which event the buyer intended to support, even if the transaction on the blockchain looks identical to a dozen others.
This approach also makes refunds straightforward. You open the event page, see the list of ticket buyers, find the person who asked for their money back, and send the exact amount from your wallet to theirs. No guesswork, no spreadsheet archaeology.
If you run a monthly meetup, you create a new event page each month. If you organise workshops, courses and social nights, each one gets its own link. The effort is small, but the clarity is immediate.
Splitting revenue without the arguments
Co-hosting an event means agreeing on money before the first ticket sells. If you use a shared wallet, you have to manually calculate each person's share after the event, which invites disputes. Someone remembers a different split, or questions whether a particular payment was a ticket sale or a donation.
A dedicated payment link for that event gives you a clean record. You know exactly how much came in, when it arrived, and what the agreement was. When the event ends, you send each co-host their share from your wallet, and everyone has a transaction to match the plan.
Some organisers go further and give each co-host their own wallet address, then set up separate payment links for different ticket types. Early-bird tickets might send funds to one wallet, door sales to another. This works if you trust your co-hosts and want to avoid a single point of control, but it adds complexity. For most small events, one link and a manual split afterwards is simpler and just as transparent.
When you actually need separate wallets
A new payment link does not always mean a new wallet. You can route several links to the same wallet and still keep the payments distinct, because the link itself carries the event information. But there are moments when a separate wallet makes sense.
If you run events for different organisations or clients, keeping their funds in separate wallets protects everyone. A community group that hires you to organise a fundraiser does not want their ticket revenue mixed with your personal event income, even temporarily. A separate wallet means you can hand over the funds cleanly, with no questions about which transactions belong to whom.
Separate wallets also help if you work with a treasurer or a committee. You can give someone else access to the wallet for a specific event without exposing the funds from every other event you run. This is especially useful for volunteer-run groups where multiple people need visibility but not blanket control.
For regular solo organisers, though, separate wallets are usually overkill. One wallet and multiple payment links cover most situations without the overhead of managing several seed phrases, backup files and wallet apps.
Setting it up so it becomes routine
The trick is to make this a habit before you need it. When you plan an event, you create the page, set the ticket types, and generate the payment link at the same time. It takes a minute, and it saves hours later.
If you already have a backlog of events and a messy wallet history, start fresh from the next event forward. You cannot retroactively separate old payments, but you can stop the problem from growing.
On Anyza Events the process is part of the setup. You describe the event, choose a date and format, add your ticket options, and the system gives you a payment link tied to that event. Share the link, and every buyer who uses it is automatically recorded. No extra wallets, no manual tagging, no confusion when someone asks for a refund three weeks later.
If you run events regularly, treating each one as a separate financial container is not extra work. It is the minimum structure that keeps your accounts clear and your co-hosts happy.






















Comments