Crypto exchange app rejected by the App Store? Stop resubmitting. Start submitting evidence.
When Apple rejects a crypto exchange app, the reviewer is almost always asking for compliance evidence, not code changes: proof that the exchange itself offers the app and holds appropriate licensing or lawful access in every region where it is available (Guideline 3.1.5). The fix is a documentation package — legal opinion letters, a country availability statement, rewritten App Review Notes and a structured reply — then a controlled resubmission.
Why crypto exchange apps get rejected — the three real reasons
Across 30+ exchange submissions we have handled, nearly every rejection maps to one of three guidelines. The email tells you which rule you failed. It never tells you which document would satisfy the reviewer. That gap is where founders burn weeks resubmitting.
| Guideline | What the rejection really means | Evidence Apple expects | CexPass deliverable |
|---|---|---|---|
| 3.1.5 Cryptocurrency exchanges | Apple cannot verify the app is offered by the exchange itself with appropriate licensing and permissions in every storefront it is available in. | Jurisdiction-by-jurisdiction legal basis for distribution; entity and licensing documentation; a defined storefront list. | Legal opinion letter + country availability statement |
| 4.3 Spam / duplicate apps | The app looks like a white-label template or is linked to other developer accounts with similar apps. | Demonstrable differentiation: entity, brand, feature matrix, account system, demo path. | Differentiation memo + rewritten metadata & Review Notes |
| 5.1.2 Data use & tracking | Privacy labels, SDK behavior, ATT prompts and third-party sharing do not match the app's real data flows. | An accurate privacy label, audited SDK list, consistent ATT implementation. | Privacy label rewrite + data-flow statement |
Guideline 4.8 (third-party login) frequently rides along with 5.1.2 — fix both in the same resubmission.
The rejection wording, decoded
The most common 3.1.5 rejection reads like this:
Your app facilitates cryptocurrency transactions, but you have not provided documentation of appropriate licensing to operate a cryptocurrency exchange in the countries or regions where your app is available.
How to read it: "appropriate licensing" does not mean one global license — no such thing exists. It means Apple wants a coherent story: who the operating entity is, which storefronts the app is actually available in, and on what legal basis (license, registration, exemption, or lawful cross-border access) it serves each of them.
Still at the "2.1 — Information Needed" stage, before any formal rejection? Read what happens after you reply to 2.1 — that reply usually decides whether the case ever escalates this far.
What not to do after a rejection
- Don't resubmit the same binary with a longer note. Repeated near-identical submissions build a negative review history and can escalate toward 4.3 spam treatment.
- Don't select all 175 storefronts and hope. Every storefront you tick is a jurisdiction you implicitly claim to be allowed to serve. Narrow first, expand later.
- Don't paste your license PDF as the entire answer. A license from one jurisdiction doesn't answer availability in a hundred others. Reviewers need a mapped statement, not raw files.
- Don't argue in the Resolution Center without a document set. Unsupported argument reads as evasion; supported argument reads as compliance.
The resubmission path that works
The pattern that consistently moves exchange apps from Rejected to Ready for Sale is a four-step evidence build, typically over about 30 days:
Fastest way to know your real blocker: send us the rejection email. We read it free and tell you within ~10 minutes which document you're missing.
Send the rejection email →Documents checklist for a crypto exchange resubmission
Frequently asked questions
Can a crypto exchange app get approved without a license in every country?
Yes. Apple's requirement is appropriate licensing and permissions in the regions where the app is available — availability is the variable you control. A coherent package combines licenses or registrations where required, exemption or lawful-access analysis where applicable, and a country availability statement that excludes storefronts you cannot justify.
How many times can I resubmit after a rejection?
There is no hard limit, but repeated near-identical submissions damage your review history and increase spam (4.3) risk. Resubmit when something material has changed — new documents, new storefront scope, new Review Notes — not before.
How long does it take to fix a 3.1.5 rejection?
Across the exchanges we have served, the average end-to-end path is about 30 days: diagnosis, legal opinion and availability statement, Review Notes rewrite, resubmission and reviewer Q&A.
Should I appeal or resubmit?
Appeal only when the reviewer misapplied a guideline and you can prove it. If the rejection is factually right — you didn't provide licensing evidence — an appeal wastes weeks. Build the evidence and resubmit.
Related guides
- Apple App Review Guidelines — 3.1.5 Cryptocurrencies
- Apple App Review Guidelines (full text)
- App Store Connect — App Review information