Cryptocurrency donations require a nonprofit to decide which assets and networks it can receive, who controls the receiving wallet, how gifts are acknowledged, and how records are reconciled. This contemporary guide is separate from Xperience 2018; it makes no claim that the conference discussed or accepted cryptocurrency.
Acceptance policy before promotion
Identify eligible assets, supported networks, minimum or maximum acceptance rules, approval roles and the decision to hold or convert a gift. A ticker symbol alone is not enough: the donor and organization must use a network the receiving process supports. Publish an address only after a second person verifies both asset and network.
Custody and reconciliation
Set access controls, backup and incident procedures before a wallet is used. Keep a transaction hash, timestamp, asset, network and valuation method with the accounting record. Reconcile the blockchain receipt against the organization’s ledger and donor acknowledgement; do not ask a donor to disclose a seed phrase or private key.
| Control | Question to resolve | Evidence to retain |
|---|---|---|
| Acceptance | Which token and network are supported? | Approved policy and revision |
| Custody | Who can authorize access or recovery? | Access review and incident plan |
| Reconciliation | How is receipt matched to the ledger? | Hash, time and valuation method |
Tax and donor communication
Tax treatment and charitable acknowledgements vary by jurisdiction and donor circumstances. In the United States, organizations should consult current IRS guidance and qualified tax professionals. This page is not legal or tax advice and does not promise a deduction.
Questions before publishing a donation policy
Should a nonprofit hold every digital-asset gift?
No. It should adopt a documented holding or conversion policy and account for custody responsibilities.
Can a donor use any network for a familiar token?
No. The receiving process must support the exact asset and network.
Is this topic part of Xperience 2018?
No such claim is made. This is a separate present-day explainer.
Build a gift-acceptance process before announcing a wallet
A nonprofit should decide whether it can accept a digital asset before publishing a wallet address or payment link. Board policy may need to specify eligible assets, networks, minimums, donor restrictions, geographic limits, conversion timing and the circumstances in which a gift will be declined. Assign an owner for each decision and document approvals so that a public donation page matches the organization’s actual operational capability.
Choose the receiving process deliberately. Direct custody gives the organization control over keys and recovery but creates security and staffing responsibilities. A processor may handle conversion or transaction monitoring, but introduces its own fees, terms, supported assets and counterparty considerations. Compare those models against the organization’s controls and recordkeeping needs rather than assuming one is universally preferable.
Verify the transaction and protect access
Before a campaign launches, have two authorized people confirm the asset, network and destination. Use role-based access, strong authentication and an incident-response plan. Decide how backups are stored and who can authorize recovery. Reconcile incoming transactions against the address, transaction hash, timestamp and internal gift record. If the organization converts a gift, record the provider, time and valuation method used. Never request a donor’s seed phrase or private key.
Communicate clearly with donors
A donation page should identify accepted assets and networks, explain any processor or conversion arrangements, and tell the donor what confirmation means. A network submission is not the same as a completed internal acknowledgment. Explain whether the organization can accept restricted gifts and how a donor can contact the appropriate staff member without sending credentials.
Accounting and tax review
Digital-asset accounting and charitable-contribution rules depend on jurisdiction and transaction details. In the United States, consult current IRS publications and qualified tax and accounting professionals before setting receipt language or reporting procedures. Do not promise a deduction or a particular valuation outcome based on a general guide. Keep policy, transaction records and acknowledgments available for the organization’s own review.
Board decisions before announcing a wallet
Before a donation address is published, the board should record who is responsible for each part of the process:
- Who approves the acceptance policy?
- Which assets and networks may the organization receive?
- Who checks wallet addresses and controls access?
- When, and by whom, is a gift converted?
- What valuation method and transaction record support accounting?
- How will restricted gifts be handled?
- What is the response if a donor sends an unsupported asset or uses the wrong network?
The donor-facing instructions should match these decisions, including the contact route for questions and the information the organization will never request.
This practical guide is separate from the archive of the 2018 conference. It does not claim Xperience 2018 accepted cryptocurrency or covered these procedures. See the event record for the organizer’s historical technology framing.
Questions about nonprofit crypto controls
Should a nonprofit publish a wallet address before setting policy?
No. It should first approve eligible assets, networks, custody and accounting procedures.
Should an organization request a donor seed phrase?
No. A seed phrase or private key must never be requested.
Does this guide provide tax advice?
No. Consult current official guidance and qualified advisers for the relevant jurisdiction.
Operational checklist for a small organization
- Approve a gift policy and list the assets and networks the organization can accept.
- Choose custody or a service provider after reviewing access, recovery, fees, conversion and counterparty terms.
- Have a second authorized person verify the receiving destination before it is published.
- Define who checks transaction status, records the asset and informs the donor.
- Reconcile the transaction to the accounting ledger using a documented valuation method.
- Review the process after a staff change, provider update or security incident.
Questions for a processor
Ask which exact assets and networks are supported, whether assets are converted automatically, how fees are assessed, what records are available for reconciliation, and who controls the wallet or keys. Determine how a donor restriction is carried through the process and what happens if someone sends an unsupported asset. A provider’s interface does not replace the organization’s own approval and accounting controls.
For the donor, explain the expected confirmation, the organization’s acknowledgment process and a safe way to ask for help. Do not ask for a private key, password or seed phrase. If an address is wrong, stop further instructions and consult a qualified technical provider; an irreversible transaction may not be recoverable.