Signed notification
PayFast sends its payment notification to TKKT after checkout.
PayFast event ticketing
Use your PayFast merchant account for payment processing while TKKT handles the listing, booking record, QR ticket, organiser dashboard, and door scanning.
01
Complete PayFast's merchant setup and verification. Retrieve the merchant ID and merchant key from its integration settings.
Choose Live for real transactions. Sandbox credentials are useful for testing but cannot enable real paid ticket sales.
Enter the PayFast passphrase when your account uses one. It must match the value in PayFast exactly.
Set the PayFast notification endpoint to https://tkkt.co.za/api/payfast_itn.php so completed payments can be verified server to server.
TKKT checks that the required values look usable and that PayFast is reachable. Only a completed test booking confirms the merchant credentials end to end.
02
PayFast sends its payment notification to TKKT after checkout.
TKKT checks the signature, validates the notification with PayFast, and checks the expected amount before issuing tickets.
Repeated callbacks do not intentionally create duplicate ticket sets for the same completed session.
03
FAQ
It is optional in TKKT because not every PayFast account uses one. If your PayFast account has a passphrase, enter the exact same value.
No. Select Live mode and use live merchant credentials for an event that is selling to the public.
No. The transaction is processed under the organiser's PayFast merchant account.
Use your PayFast account for the money movement, then contact TKKT to invalidate the matching ticket. TKKT does not hold the payment.
Start with your event details, then connect the merchant account from your organiser payment settings.
Build My Event Page R0 TKKT platform fee. No card required to start.