Ripple and SettleMint Announce Asia-Pacific Custody and Tokenization Offering

Direct answer: a same-day institutional offering, with the network still undisclosed

Ripple and SettleMint announced a combined offering for regulated financial institutions in Asia-Pacific on September 1, 2026. Ripple Custody is presented as the custody layer, while SettleMint’s Digital Asset Lifecycle Platform handles issuance and lifecycle workflows. The announcement names no blockchain network, customer, transaction volume, or XRP-specific deployment. [1] [2]

[Confirmed fact] SettleMint’s official newsroom release says the partnership integrates Ripple Custody with SettleMint’s DALP to help institutions custody, issue, and manage tokenized assets through a shared operating foundation. It says the partnership offering has already commenced in Asia and may extend to other markets as institutional demand develops. [1]

[Confirmed fact] The September 1 distribution on PR Newswire and independent reports from Blockonomi and CryptoCompass describe the same combination of custody, issuance, compliance, settlement, and servicing functions. Their coverage also preserves the release’s omissions: no named client, supported network, pricing, contract value, initial volume, or detailed implementation schedule. [2] [3] [4]

[Bounded inference] The material development is an institutional operating-model and procurement proposition, not a disclosed blockchain deployment. The record supports saying that two companies are offering an integrated custody and tokenization stack. It does not support saying that a bank has gone live, that a token has been issued, or that XRP-related demand has changed. [1] [3] [4]

Section sources[1][2][3][4]

What Ripple Custody and SettleMint DALP are meant to do together

[Confirmed fact] In the official announcement, Ripple Custody is the place where an institution holds and governs the digital asset. SettleMint says DALP manages the asset’s wider lifecycle after launch, including issuance, compliance, permissioning, settlement, and servicing. The language describes a division of responsibility between custody controls and lifecycle orchestration. [1]

SettleMint positions DALP as a governed control plane rather than a token-creation utility. Its description covers regulated financial institutions, market infrastructure operators, and sovereign entities, and presents the platform as a way to manage several operational stages through one integrated system. Those are the provider’s product and market claims, not an independently measured service-level result. [1] [3]

[Confirmed fact] Blockonomi independently reports that the offering is aimed at giving Asia-Pacific banks a platform covering tokenized-asset custody, issuance, compliance, and servicing. CryptoCompass likewise describes a single system for regulated institutions and notes that the companies did not publish named clients, revenue, or a detailed implementation timeline. [3] [4]

[Bounded inference] The integration could matter during vendor selection because it addresses a common institutional question: can custody and lifecycle workflows be procured as connected components instead of assembled from unrelated vendors? The public record does not prove that reconciliation work disappears, that operating costs fall, or that compliance approval becomes faster. Those outcomes would require customer evidence. [1] [3]

Section sources[1][3][4]

The custody boundary: signing stays with the configured provider

[Confirmed fact] SettleMint’s July 15, 2026 technical post gives more detail on the DALP model. It says DALP prepares a transaction, applies business logic and controls, routes the request to the configured custody provider, submits the signed transaction, and tracks confirmation. The post says key material does not move into the lifecycle platform. [5]

The same technical reference lists Ripple Custody, alongside other custody and signing paths, as a supported provider model. It describes approval workflows remaining inside the provider’s vault or signing environment while DALP waits for the result. This explains the mechanism the companies are presenting, but it predates the September partnership announcement and is not a third-party audit. [5]

[Confirmed fact] The September announcement assigns Ripple Custody responsibility for holding and governing the asset, while DALP handles the surrounding lifecycle. That role split is consistent with SettleMint’s earlier prepare, sign, broadcast, and track description. Neither source names a particular institution using the new combined offering or publishes an implementation record. [1] [5]

[Unresolved uncertainty] A documented separation of transaction preparation from signing does not answer every due-diligence question. Institutions still need to establish the legal custodian, key-management model, approval quorum, policy enforcement, recovery process, audit evidence, incident response, and responsibility for each network in a live deployment. None of those customer-specific controls is disclosed in the announcement. [1] [5]

Section sources[1][5]

Asia is the starting market, not proof of regional adoption

[Confirmed fact] The release is dated September 1, 2026 and identifies Asia Pacific as the target region. Its more specific operating statement says the partnership offering has commenced in Asia and may expand to other markets as institutional demand develops. That wording establishes a commercial start claim, not a list of live country deployments. [1] [2]

[Confirmed fact] Independent coverage says the companies did not identify customers, countries, production dates, supported blockchains, initial transaction volumes, pricing, or contract values. CryptoCompass similarly characterizes the customer base and implementation timeline as undisclosed. These omissions are central facts because the announcement does not give readers a way to measure the offering’s reach. [3] [4]

[Bounded inference] “Asia Pacific” should therefore be read as the announced market scope, while “commenced in Asia” should be read as the companies’ statement that the offering is available or underway somewhere in the region. It should not be upgraded into proof that banks across the region are using the system or that a regional regulator has approved it. [1] [3]

[Unresolved uncertainty] The announcement does not identify the first jurisdiction, institution, asset class, custody license, deployment environment, or go-live milestone. Without those details, readers cannot independently test whether the offering is a pilot, a signed commercial service, a production integration, or a broader sales launch. [1] [3] [4]

Section sources[1][2][3][4]

Disclosure matrix: what the announcement establishes and leaves open

The most useful way to read the release is to separate the announced proposition from the evidence that would show it operating in the market. The matrix below uses the official release as the primary record and the independent reports as a check on its disclosed boundaries. [1] [3] [4]

[Confirmed fact] The release establishes the named companies, the two named products, the intended regulated-institution audience, the Asia-Pacific market, and the stated custody-to-lifecycle division. It does not establish the rows in the final column as negative facts about the companies generally. It establishes only that those details were not disclosed in this announcement. [1] [2]

Section sources[1][2][3][4]

Why this is not yet an XRP Ledger, XRP, or RLUSD deployment story

[Confirmed fact] The announcement discusses tokenized assets and names Ripple Custody and DALP, but it does not identify a supported blockchain network for the combined offering. Independent reporting also notes that no supported blockchain was named. The announcement therefore cannot establish XRPL use, Ethereum use, another chain, or a multi-network deployment. [1] [3] [4]

Ripple’s broader company description mentions XRP and RLUSD as assets that underpin parts of its wider solutions. That background sentence does not connect either asset to this SettleMint integration. A product company can discuss its broader ecosystem without disclosing which assets a particular customer workflow uses. [1] [2]

[Bounded inference] The absence of a named network is not evidence that the offering cannot support XRPL, XRP, or RLUSD. It is evidence that this announcement leaves that implementation question unanswered. The same boundary applies to tokenized funds, stablecoin settlement, custody balances, and any other asset-specific use case a reader might expect from Ripple’s broader product portfolio. [1] [3]

[Unresolved uncertainty] No source reviewed here provides a transaction hash, public issuance record, customer case study, assets-under-custody figure, or network-level activity tied to the partnership. It is consequently not defensible to describe the announcement as XRPL adoption, an XRP demand event, RLUSD usage, or a market catalyst. [3] [4]

Section sources[1][2][3][4]

Implications for institutions, custodians, token issuers, and XRP readers

[For regulated institutions] The announcement is relevant as a due-diligence starting point. A prospective buyer would need to ask which entity holds the asset, where signing authority sits, which jurisdictions and networks are supported, how permissioning is enforced, how transactions are reconciled, and what evidence is available for audit and incident response. The release answers only part of that list. [1] [5]

[For custodians and compliance teams] The prepare-and-sign separation described by SettleMint can be a meaningful architectural boundary because a lifecycle system need not hold the institution’s signing keys. It is still a design description. It does not independently prove security, regulatory compliance, segregation, resilience, or successful operation under production load. [5]

[For token issuers and market infrastructure operators] A connected custody and lifecycle stack could make issuance and post-launch administration easier to evaluate, especially where compliance and servicing continue after an asset is created. The missing network, customer, and volume disclosures mean teams cannot yet assess liquidity, interoperability, settlement performance, or commercial fit from this announcement alone. [1] [3]

[For XRP readers] The story belongs in institutional infrastructure coverage, not in a price or adoption narrative. The cited records do not establish a Ripple Custody customer using XRP, an XRPL deployment, an RLUSD workflow, a new source of XRP demand, or a change in XRP market structure. Those claims require separate asset-specific evidence. [1] [3] [4]

Section sources[1][3][5][4]

Uncertainty label: confirmed facts, bounded inference, and open questions

[Confirmed] SettleMint’s September 1 announcement and its PR Newswire distribution support the partnership, product names, regional audience, stated role split, and claim that the offering has commenced in Asia. Blockonomi and CryptoCompass independently support the existence and broad scope of the announcement while identifying its missing customer and implementation details. [1] [2] [3] [4]

[Confirmed] SettleMint’s July 15 technical post supports the described DALP mechanism: prepare and route a transaction, keep signing with the configured custody provider, broadcast after signing, and track confirmation. That source supports product architecture, not a live result for this September partnership. [5]

[Bounded inference] The public record supports calling this a same-day institutional custody and tokenization offering with an integrated operating model. It supports asking whether the arrangement improves procurement or lifecycle coordination. It does not support converting the companies’ product language into measured adoption, cost savings, reduced reconciliation, security certification, regulatory approval, or XRP market impact. [1] [3] [5]

[Unresolved] The sources leave open the first customer and jurisdiction, production status, supported networks, asset types, commercial terms, transaction volume, assets under custody, implementation schedule, and any use of XRP, XRPL, or RLUSD. The next credible update should answer at least one of those questions with a named institution, network, dated deployment record, or measurable operating result. [1] [3] [4]

Source precedence is straightforward. SettleMint’s newsroom and PR Newswire distribution are primary for the announcement, while SettleMint’s technical post is primary for its own architecture description. Blockonomi and CryptoCompass are independent supporting sources for the announcement’s scope and omissions. Where a product claim remains unmeasured, it is labeled as a company statement rather than presented as an outcome. [1] [2] [3] [4] [5]

Section sources[1][2][3][4][5]