Institutional Infrastructure
Qivalis Chose Fireblocks: Where Ripple’s Bank Custody Fits
Qivalis’s euro stablecoin plan separates issuer infrastructure from bank custody. Fireblocks has the consortium agreement; Ripple’s existing bank clients do not establish an XRP role or a token launch.

Qivalis infrastructure and Ripple Custody answer different questions
Qivalis selected Fireblocks for its planned euro stablecoin infrastructure. Ripple supplies custody technology to banks including BBVA and DZ BANK, but those relationships do not establish a Ripple contract with the consortium or an XRP Ledger deployment. Qivalis’s authorization and the token’s actual issuance also remain separate milestones. [1][2][4]
The distinction matters after November reporting linked Ripple’s custody business to Qivalis. The Crypto Times described the separate roles on November 10. TokenPost reported on November 11 that Ripple removed its related post and blog article; that article’s URL returned a not-found response in this publication’s November 12 check. The reason for removal is unresolved here. A missing webpage does not by itself establish a changed contract. [4][6]
This explainer therefore starts with the surviving commitments: the proposed issuer’s authorization announcement, its selected infrastructure provider’s release, and Ripple’s documented bank relationships. Each names a different party and task. Readers assessing the opportunity need to identify which task a new announcement actually changes before counting it as additional customers, a product launch or blockchain adoption.
Qivalis and Fireblocks: the issuer and its technology provider
Qivalis’s October 14 release identifies an Amsterdam company backed by 37 European banks across 15 countries. It says De Nederlandsche Bank authorized it as an electronic money institution, or EMI. CoinDesk independently reported the authorization and remaining issuance requirements. These are attributed company and regulatory-status facts, not a measurement of customers using a token. [1][5]
Fireblocks’s April 21 announcement names Qivalis as the customer choosing its infrastructure. The stated work covers tokenization, wallet infrastructure and treasury management for issuance, distribution and lifecycle management. IBS Intelligence corroborated the selection on April 22. That documented relationship is more specific than a technology company pointing to overlapping bank clients. [2][7]
Fireblocks’s release also says consortium banks can use its custody, wallet and payment technology. The division is therefore not exclusive: Fireblocks is not confined to issuer software, and Ripple is not automatically selected for member-bank custody. The confirmed distinction concerns which relationship has been announced, not a permanent division of the market between vendors. [2][7]
Analysis: an issuer’s infrastructure agreement identifies a supplier for creating and administering the token. It does not automatically select every bank’s customer-facing custody system. Conversely, a bank selecting custody software does not make that software company the issuer. The useful comparison is between contracts for the same function, with the same counterparty, rather than between brand names appearing near the same stablecoin.
BBVA and DZ BANK: existing custody clients, separate decisions
Ripple’s September 9, 2025 BBVA announcement supplies a concrete example. It describes custody technology supporting the Spanish bank’s bitcoin and ether service for retail customers in Spain. Ripple’s current custody page also identifies DZ BANK among its institutional clients, while The Crypto Times confirms both banks’ existing relationships in its Qivalis coverage. [3][4][8]
Analysis: the BBVA example demonstrates why the asset, country and service matter. A contract supporting one offering cannot be silently expanded to cover another token or every subsidiary. A future Qivalis custody announcement would need to identify the bank entity, eligible clients, asset support and operating scope. Existing infrastructure might help a bank prepare, but that possibility is not a disclosed implementation result.
A bank can also occupy more than one commercial role. Participation in an issuer consortium and provision of customer custody answer different questions about the same institution. Readers should avoid counting each shareholder as a new technology customer. To establish a bank-level deployment, look for that bank’s own service terms or a specific joint announcement, then evidence that the named service is available.
EMI authorization is a milestone before euro token issuance
Qivalis’s authorization release says issuance is planned for the coming months, subject to applicable Markets in Crypto-Assets Regulation requirements and publication of its white paper. The page also states that it does not currently issue electronic money or provide payment services to the public. CoinDesk’s October report likewise distinguishes the license from the remaining launch steps. [1][5]
Unresolved uncertainty: those cited records do not establish a completed token launch. The prospective timetable should be read as the company’s stated expectation, not a calendar commitment. A white paper, an issuance notice and usable distribution terms would answer different parts of the readiness question. None should be substituted for the others merely because a regulatory milestone has been reached.
Analysis: a corporate treasury considering eventual use needs more than permission to issue. It needs to know who can obtain the token, how euro funding reaches the issuer, how redemption instructions are accepted, and when the resulting money becomes available. These are proposed due-diligence questions, not assertions about unpublished Qivalis procedures. Testing those handoffs would turn a broad launch claim into a transaction a finance team could actually reconcile.
What the Qivalis record establishes about XRP and XRPL
The cited Qivalis and Fireblocks announcements establish an intended euro token and an infrastructure relationship. They do not announce an XRP settlement requirement or an XRP Ledger deployment. The Crypto Times’ November report places Ripple’s pitch at the individual-bank custody layer. That is the evidentiary boundary for XRP readers, even when the same banking names appear in several announcements. [1][2][4]
Analysis: there are separate claims to test. A Ripple software sale would be evidence about Ripple’s business. A disclosed XRPL implementation would be evidence about network selection. An identified use of XRP would be evidence about the asset’s function. None of those claims can be completed simply by inserting a bank’s name into a partnership diagram.
This distinction leaves room for a real business opportunity without inventing an asset outcome. Banks preparing for another token may review custody and operational tooling, but an opportunity is not booked revenue. A future chain announcement could materially change this assessment. Until then, an XRP price forecast based on Qivalis would add an assumption that the reviewed operating records do not support.
The acceptance questions for banks and prospective users
Analysis: a practical review should follow the proposed transaction across organizational boundaries. Start by identifying the legal issuer in the token documents, the institution serving the customer, and the provider maintaining each relevant system. Then ask who can authorize movement, who maintains the customer balance record, and who resolves a mismatch. These questions allocate responsibility; a list of technology vendors does not.
Consider a hypothetical company paying a euro invoice with the future token. A successful token transfer, the recipient bank crediting its customer, and redemption into spendable euros would be distinct observations. The company would need records linking them to the invoice before calling the obligation settled under its agreed terms. This illustration describes a review method, not a Qivalis transaction that has occurred.
For bank procurement teams, the next useful disclosure is a named service with an accountable operator and supported workflow. For XRP holders, it is an explicit network or asset role. For treasury users, it is eligibility and an executable funding-and-redemption process. Those different evidence needs explain why Qivalis’s issuer agreement and Ripple’s bank custody relationships should be evaluated separately, even as both remain relevant to institutional digital finance.
What to watch next
- • Qivalis publishing its white paper and a dated notice of first issuance, with the legal issuer and supported networks clearly identified.
- • A bank-specific announcement or service document naming Qivalis token custody, eligible customers and the responsible legal entity.
- • Final funding and redemption terms, including eligibility, processing windows and responsibility for rejected or delayed instructions.
- • A Qivalis or technology-provider implementation record explicitly identifying any XRP or XRP Ledger role.
- • Any replacement Ripple statement clarifying the scope of its Qivalis-related discussion, without treating webpage removal as proof of a contract change.
Sources and verification
We prioritize primary records and label supporting coverage. Dates reflect each source’s publication record.
- [1]Qivalis: EMI authorization and planned issuanceprimary
- [2]Fireblocks: Qivalis infrastructure agreementprimary
- [3]Ripple: BBVA Spain custody agreementprimary
- [4]The Crypto Times: Qivalis infrastructure and bank custody rolessupporting
- [5]CoinDesk: Qivalis receives Dutch EMI authorizationsupporting
- [6]TokenPost: removal of Ripple Qivalis articlesupporting
- [7]IBS Intelligence: Qivalis selects Fireblockssupporting
- [8]Ripple: institutional custody and bank clientsprimaryUndated reference