Crypto trust charters and community banks: the binding decision sits in the core

The week

On December 12, 2025, the Office of the Comptroller of the Currency conditionally approved five national trust bank charters for digital-asset firms. Two were new charters: First National Digital Currency Bank, owned by Circle, and Ripple National Trust Bank. Three were conversions of state trust companies: BitGo, Fidelity Digital Assets and Paxos. The permitted activities differed by firm, and each still had to meet conditions before receiving final approval. National trust banks cannot take deposits or offer FDIC-insured accounts. Bank trade groups had urged the OCC to reject the applications, arguing they gave nonbanks a lighter route into the banking system. The approvals came five months after the GENIUS Act created a federal framework for payment stablecoins, while regulators were still drafting the rules to implement it.

For the largest banks, the December approvals were a competitive signal. For community banks and credit unions, they were practical. Federally supervised counterparties for digital-asset custody and, for some firms, stablecoin activity were about to exist. Fintech partners, business customers and core providers would soon ask what the institution planned to do. Earlier in this series we noted that bank crypto questions tend to arrive as custody questions. The charters made custody more ordinary. They left a smaller institution with three decisions, in sequence: what scope to accept, who holds the assets, and how any of it connects to the core. The third is the one that binds.

Scope: which activities, if any

A trust charter does not make a stablecoin a deposit. That shapes how a community institution frames the question. Holding a payment stablecoin for a customer is not the same as offering an insured account, and disclosures, risk appetite and board approvals differ accordingly.

Options run from doing nothing, to accepting stablecoin-funded transfers from a partner, to settling some business payments on a stablecoin rail, to letting customers hold tokens through a custodian. Each step adds obligations. Sanctions screening and anti-money-laundering monitoring must cover blockchain addresses as well as names. Liquidity planning must account for redemptions outside banking hours. Complaint handling must cover transfers that cannot be reversed. A one-page position, approved by the board, that names the chosen step and the reasons is enough at this stage. The charters made higher steps more feasible. They did not make them necessary.

Scope also sets the compliance build. Even the second step, accepting stablecoin-funded transfers, means the institution needs some way to screen the originating wallet, which usually means a blockchain analytics provider or a partner that provides screening under contract. Someone in the BSA function has to understand the alerts well enough to file a suspicious activity report. Examiners will ask how the board reached its decision and how the controls were tested. Each step up the ladder adds a vendor, a policy and a training need, and the costs are easier to count before the first customer asks than after.

Custody: who holds the assets

Before December, a community bank that wanted to offer digital-asset services usually depended on state-chartered trust companies or less regulated providers. A national trust bank is a more familiar counterparty. It is examined by the OCC, owes fiduciary duties and has a clearer resolution path than a technology vendor.

That lets custody run through the 2023 interagency guidance on third-party risk management. The points to press are segregation of client assets, key management and who can authorize transfers, insurance and its exclusions, audit rights, and what happens if a conditional approval is never finalized. Institutions should ask counsel how customer assets would be treated in an insolvency, because the answer depends on account structure and documents, not only on the charter.

The core: how it connects

This is the decision most institutions underestimate. Most community banks and credit unions run on a small number of core processors. Anything they offer has to appear in online banking, statements, the general ledger, contact-center screens and regulatory reports. Digital assets bring balances that move at any hour, prices that change by the minute for some tokens, and transaction identifiers unlike card or ACH references.

There are three patterns. In the first, the partner holds everything and the institution shows customers a link out. The core stays untouched, but the customer relationship weakens and the institution sees little of the activity it is accountable for. In the second, balances come into the core as a memo post or sub-ledger. Customers get one view, but the institution depends on its core vendor’s roadmap, pricing and timing. In the third, the institution builds a thin integration layer that pulls partner data, reconciles it and feeds the ledger and digital channels. That gives the most control and requires engineering capacity many small institutions lack.

Whatever the pattern, reconciliation is the control that matters most. Each day, the institution must show that what its systems say a customer holds matches what the custodian holds. That needs a defined cut-off time, because blockchain activity has no business day. It needs pricing rules for any non-stablecoin asset, and break-handling with named owners. Statements need language that distinguishes custodied tokens from deposits. Call report and other regulatory reporting treatment should be settled with accounting advisers before launch.

The contracts tie this together. The custody agreement should specify data feeds, formats and timing that the integration layer can rely on. The core contract may need amending to permit memo posting or new transaction types, and core vendors often price those changes separately. An institution that signs with a custodian before talking to its core provider can find the integration costs more than the product earns.

The sequence matters for that reason. Choosing a custodian before setting scope invites a product nobody approved. Choosing a custodian before checking the core’s capabilities locks the institution into whichever partner the core vendor happens to support. Most of the cost of getting this wrong shows up in operations, reconciliation breaks and exam findings rather than in the technology bill.

With hindsight

The December approvals started a process rather than finishing one. Through the spring of 2026 the five charters remained conditional. In July, Circle’s trust bank was reported to have received final approval, the first of the group to do so. The OCC proposed its rule implementing the GENIUS Act for stablecoin issuers under its jurisdiction in February 2026. The statute’s July 2026 deadline for implementing rules passed without a final OCC rule, and the Comptroller said in August that the agency aimed to finalize it by November. Bank trade groups’ objections did not go away.

For smaller institutions, the shape of the decision held. An institution with a written scope, custodian criteria and a view on core integration can answer a partner or business customer quickly. One without them risks letting a vendor’s roadmap decide. With final rules still pending, the integration and reconciliation work remains the part that can sensibly be prepared now.