Legacy .NET Subscription System Enhancements
Budget: $8 – $15 USD
Our ten-year-old ASP.NET site drives institutional subscriptions to our publications, granting access by recognised IP ranges and handling one-off PDF sales. The code base still runs on an older .NET Framework, yet we plan to modernise gradually once the critical issues below are under control.
Immediate focus
• Strengthen billing and payment processing, wiring PayPal into the existing workflow and ensuring transactions post back correctly.
• Tighten access control: refine the IP-recognition logic that unlocks content for authorised subscribers and blocks everyone else.
• Clean up every customer-facing email and on-screen message generated during purchases, renewals and failed attempts.
• Smooth the one-time PDF purchase flow so that a successful PayPal payment instantly activates the download.
Deliverables for this phase
1. Technical review and implementation plan outlining code changes, database adjustments and rollout steps.
2. Incremental commits that introduce the new PayPal endpoints, replace or refactor the IP gatekeeping classes, and update message templates.
3. Short test script demonstrating that subscriptions, renewals and one-time sales all complete from payment through content delivery without regression.
Once these items are stable in production we can map out the larger migration path toward a newer .NET version while continuing with incremental enhancements.
Access to the current repository, staging server and some legacy documentation will be provided. Clear commit history, straightforward communication and a reasonable hourly rate are essential as the intention is to establish a long-term working relationship on this platform.
Immediate focus
• Strengthen billing and payment processing, wiring PayPal into the existing workflow and ensuring transactions post back correctly.
• Tighten access control: refine the IP-recognition logic that unlocks content for authorised subscribers and blocks everyone else.
• Clean up every customer-facing email and on-screen message generated during purchases, renewals and failed attempts.
• Smooth the one-time PDF purchase flow so that a successful PayPal payment instantly activates the download.
Deliverables for this phase
1. Technical review and implementation plan outlining code changes, database adjustments and rollout steps.
2. Incremental commits that introduce the new PayPal endpoints, replace or refactor the IP gatekeeping classes, and update message templates.
3. Short test script demonstrating that subscriptions, renewals and one-time sales all complete from payment through content delivery without regression.
Once these items are stable in production we can map out the larger migration path toward a newer .NET version while continuing with incremental enhancements.
Access to the current repository, staging server and some legacy documentation will be provided. Clear commit history, straightforward communication and a reasonable hourly rate are essential as the intention is to establish a long-term working relationship on this platform.
Related categories:
PHP
ASP
.NET
Website Design
PayPal API
Software Development
ASP.NET
Web Development
Database Management
Payment Processing