Opening Hubbaly

Still opening. A slow connection takes longer; nothing you had open is lost.

Try again
Skip to Content
Purchases and refunds

Purchases and refunds

This guide is for both members and hub admins.

For a payment that gives you ongoing or fixed-term access to a hub’s benefits, see Paid memberships.

Purchase ledger basics

Use Purchase history for canonical order records.

Each order shows:

  • Source (Paid, Free, Comp),
  • Lifecycle state (Completed, Failed, Expired, Partially refunded, Refunded),
  • Ownership outcomes per ticket,
  • Gross/refunded/net totals.

Waiting for your ticket email

If you paid for tickets while setting up a new account, confirm your email address before Hubbaly can send your ticket email. If it is still waiting the day before the event, look for Confirm your email to receive your tickets and choose Confirm email. Hubbaly sends your ticket email after you confirm.

Event shop purchases

See Event shop on the night for buying at a stand, showing a code, helping with collection and sending items afterwards.

Running the shop? Open Shop in Event admin, then Shop orders below Shop scanner. Its row tells you what is left to do. The order list starts with each item’s progress, then the counted All, Not seen yet, Seen, To collect and With a note views, which stay in reach as you scroll. To send appears after the event or once something has been sent. Each order shows the team’s full note and who wrote it. Search by name, @username or EX- reference, or open More filters. Money and stock are below the list. Sales also links to this page. You need permission to read shop orders; permission only to hand items out opens the scanner instead.

An order that cost nothing has no refund, so its page offers Cancel order instead. Cancelling gives back the stock and the buyer’s limit for anything not yet handed out or sent, and anything already handed out or sent stays in the order’s history. The order then shows Cancelled in Shop orders, and the buyer’s purchase says Cancelled by the organiser. No email is sent. You need the same permission as for refunds.

Helping to hand out? On Home, Shop scanner under Things to do takes you straight to Shop scanner and shows how many orders are waiting. You need the organiser’s Hand out Event shop orders permission and must have accepted the work. An organiser can use the same shortcut.

Your shop code is also under your ticket in Tickets: choose Show shop code to open it. If you have no ticket for the event, look in Next up in Tickets.

Find your Event shop orders under Purchase history. Open an order to read what you bought, the seller’s instructions and when an item will be sent. Your purchase page celebrates when an item is seen at the event or handed over.

If the item says At the event, then sent after, open Your code for the event and show it to the seller at the event. It is separate from your event entry ticket. The purchase shows when you have been seen, and the code stays available while anything is still to be collected or sent. The team’s private note is never shown to you.

Organisers choose this receive method in the item’s setup and add a delivery window. Editing an item keeps it on sale and keeps its first Tax and selling check. A choice’s stock limit can be added, changed or removed after orders; the total includes what is already sold or in checkout. A smaller total is refused with the number needed.

A team member with Hand out Event shop orders opens Shop scanner, scans a buyer’s code or finds them by name, @username or purchase reference, and presses Mark as seen. They can keep a private note, save it separately and undo a mark with a reason. A current ticket holder’s arrival comes from the door’s own record. Shop orders shows the same seen record, note and arrival, and can filter Seen or Not seen yet. Marking someone as seen does not hand anything over, change stock or send an email. Mark as sent is still used after delivery.

Designated member purchases

When one person pays and designates tickets to others:

  • Order remains linked to original payer,
  • Holder and payer are tracked separately,
  • Refunds of that original payment return to the original payer,
  • Designated-at-purchase tickets stay refundable from that original purchase when otherwise eligible,
  • If one of those tickets is later transferred after checkout, it must be transferred back before a self-serve refund can be requested,
  • Order can be partial if some ticket lines are ineligible.

Paying to move to a pricier ticket

If the organiser allows ticket changes, you can pay to move a ticket you hold to a pricier ticket or session. The choice must be on sale to you and have room. Paid choices are available only when the organiser can take the payment.

  1. Open your pass in My tickets and choose Change. If you bought without an account, open View tickets in your ticket email and choose Change ticket.
  2. Choose which of your tickets to change, then the ticket and session you want. Tickets assigned to someone else are theirs to change.
  3. Read Check the change. Hubbaly compares today’s prices, including any member price you can use, without discount codes. Moving from a ticket costing £30 today to one costing £50 today means a Price difference of £20 plus a 50p fee for the change: a Total of £20.50. The fee is charged once per payment, even when several tickets change together.
  4. Choose Pay with the amount shown and complete the payment on Stripe. Several selected tickets share one payment. A cheaper move on another selected ticket does not reduce that payment. Any refund is separate and follows the event’s refund policy.
  5. Return to your ticket. Checking your payment means confirmation is still under way. When the new ticket details load, the page shows what changed and what you paid. If it says Payment confirmed while loading the details, wait for the updated pass.

Your existing ticket details stay in place until the change is confirmed. The new places are held while you pay. All selected tickets change together or none do. If the unpaid payment page expires, return to your ticket and check the choices again.

After a successful change, your QR code and reference stay the same, including saved or printed copies. Hubbaly emails the new details and a calendar file. Event extras stay on their original session; ask the organiser if those also need changing.

If you paid but the change cannot be made, Hubbaly starts a full refund of that change payment. The page shows whether the refund is being processed, is on its way back to the card, or needs help from the organiser. A refund being processed has not yet been confirmed. If your ticket has separately been cancelled, that cancellation still applies.

The person who paid finds a separate Ticket change payment in Purchase history, even if someone else bought the original ticket. Organisers see Ticket change payments in the event’s Orders. The original purchase stays unchanged.

Refunds after a paid change

Money paid for a ticket includes its original payment and its share of later paid changes. A refund uses the newest payment first and goes back to the card used for each payment. The standard refund keeps each payment’s retained fees once. The review separates retained processing fees from any processing fees covered by Hubbaly.

A cheaper move follows the event’s Moving to a cheaper ticket choice, described below. If you later return the ticket, the refund is also limited by the current ticket’s price, after fees, and by the money still available on it. If the ticket was originally free and you later paid to change it, the paid-ticket return rules apply.

Moving to a cheaper ticket

The organiser chooses what happens to the difference. Every event starts with No refund. The review shows the difference and the event’s policy before you choose Change without a refund.

With Refund the difference, the review says You get with the amount and the button says Change and get with that amount. The refund is today’s price difference, up to the money still left from the ticket’s payments, less the percentage fees on that difference. The money goes back to the card used for each payment, usually within 5 to 10 working days. A policy deadline also limits these automatic refunds. Checkout tells you the date, and once it has passed, it says the difference is no longer refunded.

Some money cannot be refunded through your change, for example when someone else paid for the original ticket. The review shows what is available. Ask the organiser if you need help.

If earlier refunds leave less than the price difference, the review shows only what can be returned and explains why. A difference under £1 counts as the same price, with no payment or refund.

Your ticket changes straight away. A refund still being processed or needing help does not undo the change. The confirmation tells you its progress. Your QR code and reference stay the same, and your changed ticket stays valid.

While Hubbaly is sending that refund, you and the organiser cannot give the ticket to someone else. This becomes available once Hubbaly confirms the refund is on its way back; you do not need to wait for it to appear in your card account.

A group change pays each price increase separately from any refund for a cheaper ticket. One change email covers the tickets you changed together. When the change refunds two or more cheaper tickets, one refund email lists each refund and the total once they are all on their way; your card statement still shows each refund on its own line. If one refund uses several payments, each person who paid gets one combined email for their share, rather than an email for each payment.

The refund is the price decrease less Hubbaly’s fee and the card company’s percentage on that difference, using the original payment’s actual rates. The card company’s fixed charge is not deducted again. A £20 ticket with a 70p Hubbaly fee and a 50p card fee, including 20p fixed, moved to £17 returns £2.85. Before confirming, you see the price decrease, fees kept and refund. Hubbaly keeps its whole original fee. A later standard refund still keeps each payment’s fees once; a full refund returns all money left.

Refund types

Baseline ticket refund policy

Tickets are for a specific date, so the usual 14-day online cooling-off right does not apply.

  • If you change your mind, can no longer attend, or bought the wrong ticket, Hubbaly does not guarantee a refund.
  • The organiser can still choose to issue a refund where their event policy allows it.
  • If the organiser cancels the event, moves it, reschedules it, or materially changes it, direct refund handling follows the organiser’s obligations, Hubbaly’s platform rules, and payment-provider requirements.
  • Optional ticket returns are separate from refund obligations. They only apply where the event has enabled them for that ticket type.
  • It is not an automatic legal refund right.

Single-ticket refund

  • Admin refunds a specific eligible ticket.
  • Works for designated-holder tickets when eligible.
  • Order may become Partially refunded.
  • The standard refund uses the money left across that ticket’s payments, after the retained fees shown in the breakdown. Each part goes back to the card used for that payment.

Whole-order refund

  • Admin can run whole-order refund when all active tickets are eligible.
  • If some tickets are blocked, action becomes eligible-only partial refund.

Refund part, keep the ticket valid

An organiser with Manage event sales can refund part of a paid ticket from Admin → Sales → Sold tickets, or select tickets in an order and choose Refund part.

  • Enter an amount or a percentage. An order amount is shared in proportion to the money left on the selected tickets. A percentage uses the total paid for each ticket, including its paid changes, capped at what is left on that ticket.
  • The ticket stays valid, with the same reference, QR code and place. This also applies if all the money is refunded.
  • Refunds use the newest payment first and go back to the card used for each payment. The payer receives an email. You can send another refund later, up to the amount available. Money awaiting refund confirmation already counts against that amount.
  • Bundles, staff passes, checked-in tickets and tickets with a return under way cannot use Refund part. After a transfer, the original payment may be unavailable to refund while money paid later to change the ticket can still be available. The review shows what you can refund now, separately from the total money left.
  • A later Refund and cancel the ticket keeps each payment’s retained fees back once. For a £20 ticket with £1.20 in retained fees and £5 already refunded, that cancellation returns £13.80. Wait for any earlier refund to finish before cancelling with a refund.

When an organiser moves a ticket to a cheaper choice, Refund the difference starts unticked. They can tick it and edit the amount, up to the money left. The ticket change stays saved if the optional refund cannot finish, and the organiser can retry that refund.

Full refund override (organiser absorbs fees)

  • Event admins can choose a fuller refund path for eligible paid tickets or orders.
  • The refund returns the money still left across the ticket’s payments, to the cards used for those payments.
  • The breakdown shows the retained fees the organiser covers and any processing fees covered by Hubbaly separately.
  • This is an override, not the default standard refund path.

Moderation-driven ticket outcomes

Some ticket changes come from a moderator decision rather than a normal attendee refund request.

  • When a moderator applies an event or hub ban, they choose the outcome for each affected active ticket.
  • INVALIDATE_REFUND means access is removed and the ticket is refunded through the normal refund path.
  • INVALIDATE_NO_REFUND means access is removed without sending money back.
  • Hubbaly does not automatically refund every banned ticket by default; the moderator makes that call explicitly.
  • Purchase history remains the ledger for refunded, partially refunded, and voided outcomes, and Safety holds the related moderation history.

Ticket returns and released tickets

Some events use ticket returns as an optional Hubbaly feature for eligible free and paid tickets. A free ticket is given back immediately with no refund step. A paid ticket enters a queue and is refunded only after another buyer fills the place. Neither path replaces the organiser’s legal obligations when an event is cancelled or materially changed.

For these return rules, a free ticket means no money has been paid for it. If you later paid to change it, the paid-ticket return rules apply.

Returning a free ticket

  1. Open the order in Purchase history.
  2. Choose Return ticket beside the eligible free ticket and read the final confirmation.
  3. Confirm only when you are sure. The ticket stops working immediately and the action cannot be undone.
  4. The place goes to the oldest eligible person on the waitlist first. If nobody is waiting, it becomes available to buy again.
  5. There is no refund or replacement-sale step because no money was paid.

For a complimentary ticket, sign in as the person who holds it, open it in My tickets, and choose Return this ticket. Its place goes to the waiting list first or back on sale, just like any other returned free ticket.

For a free ticket from checkout, the purchaser can return it while they still hold it. An email-only guest needs to contact the organiser. Staff-issued tickets, bundles, tickets with a transfer waiting, checked-in tickets and tickets for invite-only or cancelled events cannot be returned this way. Returns close when the event starts, or when the ticket’s chosen time starts if it admits one date or time.

Returning a paid ticket

Ticket return pipeline: return requested, place offered, replacement buys, refund settles.

Return requested

Your ticket stays valid for now.

Place offered

Waitlist first, then public buyers.

Replacement buys

Someone fills your place.

Refund settles

Back to your original payment method.

No replacement before the deadline: the return expires and you simply keep your ticket.

You can request a return before a ticket type is sold out. The request waits in the Ticket Return Queue until another buyer fills the place.

Your ticket shows Partial refund or Refunded under Price when the organiser has sent money back. The ticket can still be valid. If it is eligible for return, any refund depends on what remains after earlier refunds and fees. When all of the payment has been refunded, the ticket explains why it cannot be returned.

  1. Open the order in Purchase history. If you start from a live ticket page, use its shortcut back to the matching purchase row.
  2. Check both sections before confirming:
    • Tickets and returns shows what was paid, the fees and Refund if your place is filled per ticket.
    • Blocked tickets shows anything that cannot join right now, such as a pending transfer.
  3. Confirm with Request ticket return, Request holder approval, or Request returns and approvals depending on the tickets in the order.
  4. Tickets the purchaser still holds enter the Ticket Return Queue immediately. Their original ticket is locked from transfer/check-in while queued.
  5. Tickets currently held by someone else because they were assigned at checkout first ask that holder to approve the return. The holder gets an in-app notification and email, and their pass stays valid while they decide.
  6. If the holder approves, Hubbaly can release the place and the pass can stop working if a replacement buyer completes checkout. If the holder keeps the ticket, declines, or transfers it before approving, nothing is released and no refund is created.
  7. The platform tries waitlist-first, then public fallback:
    • If a waitlist offer exists, it is time-limited.
    • The released-ticket email/notification tells that buyer they are next in line and includes the exact Purchase by deadline.
    • How long that buyer gets scales with how far away the event is: roughly 48 hours a month out, about a day at one to four weeks, down to 30 minutes on event day, and never later than when ticket sales close.
    • The release email and waitlist management page can also offer Pass to next person when the buyer does not want the held tickets.
    • If that buyer passes or misses the deadline, Hubbaly offers the slot to the next eligible waitlist buyer before public fallback.
    • When that window closes, the earlier buyer is told the hold ended and gets a rejoin link.
  8. Your refund is processed only after a replacement purchase succeeds.
  9. Your refund if your place is filled uses the money still left across the ticket’s payments, less the retained fees shown in the review. Fees covered by Hubbaly are not deducted from your refund. A previous cheaper move can also limit the amount. The exact figure is shown next to the ticket before you request a return or approval.
  10. If no replacement purchase happens before ticket sales close (the event end time when one is set, otherwise the start time), the request expires and no refund is made. This is distinct from the event being cancelled by the organiser (see below).

Ticket eligibility

  • Eligible free tickets use the immediate return above and never enter the Ticket Return Queue.
  • Only paid tickets can enter the Ticket Return Queue, including a ticket that was originally free and later had a paid change. Eligible paid tickets wait for a replacement purchase before any refund.
  • Complimentary tickets use the immediate return from My tickets. Staff-issued and invite-only tickets show no self-serve return action.
  • Staff-assigned tickets (issued by an event admin outside a purchase) cannot use ticket returns - the assignment is tied to a specific person.
  • Tickets the ticket type’s admin has explicitly marked as not eligible for ticket returns never show the return action, regardless of event-level settings.
  • For the paid Ticket Return Queue, the ticket must currently be held by the original purchaser, or have been assigned at purchase and never transferred. If it is still with the designated checkout holder, that holder must approve before Hubbaly releases the place.
  • A ticket that’s been accepted by a different holder through a later transfer has to be transferred back before it can enter the Ticket Return Queue.
  • New self-serve ticket return requests stay open while ticket sales are open, which for multi-day events with an end time includes during the event. Once sales close, use organiser/support handling for refund questions, cancellations, postponements, or major event changes.

Who can request a return for a transferred ticket

  • The original purchaser is the refund owner for the original purchase. A refund of that payment goes back to its original payment method. Refunds of later paid changes go back to the cards used for those payments.
  • The current holder is the attendee. Holding a ticket after a transfer does not make that person the refund owner.
  • A ticket assigned to another member during checkout can still be requested from the original purchaser’s order when it has never moved again after checkout, but the current holder must approve before Hubbaly releases the place.
  • Pending holder approval is not a return request. The ticket stays valid and the holder can keep, use, or transfer it while deciding. If the holder transfers it before approving, Hubbaly cancels that approval request because a different person now holds the ticket.
  • If the holder approves, the purchaser sees the request move into the Ticket Return Queue. If the holder declines or the purchaser cancels first, the ticket is unchanged.
  • Once a ticket has been accepted through a later transfer, the self-serve path is: transfer it back to the original purchaser, then request the return from the original purchaser’s Purchase History.
  • Members plus guests events allow the original purchaser to hold extra guest tickets, so this duplicate-holder rule should not block transfer-back there.
  • If a strict members-only event does not allow guest tickets and the original purchaser already holds another active ticket for the same event, Hubbaly can show Transfer back blocked. That means transferring the ticket back would give the purchaser two active tickets in an event that only allows one member-held ticket per person, so organiser/support review is required.

What happens if the event is cancelled, the ticket is transferred out, or the ticket is already refunded

  • Event cancelled by the organiser: the Ticket Return Queue is closed immediately. Any queued/held/matched requests stop progressing; Hubbaly does not issue an automatic ticket return refund. The purchase detail surfaces a clear banner and points you at the organiser for a direct refund.
  • You transfer the ticket out after requesting a return: the underlying ticket is no longer yours at settlement time. Hubbaly detects this and does not refund the original purchaser. If the replacement purchase already completed, Hubbaly automatically refunds the replacement buyer so nobody keeps money for a phantom sale.
  • The ticket is already refunded or voided through another path: the queue request expires and no further refund is made. The status shows alongside the ticket so you can see what happened.

If Stripe settlement fails

  • Once the replacement sale is recorded, Hubbaly starts the refund. If a temporary connection problem prevents confirmation, Hubbaly tries again automatically, up to five attempts. A refund being processed has not yet been confirmed.
  • A refund may use several payments. The return is complete only after every part is confirmed.
  • If a bank reports that a refund failed, or the attempts cannot confirm it, the organiser or support needs to help. A failed refund is not money returned. A refund problem does not restore a ticket that has already been cancelled.

Mixed eligibility inside one order

  • A whole-order ticket return request only queues the tickets that are currently eligible.
  • If some eligible tickets need holder approval, Hubbaly queues the purchaser-held tickets and sends approval requests for the holder-held tickets instead of releasing them immediately.
  • Blocked tickets stay in the order with the blocker reason shown in the review step.
  • A pending transfer blocks that ticket until the transfer is cancelled, accepted, or expires.
  • A ticket transferred after purchase stays blocked until it returns to the original purchaser.
  • If Hubbaly already knows transfer-back will fail because the original purchaser already holds another active ticket for a strict members-only event that does not allow guest tickets, purchase detail can show Transfer back blocked instead of Transfer back first.
  • Transfer-back can fail under strict members-only holder rules, in which case the case moves to organiser/support handling.

Refund emails you may receive

  • Refund accepted means Hubbaly accepted the refund action or ticket return processing step and is still working through settlement.
  • Refund completed is the final confirmation after money movement finishes.
  • Ticket return completion emails include the ticket type, amount paid, retained fees and final refund amount.

Queue position visibility

  • While your request is still waiting, Hubbaly shows your Ticket Return Queue position on the purchase detail and ticket detail pages, and the purchase-level summary keeps the active queued positions visible.
  • Queue position is per event and ticket type.
  • Once a replacement buyer is actively being processed, the status becomes more important than the queue number and the request moves into OFFERED, MATCHED, or later settlement states.

Waitlist offer claim rules

  • Member/private contexts: the matching signed-in account must claim the offer.
  • Public contexts: waitlist email includes a one-time claim link/token; claim first, then checkout using the short-lived checkout claim token.
  • Passing a held ticket does not require a pre-existing session; the signed Pass to next person action can hand it on directly from the email.
  • Offer windows are time-limited; expired or already-used offers return unavailable/invalid outcomes and the prior buyer gets the expiry/rejoin message.

Queue statuses you may see

StatusMeaning
PENDING_HOLDER_APPROVALCurrent holder must approve before the place is released
QUEUEDRequest accepted, waiting for match/sale
OFFEREDWaitlist offer window currently active
MATCHEDReplacement checkout has started
REFUND_PENDINGReplacement sale succeeded; Stripe settlement is in progress
REFUNDEDSettlement completed
CANCELLEDYou cancelled before checkout started
EXPIREDEvent started before replacement sale
FAILEDSettlement retry/escalation required

Blocked refund reasons and what to do

Block reasonMeaningTypical next action
ticket_not_refundable_after_transferTicket moved after checkoutTransfer back to the original purchaser first, or use ops/support if transfer-back is blocked
transfer back blockedStrict members-only event does not allow the purchaser to hold another active ticketOrganiser/support handling is required
no_payment_to_refundNo paid line amount existsUse the free-ticket return when offered; otherwise no monetary refund is possible
Event already startedSelf-serve ticket returns have closedUse organiser/support handling for post-start refund questions
Already refunded/voidedTicket already settledNo further refund action
Metadata/legacy constraintsDeterministic refund split not availableUse scoped partial flow and capture operator notes

When A new paid ticket shows 0 Hubbaly fee / 0 Stripe fee

For organisers, this is a warning sign rather than the normal Connect-ready outcome.

  • On recently sold paid tickets, 0 Hubbaly fee / 0 Stripe fee usually means the sale was recorded through legacy routing or while the platform paid-ticket path was incomplete.
  • Check Hub -> Admin -> Settings -> Payments first.
  • If that card says Connected, rollout not active, Platform setup incomplete, or Needs review, investigate before more paid sales.
  • Old event versus new event is not enough to explain this by itself. The hub rollout mode and the checkout path used for that sale matter more.

If Stripe already shows a settled processing fee for a new Connect sale but Hubbaly still shows Stripe processing £0.00, that now indicates stale stored financial snapshots rather than the wrong Stripe route. Opening the purchase detail, ticket detail, or Event Admin sold-ticket view now triggers a settled-fee refresh so those snapshots can repair themselves.

Admin refund decision flow

From Event Admin Tickets:

  1. Open Order Refunds.
  2. Click Review Refund Scope.
  3. Read both sections:
    • Will refund now
    • Not refundable now (+ reasons)
  4. Confirm action:
    • Refund Whole Order when fully eligible,
    • Refund Eligible Tickets when partially eligible.

Before confirming, answer these explicitly:

  1. What amount is being refunded now?
  2. Which tickets are excluded and why?
  3. Is this the standard fee-retaining refund or the organiser-absorbed full-refund override?
  4. What should the admin do next for excluded items?
Last updated on