App Store Review Guidelines Cryptocurrency 3.1.5 Guide: What It Means, How to Evaluate It, and What to Avoid

Q: Can my app include in-app purchases for cryptocurrency?

Yes, but you must use Apple's in-app purchase system for digital goods and services. Purchasing cryptocurrency itself with fiat currency is typically handled through external payment processors, but you must still comply with the fee disclosure and licensing requirements of 3.1.5.

Apple’s App Store Review Guidelines are the gatekeeper for every app on iOS. Section 3.1.5 specifically addresses cryptocurrency, wallet, and exchange applications — but the rules are dense, and non-compliance can block your app from the App Store entirely. This guide breaks down what Guideline 3.1.5 actually requires, how to assess your app against it, and the common mistakes that trip up developers.

⚖️ What Is App Store Guideline 3.1.5?

Apple’s App Store Review Guidelines are divided into multiple sections covering safety, performance, business, design, and legal compliance. Guideline 3.1.5 falls under the Business category and is titled “Cryptocurrency”. It establishes the conditions under which apps may offer cryptocurrency-related features — including wallets, exchanges, trading, and mining — while remaining in compliance with App Store policies.

The Scope of 3.1.5

Guideline 3.1.5 applies to any app that facilitates the transmission, storage, or trading of cryptocurrency. This includes:

Wallet apps that allow users to send, receive, or store crypto assets.
Exchange apps that enable buying, selling, or swapping of cryptocurrencies.
Mining apps that permit users to mine crypto (with specific restrictions).
DeFi (decentralized finance) interfaces that interact with smart contracts or blockchain protocols.
Payment apps that process crypto transactions for goods or services.

📌 Key point: Guideline 3.1.5 is not a blanket ban. It sets a compliance framework. Apps that meet the requirements can be approved; those that don’t will be rejected.

📋 Core Requirements for Crypto Apps Under 3.1.5

To pass App Store review, your crypto app must satisfy several concrete criteria. These requirements are designed to protect users, ensure legal compliance, and maintain the integrity of the App Store ecosystem.

Wallet Functionality and Custody

Transparency: You must clearly disclose whether your app hosts user funds (custodial) or merely facilitates transactions on-chain (non-custodial).
Security: Custodial wallets must implement robust security measures (multi-factor authentication, encryption, cold storage).
Private keys: If your app controls private keys, you must explain how keys are stored and who has access.
Recovery: Provide clear instructions for account recovery and backup, especially for non-custodial wallets where users control their own keys.

Exchange and Trading Features

Licensing: If your app operates as a regulated exchange, you must provide evidence of relevant financial licenses or registrations.
Fee disclosure: All trading fees, withdrawal charges, and spread costs must be clearly displayed before a user confirms a transaction.
Market data: Price feeds must be sourced from reputable providers; you cannot manipulate or misrepresent market pricing.
Order execution: You must explain how orders are matched and executed, especially if you operate an order-book exchange.

Mining and Staking Restrictions

Apps that allow users to mine cryptocurrency are permitted only if the mining process is off-device (i.e., cloud mining or remote mining services). On-device mining is not allowed due to battery and performance concerns.
Staking features must clearly explain lock-up periods, rewards, and risks of slashing or loss.

🔍 How to Evaluate Your App’s Compliance

Before submitting your app to the App Store, run through this practical evaluation framework. Use the checklist below to identify gaps and address them proactively.

✅ Pre-Submission Checklist

Clearly state custodial vs. non-custodial model in your app description and privacy policy.
Disclose all fees (trading, withdrawal, network gas) in an in-app section before user action.
If custodial, provide a security overview (encryption, multi-sig, cold storage).
Include a clear risk warning in the app — especially for non-custodial wallets.
Confirm that your app does not mine crypto on the device itself.
Ensure your privacy policy covers cryptocurrency data handling (public keys, transaction history).
If you offer exchange services, have your financial licenses or registration documents ready for Apple’s review.
Test all transaction flows to ensure fee amounts match disclosures.

🧩 Regulatory Checkpoints

Guideline 3.1.5 also requires compliance with applicable laws in the territories where your app is available. This is not legal advice, but you should consider:

AML/KYC — Does your app implement Anti-Money Laundering and Know Your Customer procedures where required?
Sanctions — Are you screening users against sanction lists?
Tax reporting — Are you informing users about their potential reporting obligations?
Data residency — Are user data stored in compliance with GDPR, CCPA, or other privacy regulations?

⚠️ These are not App Store requirements but may affect your ability to operate legally — and Apple may ask about them during review.

📊 Compliant vs. Non-Compliant Approaches

The table below contrasts common implementation choices that determine whether your app aligns with Guideline 3.1.5 — or risks rejection.

Feature / Aspect	✅ Compliant Approach	❌ Non-Compliant Approach
Custody model	Disclosed clearly as custodial or non-custodial in app description, privacy policy, and in-app notices.	Vague or misleading statements; claiming “decentralized” while holding private keys.
Fee disclosure	All fees (trading, withdrawal, gas) shown in a dedicated section before any transaction is confirmed.	Fees buried in fine print, revealed only after user approval, or not disclosed at all.
Mining	Mining performed off-device (cloud/remote); app only displays status and rewards.	On-device mining that drains battery and overheats the device.
Licensing	Exchange apps provide evidence of financial licenses or registrations when required.	Operating without required licenses or failing to supply documentation to Apple.
Risk warnings	Prominent in-app risk warnings about price volatility, loss of funds, and smart contract risks.	No risk warnings, or warnings that are hidden, vague, or downplay risks.
Private key handling	Non-custodial: keys stay on device; custodial: keys stored with strong encryption and multi-sig.	Keys stored in plaintext, transmitted over insecure channels, or accessible by unauthorized staff.

🚫 Common Mistakes to Avoid

Even experienced developers run into trouble with Guideline 3.1.5. These recurring errors are the most frequent reasons for rejection — and they are entirely avoidable.

Failing to distinguish custodial from non-custodial. Apple reviewers will ask. If your app controls private keys but claims to be “decentralized,” you will be rejected.
Incomplete fee transparency. Many apps disclose trading fees but omit withdrawal fees or network gas costs. All costs must be visible before the user commits.
On-device mining. Even if you think it’s benign, Apple strictly prohibits mining that runs on the device due to performance and thermal impact.
No risk disclaimer. Crypto apps are inherently risky. Failing to include a clear, prominent risk warning — especially for non-custodial wallets — is a red flag.
Ignoring local legal requirements. Apple may ask whether your app complies with financial regulations in each region. Be prepared to answer with specifics.
Misleading marketing copy. Over-promising returns, downplaying volatility, or using terms like “guaranteed” or “risk-free” will trigger a rejection.
Poor privacy policy. Your privacy policy must explicitly address how you handle blockchain data, public keys, and transaction history. Generic policies are insufficient.

⚠️ Pro tip: Before submitting, read your own app description and in-app notices as if you were a reviewer. Ask: “Would I approve this based on clarity and transparency?” If the answer is no, revise.

📌 Real-World Scenario: A DeFi Wallet App

📱 Scenario

App name: “VaultBridge” — a non-custodial DeFi wallet that connects to Ethereum and Polygon, allowing users to swap tokens via Uniswap and stake stablecoins for yield.

Compliance assessment:

✅ Custody model: VaultBridge clearly states in its description and onboarding flow that it is non-custodial — private keys are stored only on the user’s device.
✅ Fees: All swap fees (Uniswap protocol fees, gas estimates, and a small service fee) are displayed before a user approves a transaction.
✅ Risk warning: A full-screen risk disclaimer appears on first launch, covering impermanent loss, smart contract risk, and price volatility.
✅ Mining: No mining features are present; staking is clearly explained with lock-up periods and reward mechanics.
✅ Privacy policy: The policy explicitly states that VaultBridge does not collect private keys, and that blockchain data (public addresses, transaction hashes) is handled only for on-chain interaction.

Outcome: VaultBridge passed App Store review on the first submission because it addressed every requirement of Guideline 3.1.5 with clarity and transparency.

⚠️ Risks and Limitations of the Guidelines

While Guideline 3.1.5 provides a clear framework, it has limitations — and app developers should be aware of them.

🚨 Risk Warning

This guide is for informational purposes only and does not constitute legal, financial, or tax advice. App Store policies change over time, and regulatory landscapes for cryptocurrency vary by jurisdiction. Always verify the latest version of the App Store Review Guidelines and consult qualified legal counsel for your specific situation.

Do not rely solely on this guide for compliance. Apple’s interpretation of Guideline 3.1.5 can evolve, and additional requirements may be introduced. You are responsible for ensuring your app meets all applicable rules.

🔒 Security Considerations

Even if your app is compliant, security vulnerabilities can lead to user loss — and subsequent removal.
Third-party libraries and smart contracts introduce risks outside your control.
Regular security audits are recommended but not required by the guidelines.

🌍 Jurisdictional Variances

What is compliant in the U.S. may not be in the EU, China, or other regions.
Apple may restrict your app’s availability based on local regulations.
You may need to implement geo-blocking for certain features or regions.

⚡ Important: The cryptocurrency industry changes rapidly. Fees, token availability, and platform features can shift. Always verify current data from official sources — Apple’s developer documentation, your local financial regulator, and the specific blockchain networks you integrate.

❓ Frequently Asked Questions

Does Guideline 3.1.5 prohibit all cryptocurrency apps?

No. It provides a compliance framework. Apps that follow the rules regarding custody disclosure, fee transparency, licensing, and risk warnings can be approved. The guideline is designed to protect users, not to ban crypto apps outright.

What happens if my app is rejected under 3.1.5?

Apple will provide a rejection notice explaining which aspect of the guideline was violated. You can revise your app and submit an appeal or a new version. In many cases, clarifying your custody model or adding fee disclosures resolves the issue.

Do I need a financial license to publish a wallet app?

Not necessarily. Non-custodial wallets (where users control their own private keys) are generally treated as software tools rather than financial services. Custodial wallets that hold user funds, however, may require licensing depending on jurisdiction. Check with local regulators.

Can my app include in-app purchases for cryptocurrency?

Yes, but you must use Apple’s in-app purchase system for digital goods and services. Purchasing cryptocurrency itself with fiat currency is typically handled through external payment processors, but you must still comply with the fee disclosure and licensing requirements of 3.1.5.

Are NFT (non-fungible token) apps covered by 3.1.5?

Yes. Apps that allow users to view, buy, sell, or transfer NFTs fall under the cryptocurrency umbrella. The same requirements apply: clear fee disclosure, custody transparency, and risk warnings.

How do I stay updated on changes to 3.1.5?

Apple periodically updates the App Store Review Guidelines. Subscribe to Apple’s developer newsletter, check the official documentation regularly, and monitor developer forums for announcements. This guide is evergreen but should be cross-referenced with the latest official text.

Can I use third-party wallet SDKs and remain compliant?

Yes, but you are still responsible for the final user experience and disclosures. If the SDK handles private keys or fees, you must ensure your app clearly communicates how those are managed. Review the SDK’s own compliance posture as part of your evaluation.

Does 3.1.5 require me to collect KYC information?

Not directly. However, if your app offers exchange or fiat on-ramp services, you may be required by law to implement KYC. Apple may ask about your compliance with anti-money laundering regulations, so be prepared to explain your approach.