SnugFit WooCommerce Plugin
Bridging 3D foot scanning to WooCommerce orders, with applied cryptography.
- Role
- Sole author
- Period
- Jan 2025 – Jan 2025
- Status
- Shipped
- Stack
- PHP, WooCommerce.
9
Custom PHP files
~1,261
Lines of code
RSA-OAEP
SHA-256 scan-link encryption
The problem
SnugFit's 3D foot-scanning service needed to hand off scan results into a WooCommerce order so a customer's scanned measurements could drive a product configuration at checkout, without exposing the scan link to tampering.
Constraints
- Scan links needed to be encrypted in transit between SnugFit's scanning flow and the WooCommerce order.
- The plugin had to work with WooCommerce's newer High-Performance Order Storage (HPOS) and block-based checkout, not just the legacy checkout.
What I built
A WordPress/WooCommerce plugin across 9 custom PHP files and roughly 1,261 lines, using phpseclib v3 for RSA-OAEP SHA-256 encryption of scan links, with product-level scan configuration and compatibility with WooCommerce's HPOS and block-checkout.
Architecture
A dedicated Crypto class wraps RSA-OAEP SHA-256 encryption and decryption of scan-link payloads, keeping the cryptographic surface in one place rather than scattered across the plugin's hooks and handlers.
Decisions and tradeoffs
Decision
Encrypt scan links with RSA-OAEP SHA-256 rather than passing them as plain query parameters.
Because
A scan link ties a customer's 3D measurement data to an order, and that link needed to resist tampering or replay in transit.
Trade-off
Every scan-link handoff now carries encryption/decryption overhead and key-management responsibility that a plain URL parameter would not.
Outcome
- Custom PHP files
- 9
- Lines of code
- ~1,261
As of 2026-08-24
Small in scope, but the only PHP and the only applied-cryptography work in this history — it adds credible range beyond the Next.js/Postgres stack that dominates the rest of the portfolio.
Related work
Want the full picture, or open to talking about your own project?