BJ BJ Cyber.

Engagement Status: Open

I build the site.
Then I break into it
before anyone else does.

BJ Cyber Solutions delivers security audits, penetration testing, and secure web development for businesses that can't afford to find out about a vulnerability the hard way.

Sample scan · gentlesoulglobalenterprises.com
  • TLS / HTTPS enforced
  • Payments verified server-side
  • Service-role keys never exposed client-side
  • Row-level access control on all client data

Full case file below ↓

CCNA — in progress HND, Networking & Cloud Computing Full-stack + Paystack integration Based in Abuja, Nigeria

Services

Three engagement types. One goal — you're not the weak link.

CASE FILE 01

Security Audits

A full review of your existing site, app, or infrastructure — misconfigurations, exposed keys, weak access control, outdated dependencies. You get a plain-language report, ranked by real risk, not jargon.

  • → Configuration & access review
  • → Dependency & exposure check
  • → Ranked findings report
CASE FILE 02

Penetration Testing

I try to break in — the way an attacker would. Authentication, payment flows, admin panels, APIs. You find out where the door was unlocked before someone else walks through it.

  • → Auth & session testing
  • → Payment & API flow testing
  • → Retest after fixes, included
CASE FILE 03

Secure Web Development

Your site or store, built from scratch with security as a default, not an afterthought — server-side payment verification, proper access control, and no secrets sitting in your frontend code.

  • → Tailwind / vanilla JS or React
  • → Supabase + Paystack integration
  • → Deployed, tested, documented

Case File — Closed

GentleSoul Global Enterprises — e-commerce, secured end to end

A frozen foods retailer in Abuja needed a full e-commerce build: live product catalogue, cart, delivery pricing by location, and Paystack checkout — without giving up control of what happens after a customer pays.

The risk with most fast-built stores: payment "verification" happens in the browser, which means it can be faked. I built a serverless verification layer instead — every payment is confirmed server-side with Paystack before an order is ever written to the database, and the database write itself uses a service-role key that never touches the client.

Get this for your business →

Risk found

Client-side payment writes are forgeable

Fix shipped

Server-side Paystack verification before any order is saved

Also hardened

Admin panel access, dual email notifications, secrets kept server-only

Status

Live in production

About

Bonzer Jay

Freelance developer and cybersecurity consultant based in Abuja, Nigeria. I build the systems and I test them — most people only offer one of the two.

2026

Pursuing CCNA certification, building on networking fundamentals from an HND in Networking & Cloud Computing at Ogun State Institute of Technology, Igbesa.

Ongoing

Building and maintaining production e-commerce systems — Tailwind, vanilla JS, Supabase, and Paystack — with a security-first approach to payments and access control.

Approach

Plain-language reports, not jargon. You'll know exactly what was found, why it matters, and what to do about it.

Open a case file

Tell me what you're worried about.

A short message is enough to start — what you have, what you're building, or what you're not sure is safe.

Send a message
bjcybersolutions@gmail.com · Abuja, Nigeria