Fix Bugs in an Ecommerce website based on PHP
Budget: ₹600 – ₹1,500 INR
My e-commerce site, socioblend.com, is suffering on two fronts. With PayU Money I’m seeing repeated transactions from the same user who is clearly cycling through stolen cards. At the moment I have zero safeguards in place—no CAPTCHA, no AVS, nothing—so fraudulent payments slip straight through. I need robust prevention put in place (reCAPTCHA, AVS, 3-D Secure or any proven alternative you recommend), followed by a round of testing to be sure legitimate customers can still pay without friction.
Stripe presents the opposite problem: checkout crawls. The payment page drags, submission hangs, and customers abandon carts. I want the integration audited, bottlenecks identified, and the code or server tweaks applied so the entire flow feels snappy on desktop and mobile.
Deliverables
• PayU Money hardening: implement real-time fraud checks, deploy visual/behavioral CAPTCHA, and confirm declined stolen-card attempts are logged.
• Stripe optimisation: profile the existing code, resolve slow scripts/API calls, and verify normal checkout time is back to industry standard.
• End-to-end tests: run sample transactions for both gateways, share before/after metrics, and hand over concise implementation notes so future updates stay secure and fast.
You’ll be working on a live production store, so changes must be staged, carefully tested, and rolled out with minimal downtime.
Stripe presents the opposite problem: checkout crawls. The payment page drags, submission hangs, and customers abandon carts. I want the integration audited, bottlenecks identified, and the code or server tweaks applied so the entire flow feels snappy on desktop and mobile.
Deliverables
• PayU Money hardening: implement real-time fraud checks, deploy visual/behavioral CAPTCHA, and confirm declined stolen-card attempts are logged.
• Stripe optimisation: profile the existing code, resolve slow scripts/API calls, and verify normal checkout time is back to industry standard.
• End-to-end tests: run sample transactions for both gateways, share before/after metrics, and hand over concise implementation notes so future updates stay secure and fast.
You’ll be working on a live production store, so changes must be staged, carefully tested, and rolled out with minimal downtime.