Event Ticketing Platform Kenya: Selling, Scanning and Getting Paid
Event ticketing platform Kenya decisions get made on the wrong criteria, and the consequences show up at exactly two moments: when someone tries to buy a ticket and when they try to get through the gate.
An organiser comparing platforms will look at the fee, the ticket page design and the reporting screens. What actually determines whether the event works is whether a buyer on a phone can complete an M-Pesa payment and receive a ticket within seconds without a second thought, and whether four hundred people arriving between seven and half past can be scanned through the gate faster than they arrive.
Fail the first and you lose sales you never learn about, because a buyer whose payment did not confirm simply stops trying and nobody tells you. Fail the second and you have a queue outside while the event starts inside, staff arguing with people holding valid tickets, and a reputation that follows the organiser to their next event.
Everything else the platform does — tiers, guest lists, reporting, settlement — matters and none of it matters as much as those two moments working. This guide covers both properly, alongside the rest: ticket structures and pricing, the payment flow and its failure modes, check-in and throughput, capacity control, complimentary and guest handling, reporting, settlement and the data obligations that come with holding buyer information.
The value of an event ticketing platform Kenya is a sale that completes and a gate that keeps moving, and an event ticketing platform Kenya that handles the payment edge cases reliably is doing the thing that determines revenue — which is why an event ticketing platform Kenya should be assessed on payment and scanning before anything else.
Table of Contents
- What a Ticketing Platform Does
- Why Organisers Move Away From Manual
- The Kenyan Context
- Event Types and Their Ticketing Needs
- Ticket Types and Tiers
- Pricing Strategy
- Early Bird and Time-Based Pricing
- Group and Table Sales
- Free Events and RSVP
- Fees and Who Pays Them
- The Ticket Buying Flow
- M-Pesa Payment in Practice
- When Payment Confirmation Fails
- Duplicate Payments
- Card and Other Payment Methods
- Ticket Delivery
- QR Codes and What They Contain
- Capacity and Inventory Control
- Complimentary Tickets and Guest Lists
- Sales Channels and Promotion
- Box Office and On-the-Day Sales
- Check-In and Gate Throughput
- Calculating Scanning Capacity
- Scanning in Practice
- Offline Operation at the Gate
- Handling Problems at the Gate
- Fraud and Duplicate Tickets
- Multi-Day and Multi-Session Events
- Reporting Before the Event
- Reporting After the Event
- Settlement and Getting Paid
- Refunds, Cancellation and Postponement
- Data Protection and Buyer Information
- Choosing a Platform
- Frequently Asked Questions
What a Ticketing Platform Does {#what-it-does}
The functions are distinct and buyers frequently assess only some.
Ticket definition including types, tiers and pricing.
Sales through a page buyers can reach.
Payment collection.
Ticket issue to the buyer.
Capacity control preventing overselling.
Check-in verifying tickets at entry.
Reporting on sales and attendance.
Settlement of funds to the organiser.
Attendee data management.
The chain matters end to end, since an event ticketing platform Kenya with excellent reporting and unreliable payment has failed at the point that generates the revenue the reporting describes, and an event ticketing platform Kenya should be judged across the whole flow rather than on its interface.
Why Organisers Move Away From Manual {#why-move}
Manual arrangements work until they do not and the failure point is predictable.
Printed tickets sold physically, which limits reach to people who can collect them.
Payment by transfer with a name on a list, which requires someone to maintain the list.
No advance visibility of sales.
Name lists at the gate, which cannot handle volume.
Duplicate and fraudulent tickets undetectable.
Cash handling at the gate with its reconciliation burden.
Reconciliation afterwards between what was collected and what was recorded.
Volume is the breaking point, since a list works for eighty people and fails for four hundred, and an event ticketing platform Kenya organiser who scaled up without changing the process will discover it at the gate.
Advance visibility is the other driver, since an event ticketing platform Kenya showing sales daily lets an organiser adjust promotion while there is time, and a manual arrangement reveals attendance on the day.
The Kenyan Context {#kenyan-context}
Local conditions shape the requirement substantially.
M-Pesa is how buyers pay, which makes payment integration the defining technical requirement rather than one feature.
Card penetration is lower, which limits card-only platforms.
Mobile is the buying device, since most purchases happen on a phone.
Data cost affects the buying experience, since a heavy ticket page consumes data buyers pay for.
Last-minute buying is common, since a substantial share of sales occur close to the event and sometimes at the gate.
That pattern matters, since an event ticketing platform Kenya organiser expecting sales to accumulate steadily will worry unnecessarily and one who understands the curve plans promotion accordingly.
Cash at the gate persists and cannot be eliminated entirely.
Connectivity at venues varies, which makes offline scanning capability essential rather than optional.
Event types span corporate, church, community, entertainment and social, each with different expectations, and an event ticketing platform Kenya serving all of them needs flexibility.
Event Types and Their Ticketing Needs {#event-types}
Different events need different configurations.
Conferences with tiered pricing, delegate categories and sometimes multi-day passes.
Concerts and entertainment with tiered seating or standing areas.
Corporate events with invitation-only access and guest lists.
Church events including conferences and conventions, frequently with registration rather than payment.
Community and charity events combining tickets with contributions.
Fundraising dinners with table sales.
Training and workshops with capacity limits and materials.
Sports and social events.
Graduations and school events with guest allocation per attendee.
Configure to the event, since an event ticketing platform Kenya applying a concert configuration to a conference will not handle delegate categories, and an event ticketing platform Kenya with flexible ticket definition serves more event types.
Ticket Types and Tiers {#tiers}
Ticket structure affects both revenue and complexity.
Single ticket type for simple events.
Tiers by access level, seating or inclusion.
Categories by attendee type including student, member or delegate.
Day passes versus full event passes.
Add-ons including meals, materials or merchandise.
Table and group tickets.
Keep it manageable, since an event ticketing platform Kenya page offering fifteen options confuses buyers where one offering three or four converts, and complexity reduces sales.
Clarity about what each includes, since a buyer uncertain what they are purchasing may not purchase.
Test the buyer’s view, since an event ticketing platform Kenya structure that made sense to the organiser may be confusing to someone seeing it for the first time.
Pricing Strategy {#pricing}
Price determines both volume and revenue and it is frequently set by instinct.
Market comparison for similar events.
Cost basis, since the event must cover its costs.
Audience capacity to pay.
Perceived value relative to what is included.
Tier differentials, since the gap between tiers should reflect a difference buyers can see.
Round numbers that work with mobile money.
Psychological thresholds.
Model the break-even, since an event ticketing platform Kenya organiser who knows how many tickets must sell to cover costs has the number that matters, and one who does not is guessing at viability.
Watch the conversion, since an event ticketing platform Kenya reporting page visits against purchases shows whether price is deterring buyers, and a page with substantial traffic and few sales has a problem that may be price or may be the buying flow.
Early Bird and Time-Based Pricing {#early-bird}
Time-based pricing brings sales forward.
Early bird at a reduced price for a defined period.
Regular pricing afterwards.
Late or gate pricing at a premium.
The purpose is cash flow and certainty, since an organiser with sales in hand weeks ahead can plan where one waiting for the day cannot.
Deadlines must be enforced, since an early bird extended repeatedly teaches buyers that deadlines are not real and next time they will wait.
That discipline matters, since an event ticketing platform Kenya that automatically switches pricing at the deadline enforces it where manual management does not.
Communication of deadlines drives the urgency that makes it work.
Quantity-limited tiers as an alternative, where a number of tickets are available at the lower price.
Measure the effect, since an event ticketing platform Kenya showing sales by tier and period tells the organiser whether early pricing actually brought sales forward or simply discounted sales that would have happened.
Group and Table Sales {#group-sales}
Group purchasing serves corporate and social buyers.
Table sales for dinners and formal events.
Group discounts for bulk purchase.
Corporate block purchase.
Named attendees against a group booking, since the buyer purchases and attendees must be identified for check-in.
That distinction matters, since a company buying ten tickets needs a way to allocate them to individuals, and an event ticketing platform Kenya that issues ten identical tickets without attendee names creates a gate problem where one that collects names does not.
Invoice-based purchase for organisations that cannot pay by mobile money, which the payment section addresses.
Seating allocation for table events.
Handle the allocation, since an event ticketing platform Kenya allowing a group buyer to enter their attendees afterwards serves the corporate buyer properly.
Free Events and RSVP {#rsvp}
Not every event charges and registration still matters.
RSVP for free events establishes expected attendance.
Capacity management even where free, since a free event with limited space needs control.
No-show rates are substantially higher for free events, since people who paid nothing lose nothing by not attending, and planning on full attendance of free registrations will overprovide.
Reminder communication reduces no-shows.
Registration data collection.
Check-in for free events still benefits from scanning, since verifying registration at the gate is faster than a name list.
Conversion to paid later where an organiser tests demand free and charges subsequently.
Church and community events frequently operate this way, since an event ticketing platform Kenya serving a church convention may be managing registration rather than sales, and an event ticketing platform Kenya that handles both paid and free uses one process.
Fees and Who Pays Them {#fees}
Platform fees affect both economics and the buyer’s experience.
Per-ticket fees or percentage of sale.
Payment processing charges separately or included.
Who absorbs them, since the organiser can absorb the fee or add it to the ticket price.
Absorbing reduces margin and presents a clean price to buyers.
Passing on shows the buyer a fee added at checkout, which may reduce conversion.
Transparency matters, since a buyer who sees an unexpected charge at the final step may abandon the purchase.
Calculate the net, since an event ticketing platform Kenya organiser who modelled revenue on gross ticket price without deducting fees and processing has overstated what they will receive.
Compare total cost rather than headline rate, since an event ticketing platform Kenya with a low platform fee and high processing charges may cost more than one with the reverse.
Ask what else is charged, since setup, withdrawal or support fees may apply.
The Ticket Buying Flow {#buying-flow}
The buying experience determines conversion and it is where sales are lost invisibly.
The buyer reaches the ticket page.
Selects ticket type and quantity.
Enters their details.
Pays.
Receives the ticket.
Every step loses some buyers, since each additional field and click is an opportunity to abandon.
Mobile experience is what matters, since most buyers are on a phone and a page that is awkward on mobile loses them.
Page speed and data weight, since a slow heavy page on a modest connection may not load.
Minimal required information, since asking for extensive detail to buy a ticket deters buyers.
Test it yourself on a phone, since an event ticketing platform Kenya organiser who completed a purchase on their own event as a buyer would knows what the experience is, and one who only saw the admin interface does not.
Abandonment is invisible, since an event ticketing platform Kenya buyer who gave up partway tells nobody, which is why the flow must be tested rather than assumed.
M-Pesa Payment in Practice {#mpesa}
Mobile money integration is the defining technical requirement.
The flow is asynchronous, since the buyer authorises on their handset and confirmation arrives separately.
Timing is unpredictable, since authorisation may take seconds or longer.
Push prompt to the buyer’s phone is substantially better than requiring manual paybill entry, since manual entry produces reference errors that leave payments unattributable.
Reference matching is the problem with manual payment, since a buyer entering the wrong reference has paid money the system cannot connect to their order.
Confirmation must be verified rather than assumed, since issuing a ticket on the buyer’s assertion that they paid is an obvious exposure.
Speed matters, since a buyer waiting for a ticket after paying begins to worry.
Feedback during the wait, since a page showing that payment is being confirmed is better than a blank screen.
Provider capabilities change, so confirming the current integration options directly is necessary rather than relying on older information.
Test the failure cases, since an event ticketing platform Kenya tested only on successful payment has not been tested, and an event ticketing platform Kenya that handles timeouts and cancellations survives production.
When Payment Confirmation Fails {#payment-failure}
Failure handling determines whether the buyer is lost or recovered.
The buyer has paid and has no ticket, which is the worst outcome.
Detection matters, since the platform should identify payments received without tickets issued, and an event ticketing platform Kenya reporting these exceptions lets the organiser resolve them.
Automatic retry of ticket issue resolves some.
Status query to the payment provider where confirmation did not arrive, since the definitive answer is whether the payment actually completed.
Manual resolution must be available, since some cases need an organiser to issue a ticket against a confirmed payment.
Support route must be visible, since a buyer who paid and received nothing needs someone to contact.
Response speed matters, since a buyer waiting a day for resolution may have given up.
Refund where it cannot be resolved.
Never leave a buyer without ticket or refund, since an event ticketing platform Kenya that took money and delivered nothing has damaged the organiser’s reputation, and an event ticketing platform Kenya that resolves these promptly protects it.
Duplicate Payments {#duplicates}
Duplicate payment is common and its handling matters.
A buyer who did not see confirmation may pay again.
The platform must recognise the duplicate rather than issuing two tickets.
Unique transaction identification is the mechanism.
Crediting or refunding the duplicate is the fair response.
Automatic detection resolves what would otherwise be a dispute, since an event ticketing platform Kenya that identifies and refunds duplicates handles it without the buyer having to complain.
Reporting frequency, since an event ticketing platform Kenya showing how often duplicates occur indicates whether the confirmation flow is failing often enough that buyers are paying twice.
Test it, since duplicate handling that has never been exercised may not work.
Card and Other Payment Methods {#other-payments}
Additional methods extend reach.
Card payment for buyers who prefer it and for international buyers.
Bank transfer for corporate purchasers who cannot pay by mobile money.
Invoice for organisations requiring one, since a company buying tickets may need an invoice and a purchase order process.
That corporate requirement matters, since an event ticketing platform Kenya serving conferences will encounter organisations that cannot pay instantly and need an invoice, and a platform with no mechanism for it loses those sales.
International payment for diaspora and foreign attendees.
Multiple methods add complexity and reconciliation.
Match methods to the audience, since an event ticketing platform Kenya offering only mobile money serves most local buyers and excludes corporate and international ones.
Ticket Delivery {#delivery}
How the buyer receives their ticket affects check-in.
Message delivery to the phone, which is immediate and reliable.
Email delivery with the ticket attached or linked.
In-platform access where the buyer can retrieve it.
Screenshot usability, since many buyers will screenshot the ticket and the scanning must work from a screen image.
Print option for those who prefer it.
Resend capability, since buyers lose tickets and an event ticketing platform Kenya with self-service resend removes support burden.
Clear information on the ticket including event, date, time, venue and type.
Test the delivery, since an event ticketing platform Kenya where tickets arrive in a format that will not scan reliably at the gate has created the problem it exists to prevent.
Confirm receipt, since a buyer who paid and received nothing will contact the organiser.
QR Codes and What They Contain {#qr-codes}
QR codes are the mechanism that makes fast check-in possible.
A unique identifier per ticket.
Validation against the platform rather than the code containing the data, since a code that can be read and replicated is less secure than one validated centrally.
Scanning speed, since a code that scans reliably in a moment is what throughput depends on.
Screen readability, since most buyers present a phone screen and the code must scan from it including in poor light or with a cracked screen.
Print readability where tickets are printed.
Uniqueness preventing duplication, which the fraud section addresses.
Size and contrast affecting scannability.
Test scanning from actual phones, since an event ticketing platform Kenya code that scans from a bright new phone may struggle with an older dimmer screen, and gate delays come from codes that take several attempts.
Capacity and Inventory Control {#capacity}
Capacity control prevents the problem of more tickets than space.
Total capacity set against the venue.
Per-tier allocation where tiers have separate limits.
Real-time decrementing as tickets sell.
Overselling prevention, since selling beyond capacity creates a situation at the door that cannot be resolved well.
Holds and reservations for sponsors, media and organiser allocation.
Release of unsold holds before the event.
Waiting list where demand exceeds capacity.
Venue capacity limits should be respected, since exceeding a venue’s permitted capacity may breach safety requirements and confirming the limit with the venue and relevant authorities is necessary.
Never oversell deliberately, since an event ticketing platform Kenya organiser who sold beyond capacity expecting no-shows has created a situation where people who paid are turned away, and the damage is substantial.
Complimentary Tickets and Guest Lists {#complimentary}
Free and invited attendance needs managing alongside sales.
Complimentary tickets for sponsors, partners, media and guests.
Guest lists for invitation-only elements.
VIP and speaker allocation.
Staff and crew access.
They consume capacity, since complimentary tickets occupy space that paying attendees would have, and an organiser who issued a hundred complimentary tickets against a capacity of four hundred has sold three hundred.
Track them explicitly, since an event ticketing platform Kenya that reports complimentary separately from sold shows the real position, and one that combines them overstates sales.
Issue them as scannable tickets, since a guest list checked by name at the gate is slow and a complimentary ticket with a QR code scans as fast as a paid one.
Control who can issue them, since an event ticketing platform Kenya where several people issue complimentary tickets without record will find more issued than intended.
Sales Channels and Promotion {#channels}
Reaching buyers determines whether tickets sell.
The ticket page link shared directly.
Social media promotion.
Messaging and direct sharing.
Email to previous attendees where consent permits.
Physical promotion with the link or a code.
Partner and sponsor channels.
Agents or sellers with their own links where used.
Track the source, since an event ticketing platform Kenya that shows which channel produced which sales tells the organiser where promotion works, and one that does not leaves them guessing.
Shareability matters, since a link that is easy to share spreads, and an event ticketing platform Kenya page that previews well when shared on messaging platforms gets more reach than one that appears as a bare link.
Box Office and On-the-Day Sales {#box-office}
Gate sales persist and must be handled.
Buyers who did not purchase in advance.
Cash payment at the gate, which requires handling and reconciliation.
Mobile money at the gate, which is faster and produces a record.
Issuing a scannable ticket at the gate so the attendee enters through the same process.
Speed matters, since a gate sale that takes several minutes blocks the entrance.
Separate the queues, since an event ticketing platform Kenya arrangement with a separate line for purchases keeps the scanning line moving, and combining them means everyone waits behind each transaction.
Gate pricing at a premium encourages advance purchase.
Cash reconciliation at the end, since money taken at the gate must be accounted for and an event ticketing platform Kenya recording gate sales in the system rather than as loose cash has the record.
Check-In and Gate Throughput {#check-in}
Check-in is where ticketing succeeds or fails visibly.
Scanning verifies the ticket and records attendance.
Speed determines whether a queue forms.
Arrival pattern is concentrated, since attendees arrive in a burst before the start rather than evenly.
Entry points and their number.
Staff operating the scanning.
Queue management and signage.
The first impression, since an event ticketing platform Kenya event where attendees waited outside while the programme started has set a tone that the content has to overcome.
Plan it as an operation, since an event ticketing platform Kenya organiser who calculated throughput and staffed accordingly has a gate that works, and one who assumed it would be fine will have a queue.
Calculating Scanning Capacity {#scanning-capacity}
The calculation is straightforward and rarely done.
Expected attendance.
Arrival window, since most attendees arrive within a concentrated period.
Arrivals per minute at peak.
Time per scan including presenting the phone, scanning and moving through.
Scans per minute per point.
Points required to clear the arrival rate.
The arithmetic is unforgiving, since four hundred people arriving over thirty minutes is more than thirteen per minute, and a single scanning point handling ten per minute cannot clear them.
Add margin, since scans fail, questions arise and some attendees are slower.
Do the calculation, since an event ticketing platform Kenya organiser who worked out the requirement will provide enough points, and an event ticketing platform Kenya event with one scanner for a large arrival burst has a queue that was predictable weeks in advance.
Scanning in Practice {#scanning-practice}
Operational detail determines actual throughput.
Devices used for scanning, whether phones or dedicated scanners.
Phone cameras are adequate and their speed varies by device.
Lighting at the gate, since scanning in darkness is slower and a lit entrance scans faster.
Staff familiarity, since an operator who has used the system scans faster than one learning at the gate.
Positioning so attendees present tickets without stopping unnecessarily.
Screen glare and how attendees hold their phones.
Battery for scanning devices across the event.
Brief and practise, since an event ticketing platform Kenya gate team that tested the process beforehand is faster, and one handed devices at the entrance will be slow during the busiest period.
Have a supervisor, since an event ticketing platform Kenya gate with someone handling exceptions keeps the scanning lines moving rather than each operator stopping to resolve problems.
Offline Operation at the Gate {#offline}
Connectivity failure at the gate must not stop entry.
Venue connectivity is unreliable and a gate dependent on it will fail.
Offline scanning validates against locally held data.
Synchronisation when connectivity returns.
Duplicate detection across devices, since two scanners operating offline may both accept the same ticket unless the arrangement handles it.
Pre-download of the attendee list before the event.
Fallback to manual verification where scanning is entirely unavailable.
This is essential rather than optional, since an event ticketing platform Kenya that stops working when the venue connection drops has stopped the entrance, and this happens routinely at venues here.
Test it, since an event ticketing platform Kenya offline capability that was never exercised may not work, and discovering that at the gate is the worst moment.
Handling Problems at the Gate {#gate-problems}
Exceptions occur and handling them without blocking the queue matters.
Ticket not found, whether through a system issue or the attendee having the wrong reference.
Already scanned, which may be duplication or may be a legitimate re-entry.
Wrong event or wrong day.
Attendee without a ticket claiming to have purchased.
Name list requests and complimentary attendees not issued tickets.
Move them aside, since an event ticketing platform Kenya gate that resolves problems in the scanning line blocks everyone behind, and a separate position for exceptions keeps the main flow moving.
Lookup capability so staff can find a purchase by phone number or name.
Authority to admit, since staff need to know who can decide to let someone in.
Be reasonable, since an event ticketing platform Kenya attendee who genuinely paid and has a system problem should not be turned away over a technical failure, and the organiser should establish that position with gate staff in advance.
Fraud and Duplicate Tickets {#fraud}
Ticket fraud occurs and scanning addresses most of it.
Duplicated tickets, where one ticket is shared or forwarded to several people.
Screenshot sharing, which is the common method.
Counterfeit tickets.
Resale above face value where the organiser prohibits it.
Single-use scanning is the control, since the first presentation admits and subsequent presentations of the same code are rejected.
That control works, since an event ticketing platform Kenya that rejects a second scan of the same ticket prevents the sharing that manual checking cannot detect.
The consequence falls on the second person, since someone who bought a forwarded ticket in good faith is turned away, and gate staff need guidance on handling that situation with some humanity.
Named tickets with identity verification for high-value events.
Report patterns, since an event ticketing platform Kenya showing repeated rejected scans indicates something worth understanding.
Multi-Day and Multi-Session Events {#multi-session}
Events spanning sessions need their own handling.
Multi-day passes admitting across days.
Day tickets for single days.
Session tickets for specific sessions within an event.
Re-entry within a day.
Capacity per session where sessions have separate limits.
Scanning per session recording attendance at each.
Session attendance data, which is valuable for conferences since it shows which sessions drew attendance.
Wristbands or alternative for multi-day where repeated scanning is impractical.
Configure it properly, since an event ticketing platform Kenya conference where a multi-day pass is rejected on the second day because the ticket was marked used has a serious problem, and an event ticketing platform Kenya configured for multi-session handles it.
Reporting Before the Event {#pre-event-reporting}
Advance visibility is a primary benefit and organisers underuse it.
Sales to date against target.
Sales by ticket type and tier.
Sales by channel.
Sales curve over time.
Revenue collected.
Capacity remaining.
Complimentary issued.
The pace is what informs action, since an event ticketing platform Kenya showing sales tracking behind the previous event at the same point tells the organiser to increase promotion, and one checked only occasionally provides the information too late.
Daily review in the final weeks, since an event ticketing platform Kenya organiser watching the curve can respond where one looking at the total on the day cannot.
Attendance forecasting for catering and logistics, since numbers must be confirmed to suppliers.
Reporting After the Event {#post-event-reporting}
Post-event data informs the next one.
Total sold and total attended.
No-show rate, which is the gap between them.
Attendance by ticket type.
Check-in timing showing the arrival pattern.
Revenue by tier and channel.
Gate sales.
Session attendance for multi-session events.
The no-show rate is the most useful figure, since knowing what proportion of buyers actually attended informs planning for the next event, and an event ticketing platform Kenya reporting it lets an organiser plan catering and capacity realistically.
Arrival pattern informs gate planning, since an event ticketing platform Kenya showing when attendees actually arrived tells the organiser how many scanning points the next event needs.
Retain it, since comparison across events builds understanding.
Settlement and Getting Paid {#settlement}
Getting the money is the part organisers worry about and should check before committing.
Timing of settlement, whether before, at or after the event.
Settlement before the event supports cash flow, since an organiser needs to pay suppliers before the event happens.
Settlement after the event is common and creates a funding gap.
That timing matters substantially, since an event ticketing platform Kenya organiser who assumed funds would be available to pay the venue deposit and discovers settlement occurs after the event has a problem.
Partial or milestone settlement as a middle position.
Fees deducted and the net amount.
Settlement destination and its verification.
Reconciliation between sales reported and funds received.
Confirm the terms before selling, since an event ticketing platform Kenya arrangement whose settlement terms were never established leaves the organiser uncertain when they will be paid.
Check the reconciliation, since sales figures and settlement should match after fees and an unexplained difference needs investigation.
Refunds, Cancellation and Postponement {#refunds}
Policy should be set before selling rather than decided during a crisis.
Refund policy stated at purchase, since buyers should know the terms.
Individual refund requests and who approves them.
Event cancellation and the obligation to refund.
Postponement and whether tickets transfer to the new date.
Partial refunds where fees are non-refundable.
Processing mechanism and timing.
Communication to buyers, since a cancelled event where buyers were not told promptly generates anger beyond the refund itself.
Establish it in advance, since an event ticketing platform Kenya organiser facing cancellation without a stated policy will improvise under pressure, and one with terms published can apply them.
Honour it, since an event ticketing platform Kenya organiser who cancelled and did not refund has taken money for something not delivered, and the reputational and legal consequences follow.
Take advice on obligations, since consumer protection considerations may apply and confirming the position is worth doing.
Data Protection and Buyer Information {#data-protection}
Ticket sales collect personal data and the Data Protection Act applies.
The data includes names, phone numbers, email addresses and purchase history.
Attendance records showing who attended what.
Collection should be limited to what is needed, since a ticket purchase requiring extensive personal detail is over-collecting.
Purpose is the event, since data collected to issue a ticket was collected for that purpose.
Marketing use is a distinct purpose requiring consent, since a ticket buyer has not thereby agreed to receive promotion for future events.
That distinction is routinely ignored, since an event ticketing platform Kenya organiser who added every buyer to a mailing list has assumed something they should have asked, and an opt-in at purchase addresses it properly.
Never sell or share attendee lists, since buyers provided details to attend an event rather than to be passed to third parties.
Access restriction, since not everyone involved needs the full attendee list.
Retention defined rather than indefinite.
Platform as processor, since the platform handles data on the organiser’s behalf and the arrangement carries obligations.
Confirm obligations with qualified advice, since an event ticketing platform Kenya organiser holding substantial attendee data should understand their position.
Choosing a Platform {#choosing}
Selection should test what actually matters.
Complete a test purchase yourself on a phone, since this is the most informative thing you can do and it reveals the buying experience directly.
Ask what happens when M-Pesa confirmation does not arrive.
Ask about duplicate payment handling.
Test offline scanning, since a platform that cannot scan without connectivity will fail at venues here.
Ask about scanning speed and how many devices can operate.
Confirm settlement timing and terms.
Understand the total cost including processing and any other charges.
Check reporting before purchase, since an event ticketing platform Kenya with weak advance reporting leaves the organiser without the visibility that is a primary reason to use a platform.
Support availability during the event, since a problem at the gate needs resolution immediately and an event ticketing platform Kenya provider reachable on the day is worth more than one who responds within two working days.
Talk to other organisers, since their experience of the payment flow and the gate is the most useful evidence.
Frequently Asked Questions {#faqs}
What matters most in a ticketing platform?
Two moments: a buyer on a phone completing an M-Pesa payment and receiving a ticket within seconds, and the gate scanning people through faster than they arrive. Fail the first and you lose sales you never learn about, since a buyer whose payment did not confirm simply stops and tells nobody. Fail the second and you have a queue outside while the event starts inside.
How many scanning points do we need?
Do the arithmetic. Expected attendance divided by the arrival window gives arrivals per minute — four hundred people over thirty minutes is more than thirteen a minute, and a single point handling ten cannot clear them. Add margin for failed scans and questions, and put a supervisor on exceptions so problems do not block the line.
What if the venue’s internet fails at the gate?
The gate must keep working, which means offline scanning against locally held data with synchronisation afterwards. This is essential rather than optional given venue connectivity here — and test it before the event, since offline capability that was never exercised may not work and the gate is the worst place to discover that.
A buyer paid and got no ticket. What should happen?
The platform should detect payments received without tickets issued and let the organiser resolve them, with a status query to the payment provider where confirmation did not arrive. There must be a visible support route and a manual issue capability. Never leave a buyer without either ticket or refund — it damages the organiser’s reputation far beyond the ticket value.
Should we absorb the platform fee or pass it on?
Absorbing gives buyers a clean price and reduces your margin; passing it on shows a charge at checkout that may reduce conversion. Either way, model the net — an organiser who calculated revenue on gross ticket price without deducting fees and processing has overstated what they will actually receive.
How do complimentary tickets affect us?
They consume capacity. A hundred complimentary tickets against a four-hundred capacity means you have three hundred to sell. Track them separately from sales so the reported position is real, issue them as scannable tickets so they check in as fast as paid ones, and control who can issue them.
When do we get the money?
Confirm this before you start selling. Settlement after the event is common and creates a funding gap, since suppliers and venues need paying beforehand. An organiser who assumed funds would be available for the venue deposit and finds settlement happens afterwards has a cash flow problem that was avoidable.
Can we email attendees about our next event?
Not without consent. A ticket buyer provided their details to attend that event, and marketing is a distinct purpose requiring their agreement — an opt-in at purchase handles it properly. Never sell or share attendee lists, since an event ticketing platform Kenya buyer gave you their details to attend rather than to be passed on.