Account under review, and you sell CBD and hemp. Migrate everything to a new Shopify store.
The email arrived without warning: your Shopify Payments account is under review. Checkouts still work. Money still lands. But the language is formal and it asks for documents you may not have ready — bank statements, tax returns, proof of product source, clarity on your business structure. The clock is invisible and no one tells you how long it will take. Here is what changes what you do. This is the moment you still have influence. A review is not a decision; it is an open question. The processor is asking because something triggered a flag — a sudden jump in volume or order value, a rise in chargebacks, documents that did not match, or simply the product category you chose. Your job is to answer the exact question asked, with evidence, and nothing else. Do not volunteer new information or try to rewrite your story. And critically: prepare a copy of your store right now, while you still have full access. If the review clears, you never need it. If it does not, you will have lost the only window where you could have saved it.
Move all of it into a new store, from $247
One-time packages, no per-record metering, no quotes. The order form unlocks the moment you pay, counts are matched against your old store, and the entire migration then runs a second time — the second pass has to create nothing.
What you are looking at
- "We are reviewing your account to ensure it meets our requirements — please provide documents by [date]"
- Bank statements, tax returns, government ID, or proof of business registration — the list depends on what triggered the review
- Checkouts processing normally while the background review runs, creating false confidence that nothing is wrong
- "Your account remains under review" — weeks or months later, with no clear next step or timeline
- Support responses that repeat the policy without explaining what specifically needs to be fixed
The real deadline is invisible: the date Shopify's or the processor's underwriter makes a final decision. You cannot know when that is, so the clock that matters is the one you control — getting a full backup of your store today, while you have admin access. A review that goes wrong becomes a suspension, and a suspension can become an account closure. Once access is gone, your data is unreachable.
Why it happened — specifically for CBD and hemp
Shopify Payments is underwritten by Stripe, and Stripe's policy treats cannabis and its derivatives as restricted — hemp-derived CBD within the legal THC limit sits on the restricted list, and anything over that limit is prohibited outright. So a CBD merchant is not being judged by Shopify at all; they are inheriting a payment processor's category policy. The secondary trigger is claims: CBD marketed as treating a condition reads to a reviewer as an unapproved drug, which moves you from "restricted" to "prohibited" without changing a single product.
Rule out the easy fix first — then deal with the real one
Rule this out first, because it takes an afternoon. Shopify does document a hemp route: US merchants sign the Attestation for the Sale of Hemp and Hemp-Derived Products and connect one of the integrated third-party providers. What merchants get wrong is thinking the attestation is an approval. It is not — it is permission to apply, and the provider behind it runs its own underwriting on your claims, your labels and your history. That second review is where the decline usually happens, which is why most people reading this page have already been through it. Shopify's documentation →
It only helps if all of these are true:
- You are US-based, and every product is within the federal THC limit
- Your store itself was not closed — only the gateway was switched off
- Your product claims survive a compliance review, because the provider will run one
- One of the integrated providers will actually board you, which is a separate decision
If any one of them does not hold, you are where everyone else on this page is: you need a store built around a gateway that will actually accept you — and everything you have built has to move into it without losing the catalog, the customers, the order history or the rankings.
What this means for a business like yours
💊 Sold to be swallowed, inhaled or applied — health claims and product-liability risk
Your account is under review because someone flagged a health claim, a dispute rate, or a product category match. The reviewer wants to see claims language, not certificates. Take your product pages and marketing copy—show exactly what you say the product does. If a page says 'supports' joint health, that is safer than 'eliminates inflammation', which reads as a drug claim to an underwriter the same way it would to a regulator. Collect your substantiation: third-party testing, published studies, ingredient lists. Answer the exact question asked. Do not offer extra risk. While the review runs, build a copy of your store on a gateway known to accept your category—you still have leverage now, and preparing silently costs nothing.
⚖️ Legal status is genuinely contested or actively changing
Your account is under review because the legal status of your category is contested or actively changing, and processors price that legislative risk separately from chargeback risk. You cannot change the law, but you can show the reviewer that you are tracking it. Gather public statements from regulators, attorneys general, or recent court filings relevant to your jurisdiction and product type. Answer the review question with that evidence in hand—show you understand the landscape and that your compliance stance matches the current legal position. Do not argue that the law should be different. In parallel, start a copy of your store on a gateway that has publicly stated it serves your category despite the legal volatility—some do, explicitly. You will learn during the review whether your current processor will survive the next legislative move, and a prepared store means you are not trapped by their risk appetite.
🔁 Recurring billing is a large share of revenue
Your account is under review, and every day the review runs, you lose recurring revenue in two ways: new signups stop, and existing subscriber billing may be suspended if the processor locks the account while reviewing. Subscription payment methods are held by the processor and cannot be exported—you cannot simply hand them to a new gateway. Answer the review question with precision, but do not wait for the all-clear to prepare. Start building a copy of your store on a gateway that accepts subscriptions in your category. If the review goes against you, migrating subscribers means either a processor-facilitated transfer (rare and slow) or asking customers to re-enter payment details (never fully recovers). The copy you build now, while review is still open, is your insurance policy.
What you actually have to fix
Underwriters do not change their minds because you asked. They change them because the facts changed. For CBD and hemp, these are the facts that move the decision:
Strip the drug claims out of every product page
This is the single highest-yield fix and the one merchants resist most, because the claims are what sell. Anything that says or implies your product treats, prevents or cures a condition — anxiety, pain, insomnia, inflammation — reads to an underwriter and to a regulator as marketing an unapproved drug. Structure and function language is defensible; therapeutic claims are not. Audit the descriptions, the blog, the reviews you display and your email flows, because reviewers read all of them.
Put your certificates of analysis where a human can find them in ten seconds
Batch-level COAs from an accredited lab, linked from the product page, with the THC result visible. Underwriters are checking that you can substantiate the legal-limit claim at all, and the merchants who pass are the ones who do not have to go looking. If your COAs live in a metafield your theme renders — as they usually do — that is also the data most likely to vanish in a badly-run store move.
Geo-block where you are not allowed to ship
Hemp legality is not uniform, and shipping into a jurisdiction that prohibits your product is both a legal exposure and an underwriting red flag. Market and ship only where you are compliant, and be able to show the controls that enforce it.
Sign the Shopify hemp attestation before you conclude you need a new store
If you are US-based and the only thing that failed was Shopify Payments, the attestation plus an integrated third-party provider may put you back in business on the store you already have. Exhaust that before migrating anything — a migration is the right tool for a genuinely new store, not a workaround for a form you have not filled in.
What underwriting will ask you for
- Certificates of analysis per batch, from an accredited lab, showing THC within the legal limit
- Supplier and manufacturer agreements
- Product labels for claims review — this is what gets applications declined
- Your Shopify hemp attestation, if you are US-based
- Three to six months of processing statements if you have any history
- Business bank account, formation documents and beneficial-owner ID
Getting underwritten for CBD and hemp
High-risk acquiring is an entire industry that exists for businesses Stripe declines, and several of them publicly underwrite CBD and hemp. What none of them will tell you up front is the number that actually matters: what your business gets offered, once they have seen your volume, your claims and your history. Rate, reserve and settlement terms vary enormously between applicants in the same category.
Get real quotes from high-risk processors that accept CBD and hemp
Six taps and three details. We put it in front of the high-risk acquirers that actually underwrite your category and come back with what they will offer you — rate, reserve and settlement terms — so you are comparing real numbers instead of cold-emailing brokers for a fortnight.
The recovery playbook
- Read the request and answer only that questionDo not assume you know what triggered the review. Read the email carefully and identify the exact documents or clarifications they asked for. If they asked for bank statements showing business revenue, send bank statements — not tax returns, not personal documents, not a general business overview. If they asked about your supplier, name the supplier and provide a wholesale agreement or invoice — not a marketing story about your brand. Do not volunteer information they did not ask for. Every piece of paper you add becomes another thing they can scrutinize, and underwriters look for inconsistencies. Stick to the question.
- Get a verified copy of your store — today, while you have accessThis is the step people skip because the review feels temporary and checkouts are still open. It is not temporary, and access can vanish without notice. A negative review decision is usually followed by an account suspension or closure. Once that happens, admin access can be revoked immediately, and you lose the ability to export anything — catalog, orders, customer data, SEO metadata, theme files, discounts, redirects, metafields. Shopify's own CSV export cannot carry metafields, orders, gift card codes, videos, themes, menus, discounts or redirects. That is why a backup taken during the review, while you still have full control, is the only insurance that works. You will almost certainly not need it. But if you do, it is the difference between a bad month and a dead business.
- Gather any supporting documents they did not ask for but might needWhile you are responding to the stated request, identify supporting evidence you can provide without volunteering it — documents that backstop your answer to their question. If they ask about volume and you have a marketing invoice showing a paid campaign, or a supplier invoice showing you bought stock in bulk to meet demand, keep those nearby. Do not send them unless they ask, or unless your first response does not clear the review and you are invited to provide more. Let them lead on scope. Over-documenting looks like you are hiding something.
- Respond before the deadline, using the communication channel they specifiedRead the email again for the exact submission method and deadline. Send your response through that channel, not through support or a different email address. If they asked you to upload documents via your Shopify admin, do that — it leaves a timestamped record. If they gave you an email address or support ticket, use that. Include a clear note stating what you are submitting and why: "Per your review request of [date], I am providing [documents] which show [specific fact you are answering]." Do not oversell; be factual and brief. Save a copy of everything you send, and the timestamp.
- Prepare for a second gateway before you hear backA review can take weeks or months to resolve, and you cannot know the outcome in advance. Do not wait for a clearing decision to act on your backup plan. Research payment gateways that publicly advertise your product category and accept merchants with histories similar to yours. Stripe, Square, Wise, 2Checkout and others operate alongside or instead of Shopify Payments for many merchants — but approval is not guaranteed, and each has its own underwriting. The time to gather your account information and test integrations is now, while your store is fully functional and you are not under time pressure. If the review clears, you delete the backup and move on. If it does not, you have already removed the panic from the migration decision.
And then there is the part that actually loses businesses
If you do need a new store, the payments problem turns out to be the easy half. This is what is sitting in your current store right now, and what happens to each piece when someone tries to move it by hand:
Why this category in particular
A CBD store's data is unusually dangerous to move by hand, for one specific reason: the compliance content lives in metafields. Batch COAs, THC results, cannabinoid breakdowns and lab-report file references are all reference-type or file-type metafields that a CSV round-trip cannot carry at all — and if they are copied naively they keep pointing at files in the old store, so the page renders and the lab results are silently blank. On a regulated product, that is not a cosmetic bug.
| What you own | How much of it | What breaks doing it by hand | What we do instead |
|---|---|---|---|
| Product images | 720images≈ 3 hrsbulk re-upload, ~15 sec each | By handthe CSV carries image URLs and alt text, but they point at your OLD store's CDN — so the moment the old store goes, every image 404s. Re-upload and Shopify appends a dedupe suffix to the filename, which breaks every theme section and product description that referenced the original URL | Automatedevery file re-uploaded through the API with its alt text and variant attachment intact, its content type preserved so image-restricted fields still accept it, and every reference to the old URL rewritten |
| Product descriptions | 120descriptions≈ 2 hrsone pass to repair inline image links — the CSV carries the text | By handdescriptions are full of inline images and links pointing at the old store's CDN. Paste them into the new store and the text survives perfectly while every embedded image quietly dies — which you usually discover from a customer, not from a report | Automatedbodies copied verbatim, then a second pass rewrites every source-CDN URL inside them to the re-uploaded file on the new store |
| Product attributes & variants | 480variants≈ 45 minthe CSV carries these; the time is verifying option order | By handoption ORDER is part of the product's identity. Rebuild "Size, Colour" as "Colour, Size" and every theme swatch, saved customer URL and app that keys on variant position breaks — silently, because the product page still renders | Automatedvariants upserted by SKU with option names and order preserved, so swatches, deep links and app data keep working |
| Metafields & metaobjects | 1,200metafields≈ 8 hrsonly the reference, JSON and metaobject fields, ~1 min each | By handthe product CSV carries simple text and number metafields — but not metaobjects, and not reference or JSON types, which is exactly where app data and theme content live. Reference fields are the real trap: copy the value and it still points at objects in the OLD store, so the page renders and the custom block is silently empty | Automatedwritten in dependency order after their targets exist, with embedded references re-pointed at the new store's objects — and any value whose reference cannot be resolved is dropped rather than written broken |
| SEO data & redirects | 249records≈ 2 hrsredirects one at a time, plus a handle audit | By handany handle that changes becomes a dead URL with no redirect, and existing 301s are not in the product CSV at all. Years of accumulated ranking and backlinks end up pointing at pages that no longer resolve — the most expensive thing on this page to get wrong, and the slowest to notice | AutomatedSEO titles, meta descriptions and handles carried across, and every existing 301 recreated, so nothing that used to rank starts 404ing |
| Your custom theme | 1theme≈ 6 hrs2–10 hrs depending on how customised it is | By handa theme is not just its files. The settings, section content and block ordering are stored against the store, so a file copy gives you the layout and none of the content. Hardcoded asset URLs and tracking snippets also still point at the old store | Automatedyour live theme pulled and pushed as-is, then scanned for tracking snippets and hardcoded URLs that need re-pointing |
| Product videos | 10videos≈ 40 minre-upload and re-attach, ~4 min each | By handthe product CSV does not carry video or 3D media, so every one is a manual re-upload. They also cannot be pulled straight from a remote URL — the bytes have to be downloaded and staged first, and a wrong content type lands the file as a generic attachment that media-restricted fields then reject | Automatedvideo bytes downloaded, staged through a proper upload target, re-attached to the right product, and verified as processed rather than silently failed |
| Customers | 4,200customers≈ 2 hrsCSV import, then cleaning up the rows that fail | By handthe importer works, but marketing consent is the exposure: the CSV carries the current opt-in state and NOT the timestamp or source behind it. Re-opting someone in is a compliance breach, dropping them burns list revenue you paid for, and you cannot prove which happened afterwards. Default-address designation is also lost | Automatedcustomers upserted by email with every address, the default-address designation, and email and SMS consent states and timestamps preserved exactly as they were |
| Order history | 9,400orders≈ 8 hrsa paid third-party importer, plus a day of mapping and reconciliation | By handShopify's own CSV importer cannot create orders at all, so the hours here assume you buy a third-party importer — key them in by hand instead and 9,400 orders is closer to 390 hours, which is why nobody does that and why order history is simply abandoned in most DIY moves. Then support cannot answer a warranty claim, repeat-purchase segments are empty, and every returning-customer flow starts from zero. Getting the mapping wrong duplicates orders or re-dates them to today, and both are worse than not importing at all | Automatedfull order history recreated through the API with line items, properties, customers re-associated, original dates and tracking numbers intact |
| Navigation menus | 3menus≈ 1 hrsabout an hour to rebuild and relink them all by hand | By handmenu items store resource IDs, not paths, so nothing about them is portable — every link has to be re-pointed at the equivalent collection, page or product on the new store | Automatedmenus rebuilt with their nesting, and every item re-pointed at the equivalent object on the new store |
| Discount codes | 30discounts≈ 1 hrsabout 1 hr via the discount CSV, or ~3 hrs rebuilt by hand | By handthe discount CSV covers basic codes, but automatic discounts, quantity breaks and combination rules are not in it and have to be reconstructed by hand. A subtly wrong rule is worse than a missing one, because nobody notices until it has been over-discounting for a fortnight | Automateddiscounts recreated through the API with their rules, usage limits and dates intact, including automatic and free-shipping types |
| Gift card balances | 45gift cardsno manual routecannot be moved by anyone | By handthis is the one thing on this page that truly cannot be moved by anyone. Gift card codes are unreadable through EVERY Shopify API, by design — no tool, ours included, can copy them. Those balances are real money you owe real customers, and abandoning the old store does not abandon the liability: the customers still turn up expecting you to honour it | Automatedwe re-issue each card with an identical balance, customer and expiry date, and hand you the new codes as a CSV with customer email copy ready to send — the only honest way to move them |
| Blogs & pages | 59articles & pages≈ 4 hrsrecreated one at a time, ~4 min each | By handno CSV route for either. Articles also have no SEO fields of their own — their title and description tags live in metafields — so a hand-rebuilt blog loses its SEO even when every word of the text is right | Automatedarticles and pages recreated with authors, tags and publish dates, their SEO written to the metafields Shopify actually stores it in, and inline image URLs rewritten |
| Apps & app data | 10apps≈ 10 hrsabout 1 hr per app to reinstall, reconfigure and re-test | By handmost app data lives in metafields on your products and customers, so reinstalling the app gets you an empty app: reviews gone, subscription plans gone, loyalty balances gone, bundles gone. Flows and automations have to be rebuilt by hand and re-tested, and anything with its own billing has to be re-subscribed | Automatedthe metafield data your apps rely on migrates with the products and customers it hangs off, so a reinstalled app finds its data waiting instead of an empty store |
See these numbers for YOUR store, free
The figures above are a typical store in your category. The demo scan connects read-only to yours and counts the real thing — every product, variant, image, customer, order and metafield — then tells you exactly what a migration would carry across. No card, and it never writes to your store.
▶ Run the free demo scanDoes this need a new company?
Most CBD merchants do not need a new company — they need a different gateway on the store they already have. A new entity earns its keep when you are separating a cannabinoid line from a mainstream brand so one cannot take the other down, or when you are moving jurisdiction for genuine regulatory reasons. It does not reset a MATCH listing.
Frequently asked
Can I sell CBD on Shopify at all?
Yes — Shopify permits hemp and hemp-derived CBD sales where they are legal, and documents the process. What you cannot use is Shopify Payments, because it is underwritten by Stripe and inherits Stripe's cannabis policy. US merchants sign Shopify's hemp attestation and connect an integrated third-party payment provider; the store, theme and checkout stay exactly where they are.
Which payment gateway works for CBD on Shopify?
The honest answer is that the gateway is the easy part and the merchant account behind it is the decision. Several high-risk acquirers publicly underwrite hemp and CBD, and they front it through gateways Shopify supports natively — but which one will take you, at what rate and with what reserve, depends entirely on your volume, your product claims and your processing history. Rather than send you to cold-email a dozen brokers, use the quote form on this page: we put your details in front of the acquirers that actually underwrite your category and come back with what they will offer.
What reserve should I expect as a CBD merchant?
The high-risk norm is a rolling reserve of roughly 5–10% held for 90–180 days, with settlement slower than the next-day you may be used to. Cannabinoid categories with contested legal status sit at the upper end or above it, because the acquirer is pricing legislative risk as well as chargeback risk. Reserves are negotiable over time as you build clean processing history.
Will my lab results and COAs survive a move to a new Shopify store?
Not through a CSV export, which cannot carry metafields or metaobjects at all — and that is where COAs, THC results and lab-report file references live. Copied naively they keep pointing at files on the old store, so your product pages render with the compliance section silently empty. An automated migration writes them in dependency order after the files exist and re-points every reference, and drops any value it cannot resolve rather than writing one that is broken.
How long does a Shopify Payments review actually take?
There is no published timeline. Merchants commonly report decisions within two to four weeks, but some reviews remain open for months with no communication. The processor does not announce when a decision has been made; you find out either when you receive a follow-up email asking for more information, or when your account status changes without notice. Checking your account settings regularly for status changes is safer than waiting for an email.
What happens to my money during the review?
Payouts typically continue during an active review. Money from orders you process lands in your bank account on your normal schedule. The risk is not immediate loss; it is the outcome of the review. If the review goes against you, that is when payouts stop. The balance may then be held against potential chargebacks or disputes for weeks or months depending on the reason for the suspension.
Will they tell me why they are reviewing my account?
The first email usually says why — it mentions a document request, a dispute threshold, a volume change, or your product category. If it is vague, reply asking for clarity on exactly what the underwriter is concerned about. Be factual and non-defensive: "I want to ensure I address your concern — can you clarify whether this is about my supplier documentation, my transaction volume, or something else?" Sometimes they will detail it; sometimes they will not. Either way, answer what they asked for.
If I cannot find the documents they asked for, what should I do?
Tell them. Do not fabricate or send a substitute. If they asked for a bank statement and your bank account is new, or if you do not have incorporation papers because you operate as a sole trader, say so in your response. Explain what you do have instead, and why. For example: "I do not have formal incorporation papers as I operate as a sole proprietor — my government-issued ID and the business registration attached show my authority to operate." Underwriters understand that not every business has every document type. What they cannot forgive is documents that appear forged or misdated.
Can I appeal if they reject my account?
A review is not the same as an appeal. If your account is rejected after this review, you can ask why — and if the rejection was based on incomplete or outdated information, you can submit a formal appeal. But you cannot appeal a policy. If your product category is on the processor's restricted list, appealing your story will not change the category restriction; it means moving to a processor that accepts it. If the category is legal in your jurisdiction but restricted by the processor, you need a different gateway. A new Shopify store with a different gateway, or a migration to a new platform, is then the real option — not another appeal.
Move everything, verified twice, from $247
Pick a package and the migration order form unlocks immediately. Your existing store is only ever read from — we never write to it, so nothing you still have can be made worse. How the migration runs, step by step →