In the finance world, there’s a familiar sequence: new asset classes emerge, engineers become overly present, regulators grow cautious, and eventually someone in the CFO’s office needs to discuss it all.
Stablecoins, in contrast to other blockchain products, seem to have the potential to break into new markets beyond just the crypto ecosystem.
This past Wednesday, BNY (New York Bank Melon Co.) reinforced the importance of Ripple’s stablecoin reserves, highlighting that stablecoins are garnering attention in traditional finance.
Emily Portney, Global Head of Asset Services at BNY, expressed enthusiasm for supporting the adoption of RLUSD, facilitating smooth transitions of reserve assets and cash.
The growth of stablecoins isn’t inherently volatile. Actually, the rise of fiat-backed digital assets could lead to greater efficiency and innovation in financial operations. Still, just because the technical capabilities exist doesn’t mean there’s no need for careful examination and institutional diligence.
CFOs might want to rethink the question: it’s less about “Should I use stablecoins?” and more about “Do stablecoins align with our financial structure, and under what conditions?”
What Defines a Stablecoin?
For stablecoins to gain traction, they must showcase their utility beyond their native crypto markets. Progress is indeed being made. Recently, news emerged about stablecoin license applications being evaluated in various countries.
Yet, the term “Stablecoin” itself can be a bit nebulous. It encompasses a wide range of digital assets, each with unique structures, governance, collateral, and intended uses. For a prudent CFO, this ambiguity can create hurdles in managing corporate capital and financial systems.
“Stablecoin” sounds reassuring but lacks a clear legal definition and isn’t necessarily sanctioned by central banks. It often refers to a digital asset pegged to the value of a fiat currency, but that’s where the similarities begin and end.
Some stablecoins are fully backed by cash and short-term treasury assets, issued by regulated entities—think USDC from Circle or PYUSD from PayPal. These tend to be rather mundane and bank-like. Others, like MakerDAO’s Dai, are collateralized by various crypto assets and adjusted through algorithms managed by token holder votes. There are algorithmic stablecoins too, but enthusiasm has waned significantly since the collapse of TerraUSD.
Ultimately, stablecoins are not merely about blockchain technology. They encompass governance aspects. Important questions arise: who makes decisions when issues occur? Who controls the reserves? What defines the rules of operation?
If a CFO possesses a stablecoin, it’s essentially a promise. Understanding who created it and what happens in a failure scenario is crucial.
Stablecoin Use Cases in Business
There are valid reasons to consider stablecoins for practical and even strategic uses, especially in global operations. They could alleviate inefficiencies in customer digital transactions and existing payment systems.
Cross-border payments serve as a clear use case. Traditional methods are often slow, pricey, and cumbersome. Stablecoins can settle transactions in minutes at a minimal cost, operating around the clock. For vendors or freelancers, receiving payment with a reliable stablecoin can be more appealing than the lengthy wait for traditional wires.
However, for CFOs, this conversation isn’t simply about exchanging money. It’s about recognizing where stablecoins can provide quicker payments, facilitate global interactions, and escape the constraints of outdated systems.
That said, using stablecoins isn’t straightforward. These aren’t neutral assets; they’re based on specific promises governed by particular issuers and settled on unfamiliar infrastructures.
CFOs don’t need to become experts in encryption, but they should ask the right questions.
Moreover, many companies choose to outsource these interactions. A lot avoid direct dealings with stablecoins altogether and rely on payment vendors instead. This can work until complications arise or an audit is necessary.
Warnings exist within the details. Issues can pop up unexpectedly, especially in invoices and contracts. The quicker teams grasp the landscape, the better prepared they will be to respond effectively.
