Skip to content

BitGo Integration for Banks, Payment Firms, Crypto Firms and Issuers

Banks, payment firms, crypto firms and issuers on BitGo still have to book transfers per address, run the endpoint behind BitGo's webhook policy and reconcile daily. Protofire builds those parts. Our multisig record: we deployed Safe on 120+ EVM networks, where it secures $2B+.

Luis Medeiros

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

On this page
  1. Overview
  2. Where booking breaks
  3. Keys, policy and exit
  4. BitGo facts
  5. What you get
  6. Why Protofire
  7. How the project runs
  8. How work starts
  9. Not the right fit
  10. Related guides and services
  11. FAQ

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

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

Why BitGo withdrawals are booked twice or missed

A BitGo integration can book a client withdrawal twice, or not at all, because of how BitGo reports transfers. A Go Account withdrawal has an internal BitGo hash as its txid. Its onchain hash appears once the withdrawal confirms (BitGo). BitGo sends a webhook for failed and removed transfers when failure states are switched on (BitGo). BitGo sends no webhook for transfers with a risk indicator, such as a SELFDESTRUCT opcode (BitGo).

None of BitGo's wallet types keeps a ledger of client positions inside a pooled wallet. So a firm that holds client assets in a pooled wallet builds one. Without that ledger, finance rebuilds balances by hand and chases each transfer that missed a webhook.

Who owns each part of a BitGo integration

BitGo holds the wallets, policies and webhooks. Your side holds the ledger and the approvals. Protofire builds the two parts between them.

The firm

Apps and operations desk

Clients ask for withdrawals, and your staff take BitGo's video ID calls.

Client ledger

Your core banking system or register of positions records client positions per BitGo wallet and address.
BitGo

BitGo enterprise

BitGo provides Custody, Self-custody and Offline Vault wallets, Advanced Wallets, one Go Account, policies and webhooks.
Protofire builds

Approval service

BitGo's webhook rule calls your endpoint, which decodes the half-signed transaction and answers 200 or not.

Booking connector and daily reconciliation

The connector stores each webhook, books per wallet and address, and compares positions with BitGo's holdings report and the chain.

Four BitGo behaviors that put wrong positions in your ledger

Each of these four problems starts with documented BitGo behavior and ends as a wrong position in your ledger.

Two hashes for one Go Account withdrawal

If a Go Account withdrawal is booked on its first txid, the onchain transaction arrives later as a second line. BitGo deduplicates on a normalized hash, which on account chains can differ from txid. The connector that Protofire builds books each transfer under wallet, coin, normalized hash and address entry. It matches Go Account withdrawals on onChainTxId.

Failed, removed and flagged transfers

A failed transfer shows a value of zero and records the amount in intendedValueString. A withdrawal that BitGo marks removed after a chain reorganization remains in transit until BitGo shows it as confirmed, failed or replaced. Protofire switches failure states on and lists the day's transfers as a backstop. We send transfers with a risk indicator to a review queue.

Withdrawal retries after a timeout

The connector that Protofire builds blocks the client's balance when an order is accepted and gives the order a sequenceId. BitGo confirms one send per sequenceId per wallet and fails later attempts. So a retry after a timeout is refused instead of paid again. If BitGo rejects the retry, the connector reads the existing transfer.

Fee rebuilds after approval

After an approval, the transaction is rebuilt with current fees, so the fee settles after approval. BitGo's guides disagree on who rebuilds the transaction. The wallet guide says BitGo rebuilds it. The withdrawal overview tells self-custody clients to rebuild and re-sign it themselves. The connector that Protofire builds handles both paths and books the fee from the final transfer.

Keys, policy and exit on each BitGo wallet type

Your BitGo wallet type decides who signs a withdrawal, what it waits for and how you exit BitGo.On custody wallets and the Go Account, BitGo holds the keys. So a withdrawal waits for BitGo's operators and a video ID call with your staff (BitGo). The Go Account is an off-chain BitGo ledger, so no chain read shows it.

On self-custody wallets, you hold the user and backup keys. BitGo holds the third key and co-signs. Your counsel decides who counts as custodian toward your clients.

You set and approve your BitGo policy. BitGo offers rules on destination, amount, velocity and webhook, and a second admin approves a policy change. Under a webhook rule, BitGo asks your own server before it signs (BitGo).

On custody wallets, where you hold no key, BitGo's service level agreement makes service credits the sole remedy for API downtime (BitGo). Your legal team weighs that remedy against DORA's contract rules. A self-custody wallet recovered with the user and backup keys moves funds without BitGo and bypasses BitGo's policies (BitGo). The recovery runbook names who may hold both keys.

BitGo wallet, withdrawal and webhook facts

Wallet types
BitGo offers Custody, Self-custody, BitGo Offline Vault and Advanced Wallets, plus one omnibus Go Account per enterprise (BitGo).
Custody withdrawals
BitGo's docs give 24 hours, with signing by BitGo Bank & Trust operators. BitGo Europe gives 48 hours excluding weekends and German bank holidays, with video ID within 24 hours. Large or suspicious withdrawals take longer (BitGo Europe).
Whitelists
Self-custody whitelists lock 48 hours after creation (BitGo).
Webhooks
BitGo signs webhooks with HMAC and makes up to seven retries. If an endpoint returns ten non-retryable 4xx answers within an hour, BitGo blocks the URL for all webhooks registered to it (BitGo).

Checked November 2026 against BitGo's documentation and legal pages.

What a BitGo integration changes on your side

An approval endpoint your auditors can test

BitGo asks your server before it signs a withdrawal that a webhook rule covers. The rule comes from your authority matrix. Protofire builds the endpoint and deploys it in your infrastructure. We run one test withdrawal per webhook answer and per approver path.

Client positions per wallet and address

The connector posts transfers in your core banking system (Temenos, Avaloq, FIS or in-house) or register of positions, including Go Account moves and memo-chain deposits. Each fiat leg is matched to its Go Account deposit. Protofire builds the connector and a runbook for transfers that BitGo marks failed, removed or replaced.

A daily break list finance can sign

Protofire's daily reconciliation matches positions per wallet against the chain and against BitGo's holdings at the snapshot time you set. Each break shows BitGo's transfer state. For an issuer, mint and burn orders are matched to reserve movements in the Go Account.

Migration onto BitGo in reconciled waves

Assets leave your current custodian in waves. Both custodians are reconciled before and after each wave. Protofire sets up wallets, whitelists and policies first. Our MiCA migration service covers the move of a whole client book between licensed firms.

Alerts with a named owner and a runbook

When a webhook URL is blocked or an EVM transaction is stuck, an alert reaches a named person with a runbook. The same applies when BitGo's large-outflow circuit breaker trips or the gas tank runs low. Protofire's managed onchain operations team or your staff can work these alerts.

Our record: Safe multisig and a blueprint that names BitGo

Protofire's multisig work applies to the approval logic of BitGo's self-custody wallets.BitGo's self-custody multisig wallets sign with two of three keys.

Safe multisig on 120+ EVM networks

Protofire deployed Safe on 120+ EVM networks, where it secures $2B+. The Safe Ecosystem Foundation wrote in May 2026 that Protofire "has been contributing to Safe since 2018". Our Safe multisig work has its own page.

BitGo in our Euro Stablecoin Issuance blueprint

Protofire's Euro Stablecoin Issuance blueprint names BitGo among the custody and tokenization vendors that an issuer can rent. The blueprint sets out the mint governance and reserve checks around those vendors. If you use BitGo beside Fireblocks or another platform, our integrations hub shows which modules apply to both.

How a BitGo project with Protofire runs

  1. Step 1

    Review of your BitGo setup before the call

    Before the call, an engineer reads your BitGo wallet types and enterprise structure. The engineer also reads your target ledger and authority matrix. A proposal follows, with findings, phases and a first step.
  2. Step 2

    Policy rules set before the whitelists lock

    Protofire drafts policy rules from your authority matrix and sets them before self-custody whitelists lock. The approval service behind the webhook rule runs in your infrastructure. Your staff keep its signing key, credentials and rules.
  3. Step 3

    Booking, daily reconciliation and a test for each path

    Booking and the daily reconciliation come next. Each path gets a test. The tests cover a withdrawal for each webhook answer, returns and stuck EVM transactions. They also cover the custody withdrawal windows. Payment legs and monitoring follow your launches.
  4. Step 4

    Ownership and access after launch

    The code, configuration and runbooks are yours. Your staff keep the wallet passphrase and the Express server. Protofire reads through a long-lived access token with read scopes and an IP restriction, as BitGo requires in production. A token that can withdraw is issued only when your written scope names one, and a spending limit caps that token.

How work with Protofire starts

You send us your BitGo wallet types, your enterprise structure and the ledger that each transfer must reach.The terms for each phase are 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.

Four BitGo setups that need little outside engineering

  • You hold long-term assets in custody wallets and make a few withdrawals a month. BitGo's web app, video ID and CSV reports cover that use. BitGo calls custody wallets "the least flexible wallet type if you're sending assets frequently".
  • You run a Crypto-as-a-Service front end, and BitGo's child enterprises are the client record. Then BitGo's licenses cover KYC, custody and fiat rails. The build is the app, webhooks and reports, as described on our Crypto-as-a-service integration page.
  • You need accounting data for your firm's own treasury and hold no client assets. Off-the-shelf accounting tools import BitGo data.
  • You are an exchange that builds Off-Exchange Settlement endpoints. BitGo supports the exchange through design and testing, so Protofire's part is limited to the exchange's ledger.

Protofire holds no key or key share in a BitGo enterprise, and no custody license. We take no admin, approver or signer role, and no video ID or recovery role. After go-live, Protofire operates the integration only under a written scope. Your counsel handles licensing questions and legal opinions on delegating custody.

FAQ

What is a BitGo integration?
A BitGo integration is the build on the firm's own side of BitGo's custody wallets, self-custody wallets or Go Account. It has three parts. A connector books each transfer per wallet and address in the firm's ledger. An approval service answers BitGo's webhook policy calls. A daily reconciliation matches positions against BitGo's holdings and the chain. Protofire builds BitGo integrations for firms that have chosen BitGo.
Who can build a BitGo integration for a bank or a payment firm?
Protofire, an engineering firm, builds the firm's own side of a BitGo integration. Protofire builds the booking into core banking or a client ledger and the approval service. Protofire also builds the payment legs and the daily reconciliation. BitGo publishes no core banking connector. Accounting tools such as Bitwave import BitGo data, but they do not book client positions in a bank's core.
Does a BitGo integration differ for a bank, a payment platform, a crypto firm or a fund?
Yes. A BitGo integration differs because each type of firm keeps a different record. A bank books one position line per client and BitGo wallet in the core's custody subledger. A payment platform on Crypto-as-a-Service books float and payouts in its own ledger, beside a Go Account per end client. A crypto firm keeps a register of positions under MiCA (Article 75(2)). A fund or issuer matches holdings reports to its administrator's file. For the bank case, see our Temenos integration page and the custody to core banking guide.
What happens to withdrawals if our approval endpoint goes down?
A withdrawal under a BitGo webhook policy rule depends on your approval endpoint's answer. An answer other than 200 triggers the rule's action, which is to deny the withdrawal or send it to named approvers (BitGo). BitGo adds that a slow or unresponsive server "may delay transaction processing". BitGo's docs give no timeout. Agree on the action with your compliance team before go-live, and run the endpoint in more than one instance.
Who handles the Travel Rule on BitGo hot wallets?
The firm handles the Travel Rule on BitGo hot wallets. BitGo's FAQ for its regulated entities in Europe, Singapore and the UAE says "the Travel Rule does not apply to hot wallets" (BitGo). So BitGo runs no Travel Rule check on hot wallets. When BitGo cannot identify the sender of an incoming transfer, the receiver declares the sender's details. BitGo says "there is no API or ability to download this information".
Can an EU crypto firm delegate custody to BitGo Europe?
Yes, if the firm's counsel confirms that delegation to BitGo Europe fits its license and client terms. ESMA's April 2026 statement says MiCA "specifically prohibits CASPs from outsourcing or delegating certain services, namely custody, to entities not authorised as CASPs themselves" (ESMA). ESMA's register lists BitGo Europe GmbH as authorized by BaFin for custody.
What goes into our DORA register and exit plan when BitGo is in the chain?
DORA asks you to list BitGo and each integrator in your register of information. DORA also asks you to hold an exit strategy where BitGo supports a critical or important function. BitGo Europe's custody agreement sets a two-year term, 60 days' notice before renewal and 90 days to withdraw coins after termination. On custody wallets and the Go Account you hold no key, so exit means withdrawing the assets within those 90 days. Under Regulation 2024/2956, building the integration is an ICT development service (S02). Operating the integration adds S14. Your risk and legal teams decide what is filed (DORA guide).

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.