DB-PRO.ONLINE
Software Development & IT Services • Official Communication • Email: mebishnusahu0595@gmail.com
⚠ PLATFORM & SERVICES TEMPORARILY SUSPENDED

The web portal, customer mobile application, administrative panels, and backend API services for Drevowheels have been suspended due to persistent non-payment of outstanding software development charges.

Addressed To: Mr. Hupesh Sahu — Drevowheels (Sahu Car Rental)
Client Email: drevowheels@gmail.com
Issued By: DB-PRO.ONLINE (DB Pro Online) • Bishnu Sahu <mebishnusahu0595@gmail.com>
Notice Date: Sat, Oct 24, 2026 • Formal Final Demand
Current Status: SERVICE SUSPENSION & ADMINISTRATIVE HOLD
Formal Notice Regarding Outstanding Payment of ₹50,000, Project Status, and Terms for Further Development
Dear Mr. Hupesh Sahu,

This notice is being issued on behalf of DB-PRO.ONLINE (DB Pro Online) concerning the Drevowheels (Sahu Car Rental) software development project.

Please treat this as a formal final payment demand and written notice concerning the outstanding dues of ₹50,000, project delays, suspension of further development and hosting services, and potential legal proceedings for recovery of the unpaid amount.

We have made repeated attempts over the past several months to resolve this matter through calls, messages, and discussions. However, the outstanding payment remains unpaid, and the same issues continue without a clear resolution of the payment dispute.

We have invested substantial time, technical resources, and development effort into this project. We cannot continue indefinitely with unpaid development work, repeated revisions, third-party API expenses, and delays caused by missing information or incomplete testing from your side.

To prevent any further misunderstanding, we are setting out the relevant facts, payment records, project dependencies, and conditions for resolution below:

1. Project Details and Agreed Financial Terms

The project was undertaken for Drevowheels (Sahu Car Rental), with the development requirements discussed and communicated between both parties. The agreed development fee was ₹60,000, with a separate ₹10,000 allocation for server and domain expenses.

The payment position recorded by our company is as follows:

Description Amount (INR)
Software development charges ₹60,000
Server and domain expenses ₹10,000
Total project cost ₹70,000
Development advance received ₹10,000
Server/domain payment received ₹10,000
Total payments received ₹20,000
OUTSTANDING BALANCE DUE ₹50,000

Accordingly, ₹50,000 remains outstanding against the total project cost of ₹70,000.

The agreed scope included the customer booking application, vendor application, admin panel, super admin panel, website and associated backend functionality, together with the agreed integrations and features.

We request that you acknowledge the above payment position or provide a specific written explanation with supporting transaction records if you disagree with any amount. Further requests for modifications do not, by themselves, settle or remove the outstanding payment obligation.

2. Development Work Completed and Application Published

Our company has invested several months in implementing the requirements communicated during the engagement. The principal development components have been built, and the application has also been published on the Google Play Store.

We have worked on the application, backend functionality, administrative interfaces, booking functionality, and other agreed components. We have also addressed feedback and made changes during the development process.

We therefore do not accept a blanket statement that no work has been completed without reference to the actual implementation, the published application, the project records, and the agreed deliverables.

Our position is that the agreed development work has been substantially completed to the extent possible with the requirements, information, access, and cooperation supplied. Any specific item genuinely remaining within the original agreed scope must be identified clearly and reviewed against the documented requirements.

In particular, work dependent on your GST/business details, valid third-party API information, or other inputs from your side cannot be completed without those necessary inputs.

The distinction between work already implemented, work blocked by missing information, and new requirements introduced after development is essential to resolving this dispute fairly.

3. Repeated Design Changes and AI-Generated Reference Images

During development, you have repeatedly sent AI-generated images and visual references and asked us to reproduce the designs or reposition elements to match those references.

We have considered the feedback provided and have attempted to implement the requirements communicated by you. However, an AI-generated image is a visual reference, not necessarily a complete technical specification. Translating such an image into a working production application can require additional design decisions, responsive layouts, frontend implementation, backend adjustments, testing, and technical changes.

Repeatedly replacing designs, changing layouts, moving interface elements, and introducing new visual expectations after earlier work has already been implemented creates additional development effort.

The project cannot reasonably be treated as an unlimited-revision engagement in which every newly generated reference automatically becomes an included requirement, irrespective of the agreed scope or outstanding payment.

We have fulfilled the requirements communicated to us within the work undertaken and the agreed scope, subject to dependencies and specific items that require clarification. If you believe a particular agreed feature has not been delivered, please identify the exact feature, explain the technical issue, and provide the relevant screen or steps to reproduce it.

General statements that the work is incomplete, without identifying a specific discrepancy in the agreed deliverables, do not provide a clear basis for further development or indefinite postponement of payment. Any substantial redesign, additional feature, or requirement outside the original agreement will need to be evaluated separately and approved in writing, including its cost and timeline.

4. Application Testing and Limited Review Over Approximately Five Months

The application was made available for testing approximately five months ago. Throughout this period, we expected the application to be reviewed, tested using realistic information, and assessed against the agreed requirements.

However, based on our observations and communications, testing and review from your side have not progressed consistently enough to establish a comprehensive list of specific outstanding issues.

Our understanding is that you personally opened or reviewed the application only approximately five or six times during the relevant period. We also understand that the addition of actual vehicle listings was delayed, with only three cars added very recently.

This limited review and late availability of realistic vehicle information made it more difficult to obtain meaningful feedback based on normal operating conditions. A software project requires timely testing and cooperation from both parties. The development team cannot be expected to identify every client-specific content issue, operational preference, or requirement that is not communicated during testing.

Where an application has been made available for review, the client is expected to examine it properly, test the agreed functionality, report specific issues, and provide the information necessary to resolve them.

We have spent considerable time waiting for feedback and attempting to address changing requirements. We cannot reasonably accept responsibility for the entire project delay when the application was available for review and necessary information and testing inputs were not supplied in a timely manner. If you dispute this account, please identify the particular testing activity, date, feature, and issue on which you rely, and provide the corresponding records in writing.

5. Real Vehicle Listings and Operational Readiness

For a car rental platform, actual vehicle listings and accurate vehicle information are essential for meaningful operational testing. We had requested that real car details be added so that the booking flow and related functionality could be evaluated with realistic inventory.

However, the addition of actual vehicle listings was delayed, and only three cars were added recently, according to our current understanding. The absence of realistic listings for an extended period limited the ability to validate the complete booking experience using the intended operational data.

Please understand that developing a platform and supplying its ongoing business inventory are separate responsibilities unless expressly agreed otherwise. The client must provide accurate vehicle details, photos, availability, pricing, and any other required business information where those items are the client's responsibility.

We have developed the relevant software functionality, but we cannot substitute for missing business information or independently assume responsibility for vehicle data that must be confirmed by the business owner.

We are willing to review specific, legitimate software defects against the original scope once the payment issue and the applicable testing requirements have been documented.

6. Payment Gateway Delay Caused by Missing GST/Business Information

For approximately the last three months, we have requested your GST registration number and relevant business details required for the payment gateway onboarding process. Despite repeated requests, the required information was not supplied to us in a timely manner.

Payment gateway providers may require merchant verification, business information, tax details, and supporting documentation before enabling payment processing. Without the relevant information, we could not complete the onboarding steps that depended on it. Consequently, the payment gateway integration could not be finalized as planned.

It is not reasonable to attribute the entirety of this delay to our development team while ignoring the absence of the information repeatedly requested from your side. We cannot submit accurate merchant verification information on your behalf without the necessary details and authorization.

If payment gateway integration remains outstanding, please provide the required business information through an appropriate secure channel after the outstanding payment arrangement has been resolved. Any remaining implementation work and timeline must then be confirmed in writing.

7. Vehicle-Tracking API: Missing Endpoint and Technical Documentation

You also provided API-related information intended for vehicle tracking. However, the information made available to us contained a placeholder displayed as URL, rather than a usable endpoint or complete integration details. The actual link and sufficient technical information were not provided despite our attempts to obtain clarification.

An API integration requires valid technical inputs, which may include the actual endpoint, API documentation, authentication credentials, request and response formats, and access permissions. A placeholder is not a functional endpoint. We cannot reliably complete or test the vehicle-tracking integration using incomplete information.

We have attempted to communicate about the missing details, but the required clarification has not been provided adequately. Any delay attributable to missing API endpoints, credentials, documentation, or access from your side cannot reasonably be represented as a failure by our development team to complete work that depends upon those inputs.

Please provide the actual endpoint and relevant documentation if you wish to proceed with this integration. Any additional or out-of-scope work will require written approval of the associated charges and timeline.

8. API Billing and Additional Third-Party Expenses

In addition to software development and server/domain expenses, API services and related technical resources have been configured or used through accounts maintained by our company for this project. These services may generate usage-based or subscription charges, including during periods in which the project is delayed or awaiting client information.

Our company cannot indefinitely bear third-party API expenses from its own funds while the agreed project payment remains unpaid.

We will retain the relevant billing records and provide an itemized statement, with supporting invoices or account records, for additional API expenses that are attributable to the project and properly chargeable under the applicable agreement.

For clarity, these additional costs will be identified separately from the existing ₹50,000 outstanding project balance. They will not be added to that balance without an appropriate basis and supporting records. No further discretionary API expenditure will be undertaken for the project after suspension unless separately approved in writing. Existing services will be managed in accordance with the relevant provider terms, contractual rights, and applicable law.

9. Calls, Meetings, and Required Written Communication

We have attempted to discuss the outstanding payment and project status through telephone calls and meetings. However, these conversations have not resulted in a clear, documented resolution.

During these discussions, the conversation has repeatedly moved away from the specific payment issue or returned to general claims that work has not been completed, without a precise written identification of the alleged defects or outstanding requirements. On certain occasions, updates or issues presented for discussion have already been implemented in the live application. Repeating an issue that has already been addressed without first checking the current live version creates unnecessary confusion and further delays.

We also need a reliable written record of the requirements, requests, commitments, and payment discussions. Verbal conversations alone are not sufficient to establish exactly what was agreed or what remains disputed.

Therefore, all further communication concerning this payment dispute, project closure, outstanding requirements, or any proposed settlement must be made by replying directly in writing via email.

We will not be taking telephone calls or arranging in-person meetings to discuss this dispute. Please do not rely on calls or verbal assurances as a substitute for a written response.

Any genuine concern about a deliverable must be documented in your email reply, specifying the exact feature, the issue observed, whether it is part of the original agreed scope, and the evidence needed to reproduce it. This requirement is intended to ensure that both parties have a clear, objective, and verifiable record and that the matter does not continue indefinitely through repeated discussions without resolution.

10. Outstanding Payment and Final Settlement Proposal

Our records show that ₹50,000 remains outstanding against the agreed total project cost of ₹70,000.

To resolve this matter without further escalation, we are giving you a final opportunity to settle the issue using the following payment arrangement:

Any further development will require the agreed initial payment to have been received and the precise scope of the remaining work to have been documented. If any amount in the payment statement is disputed, you must provide a specific written explanation and supporting records within the same deadline. Requests for further updates, verbal assurances, or promises of payment at a later stage will not constitute settlement of the outstanding amount.

11. Final Seven-Day Deadline and Suspension of Further Services

You are hereby requested to resolve the payment matter within seven calendar days of this notice.

If the required initial payment of ₹40,000 is not received within that period, and no mutually agreed written settlement is reached, we will suspend further development, additional revisions, new integrations, and non-contractual support.

Subject to the applicable agreement and law, we also reserve the right to suspend or discontinue services maintained by our company where we are contractually entitled to do so. Any suspension or closure of live hosting, software services, or integrations will be carried out in accordance with our contractual rights, applicable legal requirements, and obligations regarding data, access, and service continuity.

We will not treat this notice as authorization to delete customer data or take unauthorized action against client-controlled or third-party systems. You should therefore arrange any necessary backups, continuity measures, or migration for services under your control before the deadline.

If the matter remains unresolved after seven days, we will not continue providing unpaid development effort or indefinitely extending the project without a clear payment arrangement.

12. Refund and Server/Domain Expenses

The separate ₹10,000 received for server and domain expenses relates to infrastructure and services arranged or committed for this project. These expenses have been incurred or committed over the relevant period and are separate from the software development charges.

Accordingly, the amount is not treated as a refundable development advance. Any claim for a refund will be assessed against the actual costs incurred, services supplied, applicable contractual terms, and applicable law. Any additional API usage, renewal charges, or third-party costs will be supported by relevant records and dealt with separately in accordance with the applicable terms.

13. Formal Notice of Potential Legal Action

Our company has already invested significant technical effort, staff time, development resources, and third-party expenditure in this engagement. The prolonged non-payment, repeated follow-ups, lack of required information, and inability to obtain a documented resolution have caused substantial disruption to our work and business operations.

We have attempted to resolve the situation professionally. However, we cannot continue carrying the financial burden of a project for which a substantial agreed payment remains outstanding.

If the outstanding payment is not resolved within seven calendar days, we intend to take appropriate legal steps to recover the unpaid amount, without further telephone reminders or informal meetings.

Depending on the contractual terms, available evidence, and advice from our legal counsel, these steps may include:

Our position will be supported by relevant records, including payment details, project communications, the application publication record, development history, requests for GST/business information, API communications, and substantiated third-party billing records. We will rely on verifiable facts and applicable contractual obligations in pursuing any lawful remedy.

All rights and remedies available to DB-PRO.ONLINE under the applicable agreement and law are expressly reserved.

14. Written Response Required

Please reply directly via email to mebishnusahu0595@gmail.com within seven calendar days and confirm:

Any disagreement must be stated clearly and supported by relevant information. General statements that no work has been done, without identifying the disputed deliverables or addressing the payment records, will not provide a sufficient basis for resolving the matter.

We remain willing to resolve this dispute professionally and without unnecessary escalation. However, this requires timely payment, clear written communication, and cooperation from both parties.

Please take this as our final opportunity to resolve the outstanding payment matter amicably before we proceed with the appropriate legal process.

We expect your written response by replying directly via email within the seven-calendar-day period.