The pattern this protects against
The classic ticketing-fraud pattern isn't complicated: list a paid event that sounds real, collect money from whoever buys in, then either never hold the event or hold something far short of what was promised, and go quiet before any money has to be accounted for. By the time buyers realize something's wrong, the organizer has already been paid — or is trying to be.
This is exactly why most card networks, marketplaces, and ticketing platforms build in a holding period before money ever reaches the person who listed the event. It isn't a SPION invention — it's the standard response to a well-documented risk, and it's the first of two layers SPION uses specifically to catch it before a payout goes out.
Why your money isn't released at checkout
When you buy a ticket, that payment is processed immediately — but it doesn't reach the organizer's bank account at that moment. Ticket revenue only becomes available for an organizer to withdraw after the event's date has passed, and even then, a payout still has to be manually reviewed and approved before it's released. (We've covered the cash-flow side of this — why organizers don't get paid instantly — in a separate post; this one is about the other reason the gap exists: fraud.)
That gap between "the event is over" and "the organizer gets paid" is the entire window SPION has to catch a listing that was never real in the first place. If funds moved the instant a ticket sold, there'd be nothing left to hold back once a problem surfaced.
What gets checked before a payout is released
Before approving a payout, SPION looks at a handful of signals for the organizer's account: how many of their attendees actually checked in at past events, whether this is their first time being paid out at all, whether their identity verification is in good standing, and whether any attendee has raised a concern about one of their events (more on that below).
None of these signals blocks a payout automatically — every payout already goes through a human review before it's approved, flagged or not, so a real person is always the one making the final call. What these signals do is make sure that reviewer sees the full picture, not just a request to approve a number.
We deliberately don't publish the exact thresholds behind any of this, for the same reason a bank doesn't publish its fraud-detection rules: putting a precise line in writing just tells someone exactly how to stay under it.
The strongest signal: reporting a concern directly
Every check above is an inference from indirect data. There's one signal that isn't: a person who was actually there (or who paid for an event that never happened) telling SPION directly. If you bought a ticket to an event that didn't take place as advertised, or something about it felt wrong, you can report it — look for the option on the event's page once it's ended, or from your My Tickets dashboard if you're already signed in there.
We first confirm you actually held a ticket to that event, so the channel can't be used to anonymously target an organizer with no connection to them. Once that's confirmed, your report goes straight to a dedicated review queue — it is never shown to the organizer, and it directly feeds into the risk review on that organizer's next payout.
What to do if something feels wrong
Reporting a concern isn't the same as requesting a refund, and it's worth keeping those two separate. Refunds follow whatever policy the organizer set (or happen automatically, in full, if the event is formally cancelled) — that process doesn't change here. Reporting a concern is how you tell SPION something is wrong with the organizer's account itself, which matters whether or not you've already been refunded some other way.
If you're unsure whether to report something, the honest test is simple: would you want the next person buying a ticket from this organizer to know what you now know? If yes, report it. It costs you nothing, it's confidential, and it's reviewed by an actual person.
Why this protects honest organizers too
None of this adds friction for the overwhelming majority of organizers who run the event they listed. A clean check-in rate and no reported concerns means a payout review that's a formality, not an obstacle. The real beneficiary of a system like this is actually the honest organizer — every buyer deciding whether to trust a first-time event page is, in effect, also trusting the platform behind it. The more credible that trust is, the easier it is for a legitimate organizer to sell tickets to people who've never heard of them before.
Give your buyers a platform they already trust
Every organizer on SPION benefits from the same payout-review and trust & safety system — one more reason for a first-time buyer to say yes at checkout.
Create Your Event
