JOB TITLE OpenCart 3.x – Improve and Fix Offline Credit Card Module (Auto-Delete Card Data) JOB DESCRIPTION I am looking for an experienced OpenCart 3.x developer to improve and stabilize an existing Offline Credit Card payment module. The base module already exists and has been partially modified, but it is not fully compatible with a modern custom checkout theme. This is not a new module from scratch. The goal is to fix and harden the existing module, simplify where needed, and make it safe and reliable. CURRENT SETUP - OpenCart 3.0.x (tested on 3.0.4.0) - PHP 8.1+ - Custom frontend theme with a custom checkout (not default OpenCart checkout) - Existing Offline Credit Cards module (legacy module, already modified) - Manual card processing (no automatic charging) CURRENT PROBLEMS - Offline Credit Card payment does not work reliably with the custom checkout theme - Frontend confirm button / JavaScript flow is unstable or incompatible - Module was designed for old OpenCart default checkout - Too much frontend dependency for a manual payment method WHAT I NEED 1) Frontend behavior The developer should recommend and implement one of the following approaches, and explain clearly why: Option A (preferred and safer): - Disable card input on frontend completely - Use Offline Credit Cards as an admin/manual-only method - Customers place orders using another method (Bank Transfer, Manual Order, etc.) - Card details are handled only by admin, not entered on checkout Option B (only if feasible with custom checkout): - Make Offline Credit Cards work correctly with the custom checkout theme - Clean confirm flow - No broken JavaScript - No duplicate or stuck orders Security and PCI implications must be respected. I do not want unsafe hacks. 2) Automatic card deletion (mandatory requirement) This must be implemented: - Add admin setting: “Auto-delete card details after order status change” - Admin selects order status (default should be Shipped or Complete) - When order status changes to the selected status: - All stored card data for that order must be permanently deleted - Must use OpenCart event system (not cron jobs) - Must be compatible with PHP 8.1+ and future PHP versions 3) Code quality requirements - Clean and readable code - No hardcoded theme paths - No core file edits unless done via OCMOD - Proper use of OpenCart events such as addOrderHistory/after - PHP 8.1 / 8.2 compatible - Clear comments for important logic DELIVERABLES - Improved and working module - Installable extension package (OCMOD or extension installer) - Short documentation explaining: - How frontend behavior works - When card data is stored - When and how card data is deleted - Confirmation that no card data remains after the configured order status is reached REQUIRED EXPERIENCE - Strong experience with OpenCart 3.x - Experience with custom checkout themes - Experience fixing or modernizing legacy OpenCart extensions - Understanding of payment flows and OpenCart event system - Awareness of security and PCI best practices WHEN APPLYING, PLEASE ANSWER 1) Have you worked with Offline Credit Card or manual payment modules in OpenCart before? 2) How would you handle incompatibility with a custom checkout theme? 3) How would you implement automatic deletion of card data after order status change? 4) Which approach do you recommend (frontend or admin-only), and why?