Major Bank Offering Bitcoin Custody Should We Use: Vendor Availability, Custody Due Diligence, and the Allocation-Custody Separation
Institutional Custody Vendor Selection Process
This memo is published by Bitcoin Treasury Analysis, an independent decision-record instrument for Bitcoin treasury governance.
When a Trusted Vendor Introduces a New Product Category
When a major bank offering bitcoin custody approaches the organization and the question becomes whether we should use the service, two distinct governance decisions collapse into one conversation. The first decision—whether the organization's treasury framework includes bitcoin as a permissible allocation—is an allocation decision governed by the organization's investment policy, risk tolerance, and governance infrastructure. The second decision—whether a particular custodian is appropriate for holding the organization's bitcoin—is a vendor selection decision governed by operational due diligence, contractual terms, and counterparty risk assessment. The conflation of these decisions occurs naturally when a trusted banking partner introduces the custody product, because the relationship's existing trust level may be perceived as answering both questions simultaneously. This record covers the governance posture when a major bank offering bitcoin custody surfaces the allocation question through the vendor channel, the structural separation between the allocation decision and the custody decision, and the due diligence obligations that attach to each.
This record does not evaluate whether the bank's custody offering is appropriate or whether the organization's treasury framework accommodates bitcoin. It documents the governance architecture that applies when a custody product offering intersects with an unresolved allocation question.
Vendor Availability as a Non-Allocation Rationale
The availability of a bitcoin custody product from a major financial institution does not constitute an allocation rationale within a structured governance framework. Allocation decisions are evaluated based on the asset's role within the treasury, the organization's risk tolerance, the allocation's interaction with existing holdings, and the governance infrastructure available to oversee the position. That a particular custodian now offers the service addresses the operational feasibility of holding bitcoin but does not speak to the strategic question of whether holding bitcoin serves the organization's treasury objectives.
Organizations frequently encounter this dynamic with other asset classes. A bank that introduces a new fixed-income product, a private credit fund, or a structured deposit vehicle does not, by introducing the product, create a governance rationale for allocating treasury funds to it. The product introduction creates an opportunity that the governance framework evaluates on its merits. The same structural analysis applies to bitcoin custody: the bank's decision to offer the product reflects the bank's assessment of market demand and its own strategic objectives, not an assessment of the product's suitability for any particular client's treasury.
The governance record documents whether the organization's interest in bitcoin preceded the bank's custody offering or was initiated by it. This distinction matters because it defines whether the vendor offering is responsive to an existing organizational objective or generative of a new one. An organization that was already evaluating bitcoin allocation and receives a custody offering from its banking partner encounters a sequencing alignment between allocation interest and vendor capability. An organization that had not considered bitcoin allocation until the bank introduced the product confronts a vendor-driven consideration that the governance framework evaluates differently.
The Trust Transfer Problem
Established banking relationships carry accumulated trust built through years of service, reliability, and regulatory compliance. When the banking partner introduces a bitcoin custody product, the trust accumulated in the banking relationship may transfer to the custody product without independent evaluation—a cognitive shortcut that the governance framework does not accommodate. The bank's competence in traditional banking services does not establish competence in digital asset custody, which involves different technical infrastructure, different risk vectors, and different operational capabilities than those required for conventional banking.
Digital asset custody requires cryptographic key management, blockchain-native transaction processing, and security architecture that differs fundamentally from the safekeeping of traditional financial assets. A bank entering the digital asset custody space may be operating with newly built or recently acquired capabilities whose operational track record is limited. The relationship manager presenting the product may not possess the technical depth to address the organization's questions about key management architecture, disaster recovery for digital assets, or insurance coverage specific to cryptographic loss events. Trust in the relationship does not substitute for due diligence on the specific product.
The governance record documents whether the organization's evaluation of the custody offering was informed by independent due diligence specific to the bank's digital asset capabilities or relied primarily on the trust established through the existing banking relationship. This documentation captures a governance distinction that may be significant in future review: whether the organization made a custody decision based on product-specific analysis or based on relationship-level confidence.
Custody Due Diligence Independent of the Allocation Decision
If the organization has independently determined that bitcoin belongs in its treasury—through a governance process that evaluated the allocation on its merits—the custody decision proceeds as a separate vendor selection exercise. Due diligence on the bank's custody offering encompasses the technical infrastructure for key management, the insurance coverage available for digital asset losses, the contractual terms governing access and withdrawal, the bank's regulatory status with respect to digital asset services, and the operational history of the digital asset custody platform.
Contractual terms deserve particular attention because digital asset custody agreements may differ materially from the deposit and safekeeping agreements that govern the organization's existing banking relationship. Withdrawal procedures, transaction authorization requirements, liability limitations, and dispute resolution mechanisms specific to the digital asset custody agreement define the governance relationship between the organization and the custodian for the bitcoin position specifically. These terms may be more restrictive, less favorable, or structured differently than the terms governing the organization's other accounts with the same bank.
The governance record documents the scope and depth of the custody due diligence as conducted, distinguishing between due diligence that evaluated the bank's digital asset capabilities specifically and due diligence that relied on the bank's general reputation and regulatory standing. This documentation creates a record of the organization's custodial decision-making process that is separable from the allocation decision record, reflecting the structural independence of the two governance decisions.
Relationship Dynamics and the Soft Pressure of Banking Partnerships
A custody offering from the organization's primary banking partner introduces relationship dynamics that the governance framework accounts for without treating as dispositive. The organization may perceive commercial pressure to adopt the new product—whether because the bank has invested in building the capability and expects its clients to participate, because the relationship manager's compensation is tied to product adoption, or because declining the offering may be perceived as a signal about the health of the broader banking relationship. These dynamics do not create a governance rationale for the allocation, but they create an environmental condition that may influence the governance process.
The governance record captures whether relationship dynamics were present in the organization's evaluation of the custody offering, not to attribute improper influence but to document the full governance context within which the decision was made. A decision record that acknowledges the relationship context and demonstrates that the allocation and custody decisions were evaluated independently of that context produces a stronger governance artifact than one that omits the context entirely.
Regulatory Status and Insurance Coverage of the Custody Offering
The regulatory framework under which the bank offers digital asset custody may differ from the framework governing its traditional banking services. Some jurisdictions authorize banks to offer digital asset custody under existing banking charters; others require separate licensing, registration, or approval. The regulatory status of the custody service affects the protections available to the organization as a client: deposit insurance that covers traditional banking deposits may not extend to digital assets held in custody, and the regulatory oversight mechanisms applicable to the bank's traditional services may apply differently—or not at all—to its digital asset custody operations.
Insurance coverage for the custody offering warrants specific examination within the due diligence process. The bank's general insurance coverage may not extend to digital asset custody losses, and the specific insurance available for the custody offering—whether carried by the bank, obtained through a specialty insurer, or offered as an optional add-on—defines the risk transfer framework that protects the organization's position. Coverage limits, exclusions, and claims procedures specific to digital asset losses may differ materially from the insurance terms the organization is accustomed to under its traditional banking relationship.
The governance record documents the regulatory status of the custody offering and the insurance coverage applicable to it, because these elements define the protective framework surrounding the organization's bitcoin holdings if the custody service is adopted. An organization that assumes the bank's traditional regulatory and insurance protections extend to the custody offering without verifying this assumption creates a governance gap that the record identifies.
Sequencing: Allocation Decision Before Custody Decision
The governance framework addresses allocation and custody as sequential decisions: the allocation decision determines whether bitcoin belongs in the treasury; the custody decision, which follows only if the allocation is approved, determines how the bitcoin is held. When a banking partner introduces a custody product before the organization has resolved the allocation question, the sequencing reverses—the custody solution arrives before the governance framework has determined whether a custody solution is needed.
This reversed sequencing creates a governance condition that the record documents. An organization that evaluates the custody offering and proceeds to evaluate the allocation has been influenced by the availability of a solution before confirming that a problem exists. The governance framework addresses this sequencing by requiring that the allocation decision be evaluated and documented independently, with the custody evaluation proceeding only after the allocation has been authorized through the organization's governance process. The governance record captures the actual sequencing of the organization's deliberation, documenting whether the allocation decision preceded, followed, or was conducted simultaneously with the custody evaluation.
Conclusion
The governance record documents that a major bank offering bitcoin custody has created an organizational question in which allocation rationale and vendor selection are structurally distinct decisions that the governance framework evaluates separately. The bank's introduction of a custody product does not constitute an allocation rationale; the existing banking relationship's trust does not substitute for product-specific due diligence; and the custody decision proceeds on its own governance track independent of whether the allocation itself has been authorized. The conflation of these decisions represents a governance risk that the record identifies as a condition requiring structural separation within the organization's deliberative process.
The determination is recorded as of the date the custody offering was received and reflects the allocation posture, due diligence status, and relationship dynamics in effect at that point.
Constraints and Assumptions
The bank's custody offering terms, capabilities, and regulatory status are specific to the offering as presented and may change after the documentation date. The organization's investment policy framework's treatment of bitcoin allocation depends on the policy's specific terms. Relationship dynamics between the organization and the banking partner are subjective conditions that the governance record documents based on available information. Subsequent changes in the bank's custody platform, the organization's allocation posture, or the regulatory environment create new governance conditions rather than amendments to this record.
Record Summary
This record describes the governance stance surrounding a major bank offering bitcoin custody and the organizational question of whether to use the service, capturing the allocation-custody separation, trust transfer risk, custody due diligence requirements, and relationship dynamics. The vendor offering functions as a governance catalyst that introduces the allocation question through a custody channel, and the governance record captures the structural conditions within which both the allocation and custody decisions are evaluated.
The record does not evaluate whether the bank's custody offering is suitable or whether bitcoin belongs in the organization's treasury. It documents the governance architecture that applies when a vendor-driven consideration intersects with an unresolved allocation question as a formal artifact of institutional record.
No recommendation, projection, or execution authorization is contained in this memorandum. The governance record stands as a contemporaneous artifact of structured vendor-consideration analysis, documenting the conditions under which the custody offering was assessed without substituting for the decision authority of the board, committee, or officer empowered to determine the allocation or custody outcome.
Framework Context
Cross-Domain Intersection Index
The risk is often not the decision itself, but the absence of a durable record explaining how it was made.
Generate Decision Record$995 · 12-month access · Unlimited analyses
A Bitcoin Treasury Decision Record is a formal governance document that classifies an organization's readiness to allocate Bitcoin as a treasury asset and records the basis for that classification under a defined standard.
View a completed Decision Record →Framework References
Medical Practice Bitcoin Treasury
Bitcoin Treasury Compliance Officer Responsibilities
Bitcoin Treasury Policy Integration Existing Controls
Relevant Scenario Contexts
Manufacturing — Considering (5M) →
