Apple asked for "more information" under Guideline 2.1? That email is discovery, not support chat.
For a crypto exchange app, Apple's "Guideline 2.1 — Information Needed" email is rarely a formality. Its questions — who operates the exchange, where it is authorized, which countries the app serves — map one-to-one onto Guideline 3.1.5. Your written reply is filed with the case and cross-checked against the storefronts you enabled in App Store Connect. A reply with the wrong scope commonly comes back as a 3.1.5(iii) citation naming specific countries. Treat the reply as testimony: it can upgrade the case, and it cannot be unsaid.
What "2.1 Information Needed" actually is
Guideline 2.1 is formally about app completeness — but for exchange apps, the "Information Needed" email is how App Review opens a licensing file. The reviewer pauses the submission, asks a short list of questions, and waits. The tone is administrative. The content is regulatory. Each question exists to populate a checklist that belongs to a different guideline entirely:
| The question in the 2.1 email | What it is actually checking | Where your answer goes |
|---|---|---|
| "Where did you obtain authorization / licensing to offer exchange services?" | Whether any entity-level legal basis exists — Guideline 3.1.5's licensing test. | Filed with the case. Quoted back to you if the claimed scope doesn't hold up. |
| "In which countries or regions is your app available?" | Your claim versus the storefront list you actually enabled in App Store Connect. | Cross-checked storefront by storefront — this is where named-country citations come from. |
| "Is the app offered by the exchange itself or a third party?" | Guideline 3.1.5's operator test: developer account versus operating entity. | A mismatch pushes the case toward 4.3 and operator questions. |
| "Please provide supporting documentation." | Whether evidence exists in reviewable form — not just claims. | Becomes the permanent baseline every later round is measured against. |
Nothing in the email says "3.1.5". That number usually appears one reply later — after your answer gives the reviewer something to cite.
A real escalation, redacted
Below is the two-email arc we see most often, redrawn from a real exchange case file. App name, Submission ID, dates and identifying details are removed; wording is paraphrased. The pattern is the point.
We have started the review of ████████, but we need additional information to continue.
— Does your app facilitate cryptocurrency exchange services?
— Where did you obtain authorization to provide these services? Please provide supporting documentation.
— In which countries or regions is your app intended to be available?
— Is this app offered by the exchange itself?
Your app facilitates cryptocurrency exchange services, but it does not appear to have the appropriate licensing and permissions in all of the countries or regions where it is available. Specifically, your app is available in India, but you have not provided documentation of authorization to operate a cryptocurrency exchange in India.
Next steps: provide documentary evidence of appropriate licensing and permissions in all of the regions where your app is available.
Why the upgrade happens
The escalation is not bad luck. It is the designed sequence:
- Your reply is evidence. Everything you write in the Resolution Center is stored with the case and quoted in later rounds. A confident sentence like "we are fully licensed" becomes a claim the reviewer is now obliged to verify.
- The storefront list is the checklist. Every country you left enabled in App Store Connect is a jurisdiction you implicitly claim to serve lawfully. The reviewer only needs to find one storefront your answer doesn't cover to convert the file from questions into a citation.
- One named country stands for all of them. India in the case above is a sample, not the scope. The citation's operative sentence is "in all of the countries or regions where it is available" — the named storefront just proves the gap exists.
- After the upgrade, the standard changes. Under 2.1 the reviewer is asking. Under 3.1.5(iii) the reviewer is asserting — and the burden of documentary proof is now formally on you, region by region.
The consequence timeline
Replies that make it worse
- "We are fully licensed." Unscoped claims are the single most common trigger for a named-country citation. If one enabled storefront falls outside the claim, the claim is now on file as inaccurate.
- "We will geo-block that country later." A promise about future configuration answers nothing about present availability — and it concedes the gap in writing.
- Attaching one license PDF as the whole answer. A document from one jurisdiction doesn't explain the other storefronts you left enabled; it invites the reviewer to name one of them.
- A long explanatory essay with no documents. Unsupported narrative reads as evasion. The reviewer's next move is to make the request formal — under 3.1.5.
- Withdrawing and resubmitting to "reset" the case. The record stays with the app and the account. Near-identical resubmissions add 4.3 spam risk on top of the licensing question.
About to reply to a 2.1 email? The most expensive email in this process is the one you send back. We read your Apple thread free and tell you what the reply will be measured against — before you commit it to the record.
Get a free first read →Already got the 3.1.5(iii) email?
Then the discovery phase is over and the case is a formal licensing citation. What the reviewer accepts as proof at that stage — and how exchanges structure it — is covered in our rejection field guide and the Guideline 3.1.5 explainer. The next reply is the highest-stakes document in the whole process; across the 30+ exchanges we've served, the controlled path from citation to approval averages about 30 days.
Frequently asked questions
Is "2.1 Information Needed" a rejection?
Not yet. The submission is paused, not refused. But for crypto exchange apps it is usually the discovery step before a licensing citation — and the distance between the two is exactly one reply. What you write determines whether the case closes as a completeness check or upgrades to Guideline 3.1.5(iii).
Why did Apple name only one country when the app is live in dozens?
The named storefront is the sample the reviewer verified, not the limit of the citation. The operative wording is "all of the countries or regions where your app is available" — every enabled storefront is in scope, and later rounds can name different ones.
Can I withdraw the submission and resubmit to get a clean slate?
No. The Resolution Center thread and your written answers stay with the app and the developer account. Repeated near-identical submissions also build the pattern Apple treats as 4.3 spam behavior, which adds a second problem on top of the first.
How fast should I reply to a 2.1 email?
Scope matters more than speed. A fast answer with the wrong scope converts questions into citations; that upgrade is very hard to walk back. Take the time to know exactly what your storefront list, entity structure and documentation can support before anything goes on the record.
Related guides
- Apple App Review Guidelines — 2.1 App Completeness
- Apple App Review Guidelines — 3.1.5 Cryptocurrencies
- App Store Connect — App Review information