Custody and transfer create different boundaries
Citing Bloomberg, BlockBeats reported that Deutsche Bank plans to offer custody and transfer of BTC, ETH and selected stablecoins to institutional and corporate clients later this year after regulatory approval, with tokenized instruments considered for future support. Custody focuses on keys, books and segregation, while transfers add recipient, approval, network and sanctions risks; one generic control is insufficient. Custody addresses key control, segregation, books and recovery, whereas transfer services introduce destination, network, business authorization and travel-rule information. The two activities need different approval matrices even when one bank performs both. An outbound blockchain transfer can cross jurisdictions and encounter sanctions exposure while the assets remain inside the same client relationship. Controls therefore have to follow the transaction, not merely the custodian's institutional identity. A custodian should periodically demonstrate segregation between customer assets and its own holdings and reconcile blockchain balances, internal books and independent records. Differences need an exception workflow with ownership and deadlines. This evidence is more useful than a single proof-of-assets snapshot because it tests whether transfers and fees continue to be recorded correctly through normal operations. Regular reconciliation also detects operational errors that may resemble theft on-chain but originate from delayed or duplicated internal postings.
What support for selected stablecoins implies
Selected stablecoins implies a limited scope, requiring checks on asset, network, redemption entity and address allowlists rather than ticker alone. The phrase selected stablecoins leaves the supported inventory unspecified. Clients should verify contract address, issuer, redemption rights, freeze functionality and network before sending funds, because identically named assets on another chain may not be credited. Product interfaces also need versioned notices when support or collateral treatment changes. A logo or ticker alone is not reliable evidence that a particular token contract belongs to the bank's approved service scope. Stablecoin issuers may retain freeze, upgrade or redemption powers that alter how an incident can be handled. Those governance features belong in customer agreements and asset risk scoring, alongside reserve and jurisdiction information. Supporting two tokens with the same economic label does not mean that recovery options, legal claims or operational dependencies are identical. Network-specific freeze procedures should be tested before an emergency, because issuer capabilities and response channels vary across supported assets.
How institutions can enforce four-eyes approval
Four-eyes approval should cover instruction, review, signature and release, while large transfers link beneficiaries, business purpose and source of funds. Four-eyes governance can separate instruction entry, business review, compliance review and signing release, with higher thresholds for new destinations or large amounts. An allowlisted wallet should not remain trusted indefinitely: beneficial ownership changes, sanctions updates and a deteriorating risk score can all trigger revalidation. The audit trail should also identify who changed limits, who approved an exception and whether the broadcast transaction ultimately confirmed, failed or was replaced. When a mistaken transfer or suspicious deposit occurs, frontline support should not promise recovery before technical and legal review. The case needs shared custody among compliance, operations and counsel, preserving transaction identifiers and all communications. A controlled workflow reduces contradictory instructions and provides evidence if an issuer, exchange or authority must later participate. A documented decision tree prevents urgency from bypassing authorization while preserving the option to contact a receiving venue quickly.