Application rejected, and you sell kratom. Migrate everything to a new Shopify store.
The email came back fast: your Shopify Payments application has been declined. No reason given, or a one-line reason that doesn't quite fit. You have no payouts held, no suspension notice, no terminated-merchant file record — just a gateway that won't activate. This is the cleanest version of a payments crisis, and it's worth understanding why. Shopify Payments is underwritten by Stripe, and Stripe screens applications against the product category you declared, the countries you ship to, and the completeness of your business profile. Rejection at application stage means the review happened before any money moved. You can stay on this Shopify store, keep your domain, keep your design, and simply activate a different payment gateway instead. No migration needed. No data loss. The store is fine; the first gateway you tried wasn't the fit.
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
- "Shopify Payments is not available for your business type" — with no detail on which part of your business triggered it
- "Your application does not meet our underwriting requirements" — rejection with no explanation of what failed
- Application status stuck on "Pending" for weeks, then declined without a decision document
- Request to reapply immediately rejected, suggesting a category-level block rather than a profile issue
- A business profile that looks complete to you, but Stripe's questions were answered incompletely or ambiguously
The only clock that matters is your launch timeline. You have no external deadline. Take time to choose the right gateway for your category and geography, because switching gateways mid-launch is friction you don't want. Activation is fast; selection is the real work.
Why it happened — specifically for kratom
Shopify Payments is underwritten by Stripe, and Stripe's restricted-businesses policy covers substances designed to mimic illegal drugs. Kratom is declined under that clause, not by a named category—it is not explicitly listed, but it sits in a family of botanicals that trigger the restriction by analogy. The secondary trigger is jurisdiction: kratom is banned outright in several US states and countries, which means your buyer's location itself can be a disqualifier even if your store is legal where you operate.
Rule out the easy fix first — then deal with the real one
Rule this out first. Shopify does not document a kratom-specific route. You might try the Attestation for the Sale of Hemp and Hemp-Derived Products, but kratom is botanically distinct from hemp and not covered by that pathway—applying through it will almost certainly be declined. The honest equivalent is that most merchants in this category go straight to third-party high-risk acquirers rather than waste time on platform-layer exceptions. The acquirer will run its own underwriting on your claims, your shipping destinations and your processing history, and that is where the real decision happens.
It only helps if all of these are true:
- You operate and ship only to US states where kratom is not banned.
- Your product descriptions make no medical or therapeutic claims.
- You can document age-gating at checkout to prevent sales to minors.
- You have not been declined by another payment processor for this category.
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 application was rejected because processors see claims language, not products. A supplement that 'supports bone health' reads as a medical claim—the FDA line between structure–function and drug language is where most rejections happen. Get your product pages reviewed by someone who reads regulatory guidance, not marketing copy. Remove anything that sounds like a treatment or cure. Have certificates of analysis, third-party testing, or safety documentation ready to upload. When you reapply with cleaned language, include a one-paragraph summary of your compliance stance. The rejection is fixable; it is almost never a categorical ban.
⚖️ Legal status is genuinely contested or actively changing
Categories in legal flux—where the law is contested, actively changing, or inconsistently enforced—trigger acquirer pricing on legislative risk, not just chargeback risk. Your rejection reflects genuine uncertainty about your legal status, not a judgment of your compliance. Processors cannot afford to be sued by state regulators, so they avoid categories where regulators themselves disagree. Before you reapply, gather evidence: legal counsel opinion, regulatory guidance letters, or clarity on your specific jurisdiction's stance. If your legal status is genuinely unsettled, some processors will still underwrite you, but they price it separately. Be transparent about the contested ground. Honesty about uncertainty moves you further than claims of certainty.
🔞 Requires age verification, and shipping is regulated in its own right
Age-restricted goods trigger both category screening and shipping carrier rules that vary by state. Your application may have been rejected because the underwriter could not verify your fulfillment process—signature capture, age verification at delivery, state-by-state carrier restrictions. Some carriers won't touch certain age-gated categories at all. Before you reapply, document exactly how you will verify customer age at checkout and confirm your chosen carrier accepts the category in your target states. A written fulfillment plan, with carrier agreements attached, moves you from 'unknown' to 'managed'. Rejection here is process, not judgment.
What you actually have to fix
Underwriters do not change their minds because you asked. They change them because the facts changed. For kratom, these are the facts that move the decision:
Remove all therapeutic claims from product pages and marketing
This is the single highest-yield fix. Any language stating or implying your kratom treats, prevents or cures a condition—pain, anxiety, energy, focus—reads to an underwriter as marketing an unapproved drug. You must audit product descriptions, blog posts, reviews you display, email flows and social media links, because acquirers review all of them. The defensible frame is 'traditional use' or 'botanical source'; therapeutic claims disqualify you outright.
Map your shipping destinations and exclude banned jurisdictions
Kratom is banned in several US states and in countries outside the US. You cannot legally ship to those places, and processors will decline you if they see orders going there. Before you apply, identify which states and countries you will serve, document that decision, and implement shipping restrictions at checkout that match it. Acquirers ask for this map explicitly, and it must be consistent with your actual fulfillment.
Document your age-gating system and enforce it at checkout
Kratom is age-restricted in many jurisdictions. You must have a checkout mechanism that verifies the buyer's age before payment—usually 18 or 21 depending on local law. Screenshot your implementation and document what age gate your system enforces. If you rely on manual verification or honour-system checkboxes, you will be declined.
Gather lab reports and compliance documentation before applying
Acquirers in this category ask for certificates of analysis (COAs) from your suppliers, showing alkaloid profiles and contaminant testing. Have these documents ready, named consistently and hosted somewhere you can quickly share them. If your supplier cannot provide them, find one who can—the absence of lab data is an automatic decline.
What underwriting will ask you for
- Lab report or certificate of analysis (COA) confirming the kratom's origin, alkaloid profile and absence of contaminants.
- Shipping and state-ban compliance map showing which US states and countries you do and do not serve.
- Age-verification system documentation proving you gate sales to 18 or 21 depending on local law.
- Merchant processing history for the past 24 months, including any prior payment processor declines.
- Clear product descriptions showing no medical or therapeutic claims—structure and function language only.
- Proof of regulatory compliance documentation for any state where kratom faces additional licensing or registration requirements.
- Customer acquisition strategy and marketing channels, confirming no claims of health benefits.
Getting underwritten for kratom
High-risk acquiring is an entire industry that exists for businesses Stripe declines, and several of them publicly underwrite kratom. 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 kratom
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
- Check your business profile for gapsLog into your Shopify admin and review the business information Stripe saw: your legal business name, tax ID, business address, product category, and description of what you sell. Read it as a stranger. Is the category accurate? Some categories are harder to underwrite than others — if you sell general merchandise but wrote "beauty products", Stripe screens you against beauty-specific rules. Is every required field actually filled in? Partially-completed profiles often get rejected because underwriting is automated. If something is wrong, fix it — then you can either reapply to Shopify Payments or move forward with a different gateway.
- Research which gateways accept your category and countryYou don't have time to wait for a reapplication. Other gateways underwrite the same categories that Shopify Payments rejected, and some don't. The gateways that publicly advertise support for your product category are the ones to approach. Search for your category plus "payment gateway" or "payment processor", and look for gateways that list your country as supported and your category as acceptable. Check their integration with Shopify: most major gateways offer a public Shopify app. You're looking for one that will activate before your launch date.
- Activate the new gateway on your Shopify storeOnce you have selected a gateway that accepts your category, install its Shopify app or follow its setup instructions. No data migration needed. Your catalog, your design, your customers list, your orders — everything stays on your Shopify store. You're only swapping which processor settles your money. The new gateway typically activates within hours of setup. Test a transaction in sandbox mode, then switch to live. You can delete Shopify Payments from your payment methods as soon as the new gateway is active.
- Rebuild your checkout for the new gateway's requirementsSome gateways have stricter data collection than others. Check whether your new gateway requires address verification, CVV, or three-D Secure. If your checkout was set up for minimal friction, adding these fields might drop your conversion rate slightly — but an active checkout beats a perfect one that doesn't work. You can always soften friction later. Set up the new gateway's webhook and monitoring now, so you know immediately if transactions start failing. Test again with a real transaction.
- Keep Shopify Payments as a backup option, or don'tIf you want to reapply to Shopify Payments in three to six months, you can. Your store will remember the rejection, but there's no rule against trying again after you've fixed your profile or grown your order history. Some gateways have higher fees than Shopify Payments — if you plan to go back, set a reminder for the reapplication and make sure your business profile is locked in. More likely: you'll find a gateway that works, your sales will grow, and you'll never think about Shopify Payments again. Either way, you're selling now instead of waiting.
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 kratom store's data is unusually dangerous to move by hand because compliance content lives in metafields. Lab-report file references, alkaloid testing data, COA document links and batch-compliance notes are stored as reference-type or file-type metafields that a CSV export cannot carry at all. If they are copied naively they keep pointing at the old store's assets, so pages render but lab data silently vanishes—and on a regulated botanical product, missing compliance documentation is a risk you cannot take.
| What you own | How much of it | What breaks doing it by hand | What we do instead |
|---|---|---|---|
| Product images | 1,400images≈ 6 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 | 280descriptions≈ 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 | 840variants≈ 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,680metafields≈ 11 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 | 430records≈ 3 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 | 8videos≈ 32 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 | 1,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 | 4,100orders≈ 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 | 22discounts≈ 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 |
| Blogs & pages | 30articles & pages≈ 2 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?
A new legal entity does not reset your payment history. Shopify Payments and other processors maintain records on the beneficial owner, not just the company name, and a new company on the same ownership will be declined the same way. You should form a new entity only if your business model genuinely requires it—not as a workaround for a processor decline. A new entity bought time in the past; it does not now.
Frequently asked
Will Shopify Payments approve kratom if I change my claims?
No. Shopify Payments is underwritten by Stripe, and kratom is declined by category policy, not by the content of your pages. Removing therapeutic claims helps you with a third-party acquirer, but it does not unblock Stripe itself. You must move to a high-risk payment processor that explicitly underwrites botanical or restricted substances. That is a different underwriting path, not a fix to the one you are on.
Which payment gateway will actually approve my kratom store?
Several high-risk acquirers publicly underwrite kratom—PaymentCloud, Soar Payments and Easy Pay Direct are the most established—but approval is never guaranteed and depends on your geography, your claims, your volume and your processing history. Rather than email them cold, use the merchant quote form on this page and we will put you in touch with an acquirer that has capacity in your segment. The gateway is the easy part; the merchant account underwriting is where the decision is made.
What reserve should I expect if I get approved?
High-risk kratom processors typically hold a rolling reserve of 10–25%, sometimes for 180 days or longer. That means if you process 10,000 pounds in sales, 1,000 to 2,500 pounds sits in the processor's account rather than yours. Reserves are higher if you are new to the category or if you have a history of chargebacks. Ask for the reserve terms upfront in writing before you sign anything.
Will my lab reports and compliance metafields survive a store migration?
No. Shopify's CSV export cannot carry metafields, and if you copy them manually they will point at URLs in your old store. Lab reports, COA files and alkaloid data must be re-hosted on the new store and re-linked explicitly. We rebuild these references as part of our migration, but you must gather your source documents beforehand—have them organised and accessible before migration begins.
Why did Shopify Payments reject me if I filled in every field?
Stripe uses automated underwriting that screens your product category against its policy. Some categories carry higher chargeback or fraud risk, and Stripe declines applications in those categories even if your profile is perfect. Others are harder to underwrite if your business description is vague. Stripe does not publish the exact reason for individual rejections. If your category is on its public restricted list, rejection is policy. If your category is general, the problem was likely profile clarity — describe exactly what you sell, not categories.
Can I reapply to Shopify Payments right now?
Technically yes, but reapplying with an identical profile will likely be rejected again. Shopify (via Stripe) publishes no SLA for reapplication review. If you believe your first application had incomplete information, fix your profile first, then try again. If your product category is what triggered the decline, reapplication will not help unless you've genuinely changed what you sell. In the meantime, activating a different gateway lets you start taking payments immediately.
Will switching to a different payment gateway lose my customer data or orders?
No. Switching payment gateways does not touch your store, your catalog, your customers, your order history or anything else in Shopify. You are only changing which processor settles your money. All your Shopify data stays exactly where it is. The new gateway integrates with your checkout, and new orders go through it instead of Shopify Payments. Old orders stay in your Shopify admin. No migration, no data loss.
What if every gateway rejects me?
This is rare at application stage (as opposed to after trading). If multiple gateways decline you, the issue is usually your product category being on most processors' restricted lists, or incomplete business information that raises flags across the board. Read their rejection emails for hints. Complete your business profile fully and honestly. If your category is genuinely restricted (adult content, certain financial services, high-risk gambling), mainstream gateways won't work — you would need a high-risk processor, which is slower to activate and more expensive.
Can you reactivate Shopify Payments for me after I switch gateways?
No. We can't turn Shopify Payments back on, and Stripe's decision is not reversible by Shopify support. What we do is move your store to a new Shopify store built around a gateway that will accept you — migrating your catalog, descriptions, images, customers, orders, themes and more. But for an application rejection with no funds held, you don't need a migration. Activating a different gateway on your current store is faster, cheaper and keeps everything you've built. Migrate only if you later face a termination and need to move to a new Shopify account entirely.
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 →