A nonprofit organization receives an unsolicited cryptocurrency donation from a supporter. The gift arrives on the Ethereum network as USDC, but the organization’s finance team has no infrastructure to receive it, no process to value it for tax records, and no clear path to convert it to operating funds. The donor expects a receipt. The board requires accounting compliance. The IRS requires documentation. Most charities face this situation unprepared, treating cryptocurrency as an anomaly rather than an operational reality.

Self-custody wallets designed for individual users can become the foundation of nonprofit treasury management when configured correctly. Phantom Wallet, originally built for Solana but now supporting Ethereum, Bitcoin, Base, Polygon, and other networks, offers features suited to this problem: multi-signature account structures, transaction previews that reveal what assets move and where, hardware wallet integration for operational security, and the ability to hold assets across multiple blockchains without relying on centralized custodians. But implementing it for a charity requires understanding not only how to receive and hold the funds, but also how to document their value, track them through accounting systems, and satisfy both nonprofit governance and federal tax requirements.

Why self-custody makes sense for nonprofit treasuries

Most nonprofits that accept cryptocurrency today use a third-party service: a custodian such as Coinbase Commerce, BitPay, or a specialized nonprofit crypto platform. These services handle conversion, custody, and tax reporting. They also take a fee, require ongoing account maintenance, and concentrate the organization’s digital assets with a single provider. If that provider faces regulatory action, closure, or security compromise, the organization loses access or faces unexpected costs to recover.

Self-custody using a wallet like Phantom shifts both the responsibility and the control. The organization holds its own keys, not a service. No intermediary can freeze, seize, or lose the funds through their own operational failure. The organization avoids fees charged by custody providers and retains the ability to move assets to any recipient without permission from a third party. For a nonprofit with a stable board, clear governance, and a willingness to implement basic operational security, this model reduces dependencies and operational costs.

The trade-off is that the organization becomes responsible for key management, backup procedures, and compliance. There is no customer service team to call if a transaction is approved by mistake. There is no insurance if a private key is compromised. The organization must develop internal policies covering who can approve transactions, under what conditions, and how those approvals are documented. That governance burden is real, but it is not unique to crypto. The same care applied to signing authority for bank checks, credit cards, and investment accounts applies here, with the added benefit that transaction history is cryptographically immutable.

Setting up a multi-signature Phantom account for governance

A single-signature Phantom account, where one person controls the recovery phrase, creates an obvious governance problem. One person leaving, being compromised, or acting unethically puts all funds at risk. Multi-signature structures require approval from multiple parties before funds can move. Phantom’s support for hardware wallets such as Ledger provides a foundation for this: each signatory can hold a key on a dedicated device that never exposes the private key to an internet-connected computer.

The practical setup involves designating a threshold: a 2-of-3 arrangement means that any two of three designated signatories must approve a transaction. A 3-of-5 arrangement requires three approvals out of five possible signers. The board might select the executive director, treasurer, and one independent board member, creating a structure where no single person can unilaterally move funds but the organization can operate without requiring all parties present. This mirrors practices already familiar from nonprofit banking: checking account signatories, approval thresholds for expenditures, and documented approval chains.

Implementing this in Phantom requires understanding the wallet’s architecture. Phantom’s phantom account management tools let the organization create watch-only addresses, manage multiple accounts, and organize assets by purpose. A separate account for restricted gifts, endowment funds, and operating reserves keeps these funds logically distinct. Each account can be configured with different access permissions: an endowment account might require all three signatories, while an operating account might require only two.

The hardware wallet integration is not optional for nonprofit use. A Ledger device connected to each signatory’s computer, rather than storing keys in Phantom directly, means that even if the computer is compromised, the private key remains on the hardware device and cannot be extracted. The transaction flows to the Ledger, is signed there, and returns to the wallet without the private key ever being exposed online. This setup requires more deliberate action from signatories but provides substantially stronger security than storing keys in browser extensions.

Accepting donations and documenting fair market value

A donor sends cryptocurrency to the organization’s Phantom wallet address. The transaction settles on the blockchain. The organization now holds the asset, but from a tax and accounting perspective, the process is just beginning. The IRS requires nonprofits to report the fair market value of donated assets as of the date of donation. For cryptocurrency, that means recording the USD (or applicable fiat) value at the moment the transaction was confirmed, not when it was later converted or valued.

This is where phantom wallet features that provide clear transaction history become essential. Phantom displays each transaction with a timestamp, the asset received, the amount, and whether it came from an external address. This information is the foundation of your donation record. Take a screenshot or export the transaction details immediately. More importantly, cross-reference the donation with a price feed from a reputable source—CoinGecko, CoinMarketCap, or your accountant’s preferred provider—to establish the USD value at that exact time.

Create a donation form requiring donors to provide their name, address, and the intent of their gift (unrestricted, restricted to a program, or a pledge for future use). When the donation is received, pair that form with the blockchain transaction record and the fair market value calculation. Your accountant uses this bundle to create a charitable contribution receipt showing the date, the asset, the quantity, and the USD value. The donor uses this receipt for their own tax deduction. Your organization uses it for Form 990 reporting and restricted fund accounting.

Common mistakes include valuing the donation at the price at conversion time rather than donation time, failing to document the donor’s intent, and not retaining the transaction screenshot. If the donor transferred USDC on January 15 when it was worth $1.00, and your organization converted it to USD on January 20, the donation is valued at January 15’s price, not January 20’s. That difference matters for tax reporting and for your organization’s records. The solution is discipline: create a spreadsheet with columns for donation date, donor name, asset, quantity, price on donation date, USD value, and donor intent. Update it immediately after each transaction settles.

Managing assets across multiple supported networks

Phantom’s support for Ethereum, Bitcoin, Base, Polygon, and other networks creates both opportunity and complexity for nonprofit donors. A donor might send USDC on Ethereum because that is what their exchange provided. Another donor sends Bitcoin directly. A third sends Solana tokens. Your organization now holds the same value in different assets on different networks, each with different characteristics, fees, and custody implications.

The operational solution is to consolidate into a standard settlement asset. Many nonprofits choose USDC or USDT on Ethereum because those stablecoins are widely supported and can be converted to USD efficiently. A donor sends Bitcoin to the Phantom wallet, and your organization uses Phantom’s built-in swap feature to convert it to USDC on Ethereum. This step should happen as soon as practical after the donation is received and the fair market value has been recorded. The organization records the donation in USD (using the value at donation time, not conversion time), then converts the asset and records the conversion as a movement of funds, not a new donation or taxable event.

This approach requires establishing a clear policy: which assets the organization will accept, where they should be sent (which blockchain), and how quickly they should be converted. A policy stating “we accept donations in USDC on Ethereum, or equivalent value in other assets converted within 48 hours” gives donors clear guidance and gives the organization a predictable process. Phantom supported networks include the major chains where donors are likely to send funds, so the wallet can receive across multiple blockchains without requiring separate wallets for each network.

Tax documentation and reporting obligations

The IRS requires nonprofits filing Form 990 to report the total value of noncash contributions received. If your organization received $50,000 in cryptocurrency donations during the year, that figure appears on the return. More important, the organization should maintain contemporaneous written acknowledgments from each donor, showing the date of the contribution, the description of the property (asset name and quantity), the fair market value, and a statement of whether any goods or services were provided in return.

In cryptocurrency’s context, “contemporaneous” means the acknowledgment is provided by the nonprofit before the donor files their tax return, not six months later. In practice, this means sending a receipt within a few days of receiving the donation. The receipt should show the exact USD value assigned to the donation, based on the price feed used and the date evaluated. Keep records of the price feed source: a screenshot from CoinGecko with the timestamp, for example. If the IRS later questions the valuation, you can demonstrate that it was reasonable and well-documented.

Your accountant or bookkeeper should work with your organization’s tax preparer to ensure that cryptocurrency donations flow correctly into restricted and unrestricted fund accounting. A gift restricted to a specific program must be reported separately from unrestricted general support. If a donor contributed to your endowment, that asset may be held in perpetuity, and the contribution should not appear in operating revenue. The blockchain transaction is immutable, but your accounting interpretation of it determines tax reporting accuracy.

One additional requirement: if your organization later sells the cryptocurrency or converts it, the IRS may view that transaction as a disposition of property. If USDC you received when it was worth $10,000 is later converted to USD when stablecoins trade at a different rate, the difference is a gain or loss. Nonprofits are generally exempt from capital gains tax, so the result is not a tax liability, but the transaction should still be recorded in your accounting system to create a complete trail. Your accountant can show that the asset was donated, valued at receipt, and later converted at specified terms.

Operational security and backup procedures

A nonprofit’s Phantom wallet is not a personal account. It is a financial asset with governance, audit, and security requirements. The recovery phrase that underpins the wallet is equivalent to the nonprofit’s bank account access credentials. It must be protected accordingly. The recommended approach is to divide the recovery phrase into shares, store each share in a separate secure location, and require multiple shares to be produced before the wallet can be recovered. This prevents any single person from unilaterally accessing the funds.

One common practice is to split the recovery phrase into shares and provide them to the board treasurer, board secretary, and an external advisor such as the organization’s CPA or attorney. Each party holds one share and stores it in a secure location—a safe deposit box, a fireproof safe, or a vault. If the wallet device is lost or compromised, the organization can recover it by producing two of the three shares. If one party becomes unavailable, the organization is not locked out.

This backup procedure must be tested annually. At least once per year, the organization should conduct a recovery drill: produce the shares, recover the wallet to a test device, confirm that it contains the expected funds and history, then wipe the test device. This test is not optional. It ensures that the backup procedure actually works and that responsible parties understand the process. It also surfaces problems: shares that have degraded, locations that are no longer accessible, or signatories who no longer know where their share is stored.

To download Phantom safely and securely, the organization should retrieve it only from official sources: the official Phantom website, the Chrome Web Store, or the official iOS and Android app stores. Do not download from links in emails or third-party websites. A counterfeit version could steal the recovery phrase or redirect funds. Verify that the official extension or app is published by Phantom Labs before installing.

Converting to fiat and operational cash flow

At some point, the nonprofit needs operating funds in USD. The cryptocurrency in the Phantom wallet must be converted to fiat currency and moved to a bank account. This step introduces a regulated intermediary: an exchange or on-ramp service that connects blockchain assets to the traditional banking system. The organization might use Kraken, Coinbase, or a blockchain banking service such as Anchorage. The choice matters for compliance, fees, and documentation.

When a nonprofit converts cryptocurrency to USD through an exchange, the exchange may file a Form 1099-K reporting the transaction to the IRS. While nonprofits are generally exempt from income tax, the Form 1099-K creates a reporting requirement that must be reconciled with your tax return. The IRS expects that the charitable contributions are reported separately from unrelated business income or other transactions. Your tax preparer should be informed of any Form 1099-K to prevent misreporting.

The operational workflow is: donation received in crypto, fair market value recorded, asset held briefly, converted to a stablecoin on Ethereum (if not already), moved to an exchange, converted to USD, and deposited to the nonprofit’s bank account. Each step should be documented: transaction hashes from the blockchain, screenshots of exchange confirmations, bank deposit receipts. This complete trail demonstrates that the funds were charitable donations, that they were valued appropriately, and that they were converted at arm’s-length rates, satisfying both the nonprofit’s internal audit and external IRS scrutiny.

Governance policies and board oversight

A nonprofit accepting cryptocurrency should adopt a written cryptocurrency donation and management policy. This document establishes which assets the organization will accept, on which networks, how they will be valued, who has authority to approve transactions, and what conversion and accounting practices apply. The policy should address a specific scenario: when a donor sends an unsolicited cryptocurrency gift that does not fit the organization’s preference. Will you accept it? Convert it immediately or hold it? Who decides?

The board should review this policy annually, particularly if there are changes in organizational leadership, tax law, or Phantom’s supported networks. The policy should also address what happens if a key signatory becomes unavailable. If the treasurer, who controls one of three multi-sig keys, becomes unable to participate in approvals, the organization should have a documented process to rotate keys and designate a replacement. This process is not a transaction to execute casually; it involves producing the recovery phrase, importing the wallet to a new device, and establishing new multi-sig arrangements with new signatories.

Audit considerations are important. If your organization has an external audit, the auditor will want to verify that the cryptocurrency holdings are real, that they are valued correctly, that the donations are legitimate, and that the transactions are authorized. Provide the auditor with blockchain transaction records, the policy document, board meeting minutes approving cryptocurrency acceptance, donation receipts, and the valuation methodology. Demonstrate that the transaction history in Phantom is complete and has not been altered. The immutability of the blockchain is a substantial advantage here: unlike digital ledger entries that could theoretically be modified, blockchain transactions can be verified independently by anyone.