Background
Ripple Labs Singapore Pte Ltd (RLSG) and I-Remit Inc (IRI), a Philippines-based remittance company, entered into a Master XRP Commitment to Sell Agreement in May 2022. In November 2022, IRI purchased XRP (a digital asset) from RLSG for US$16 million, with payment due on 18 November 2022. IRI failed to pay. Over the following two years, IRI’s representatives repeatedly acknowledged the debt—including offers to pay US$1m monthly starting December 2023, acknowledgments in July 2024 that the obligation was “overdue,” and apologies in September 2024 for non-payment—but made no payments.
On 1 October 2023, RLSG was amalgamated with Ripple Markets APAC Pte Ltd (RMA), with RLSG’s rights and obligations automatically vesting in RMA by operation of section 215G(c) of the Companies Act 1967. RLSG sent IRI notice of the amalgamation on 30 September 2023. On 30 September 2024, RMA commenced suit seeking the unpaid invoice amount (US$16m plus accrued late payment charges) and damages for other alleged breaches of the agreement. A Registrar granted summary judgment on the invoice claim; IRI appealed, arguing that RLSG had failed to provide proper contractual notice of the amalgamation and thus RMA could not enforce the agreement.
The Court’s Holding
Justice Kristy Tan upheld summary judgment, holding that RMA has a valid claim for the unpaid invoice. The court rejected IRI’s defenses on two independent grounds. First, as a matter of contractual interpretation, clause 9(d) of the agreement (the “Successors and Assigns” clause) does not require notice of an amalgamation. The clause applies only to “assignments” of contractual rights in the traditional sense—a limited transfer of benefits without transfer of burdens. Amalgamation is distinct: it transfers both rights and liabilities to the successor entity. The parties’ own language proved this: clause 4(c)(ii) of the same agreement explicitly uses the word “amalgamate” when imposing restrictions on one party’s ability to merge. The absence of that specific terminology in clause 9(d) demonstrates the parties did not intend it to cover amalgamations. Courts in the United States have held that “absent language to the contrary, an assignment does not include an amalgamation.”
Second, even if notice of the amalgamation were required, IRI received it. The agreement’s notice provision (clause 9(b)) permits electronic notice and states that notice “shall be effective upon receipt” at specified email addresses—but does not state that notice is effective only if sent in that manner. RLSG sent the 30 September 2023 email to Ms. Lanie Cortez, IRI’s Corporate Treasury Head, before the amalgamation took effect on 1 October 2023. IRI had actual notice. The court distinguished the British case Capital Land Holdings, which involved mandatory language (“shall be sent to”), whereas clause 9(b) merely prescribes when notice “shall be effective,” leaving room for proof of actual notice by other means. Most damaging to IRI’s position: Ms. Bernadette Tiu, IRI’s former CFO, subsequently acknowledged in September 2024 correspondence that the debt was owed to RMA itself (not just RLSG), contradicting any claim that this was a bona fide defense rather than a belated legal contrivance.
Key Takeaways
- Amalgamations are not subject to contractual “notice of assignment” provisions unless the contract explicitly extends those provisions to corporate restructurings or uses language like “transfer” or “successor” in a way that clearly encompasses amalgamations.
- Courts interpret contracts by examining the specific language parties use in different clauses; deliberate use of “amalgamate” in one clause and absence of it in another clause addressing assignments signals different intent.
- Notice provisions that establish when notice “shall be effective” (e.g., “effective upon receipt at these email addresses”) do not preclude proof of actual notice by other means in the same communication channel, absent language stating notice is effective “only” if sent a particular way.
- Contemporaneous acknowledgments of debt undermine a defense based on technical defects in notice or succession, particularly when the defending party later concedes the debt is owed to the successor entity.
Why It Matters
This decision clarifies the boundary between contractual assignments and corporate succession events. When a company is amalgamated, its successor automatically acquires all rights and liabilities by operation of law—a fundamentally different transaction from an assignment, where one party voluntarily transfers limited contractual rights to another. Courts will not read assignment-related notice requirements into amalgamations without clear contractual language. This principle is critical for companies engaged in cross-border digital asset transactions and international remittance services, where corporate restructurings are common and counterparties need certainty about who holds contractual rights.
The decision also signals that courts are skeptical of technical defenses raised belatedly after years of acknowledgments. IRI’s sudden invocation of a notice defense in 2025–2026, after repeatedly admitting the debt over two years, undermined its credibility and likely influenced the court’s interpretation of the contract. For practitioners, the takeaway is clear: expressly address amalgamations and corporate succession in cross-border commercial agreements if you want to impose notice requirements or other conditions on successors.