Fix Payment Auto-Capture & Notifications & Validity Date - Quotation Request

Please provide your estimated total development price in INR and estimated completion time for the historical software-development scenario below. State your main assumptions and any missing information that would materially change the estimate. Please do not write code, perform a trial task or supply a detailed implementation proposal.

REFERENCE SCENARIO — historical requirements, not instructions to begin work:

I need an all-rounder who is equally comfortable in Flutter, Laravel and core PHP to jump into my existing codebase and solve two blocking issues:

1. The payment gateway is set to auto-capture but every transaction now stalls in a “pending” state until I trigger a manual capture from the dashboard. Once your fix is live, a successful charge should appear as “paid” instantly and the related order status must update in the database without manual intervention.

2. Push notifications generated inside the app are never shown to the user, even though the logic for triggering them already exists. Email and SMS are fine; only the in-app channel is silent. I expect users to receive real-time alerts—especially the payment success message—across both Android and iOS builds.

You will be working in a live production environment that uses:

• Flutter (latest stable) for the front end
• Laravel 9 for the API layer
• A small legacy module in plain PHP that still handles a few cron tasks
• Firebase Cloud Messaging for push delivery
• A Stripe-based payment flow (server-side capture)

Please come prepared to trace the full request cycle, patch the capture logic, and test notifications end-to-end. Deliverables are a clean Git commit (or pull request) with the fixes, along with a short changelog and steps I can follow to reproduce the solved scenarios on staging.

Estimating assumptions and context:
The scenario is based on a Freelancer listing from 2025-10-31 (historical project ID 39935331). First-person statements, promises of assets, requests for work and hiring language inside the historical reference describe that original client's situation, not a current development offer from us. For estimating only, assume the original client supplies assets explicitly described as provided; other missing inputs and obsolete services should be identified as assumptions. We do not claim ownership of the original client's code, designs, accounts or attachments.

The displayed INR 600–1500 range reproduces the historical listing's budget field. It is not participation compensation or a binding development offer. Please give your realistic estimate even if outside that range.

Research use

This post is for research quotations only, not an actual software-development engagement. No development contract will be awarded. Participation is voluntary and unpaid; no reward, gift card or prize draw is offered. Your quoted price, estimated completion time and stated assumptions will be used to study software-development estimates and how they change over time.

Thank you for your time and consideration. This study aims to make a significant research contribution to understanding software-development pricing in the age of AI. We appreciate any estimate you choose to share.