Complete Members is built to be secure by default, but a launch is only as safe as the steps you take around it. Run through this checklist before you take your first real payment.
What's already protecting you
Out of the box, every form is CSRF-protected, sessions are hardened and database-backed, admin accounts support two-step verification and roles, and there is rate limiting and login throttling. Secrets are encrypted at rest with libsodium, the site API is signed and replay-protected, and a strict Content-Security-Policy and security headers are set. Uploads are checked by content type and images are re-encoded, and an allowlist sanitiser cleans any HTML. An audit log records admin actions.
Your pre-launch checklist
- Delete
install.phpfrom the hub once the install wizard has finished. - HTTPS everywhere - on the hub and on every site domain. Card pages and signed APIs assume it.
- Turn on two-step verification for the owner account (Account → 2FA), and for any other admins.
- Finish real billing tests for each processor, then switch Test mode off. See Test your billing before you go live.
- Publish your legal pages - terms, privacy, and for adult sites the 2257 statement and a complaints/takedown route.
- Set the cron job so memberships expire, commissions approve and postbacks flush on time.
- Keep your Installation Key and API key private; the hub stores the API key masked.
If you intend to advertise strong security, consider an independent penetration test before launch. The platform gives you the controls; a test gives you - and your customers - the assurance.
After launch
Watch the payment log and the audit log for the first days. Keep the hub updated - database upgrades apply themselves on the next admin page load, and you never overwrite config/config.php, config/service.php, config/installed.lock or the storage/ folder when you upload new files.
Secure, live and taking payments - that's the whole stack running on your own hosting. If you're still setting up, go back to installing the hub.
Frequently asked questions
What security is built in?
CSRF protection on every form, hardened sessions, admin two-step verification and roles, rate limiting, an audit log, encrypted secrets at rest, replay-protected signed APIs and a strict Content-Security-Policy.
What must I do myself before launch?
Turn on HTTPS everywhere, enable 2FA on the owner account, delete install.php, finish real billing tests, and publish your legal pages (terms, privacy, 2257 and complaints).
