Tools
Four browser-based tools covering the steps that are easiest to get wrong by hand: signing a payment request, assessing data-protection readiness, structuring a prompt and fixing common website problems.
Quick answer
All four run entirely in your browser. Nothing is transmitted, nothing is stored and none of them asks for an account or a real credential. Each one links to the guides that explain the concepts behind it, because a generator is only useful to someone who can check what it produced.
The tools
PayFast Webhook Code Generator
Produces the checkout-signing and ITN-verification functions for your platform and environment, with the field order and PHP-style encoding that PayFast's own server expects.
POPIA Compliance Checker
A readiness checklist for any app built with AI: where its data is stored and sent, your written agreements, your app controls and your Information Officer. Never a pass or fail badge.
Custom Prompt Builder
Describe your task in your own words and get a prompt with clear limits for your AI, plus a list of what to check in its answer.
Website Prompt Generator
Ready-made prompts for 10 common website fixes, from page titles and alt text to secret keys and cookie consent, written for where you work with AI.
Why every tool links back to a guide
A tool that hands you a result you cannot evaluate puts you exactly where an AI builder does when it writes code you cannot check. That is the problem this site exists to solve, so reproducing it in tool form would be self-defeating. Each of these four carries the reasoning on the page beside it and links to the guides that cover the concepts in full, and none of them is a substitute for reading those guides once.
The practical test is whether you could spot a wrong answer. If the PayFast generator produced a signature function with the fields in the wrong order, you should be able to tell, and the guide beside it is what makes that possible.
Why nothing is sent to a server
Two of these tools touch material you should never paste into someone else's form: payment integration details and a description of what personal information your application collects. Building them client-side is the only design that makes that safe by construction rather than by promise. There is no endpoint to trust, no log to leak and no account to breach, because the tool never leaves the browser tab it runs in.
It also means the tools work offline once the page has loaded, and that closing the tab is a complete reset. Nothing carries between sessions.
What these tools deliberately do not do
None of them makes a judgement that belongs to you. The PayFast generator produces a correct starting point, not a production integration: order matching, failure handling and what a customer sees next are specific to your data model. The POPIA checker maps readiness against a checklist and states plainly that compliance is a question about your conduct, not your configuration. The prompt builder structures your own words and will happily assemble a vague prompt out of vague input, because it cannot know what you actually meant. The website prompt generator gives your AI a checked standard and firm limits, but it can't see your site, so the AI's report is still yours to read before you say go.
Not affiliated with the platforms we write about
AI Build South Africa is an independent resource. We're not endorsed by, or an official partner of, PayFast, Supabase, Base44, Lovable, Bolt.new, Anthropic or any other platform named on this Site. We do participate in affiliate and referral programmes with some of these providers, including Base44. Generated code and tool output are a starting point, not a drop-in production integration, and nothing here is legal advice. See our Disclaimer for the full disclosure and our Terms of Service for the wider terms.
Frequently asked questions
Do these tools send anything to a server?
No. All four run entirely in your browser as plain JavaScript. Nothing you type or select is transmitted, logged or stored, and none of them requires an account. Close the tab and the state is gone.
Does the PayFast generator need my real merchant credentials?
No, and it never asks. The code it produces reads your merchant ID, key and passphrase from environment variables or your platform's secrets manager at runtime, so a real credential never has to be typed into a browser form or committed into source code.
Can a tool tell me whether my app is POPIA compliant?
No tool can, and the POPIA Compliance Checker deliberately never claims to. POPIA regulates your conduct as the responsible party, not a checkbox state captured at one moment. The tool returns a three-part readiness readout naming confirmed steps and remaining gaps instead of a pass or fail badge.
Do the tools replace the guides they came from?
No. Each tool exists to make one guide's concept concrete, and every tool links back to the guide that explains it. A generator you can use without understanding what it produced puts you in the same position as an AI writing code you cannot check, which is the problem this site exists to solve.
Related reading
- How to Add a Payment Gateway to Your AI-Built Website: why the checks the webhook generator writes run on your server, not in the browser.
- Supabase & POPIA Compliance: the reasoning the readiness checklist is built on.
- Writing Prompts AI Coding Agents Understand: why the three-part prompt structure works.