List Event

Payment safety

Your gateway processes the money. TKKT verifies the ticket.

TKKT coordinates the booking record and ticket issue while Yoco, PayFast, or Paystack handles the payment transaction under the organiser's account.

Current limitation: automated end-to-end reconciliation is still being strengthened, especially when a successful Yoco buyer does not complete the return flow.

01

The payment path

  1. 01

    Booking session created

    TKKT records the intended event, quantity, price, and gateway before sending the buyer to payment.

  2. 02

    Provider processes payment

    The buyer completes the provider-hosted or provider-controlled payment flow. TKKT does not receive card details.

  3. 03

    Success is verified

    The integration checks the provider response or callback and validates the expected payment details before finalisation.

  4. 04

    Tickets are finalised once

    A shared database-locked finaliser creates the booking reference and tickets while guarding against repeated provider notifications.

  5. 05

    Buyer and organiser are notified

    The ticket email and organiser reporting follow the completed booking record.

02

Who is responsible for what

Payment provider

Card processing, merchant verification, provider settlement, disputes, and provider-side refunds.

Organiser

Accurate event information, delivery of the event, taxes, refund policy, and the security of their payment account.

TKKT

Booking-session integrity, provider integration, ticket issue, attendee records, organiser reporting, and scanner behavior.

03

Current limitations, stated plainly

  • Yoco ticket finalisation currently depends primarily on the buyer returning to TKKT after payment
  • Automated reconciliation between every provider record and TKKT session is still being strengthened
  • Gateway credentials travel over HTTPS, but dedicated application-level encryption at rest remains planned work
  • Keep the gateway receipt and TKKT booking reference when reporting a missing ticket

FAQ

Questions organisers ask

Can TKKT see my card number?

No. Card entry happens in the selected provider's payment flow. TKKT receives transaction status and booking information, not the buyer's card number or CVV.

What if I am charged but receive no ticket?

Keep the gateway receipt and contact the organiser and TKKT with the event name, payment time, payer email, and payment reference. Never send card numbers, CVVs, or gateway secret keys.

Who handles chargebacks?

Chargebacks and payment disputes are handled under the organiser's relationship with the connected payment provider.

Set up your event before connecting payments.

A gateway is needed only for paid ticket sales.

Describe Your Event R0 TKKT platform fee. No card required to start.