12-09-2022 | treasuryXL | Kyriba | LinkedIn |

Despite the current market volatility, cryptocurrencies⁽¹⁾ are slowly seeping into everyday transactions,⁽²⁾ driven largely by small businesses. There are an estimated tens of thousands of businesses that are accepting cryptocurrencies as payments roughly representing about 0.01% of businesses worldwide.

By Rishi Munjal, Vice President Product Strategy, Payments, Kyriba

Source

Large corporations have stayed away from cryptocurrencies with a few exceptions⁽³⁾ where the use is limited to holding cryptocurrencies in treasury. The treatment of cryptocurrencies as an “indefinite-lived intangible asset”⁽⁴⁾ poses an accounting risk, forcing companies to write down⁽⁵⁾ the value of these assets when their value plummets.

The level of adoption is by no means impressive. Meanwhile, challenges with high-fees, scalability and volatility will continue to limit broad adoption of cryptocurrencies as a form of payment. Such limitations pose an important question for CFOs and treasurers: Are cryptocurrencies worth paying attention to?

Stablecoins and the Future of Payments

The answer is yes, given the potential for innovations that can shape the future of payments for corporates and merchants alike. This is especially true for Stablecoins⁽⁶⁾, as they present an opportunity to lower fees, reduce barriers and drive better services like instant cross-border payments. The promise hinges on a stablecoin’s ability to maintain its peg to a specified asset (typically U.S. dollars), or a pool or basket of assets, and provide perceived stability when compared to the high volatility of unbacked crypto-assets.

Since the launch of BitUSD in 2014 on the BitShare⁽⁷⁾ blockchain, stablecoins have evolved into public and private stablecoins. Public stablecoins exist in two forms. Reserve-backed or custodial stablecoins are backed by cash-equivalent reserves such as deposits, Treasury bills and commercial paper. These are issued by intermediaries who serve as the custodians of the cash equivalent assets and offer a 1-for-1 redemption of their stablecoin liabilities for the asset it is pegged against.

Algorithmic stablecoins (e.g.,UST) rely on mechanisms other than cash-equivalent reserves to stabilize their price. The peg to a specified asset is achieved by overcollateralized crypto and/or smart contracts that defend the peg by automatically buying or selling the stablecoin. These public stablecoins provide liquidity across the thousands of cryptocurrencies currently in the market. The private institutional stablecoins use tokenized deposits held by the bank for efficiently providing internal liquidity or liquidity for the bank’s wholesale clients between accounts held at the same bank. These coins (e.g., JP Coin) form a closed loop payment network similar to the ones offered by wallet providers like PayPal.

Stablecoin Guidance

Stablecoins have had their share of troubles⁽⁸⁾ and collapses⁽⁹⁾ in their short history. These risks were well understood by regulatory agencies. However, the explosive growth in cryptocurrencies has made it difficult if not impossible for regulators⁽¹⁰⁾ to keep up. Outside of the ad-hoc enforcement actions against crypto firms by the SEC⁽¹¹⁾, the industry continues to operate largely outside of regulations. Given the complexity of the crypto ecosystem, it is pragmatic for regulators to start with Stablecoins as they are relatively simpler and have real applications. It is therefore not a surprise, that despite the market turmoil, New York became the first U.S. state to issue guidance for Stablecoin issuers.

The Virtual Currency Guidance⁽¹²⁾ provided by the New York Department of Financial Services (DFS) outlines redeemability, reserve and attestation requirements for entities issuing U.S. dollar-backed stablecoins. The industry has been waiting for long-overdue commonsense regulations for reducing systemic risk and providing a fertile ground for stablecoin issuers and other fintechs to drive broad innovation in financial services and payments.

Table 1: Key points from The Virtual Currency Guidance provided by the New York DFS

Kyriba has taken a forward looking posture in this space, for example via partnership with Copper to offer corporate treasury direct access to Copper’s award winning digital asset investment platform, and the ability to manage liquidity across fiat, crypto and money market funds.

While the specific time-horizon on when a trend would become meaningful is not easy to predict, CFOs and treasurers can preserve optionality by partnering with providers that stay at the forefront of payment market trends.

More to Read:

1. API: Copper Integration
2. Blog: The Top 5 Trends for CFOs in 2022
3. Blog: Digital Currencies: Not Ready for Corporate Treasury

References

⁽¹⁾ FSB defines all private sector digital assets that depend primarily on cryptography and distributed ledger or similar technology as crypto-assets and not currencies; for this article the two terms are being used interchangeably.
⁽²⁾ Map of Cryptocurrency ATMs and Merchants, Coinmap.org
⁽³⁾ Public companies holding bitcoin, Coingecko.com
⁽⁴⁾ Accounting for and auditing of digital assets
⁽⁵⁾ MicroStrategy Posts a Loss After Taking Bitcoin Impairment, Bloomberg 2/22
⁽⁶⁾ Financial Stability Board, Crypto-assets and Global “Stablecoins”
⁽⁷⁾ Whitepaper: BitShares – A peer-to-peer polymorphic Digital Asset Exchange
⁽⁸⁾ Terra Luna timeline; TerraLuna UST collapse – What Happened?
⁽⁹⁾ CFTC fines Tether and Bitfinex for misleading claims; Panics and Death Spirals: A history of- failed stablecoins
⁽¹⁰⁾ Stablecoin risks and potential regulations, BIS Working Paper 11/2020
⁽¹¹⁾ Crypto Assets and Cyber Enforcement Actions, notes seven enforcement action for the period Jan – April 2022
⁽¹²⁾ Guidance on issuance of US Dollar backed stablecoins, New York Department of Financial Services, Jun 2022

08-08-2022 | treasuryXL | Kyriba | LinkedIn |

Nowadays if you work in treasury, probably not a day goes by without you seeing a social post or article from your subscribed newsletters on the topic of real-time Bank API. It stands for the future of bank connectivity, and it will change the way data is exchanged between corporates and banks. Trent Ellis, Senior Solution Engineer at Kyriba, spends his time assisting clients to evaluate what works the best for them from a solution point of view, with both their current and future business needs in mind. In his discussions with clients and prospects, bank connectivity has always been a focus area and recently he noticed a growing interest in real-time Bank APIs.

By Trent Ellis, Senior Solution Engineer

Source

When it comes to real-time bank connectivity, the first thing I usually tell my clients is that it’s important to delineate between the different data flows such as inbound balance reporting, transaction details, confirmation reporting and outbound payment initiation. When an organization plans to make real-time bank connectivity a reality, the first thing they should do is to look at their data flows from daily operations. Identify and determine what data would benefit from a real-time update? Which items are critical for that real-time treasury decision making? Where are you going to maintain the balance and transaction data once it is received or payment data prior to it being transmitted to the bank?

Next, because many banks have grown their footprint by acquisition, bank accounts held in different regions (even regionally within a country) can be on different platforms with different technology. Therefore, within a single bank, API readiness can have a different status for different subsets of bank accounts based on branch and geographic location.

Now that the bank may have made an API connection available, how are you going to connect to it? Do you look at internal technical expertise and availability? Do you look to a third-party vendor? Consider a specialist that just does API connections or a TMS vendor that has other integrated modules and additional functionality beyond just the bank connection for statements and/or payments?

Real-time Bank Reporting, what does this really mean?

Banks are now offering bank balance API’s as well as transactional statement APIs, but sometimes not (yet) both. It’s more than likely not the same as what you would get from that same bank in the form of a BAI or MT940 standard bank statement as banks are still working on what data becomes available through the API. Bank balance reporting is important for real-time liquidity monitoring but will not always help your treasury or AP team confirm the status of a cleared payment, or the status of an important cash credit.

Yes, an API can deliver data in real-time but is the underlying platform that holds that data providing real-time data? Some banks are providing their “real-time” data on a predefined schedule throughout the day which means it is not what most would consider “real-time”. True real-time reporting requires process changes at the bank. Decreasing update time from day to hours or within the hour is an improvement that is easier to absorb without restructuring the process.

Real-time payments, what does this really mean?

Real-time payments are payments that are cleared and settled nearly instantaneously. Real-time payments are generally facilitated by domestic or regional payment infrastructures on a 24x7x365 basis including weekends and holiday.¹

Many may not be aware that globally real-time payment infrastructures have been around for as long as 40+ years, and real-time payments can be enabled via FTP or API based on Bank / FI’s offerings and the connectivity option preferred by the corporate customer. Relatively, it has been a recent development in the US payment ecosystem. In November 2017, The Clearing House launched the first real-time payment infrastructure RTP® network in the US, built on the same Vocalink technology that powers the UK’s Faster Payment System. The RTP® network was built for financial institutions of all sizes and serves as a platform for innovation allowing financial institutions to deliver new products and services to their customers. Financial Institutions can integrate into the RTP® network directly, through Third-Party Service Providers (TPSPs), Bankers’ Banks and Corporate Credit Unions.² The US Federal Reserve will be launching its real-time payment infrastructure FedNow^SM in the 2023 – 2024 timeframe.

Globally real-time payments are growing at a double-digit growth rate across all major markets. Adoption of real-time payments will continue to be use case specific, especially for use cases that are underserved by existing payment infrastructures. In the long-term, we should expect real-time payments to be an important part of corporate’s payments mix alongside other traditional payment systems. Like other real-time payment infrastructures globally, the RTP® network has been increasing its transaction limits, which currently stands at $1million. This makes it more relevant for B2B / Corporate payment use cases – a very good example from our client HUNT Companies being the intracompany transfers for efficient deployment of working capital. However, this also means that if you need to make payments with value greater than $1million, you would need an alternative type or method for the time being. You cannot rely on the RTP® network as your only means to make payments and will still require connections for other payment types such as Wire, ACH and international formats.

Recommendations to clients

The world is certainly migrating towards real-time bank connectivity, but organizations will ultimately require various connectivity strategies to fit different geographical and banking technology. In 2022, most real-time Bank APIs are an incremental addition to existing connection methods and formats for both statements and payments. Currently, Bank APIs are not a replacement for other options, which are still required to get a complete picture of prior day statement activity and/or ability to send all required payments. Therefore, my recommendations to my clients always remain the same:

• Identify and evaluate your data flows.
• Where does real-time data make sense?
• Talk to your banking partners and understand their offerings in detail.
• Ask the question: Do your internal requirements align with the bank’s offerings?
• Where are you going to house the data that is received/transmitted via the real-time Bank connectivity?
• Talk to vendors that have teams of people that do this every day and evaluate their perspectives and subject matter expertise.

Find out more details on Bank APIs from the Kyriba Developer Portal, and watch any time an on-demand webinar on everything you need to know about APIs: Bank Connectivity and Beyond.

¹ Real-Time Payments: Everything You Need to Know. Paymentsjournal.com. 2021
² The RTP® Network: For All Financial Institutions. The Clearing House.