Skip to content

Ripple Custody Integration for Banks, Crypto Firms and Token Issuers

On Ripple Custody, banks, crypto firms and issuers get deposits released after screening, one posting per transfer and a daily reconciliation. Protofire builds these services. We built and operated the reserve-data pipeline behind 15+ proof-of-reserve and real-time attestation deployments for asset-backed tokens, for a large auditing firm.

Luis Medeiros

Reviewed by Luis Medeiros, Field CTO at ProtofireLast reviewed: November 2026

On this page
  1. Overview
  2. What Ripple leaves to you
  3. Ripple Custody facts
  4. What you get
  5. Why Protofire
  6. Order of work
  7. How work starts
  8. Not the right fit
  9. Related guides and services
  10. FAQ

Work shipped for 60+ networks and 95+ protocols, including

  • Chainlink
  • Ethereum
  • Solana
  • Safe
  • Ripple
  • Aave

What a Ripple Custody integration has to decide

A Ripple Custody integration has to settle which client a deposit belongs to, when the deposit counts as theirs and how finance proves the totals. Suppose you have chosen Ripple Custody for client assets and a client's deposit has arrived on chain. Ripple shows the deposit, but your ledger does not.

Ripple Custody (Vault), formerly Metaco Harmonize, runs each change as a signed intent under your policies. The keys are held in your HSM or split across MPC nodes (Ripple). Ripple's Wallet product, from Palisade, is out of scope here.

Who runs or builds each part of a Ripple Custody setup

A deposit waits in quarantine, is released by the firm's own service and then becomes a position in the firm's ledger.

The firm

Client channels

Clients see positions and request withdrawals in e-banking or the app.

Firm ledger

The firm keeps custody positions in core banking, a register of client positions or an issuer's supply ledger.

Keys

The firm's HSMs hold the keys, or the firm has two of the four MPC nodes and Ripple runs the other two.
Ripple

Ripple Custody (Vault)

Ripple Custody provides domains, policies, intents, the vault, the Events API and webhooks.
Protofire builds

Ledger connector

The connector stores each event ID once, posts once per transfer and stage, and catches up through the Events API.

Release and withdrawal services

They submit releases after the firm's screening and propose withdrawals as the firm's own users.

Daily reconciliation and exit runbook

The reconciliation sets Ripple's reports against the ledger and the chain, and the runbook lists the steps that move assets out.

What Ripple Custody leaves to your own services

A Ripple Custody deposit waits for your own service to release it, and a missed webhook leaves a gap in your records.A transfer from outside the platform waits in quarantine until someone submits a release intent (Ripple). Even under Ripple's automatic release policy, "each release is still a v0_ReleaseQuarantinedTransfers intent that someone must submit". Ripple's SDKs ship an agent that submits releases. The agent checks no screening result, so your own screening has to gate its submissions.

Webhook pushes cannot be your record of events. By default, a webhook delivery that fails three quick retries is marked FAILED, and automatic retries stop (Ripple).

Mapping clients to accounts is also your firm's work. On pooled funds, Ripple writes: "Mapping users to tenants and virtual accounts is the customer's responsibility unless the Omnibus UI or customer integration enforces a stricter model" (Ripple). A crypto firm has a further rule. MiCA asks a custodian to open a register of positions "in the name of each client" (MiCA Article 75).

New Ripple Custody versions change what a booking connector reads. On premises, support for version 1.26 ended on 10 October 2026 (Ripple). Long-term releases cannot be skipped (Ripple). On premises, the new indexer in version 1.43 starts at the chain tip when its last processed block is more than 24 hours old. The indexer does not replay the blocks it skipped. If these changes are left to chance, the first sign is a client asking where a deposit went.

[...] tokenisation challenges traditional operating models. It raises questions about how investor rights are recorded, how registers are maintained, how segregation works, and how responsibilities are allocated across the value chain.
Natasha Cazenave, Executive Director, European Securities and Markets Authority · Speech at the BVI Fund Operations Conference, 24 February 2026

Ripple Custody history, deployment, licenses and versions

Company
Ripple bought Metaco, maker of Harmonize, in May 2023 (Ripple). Version 1.11 of 23 February 2024 is the first listed as Ripple Custody (docs).
Deployment and keys
Ripple Custody runs on premises, in Ripple Cloud with the firm's own vault and HSM, or in Ripple Cloud with MPC. With MPC, signing is 3-of-4 across two Ripple nodes and two customer nodes (docs).
Regulatory status
Ripple Payments Europe S.A. holds EU MiCA authorization for exchange and transfer. The same entity "is not authorised to provide custody and administration of crypto-assets on behalf of clients" (Ripple).
Ripple trust company
Ripple describes Standard Custody & Trust Company as its "New York Department of Financial Services (NYDFS)-regulated limited purpose trust company" (Ripple, 26 October 2026).
Ripple trust bank
Ripple "has been granted final approval" by the OCC to charter Ripple National Trust Bank. The bank may offer custody "upon opening" (Ripple, 26 October 2026). The OCC's conditional approval dates from 12 December 2025 (OCC).
Long-term release
Version 1.43 LTS was released on 5 October 2026 and is supported until 5 October 2027 (docs).

We checked these facts against Ripple's documentation in November 2026. Protofire integrates Ripple Custody for firms that have chosen it.

What a Ripple Custody integration from Protofire includes

Deposits released after your compliance team clears them

A deposit becomes the client's once your compliance team has cleared it. Your own user signs the release. Ripple counts a proposer's signature as the first approval (Ripple). So the release policy that you sign decides whether the proposer's signature alone frees the funds. Protofire builds the release service, which submits releases as your compliance-domain user.

One ledger posting per transfer and stage

Finance sees one posting per transfer and stage. A deposit is posted as pending while quarantined and as the client's position once released and confirmed. Protofire builds the connector that stores each event ID, posts under the transfer ID and catches up from the Events API after an outage.

Client withdrawals that follow your authority matrix

A client's withdrawal request blocks the position at once. The request reaches Ripple as a signed intent under your policies, and the position is debited at Confirmed. Protofire builds the service behind your client channels and the mandate-limit checks that run before an intent is proposed.

A daily reconciliation that finance can sign

At the cut-off, ledger positions are matched against Ripple's Position and Movement Reports and the chain. Transfers that are still quarantined or Pending are listed under their status, apart from settled ones. Protofire builds the reconciliation job, which checks control totals. Where assets are pooled, the job also covers the Omnibus Position Report.

Version upgrades tested before production, and an exit runbook

Each new Ripple Custody release runs against your bookings before production. Protofire writes the regression suite and an exit runbook that moves assets as well as keys.

Our record: reserve data, Safe and a published bank blueprint

Three parts of Protofire's record apply to Ripple Custody work.They are reserve records checked against outside data, approval by several parties and a published bank blueprint that names Ripple Custody.

Reserve records matched to outside data

Protofire built and operated the reserve-data pipeline behind 15+ proof-of-reserve and real-time attestation deployments for asset-backed tokens, for a large auditing firm. The daily reconciliation follows the same practice: it checks your records against a source that you did not write. Our proof of reserve page describes the service.

A Safe{Wallet} interface for approval by several signers

The Safe Foundation's blog of 15 October 2025 names Protofire among the independent teams that operated an instance of the Safe{Wallet} interface (Safe Foundation). A Safe and a Ripple Custody policy both decide who has to agree before funds move. Protofire's Safe multisig work has its own page.

A bank blueprint that lists Ripple Custody

Protofire's In-App Crypto Brokerage blueprint lists Ripple Custody among the custody vendors that a bank can rent. The blueprint puts the link between custody and core banking on the build side.

Order of work on a Ripple Custody project

  1. Step 1

    An engineer reads your Ripple Custody setup first

    A Protofire engineer first reads your Ripple Custody setup and the ledger that it feeds. A written proposal follows with findings, phases and the first step that we recommend.
  2. Step 2

    The release service and the connector come first

    Deposits wait in quarantine until the release service exists, so Protofire builds it and the connector first. Withdrawals, the reconciliation and the regression suite follow your launches.
  3. Step 3

    Alerts routed to a named person

    Alerts for a failed webhook delivery, a transfer left in quarantine or a failed posting reach a named person with a runbook. Your on-call team takes the alerts, or Protofire takes them under a written scope through our managed onchain operations service.
  4. Step 4

    Your firm keeps the code, keys and approvals

    The code, configuration and runbooks are yours, and your staff keep the keys and the approval roles. Protofire lists each custody and stablecoin platform that we connect on our integrations hub.

How work with Protofire starts

You send your Ripple Custody version and deployment model.You also send your domain tree and the ledger that Ripple Custody feeds. The first written proposal then splits the release service, connector and reconciliation into phases for that setup. The terms below apply to each phase, as set out on how we work.

Proposal
In writing, one business day after the discovery call: findings, a plan in phases and the first step we recommend.
Price
Fixed per phase when you commission it, against written acceptance criteria. Overruns inside them are ours to absorb, invoices follow delivered milestones, and you can stop at any phase boundary. Anything we operate after launch is priced in the proposal as its own recurring line, with the notice to end it.
Ownership
Code we write for you, contracts, the keys and credentials this work creates and the accounts your infrastructure runs in are yours by contract, within the license of any third-party software involved. Keys that a custody platform or a staking provider holds under its own key model stay with it under your contract; every other custody key stays with you or the custodian you appoint. Where the scope places something on servers we rent, it says what moves to you and when. An NDA is available from your first message, and we sign a data processing agreement (DPA) together with it.
After launch
Delivery closes with a hypercare window and a defect warranty, with their terms written into the proposal. A service we operate continues under its written scope until that scope ends.
Access
Read-only by default. A role that can start requests only if your written scope names one; never a signer, approver, administrator, key holder or recovery role on your contracts, wallets or custody platform. Services we build call each platform on credentials your staff issue and keep in your vault. Anything that approves or moves funds runs in your environment, and a scope under which we operate a service lists every write call it makes. Where the scope has us operate nodes, validators, monitors, explorers or indexers, it names the role and any key we hold on those servers, and in your own cloud account you can remove it.
Licenses
Protofire is an engineering firm and holds no financial or crypto-asset license; licensed activity stays with you and your providers.

How we work shows a worked proposal.

When a Ripple Custody build is smaller or not needed

Three setups need less of this build, or none of it.

  • Your core vendor has the link to Ripple Custody. A bank on Avaloq's platform, as at BBVA Switzerland, starts with the core vendor. So does a Hogan bank once DXC's integration reaches it. Protofire adds the release service, reconciliation and channels around that link.
  • You want branded wallets for end users, fast. For a payment firm or e-money institution with that need, Ripple's Wallet product from Palisade is a lighter option than this Vault build.
  • Your book is small. With one asset and a few clients, positions can be matched from the daily Position Report and the operator UI. That works until volume calls for the connector.

Your team and Ripple keep responsibility for platform upgrades, HSM and MPC node operations and support tickets. The firm that offers custody holds the custody license. Protofire holds no custody license and no signing key. Protofire also holds no approval role or recovery role, and gives no legal opinions on MiCA or DORA.

FAQ

What is a Ripple Custody integration?
A Ripple Custody integration connects Ripple Custody (Vault) to the ledger and controls of a regulated firm. Quarantined deposits are released after the firm's screening, and each transfer is posted once per stage. Client withdrawals are sent as signed intents under the firm's policies. A daily reconciliation matches the ledger against Ripple's reports. Protofire builds the integration, and the firm holds the keys and approval roles.
Who can build a Ripple Custody integration for a bank, a crypto firm or a token issuer?
Protofire builds the firm's own side of a Ripple Custody integration. That side covers the release service and the ledger connector, plus client withdrawals and the reconciliation. The ledger differs by type of firm. A bank books a pending position first, then a position in the core's custody subledger. A crypto firm keeps a register per client domain or virtual account. An issuer tracks outstanding supply against its reserve or fund register.
Does Ripple Custody already connect to Avaloq, Hogan or Temenos?
Partly. As of November 2026, Protofire found a published link for two cores. BBVA described Metaco Harmonize as fully integrated as SaaS on Avaloq's platform when BBVA Switzerland moved its custody service (BBVA, December 2023). DXC announced in January 2026 that it integrates Ripple's custody and payments technology into its Hogan platform (DXC). Protofire found no published link for Temenos or FIS. Our Temenos integration page covers booking into Temenos.
What happens when a Ripple Custody webhook is missed?
The ledger connector that Protofire builds catches up through the Events API. The connector pages the API from the last event ID that it processed, 100 events at a time. It sets the scope to SelfAndDescendants, so client domains are included. The default scope returns just the queried domain's own events (Ripple). The Events API has no time filter, so the stored ID is the cursor. Sequence numbers can skip values, so a gap alone proves nothing.
Who signs client withdrawals, and what can Protofire access?
A machine user in your Ripple Custody domain signs client withdrawals. Its key is held in your HSM or KMS, and your policies limit its role to client withdrawals. The later workflow steps belong to your staff. Protofire gets a read-only user, and its operators hold no user that can propose, release or approve.
Can a crypto firm pool client assets in one Ripple Custody omnibus wallet?
Yes, for non-native tokens on Solana, XRPL and EVM networks. In version 1.43, native coins such as ETH, SOL and XRP are excluded from omnibus (Ripple). Funds sent straight to the omnibus wallet are credited to a host account. The reconciliation that Protofire builds alerts on a negative host balance. MiCA asks custodians to keep client crypto-assets apart from their own on the distributed ledger (Article 75(7)). Your counsel decides how a host account fits that rule.
How does an exit from Ripple Custody work, and where does Protofire appear in our DORA register?
Ripple's exit tools cover the keys, and Protofire's runbook builds and broadcasts the transfers. From version 1.29, an HSM-backed firm can hold its own copy of the wrapped seed. Neither tool builds or broadcasts a transaction (Ripple). Positions are matched before and after the transfers. In the Annex III template of Regulation 2024/2956, building the connector and release service is an ICT development service (S02). Operating the connector adds ICT operation management (S14). Your risk and legal teams decide what is filed. Our DORA guide explains both classes.

Get a proposal

Tell us what you are building. An engineer reads it, we have a short call, and the written proposal follows within one business day.

Luis MedeirosField CTO, reads every request · LinkedIn

A demo or repository link also works.