Positive Pay System (PPS) in M&A Transactions: Rethinking PDC-Based Security and Section 138 Enforcement

Across share acquisitions, business transfers, slump sales, and asset acquisitions, securing deferred purchase consideration is one of the most heavily negotiated points between Purchaser and Seller.

Three mechanisms dominate in practice: Bank Guarantees (BGs), Escrow arrangements, and Post-Dated Cheques (PDCs) layered with electronic transfers (RTGS/NEFT).

Each secures the Seller differently, and each imposes a different cost on the Purchaser. Bank Guarantees and Escrow both tie up the Purchaser's credit or cash upfront; Post-Dated Cheques are capital-efficient for the Purchaser but depend on cheque-clearing mechanics working correctly when the Seller actually needs to rely on them.

The Reserve Bank of India's (RBI) Positive Pay System, rolled out under the Cheque Truncation System (CTS) with effect from 1 January 2021, has materially changed that third mechanism's mechanics, and it does so identically regardless of deal structure.

Without documentation that anticipates the Positive Pay System, a Seller in any of these transaction types risks a high-value security cheque being returned unpaid on a technical ground, and then having to argue — rather than simply rely on the fact — that this still amounts to dishonour under Section 138 of the Negotiable Instruments Act, 1881 ("NI Act").

1. Why Positive Pay System Matters in M&A Transactions

Post-Dated Cheques (PDCs) remain an attractive security mechanism in M&A transactions because they provide the Seller with a readily presentable payment instrument without the cost, collateral requirements or credit-line impact typically associated with a Bank Guarantee.

For example, consider a share acquisition where the Purchaser is required to pay 60% of the purchase consideration at Closing and the remaining 40% in two deferred tranches. The Purchaser issues PDCs for the deferred tranches, with the Seller entitled to present the relevant cheque if the corresponding electronic payment is not received by the agreed due date. If the Purchaser has failed to complete the applicable Positive Pay formalities, the cheque may be returned unpaid when presented. This can create an additional enforcement issue for the Seller: while the cheque has been returned unpaid, the precise application of Section 138 of the Negotiable Instruments Act, 1881 to a return specifically attributable to non-compliance with Positive Pay requirements remains an unsettled question.

That is exactly why PPS deserves attention regardless of which Transaction Agreement is used. A cheque used to secure deferred consideration is subject to the same PPS registration requirement as any other high-value cheque, and a Purchaser who wants to create friction at the point of encashment has the same opportunity to do so whether the deal is a share sale, a business transfer, or an asset purchase. Deal counsel drafting for one structure and assuming the risk doesn't apply to another is a gap worth closing across a firm's precedent bank, not just in one template.

2. How Positive Pay System Changes Cheque-Based Security

Under the Positive Pay System, the issuer of a cheque must pre-register the instrument's essential details like cheque number, date, payee name, account number and exact amount with the issuing bank, electronically or by formal letter, before the cheque is presented for payment.

The thresholds are less uniform than commonly assumed. RBI's governing circular required banks to enable Positive Pay confirmation for any cheque of INR 50,000 or more at the account holder's option, and separately permitted banks to make it mandatory for cheques of INR 5,00,000 and above. Most banks like SBI, PNB and several private banks among them have exercised that discretion and made registration compulsory at INR 5 lakh (some at lower values), and RBI's CTS dispute-resolution grid will not entertain a claim on an unregistered instrument. For deal structuring, the practical point is that the exact mandatory threshold is bank-specific, not a single RBI-wide figure, it should be confirmed against the Purchaser's actual bank, not assumed from a template.

The loophole for Purchasers. If a Purchaser issues PDCs as tranche security but declines to register the instrument details under the Positive Pay System, the clearing bank will return the cheque on presentation, typically with a return memo citing a reason distinct from "insufficient funds," commonly worded as "Positive Pay details not available" or "not confirmed under Positive Pay," rather than the classic "refer to drawer" language. This risk exists for a Purchaser under any deal structure that uses PDC-based security, not just one type of transaction.

No court has yet issued a ruling dealing specifically with a cheque returned solely for a Positive Pay–related reason; the point remains genuinely open. A Purchaser facing a Section 138 complaint on these facts may argue that such a return is not "insufficiency of funds" or "exceeding the arrangement" within the Explanation to Section 138, and therefore falls outside the section altogether. Section 4 below examines why that argument is weaker than it looks but until a court actually rules on it, a Seller should not assume it will automatically fail, which is exactly why the drafting in Section 3 matters.

Cheque validity. A cheque is legally valid for presentment for exactly three months from the date written on the instrument. RBI reduced this from six months to three months in 2012; once the three-month window lapses, the cheque becomes a "stale" instrument that the paying bank will not honour, regardless of whether funds are available. In any M&A structure with tranches staggered beyond ninety days — earn-outs, multi-year deferred consideration schedules, milestone-linked payments, a PDC dated at Closing for a distant tranche can lapse before it is ever presented. Closing checklists across deal types rarely build in a re-dating and re-registration cycle for PDCs nearing their validity window; this should be an explicit, calendared obligation in every Transaction Agreement that uses PDC security, not an afterthought specific to one deal type.

3. Building PPS Compliance into M&A Documentation

A well-drafted Transaction Agreement should convert PPS compliance into a mandatory, evidenced Closing deliverable, through three linked mechanisms that work the same way across share, business, and asset transactions:

Simultaneous execution deliverable. The Purchaser delivers the tranche PDCs on the Execution or Closing Date (as the Transaction Agreement defines it), and simultaneously hands over a copy of the PPS intimation letter submitted to its bank, duly stamped and acknowledged.

Wire-failure trigger. RTGS remains the primary payment mode, but the Transaction Agreement fixes a hard trigger: if the wire transfer fails, is rejected, or is not fully credited (not merely initiated) to the Seller's account within a stipulated period, the Seller becomes unconditionally entitled to present the corresponding PDC without further notice to, or consent from, the Purchaser. This clause removes the Purchaser's contractual defences (lack of consent, lack of notice, dispute over whether the trigger occurred). It cannot and does not shorten the statutory notice-and-cure sequence under Section 138 itself.

Safe-return protocol. To prevent double recovery, the Transaction Agreement obliges the Seller to return or courier the corresponding PDC to the Purchaser within a fixed window of confirmed RTGS receipt, evidenced by a bank credit confirmation rather than the Purchaser's own payment advice.

4. Section 138: What Happens When a PDC Is Dishonoured?

"Cheque bouncing" is not itself a defined legal term; it is shorthand for what the NI Act calls dishonour of a cheque. Section 138, read with its Explanation, ties criminal liability to a cheque that is returned unpaid either because of insufficiency of funds in the drawer's account or because it exceeds an arrangement made with the bank. On a literal reading, that would seem to exclude returns for other reasons including a Positive Pay–related return. But as the case law below shows, courts have not read Section 138 that narrowly: dishonour for a range of reasons attributable to the drawer, beyond just the two named in the Explanation, has been held to attract liability, provided the cheque was issued for a legally enforceable debt and the statutory notice procedure is followed.

Pre-existing liability across M&A structures. Once a transaction closes, a deferred consideration tranche is an existing contractual payment obligation, not a contingent or unliquidated sum. This holds regardless of how the deal is structured, because the obligation to pay crystallises on Closing under the Transaction Agreement, independent of what is being transferred.

This is reinforced by the Supreme Court's ruling in Sampelly Satyanarayana Rao v. Indian Renewable Energy Development Agency Ltd., (2016) 10 SCC 458, which held that a post-dated cheque issued towards an instalment — even where described as "security" — attracts Section 138 once that instalment falls due and remains unpaid. The debt does not need to be enforceable on the date the cheque is handed over; it needs to be enforceable on the date the cheque is presented. Applied to any of these deal types, the tranche PDC matures into a fully presentable, statutorily protected instrument precisely at the moment the RTGS-failure trigger date passes without payment.

Does a PPS-related return still count as "dishonour"? This is the more open question, but existing precedent points the right way for Sellers. In Laxmi Dyechem v. State of Gujarat, (2012) 13 SCC 375, the Supreme Court held that Section 138 is not confined to the two grounds listed in its Explanation; dishonour for other reasons attributable to the drawer — including signature mismatch and mandate changes — was held to attract liability, extending the reasoning already applied to "account closed" cheques in NEPC Micon Ltd. v. Magma Leasing Ltd., (1999) 4 SCC 253.

By the same logic, a return caused by the Purchaser's own failure to complete PPS registration — a step entirely within its control — should fall within this expansive reading, since the non-payment traces back to the drawer's own omission rather than a bank error or a fact outside anyone's control. This reasoning does not depend on which type of M&A transaction generated the underlying debt.

That said, no reported Supreme Court or High Court decision has yet tested this specific PPS fact pattern, in any transaction context. Sellers should treat this as a reasoned extension of Laxmi Dyechem and NEPC Micon, not settled law, and should not rely on the argument alone — which is precisely why the contractual deliverables in Section 3 (the bank-acknowledged PPS letter as documentary proof of the Purchaser's registration obligation, and its breach) matter: they let the Seller frame the case on the Purchaser's contractual default and documentary bad faith, rather than resting solely on how a court will eventually characterise the bank's return code.

The statutory notice-and-cure period cannot be contracted around. However "unconditional" the Transaction Agreement makes the Seller's right to present the PDC, Section 138's proviso still requires: presentment within the cheque's three-month validity; a written demand notice to the drawer within 30 days of the return memo; and 15 days from the drawer's receipt of that notice within which to pay before a criminal complaint can be filed. No contractual clause in an SPA, BTA, APA, or slump sale agreement alike — can shorten or waive this cure period. Deal counsel should draft the wire-failure trigger and notice mechanics on a timeline that leaves room for full compliance with this sequence.

Cumulative, not exclusive, remedy. The Transaction Agreement should expressly record that PDC presentation is a remedy cumulative with, and without prejudice to, specific performance and monetary damages under the agreement, and does not affect the Seller's independent statutory rights under the NI Act.

5. Drafting Safeguards for M&A Transactions

Security Feature	Standard PDC Clause (Weak)	PPS-Integrated Transaction Clause (Airtight)
PDC Delivery	Delivered at Closing with no bank confirmation	Delivery conditional on simultaneous handover of a bank-acknowledged PPS intimation letter
Encashment Trigger	Ambiguous notice period before deposit	Automatic right to deposit if RTGS is not credited (not merely initiated) within specified Business Days
Cheque Validity	PDC dated once at Closing, no refresh mechanism	Transaction Agreement schedules re-dating and re-registration of PDCs approaching the 3-month presentment limit
Indemnity Interlocking	Purchaser can stop payment citing indemnity or price-adjustment claims	Set-off contractually barred against early tranches; restricted exclusively to the final tranche
Statutory Sequence	Left to be worked out after dishonour	Notice and re-presentment timeline drafted to preserve full compliance with Section 138's notice/cure period
Document Exchange	No timeline for cheque return post-payment	Mandatory return window following confirmed electronic credit
Applicability Across Structures	Drafted for one deal type, not revisited for others	Built as a standard module usable across SPAs, BTAs, APAs and slump sale agreements alike

Conclusion

PDCs remain a cost-effective alternative to Bank Guarantees for securing deferred consideration across share acquisitions, business transfers, slump sales, and asset deals alike. PPS has added a genuine, still largely untested, procedural risk that applies equally to all of them: a Purchaser who quietly withholds PPS registration can manufacture a dishonour that looks different, on paper, from "insufficient funds." Existing Supreme Court precedent on the scope of Section 138 (Laxmi Dyechem, NEPC Micon, Sampelly Satyanarayana Rao) supports treating such a dishonour as covered — but the safer position, and the one that actually protects a Seller, is not to rely on that argument reaching a court favourably. It is to make bank-acknowledged PPS registration a mandatory, evidenced Closing deliverable, build the wire-failure trigger and cheque-refresh cycle into the Transaction Agreement's timeline, and leave the Section 138 notice-and-cure sequence fully intact and uncontested — whatever the deal is called.

About the Author: Reetika Gupta, Advocate

Reetika Gupta is a lawyer with over 15 years of experience advising startups and growth-stage companies on investments, commercial contracts and legal frameworks that support business growth and ease of doing business.

She is the Founder of Aristo Legal, a law firm focused on providing practical, business-oriented legal guidance to companies as they navigate growth, transactions and day-to-day legal requirements.

Disclaimer: This article is intended for general informational purposes only and reflects the author's personal views as of the date of publication. It does not constitute legal advice, and nothing in it should be relied or acted upon without independent professional advice tailored to your specific facts. Judicial precedent and RBI circulars referenced above are current as of the publication date and may be superseded by later rulings or regulatory changes; readers should independently verify the current position before relying on it. Transmission or receipt of this article does not create an advocate-client relationship. This publication is not an advertisement, solicitation, or invitation to engage the author or any associated firm.