Judicial Officer Nassir Al Nasser rejects a request for alternative service by email, mandating strict adherence to standard RDC service protocols in a multi-party banking dispute.
Why did Union Bank of India (DIFC Branch) seek permission to serve the claim form on Velocity Industries LLC and seven other defendants via email in CFI 025/2020?
The dispute arises from a banking claim initiated by the Union Bank of India (DIFC Branch) against a complex array of corporate and individual defendants, including Velocity Industries LLC, Velocity Venture Ltd, Umaku Trade Invest Limited, and five individual respondents: Vijey Kapoor, Ravi Kuchimanchi, Rajender Makhijani, Parag Gupta, and Devika Swati. The Claimant sought to bypass traditional service methods, likely due to difficulties in locating the defendants or ensuring timely receipt of the claim form, and filed an application notice on 7 June 2020 requesting the Court’s permission to effect service via email.
The Claimant’s reliance on email service suggests a strategic attempt to expedite the commencement of proceedings against the eight named defendants. However, the Court maintained a rigorous stance on procedural compliance, requiring the Claimant to demonstrate why standard methods were insufficient before granting such an extraordinary measure. As the Judicial Officer noted in the final order:
The Claimant shall serve the Defendants pursuant to the methods listed in RDC 9.2 and 9.3.
The refusal to grant the application underscores the DIFC Courts' commitment to ensuring that defendants are served through established, reliable channels that provide clear evidence of receipt, thereby protecting the integrity of the litigation process from the outset.
Which judge presided over the application for alternative service in the DIFC Court of First Instance on 16 June 2020?
The application was heard and determined by Judicial Officer Nassir Al Nasser. The order was issued within the Court of First Instance on 16 June 2020, following a review of the Claimant’s application notice dated 7 June 2020. The decision was formally issued by the Deputy Registrar, Nour Hineidi, at 2:00 PM on the same day.
What specific procedural arguments did Union Bank of India (DIFC Branch) advance to justify departing from RDC 9.2 and 9.3?
While the specific written submissions of the Claimant are not detailed in the final order, the application notice CFI-025-2020/1 sought permission to serve the claim form by email as an alternative to the standard methods prescribed by the Rules of the DIFC Courts (RDC). In the context of DIFC litigation, such applications typically rely on the argument that the defendants are either evading service, are located in jurisdictions where traditional service is prohibitively slow, or that email is the most effective means of ensuring actual notice in a modern, digital-first commercial environment.
The Claimant’s position was essentially that the Court should exercise its discretion to permit a more flexible approach to service to avoid unnecessary delays in the litigation. By contrast, the Court’s refusal indicates that the Claimant failed to meet the high threshold required to deviate from the default rules. The Court implicitly held that the convenience of the Claimant does not override the necessity of adhering to the structured service requirements set out in the RDC, which are designed to ensure that all parties are properly apprised of the claims against them through verified channels.
What was the precise jurisdictional and procedural question Judicial Officer Nassir Al Nasser had to resolve regarding the method of service?
The core question before the Judicial Officer was whether the Claimant had provided sufficient grounds to justify an order for alternative service under the RDC, specifically whether the Court should permit service by email in lieu of the methods prescribed under RDC 9.2 and 9.3. The Court had to determine if the circumstances of the case—involving a mix of corporate entities and individual defendants—warranted a departure from the standard procedural rules that govern the commencement of proceedings.
This issue touches upon the fundamental principle of due process in the DIFC. The Court had to weigh the Claimant’s interest in efficiency against the procedural safeguards inherent in the RDC. By denying the application, the Court reaffirmed that the burden rests on the applicant to demonstrate that standard service is either impossible or impracticable before the Court will authorize alternative methods, such as electronic service, which may carry a higher risk of disputes regarding the validity of service.
How did Judicial Officer Nassir Al Nasser apply the requirements of the RDC to the Claimant’s request for email service?
The Judicial Officer’s reasoning was grounded in a strict interpretation of the RDC, prioritizing the established methods of service over the Claimant’s request for digital convenience. By reviewing the application notice and the case file, the Court determined that the Claimant had not established a sufficient basis to bypass the standard protocols. The reasoning follows a clear procedural logic: the RDC provides a comprehensive framework for service, and any deviation from this framework requires a compelling justification that was absent in this instance.
The Court’s decision to deny the application serves as a reminder that the DIFC Courts will not lightly set aside the rules of procedure. The reasoning is encapsulated in the following directive:
The Claimant shall serve the Defendants pursuant to the methods listed in RDC 9.2 and 9.3.
By mandating adherence to RDC 9.2 and 9.3, the Judicial Officer ensured that the service of the claim form would be conducted in a manner that is beyond reproach, thereby preventing potential future challenges to the Court’s jurisdiction or the validity of the proceedings based on defective service.
Which specific RDC rules govern the service of a claim form in the DIFC Court of First Instance?
The primary rules governing the service of a claim form are found in Part 9 of the Rules of the DIFC Courts (RDC). Specifically, RDC 9.2 and 9.3 outline the standard methods by which a claim form must be served on a defendant. These rules are designed to ensure that service is effected in a way that provides the defendant with a fair opportunity to respond to the claim.
RDC 9.2 typically details the methods for serving individuals, while RDC 9.3 addresses the service of documents on companies and other corporate entities. These rules are mandatory, and any attempt to use alternative methods, such as email, requires an express order from the Court, which is only granted when the applicant can demonstrate that the standard methods are not viable.
How does the decision in Union Bank of India v Velocity Industries align with previous DIFC Court rulings on alternative service?
The decision aligns with the consistent approach of the DIFC Courts in maintaining the integrity of service requirements. While the DIFC Courts have, in other instances, permitted alternative service where it is shown that the defendant is actively evading service or where traditional methods have been exhausted, this case reinforces the principle that such permission is not a default option.
The Court’s reliance on the standard RDC provisions reflects a broader judicial philosophy that procedural rules are not merely suggestions but are essential for the orderly administration of justice. By requiring the Claimant to follow RDC 9.2 and 9.3, the Court maintained consistency with the principle that the burden of proof for alternative service lies squarely with the party seeking the departure. This ensures that the Court does not inadvertently facilitate service that could later be challenged as ineffective or unfair.
What was the final disposition of the application filed by Union Bank of India (DIFC Branch) on 7 June 2020?
The application was denied in its entirety. Judicial Officer Nassir Al Nasser issued a formal order on 16 June 2020, which explicitly stated that the Claimant’s request for permission to serve the claim form by email was rejected. The Court ordered the Claimant to proceed with service using the standard methods prescribed under RDC 9.2 and 9.3. Furthermore, the Court made no order as to costs, meaning each party was left to bear their own legal expenses associated with the application.
What are the practical implications for practitioners seeking to serve claim forms via email in the DIFC?
Practitioners must recognize that the DIFC Courts maintain a high threshold for granting permission for alternative service. The denial of the application in this case serves as a clear warning that practitioners should not assume that email service will be permitted simply because it is more efficient or cost-effective.
Before filing an application for alternative service, practitioners should ensure they have exhausted all standard methods of service under RDC 9.2 and 9.3 and have documented their efforts thoroughly. Any application for alternative service must be supported by robust evidence demonstrating why standard methods are ineffective. Failure to provide such evidence will likely result in the application being denied, leading to unnecessary delays and additional costs for the client.
Where can I read the full judgment in Union Bank of India v Velocity Industries [2020] DIFC CFI 025?
The full text of the order can be accessed via the official DIFC Courts website: https://www.difccourts.ae/rules-decisions/judgments-orders/court-first-instance/cfi-025-2020-union-bank-india-difc-branch-v-1-velocity-industries-llc-2-velocity-venture-ltd-3-umaku-trade-invest-limited-4-vije-4 or via the CDN link: https://littdb.sfo2.cdn.digitaloceanspaces.com/litt/AE/DIFC/judgments/court-first-instance/DIFC_CFI-025-2020_20200616.txt.
Cases referred to in this judgment:
| Case | Citation | How used |
|---|---|---|
| N/A | N/A | No cases were cited in this order. |
Legislation referenced:
- Rules of the DIFC Courts (RDC) 9.2
- Rules of the DIFC Courts (RDC) 9.3