Moneygram Halts Using Ripple Due to SEC Lawsuit Over XRP Cryptocurrency – Regulation Bitcoin News


Moneygram Halts Using Ripple Due to SEC Lawsuit Over XRP Cryptocurrency

Moneygram has announced that it has suspended using Ripple’s platform due to the lawsuit against Ripple Labs and its executives by the U.S. Securities and Exchange Commission (SEC). Last year, the company earned $50.2 million from Ripple for using the platform.

Moneygram Stops Using Ripple’s Platform

Moneygram International announced Monday that it has suspended trading on Ripple’s platform. The announcement came as part of the company’s earnings report for the fourth quarter and full year 2020. For the year 2020, Moneygram recorded total revenue of $1,217 million; its money transfer revenue was $1,105 million.

As part of its first quarter 2021 outlook detailed in the report, Moneygram wrote that it “is not planning for any benefit from Ripple market development fees in the first quarter,” adding:

Due to the uncertainty concerning their ongoing litigation with the SEC, the company has suspended trading on Ripple’s platform.

How Much Ripple Is Paying Moneygram

Moneygram has had a commercial agreement with Ripple since June 2019 to “use Ripple’s foreign exchange (FX) blockchain trading platform (ODL) for the purchase or sale of four currencies,” the company explained. The platform utilizes the XRP cryptocurrency. Its use by Moneygram is subsidized by Ripple.

In its earnings release Monday, Moneygram revealed that “In the first quarter of 2020, the company realized a net expense benefit of $12.1 million from Ripple market development fees.” In the fourth quarter, it generated “$8.5 million net benefit from Ripple market development fees of $9.2 million, partially offset by related transaction and trading expenses of $0.7 million.”

Meanwhile, its financial statements for the year 2020 and 2019 include Ripple market development fees of $50.2 million and $11.3 million, respectively. These figures were partially offset by related transaction and trading expenses of $11.9 million and $0.4 million, respectively.

Moneygram Cites SEC Lawsuit as Reason for Suspending Use of Ripple’s Platform

The SEC filed a lawsuit in December against Ripple Labs Inc., its CEO Brad Garlinghouse, and co-founder Christian Larsen, charging them with conducting a $1.3 billion unregistered securities offering of the XRP cryptocurrency.

The SEC lawsuit alleges that “Much of the onboarding onto ODL was not organic or market-driven. Rather, it was subsidized by Ripple.” The regulator further described: “Though Ripple touts ODL as a cheaper alternative to traditional payment rails, at least one money transmitter … found it to be much more expensive and therefore not a product it wished to use without significant compensation from Ripple.”

Without naming the money transmitter in question, the SEC detailed, “The money transmitter has served that principal purpose for Ripple in exchange for significant financial compensation,” adding:

The money transmitter became yet another conduit for Ripple’s unregistered XRP sales into the market, with Ripple receiving the added benefit that it could tout its inorganic XRP ‘use’ and trading volume for XRP.

Tags in this story
Brad Garlinghouse, moneygram ripple, moneygram sec, moneygram xrp, ripple lawsuit, ripple sec, sec lawsuit ripple, xrp lawsuit, xrp security

What do you think about Moneygram’s decision to stop using Ripple’s platform? Let us know in the comments section below.

Kevin Helms

A student of Austrian Economics, Kevin found Bitcoin in 2011 and has been an evangelist ever since. His interests lie in Bitcoin security, open-source systems, network effects and the intersection between economics and cryptography.

Image Credits: Shutterstock, Pixabay, Wiki Commons

Disclaimer: This article is for informational purposes only. It is not a direct offer or solicitation of an offer to buy or sell, or a recommendation or endorsement of any products, services, or companies. does not provide investment, tax, legal, or accounting advice. Neither the company nor the author is responsible, directly or indirectly, for any damage or loss caused or alleged to be caused by or in connection with the use of or reliance on any content, goods or services mentioned in this article.

Read disclaimer
Show comments