Crypto Copycats Beware: Fair Use Of Financial Technology In Wake Of Oracle v. Google

by Locke Lord LLP

Locke Lord LLP

FinTech companies beware: your use of code that was originally developed via open-source methods may not be shielded from future copyright infringement claims by the fair use doctrine. Recently, in Oracle America, Inc. v. Google LLC, 750 F.3d 1339 (2014), the United States Court of Appeals for the Federal Circuit decided that the doctrine of fair use did not protect Google from liability when during development of its mobile Android platform it selectively copied the structure, sequence, and organization of JAVA source code. Specifically, Google copied Application Programming Interface or “API” packages built using Oracle’s JAVA language, appended onto them Google’s own implementing code, and sold the combined code for use in Google’s Android operating system. While Oracle made its JAVA programming language open and free for anyone to use (e.g., an “open source” license), such use required Google to contribute back its innovations to the public, which Google did not do.1

The impacts of Oracle are significant and will have a lasting impact across the technology industry, including in the financial technology segment, where emergent financial platforms often have a relationship with the open-source community. Surging platforms such as Bitcoin, Ethereum, InterPlanetary File Systems, Monzo, Aragon, Humaniq, have origins in or a connection with open-source development, whether for the platforms themselves or for interlinking companion software products. As critical financial technology projects continue to be open-sourced, particularly with further developments in blockchain technology, additional companies will further contribute and reap the benefits from this community software development through the copying and refining of open-sourced code. By sampling some or all of these community data sources, these companies very likely will build their own proprietary platforms such as new cryptocurrencies, payment networks, collateral assignments tracking, or other financial transaction systems. 

However, the massive impact these technologies will have on the existing banking system has already invited, and will continue to invite, the entrance into the market of institutional technology and financial players. These established companies will likely use and develop these underlying source codes and then seek maximum enforcement of any potential intellectual property rights they may create, whether immediately or years down the line. This is being done in particular within the blockchain space at a rapid pace, with banks and technology companies making massive investments in recent years as to the application of decentralized ledger technology to their adjacent businesses.

As a result, it is conceivable that future developers of FinTech products, whether those that compete with or are compatible with these advances, may find themselves implementing some of the underlying code without a clear understanding of whether such use is allowed or prohibited. Indeed, platforms created via open source software licenses, which make the software available to the public for use and distribution under certain conditions, can still control the modification and distribution of their copyrighted material.2 However, as Oracle shows, there is no blanket prohibition against being sued for copyright infringement despite the existence of open source arrangements. It is now clear that the mere existence of open source licenses does not make copying such code a fair use in all circumstances. In Oracle, the Court was unpersuaded by Google’s fair use defense based on the mere existence of Oracle’s grant of an open source license to its JAVA programs. The Court instead cited the potential right of Oracle to enter new markets or create derivative works.3

Moreover, the Court in Oracle appears to argue that it is not fair use to incorporate source code subject to copyright into a new platform, even if the infringing party adds its own implementation code, when the implementation code does not have a different intrinsic purpose compared to that of the incorporated code.4 This is also heavily problematic for the FinTech industry. For example, if a digital wallet code was subject to copyright and a developer used portions of that code to design a digital currency bank, that use would likely be viewed as having the same intrinsic purpose as the incorporated code - namely, acting as a digital currency repository, thereby opening the later developer to claims of infringement.

This potential risk becomes more unclear when incorporating copyrighted encryption code, such as a particular type of blockchain code, into other unique code meant to implement a new form of digital currency, inventory tracking, or secure contract. To argue that the incorporated code is being used in a new context, such as in finance or commerce, would likely be unavailing for the same reasons Google’s “new context” argument in Oracle was rejected.5 Thus, any potential “fair use” defenses to those who choose to incorporate copyrighted encryption code into their financial technology products may be severely weakened in light of Oracle.

In conclusion, while development in the financial technology space presents a host of possibilities and enterprises, care must be taken when designing the architecture of any platform on which the business will be based. Regardless of the origins in the open-source community or the amount of implementation code that is added to copied source code, the fair use doctrine is not an ironclad defense to claims of infringement. Consulting with experienced intellectual property counsel early on in the process can ensure proper due diligence is taken before launching your financial technology for use by the public. The last thing a thriving business wants or needs is to find itself the subject of a multi-million dollar lawsuit targeting the heart of what makes the business money.


[1]  Although Oracle owns the copyright on Java SE and the API packages, it offers an open source license, which is a license to use the code free of charge, both declaring and implementing code, with the requirement that the user “contributes back” its innovations to the public. See Oracle Am., Inc. v. Google LLC, 2018 WL 1473875, at *2 (Fed. Cir. Mar. 27, 2018) (“Oracle II”) (citing Oracle Am. Inc. v. Google Inc., 750 F.3d 1339, 1350 (Fed. Cir. 2014) (“Oracle I”)). 

[2] Jacobsen v. Katzer, 535 F.3d 1373, 1381 (Fed. Cir. 2008) (“Copyright holders who engage in open source licensing have the right to control the modification and distribution of copyrighted material.”)

[3]  Oracle II, at *22.

[4]  Oracle II at *13-16.

[5]  Id. at *15 (“because the [copyrighted code] was already being used in smartphones, Google did not ‘transform’ the copyrighted material into a new context and no reasonable jury could conclude otherwise.”)

DISCLAIMER: Because of the generality of this update, the information provided herein may not be applicable in all situations and should not be acted upon without specific legal advice based on particular situations.

© Locke Lord LLP | Attorney Advertising

Written by:

Locke Lord LLP

Locke Lord LLP on:

Readers' Choice 2017
Reporters on Deadline

"My best business intelligence, in one easy email…"

Your first step to building a free, personalized, morning email brief covering pertinent authors and topics on JD Supra:
Sign up using*

Already signed up? Log in here

*By using the service, you signify your acceptance of JD Supra's Privacy Policy.
Custom Email Digest
Privacy Policy (Updated: October 8, 2015):

JD Supra provides users with access to its legal industry publishing services (the "Service") through its website (the "Website") as well as through other sources. Our policies with regard to data collection and use of personal information of users of the Service, regardless of the manner in which users access the Service, and visitors to the Website are set forth in this statement ("Policy"). By using the Service, you signify your acceptance of this Policy.

Information Collection and Use by JD Supra

JD Supra collects users' names, companies, titles, e-mail address and industry. JD Supra also tracks the pages that users visit, logs IP addresses and aggregates non-personally identifiable user data and browser type. This data is gathered using cookies and other technologies.

The information and data collected is used to authenticate users and to send notifications relating to the Service, including email alerts to which users have subscribed; to manage the Service and Website, to improve the Service and to customize the user's experience. This information is also provided to the authors of the content to give them insight into their readership and help them to improve their content, so that it is most useful for our users.

JD Supra does not sell, rent or otherwise provide your details to third parties, other than to the authors of the content on JD Supra.

If you prefer not to enable cookies, you may change your browser settings to disable cookies; however, please note that rejecting cookies while visiting the Website may result in certain parts of the Website not operating correctly or as efficiently as if cookies were allowed.

Email Choice/Opt-out

Users who opt in to receive emails may choose to no longer receive e-mail updates and newsletters by selecting the "opt-out of future email" option in the email they receive from JD Supra or in their JD Supra account management screen.


JD Supra takes reasonable precautions to insure that user information is kept private. We restrict access to user information to those individuals who reasonably need access to perform their job functions, such as our third party email service, customer service personnel and technical staff. However, please note that no method of transmitting or storing data is completely secure and we cannot guarantee the security of user information. Unauthorized entry or use, hardware or software failure, and other factors may compromise the security of user information at any time.

If you have reason to believe that your interaction with us is no longer secure, you must immediately notify us of the problem by contacting us at In the unlikely event that we believe that the security of your user information in our possession or control may have been compromised, we may seek to notify you of that development and, if so, will endeavor to do so as promptly as practicable under the circumstances.

Sharing and Disclosure of Information JD Supra Collects

Except as otherwise described in this privacy statement, JD Supra will not disclose personal information to any third party unless we believe that disclosure is necessary to: (1) comply with applicable laws; (2) respond to governmental inquiries or requests; (3) comply with valid legal process; (4) protect the rights, privacy, safety or property of JD Supra, users of the Service, Website visitors or the public; (5) permit us to pursue available remedies or limit the damages that we may sustain; and (6) enforce our Terms & Conditions of Use.

In the event there is a change in the corporate structure of JD Supra such as, but not limited to, merger, consolidation, sale, liquidation or transfer of substantial assets, JD Supra may, in its sole discretion, transfer, sell or assign information collected on and through the Service to one or more affiliated or unaffiliated third parties.

Links to Other Websites

This Website and the Service may contain links to other websites. The operator of such other websites may collect information about you, including through cookies or other technologies. If you are using the Service through the Website and link to another site, you will leave the Website and this Policy will not apply to your use of and activity on those other sites. We encourage you to read the legal notices posted on those sites, including their privacy policies. We shall have no responsibility or liability for your visitation to, and the data collection and use practices of, such other sites. This Policy applies solely to the information collected in connection with your use of this Website and does not apply to any practices conducted offline or in connection with any other websites.

Changes in Our Privacy Policy

We reserve the right to change this Policy at any time. Please refer to the date at the top of this page to determine when this Policy was last revised. Any changes to our privacy policy will become effective upon posting of the revised policy on the Website. By continuing to use the Service or Website following such changes, you will be deemed to have agreed to such changes. If you do not agree with the terms of this Policy, as it may be amended from time to time, in whole or part, please do not continue using the Service or the Website.

Contacting JD Supra

If you have any questions about this privacy statement, the practices of this site, your dealings with this Web site, or if you would like to change any of the information you have provided to us, please contact us at:

- hide
*With LinkedIn, you don't need to create a separate login to manage your free JD Supra account, and we can make suggestions based on your needs and interests. We will not post anything on LinkedIn in your name. Or, sign up using your email address.