The problem
PayFast doesn’t plug into Swoogo’s registration flow on its own. This client needed registrants to pay through PayFast and come back to a Swoogo registration already marked paid, without a support ticket every time a confirmation was slow to arrive.
The approach / solution
- Built a custom payment form, pre-filled with the registrant’s own Swoogo event and profile data, submitting straight to PayFast.
- Built a confirmation watcher that polls the registrant’s Swoogo field for a “confirmed” PayFast status and auto-clicks the hidden continue button the instant it appears.
- Extended that watcher with retries and a 30-second manual-show fallback, so a slow PayFast confirmation never leaves someone stuck on a payment screen with no way forward.
Outcome / result
A registrant pays through PayFast and moves on in their Swoogo registration on their own — typically within a couple of seconds, worst case within thirty.
Why it matters for enterprise event-tech
A payment confirmation screen that just sits there, with no indication whether it worked, turns into a support ticket fast. Covering both the normal case and the slow one is what makes a third-party gateway feel like part of the registration flow.
