Skip to content

Anchorage Digital Integration for Lenders, ETF Programs and Stablecoin Brands

Anchorage Digital Bank's API leaves balance history, deposit attribution, a client sub-ledger and webhook replay to the firm. Protofire builds them for lenders, ETF programs, stablecoin brands and firms serving clients there. Protofire engineers helped build the Gnosis Safe web app with Gnosis's team from 2019 to 2021.

Luis Medeiros

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

On this page
  1. Overview
  2. Where integrations break
  3. Anchorage Digital facts
  4. What you get
  5. Account models
  6. Vault layout
  7. Why Protofire
  8. How the project runs
  9. How work starts
  10. Not the right fit
  11. Related guides and services
  12. FAQ

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

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

What Anchorage Digital Bank does and what your side decides

An Anchorage Digital integration starts where the bank's job ends. Anchorage Digital Bank keeps the keys in its HSMs. The bank signs after your approvers and its own staff have agreed (Anchorage Digital). The bank is on the OCC's list of active trust banks as of 30 September 2026, under charter 25243 (OCC list).

Your side decides which client a deposit belongs to, which balance counts at the cut-off and what a lost notification does to a booking. Each of these gaps breaks the daily match if nobody owns it.

For example, say you have chosen Anchorage Digital for custody. At the daily close, finance asks for yesterday's balance per client, and the API returns today's.

Who runs each part of an Anchorage Digital movement

An order waits for your approvers and Anchorage Digital's review. The result then returns to your ledger through webhooks, API reads and stored snapshots.

The firm

Order and client systems

The desk or app places the order, and the ledger records each client's position.

Approvers

Vault members meet each quorum on enrolled iPhones or iPads.
Anchorage Digital

Vaults, review and HSM signing

Anchorage Digital holds custody, its staff review each transaction, and the bank signs in its HSMs once both approvals are present.

API and webhooks

Anchorage Digital offers REST v2 and Atlas settlement calls, plus signed webhooks that include a record ID.
Protofire builds

Connector and attribution queue

The connector starts transfers and withdrawals, and the queue posts the sender of each held deposit.

Snapshots and webhook replay

Jobs save balances at your cut-off, match them to the ledger and replay missed events.

Four ways an Anchorage Digital integration breaks

Each of these four failures starts with documented Anchorage Digital behavior.The result is a wrong balance, a client who cannot see funds or a payment booked twice.

Balances returned only as of the request

GET /v2/wallets "has no date parameter" (Anchorage Digital). So the API gives a balance only as of the request. Protofire's job stores a snapshot at your cut-off, in your time zone, with the request time. The job flags a late snapshot. The API filters transactions on whole UTC dates, so a business day outside UTC spans two dates. The job therefore pulls both dates and assigns each final record to your day by its dateTime.

Deposits held until the sender is attributed

A deposit from an unknown sender shows SUCCESS on-chain. But the deposit is left out of availableBalance until its sender is attributed (Anchorage Digital). Protofire's queue lists those held deposits. Your compliance staff confirm the sender. The service then posts the attribution with an API key that your organization issues and can revoke.

Webhooks canceled without an alert

Anchorage Digital retries a notification up to 50 times over 75+ hours and then cancels it with no alert (Anchorage Digital). Events can also arrive twice or out of order. Protofire's receiver checks the signature and stores each event first. The receiver drops an event with a repeated message_id. A scheduled job replays the missed events.

Withdrawals that stall or book twice

A second withdrawal from a wallet with one already in flight fails with 409. A request answered 201 can still fail after quorum, for example when the network fee is short (Anchorage Digital). Protofire's connector sends each request with an idempotentId and reuses it on a retry. The connector books each movement on the transaction id. The held amount clears at SUCCESS and returns at FAILURE, REJECTED or EXPIRED.

Facts about Anchorage Digital's bank and API

Bank
Anchorage Digital Bank National Association, the bank for custody, settlement, staking and governance (Anchorage Digital).
API
The API is REST v2, and each call includes an Api-Access-Key. Sensitive endpoints also need an Ed25519 signature from a key pair that the firm brings (Anchorage Digital).
Approvals
Each vault has at least 3 members and a quorum of 2. Sub-quorums apply to withdrawal, staking and governance (Anchorage Digital).
Rate limit
All API keys share 20 requests a second per organization, with bursts up to 100 (Anchorage Digital).
Reports
The API returns balances as of the request and transactions by UTC date. Monthly statements and daily balance reports are in the dashboard. The audit-events API was in development in November 2026 (Anchorage Digital).

Checked November 2026 against Anchorage Digital's documentation and legal page and the OCC's trust bank list.

What your finance, compliance and operations teams get

A daily close that finance can sign

Wallet balances at your cut-off are tied to the ledger and to the signed sums of the day's transactions. Each difference is recorded on a break list.

Clients credited once their sender is known

A held deposit is no longer a support ticket. Compliance sees an aged list of deposits still on hold.

Transfers and withdrawals posted once

Transfers and withdrawals start in your order or treasury system. They use a key whose permission group lists the allowed operations and destinations. Each movement is posted a single time.

Client positions that add up to the pooled wallets

Where Anchorage Digital approves an omnibus account, you need one position line per client and asset. If Protofire's service cannot map a deposit, the deposit waits in suspense for a person.

Atlas settlements and stablecoin conversions on your books

For venues and lenders, Protofire builds the Atlas propose, accept and authorize calls. Authorization goes through your quorum or uses a key that you hold (Anchorage Digital). For a stablecoin brand, one Anchorage Digital endpoint handles mint, redeem and bridge (Anchorage Digital). Protofire books each leg. Anchorage Digital Bank issues Western Union's USDPT, which was announced in May 2026 (Anchorage Digital).

A named owner for each canceled webhook or failed posting

A canceled webhook or a failed posting goes to a named person, who works from a runbook that your staff own.

Who keeps client balances in each Anchorage Digital account model

The account model decides whether you build a client ledger at all.

Who keeps client balances
Anchorage Digital. Each end client has one vault and wallet and is KYC'd by Anchorage Digital's compliance team. In Anchorage Digital's words, "You don't build or maintain a ledger on top" (Anchorage Digital).
Build
An onboarding flow sends each KYC package, and webhooks feed the client app. Wire instructions for the vault's one USD wallet show the firm's legal name.

Why withdrawals and automated transfers need separate wallets

Withdrawals that need a quorum and automated payouts should not share a source wallet.A pending withdrawal holds the transfers queued behind it until the withdrawal is broadcast. A transfer skips the quorum for each request, because its destination was approved once. A withdrawal goes to the quorum each time. Up to 50 transfers can queue behind one source wallet (Anchorage Digital). Requests should name the WALLET. If a request names the VAULT, Anchorage Digital picks the first-created wallet for the asset, "even if that wallet has been archived".

One Anchorage Digital limit is outside the vault design. "Any user added to the organization can see activity across all vaults in the org," says Anchorage Digital's security page (Anchorage Digital). In November 2026, the same page listed vault-level visibility gating as coming soon. Until it ships, a firm that must wall off client data by team does so in its own systems.

Our record: the Gnosis Safe web app and a lending blueprint

Protofire's work covers approval logic, which decides who must agree before funds move, and a lender's books when a custodian holds the collateral.

The Gnosis Safe web app, 2019 to 2021

Protofire engineers helped build the Gnosis Safe web app with Gnosis's team from 2019 to 2021. Gnosis's issue tracker of July 2020 refers to "Gnosis/Protofire users and bots" on the project. A Gnosis Safe transaction runs once its set number of owners have approved it. An Anchorage Digital quorum asks the same question. Protofire's part is the systems that record the quorum's result. Our Safe multisig work has its own page.

Crypto-Backed Lombard Loans blueprint

Protofire's Crypto-Backed Lombard Loans blueprint maps the loans, interest and liquidations that a lender books into its core ledger. The blueprint covers the case where a custodian such as Anchorage Digital holds the collateral.

Protofire starts with read access, and your organization issues write keys

  1. Step 1

    Review of your account structure

    A Protofire engineer reads your vault layout, quorums and target ledger. A written proposal then scopes the connector, the queue and the match of snapshots to your ledger.
  2. Step 2

    API keys issued by your organization

    Protofire reads through an API key with the Read vault activity permission. Your organization issues and revokes the write keys for attributions and allowlisted transfers, which are kept in your own vault. Where Protofire operates a connector through managed onchain operations, the written scope names each write call.
  3. Step 3

    Who holds the custody keys and the signing key pair

    Anchorage Digital holds the custody keys. With BitGo self-custody wallets, by contrast, the firm keeps the user and backup keys. The Ed25519 key pair that signs your API requests is kept in your own key store. Your runbook names a deputy for each approver.

How work with Protofire starts

You send your Anchorage Digital account structure, the ledger that the movements must reach and your daily cut-off time.The terms in this section 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 an Anchorage Digital project with Protofire does not fit

  • You are outside the US and Singapore. Anchorage Digital's services "are not marketed to residents outside the US and Singapore" (Anchorage Digital).
  • You run a brokerage on the fully managed tier of Anchorage Digital's Crypto-as-a-Service, whose page says "You launch with no build" (Anchorage Digital).
  • Your client program uses segregated vaults at light volume. The work that remains is onboarding calls and webhook handling.
  • You make a few moves a month, or you keep books for your own holdings. Bitwave lists an Anchorage Digital connector.

Anchorage Digital holds custody and the bank license and reviews each transaction. Your staff hold the approvals. After launch, Protofire holds no Administrator role, quorum seat, enrolled device or private signing key.

FAQ

What is an Anchorage Digital integration?
An Anchorage Digital integration connects a firm's ledger and order systems to custody at Anchorage Digital Bank. The integration starts transfers and withdrawals through the REST API and books each record on its transaction id. It also attributes held deposits, stores a balance snapshot at the firm's cut-off and replays dropped webhooks. Protofire builds Anchorage Digital integrations. Approvals still happen in Anchorage Digital's iOS app.
Who can build an Anchorage Digital integration for a lender, an ETF program or a stablecoin brand?
Protofire, an engineering firm, builds the firm's side of an Anchorage Digital integration. Anchorage Digital supplies custody, the API and its own review. Protofire builds the connector and the attribution queue. Protofire also builds the snapshots, the sub-ledger and the webhook replay. Protofire's record includes multi-party approval on Safe and a blueprint for loans against custodied collateral.
Why is a deposit confirmed on-chain but missing from availableBalance?
The deposit is held because its sender has not been attributed yet. The deposit becomes available once the firm posts the originator's name, country and wallet type. A trusted source or a travel-rule message can also attribute the deposit. Deposits from VASPs above Anchorage Digital's $2,100 travel-rule reporting threshold are attributed automatically once a participating VASP's message arrives. But Anchorage Digital's docs note that "This isn't instant" (Anchorage Digital).
What happens to Anchorage Digital webhooks while our endpoint is down?
Anchorage Digital retries the webhooks and then drops them. A dropped notification is "permanently canceled and won't be redelivered" (Anchorage Digital). The endpoint itself remains registered. A replay job that reads the transaction list, each open movement and the deposit-attributions list recovers the missed states.
Do our approvers need iPhones?
Yes, approvers need iPhones or iPads. Anchorage Digital supports iOS devices only, because approval keys are stored in the device's Secure Enclave (Anchorage Digital).
Which core banking or accounting systems does Anchorage Digital already feed?
Anchorage Digital already feeds accounting tools: Bitwave lists a connector. For a core banking system, Anchorage Digital's developer docs give the building blocks: its API, reports and webhooks. Client positions reach a core through a connector that the firm builds or commissions.

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.