Finding a high-risk payment gateway, and you sell kava. Migrate everything to a new Shopify store.
You have been looking at lists of payment gateways that work with Shopify. Stripe, Square, PayPal, Adyen — they all have checkboxes next to them saying 'high-risk' or 'supports adult' or 'accepts CBD'. Here is what those lists do not say. The gateway is the technical plumbing. It connects your checkout to a payment processor. Shopify supports dozens of them natively, and more through apps. But the gateway itself does not underwrite you. Behind every gateway sits a merchant account — a MID, a relationship with an acquiring bank or payment processor. That is where the actual application lives. That is where a human or an algorithm decides whether to accept your business type, your geography, your volume, your history. A gateway that 'supports high-risk' merchants does not mean it will approve you. It means it accepts applications from people in your category. The approval is separate, specific, and yours alone. Merchants commonly spend weeks comparing gateways and hours on the actual underwriting — and then get declined by the merchant account on day one.
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
- Gateway comparison lists showing 20 options, each marked 'high-risk friendly', with no mention of MID approval odds
- Shopify's app store showing third-party gateways as a simple install, with no warning about the separate merchant account application
- A message that a gateway 'accepts high-risk merchants', interpreted as approval, actually meaning only that they take applications
- Assumption that if Shopify integrates a gateway, it will approve a new high-risk merchant — not true
- Discovery three weeks into setup that the gateway's parent processor has declined the merchant account application
The merchant account decision is the actual deadline. You can prepare the technical setup while applications are pending, but nothing clears until underwriting says yes. Some processors publish estimated timelines; most do not. Time in underwriting is time your store makes no money.
Why it happened — specifically for kava
Stripe's restricted businesses list names kava directly: "Illegal drugs, substances designed to mimic illegal drugs, including kava". The policy treats it as a controlled substance analogue, which is the primary trigger. The secondary trigger is geography: although kava remains legal to sell in the US federally, some states and territories have restricted or banned it, and a processor applying a blanket rule avoids the compliance cost of jurisdiction-by-jurisdiction underwriting. So you are not being declined for breaking a law; you are being declined because the processor classifies the product category itself as unacceptable risk.
Rule out the easy fix first — then deal with the real one
There is no documented Shopify platform route for kava. What you may have tried first is the hemp attestation, which does not apply here — hemp requires a specific legal attestation, kava does not. Some merchants try re-filing their MCC as general merchandise (5499) instead of health and beauty (5912), hoping to slip through. That fails because underwriting now happens on the merchant's actual product list, not the declared category. The realistic path is a high-risk acquirer who will underwrite kava explicitly. Several do. They will ask for compliance documentation that a mainstream processor will not, and they will hold a rolling reserve — which is the cost of admission to this category.
It only helps if all of these are true:
- Your products must comply with the laws of every state where you ship.
- You must disclose kava's legal status and health warnings on every product page.
- You will need a merchant account with a provider who explicitly accepts kava.
- You cannot omit or obscure the fact that you sell kava during underwriting.
- You must be prepared for a 10–25% rolling reserve held for 180+ days.
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
When you find a gateway that lists ingestible merchants as accepted, remember that the gateway is only the technical connection—the actual underwriting happens at the merchant account level. The acquirer will inspect your product claims, certificates of analysis, and dispute history as the real basis for acceptance or rejection. Processors in this space price for chargeback risk heavily, because 'it did not work' disputes are routine in consumables. You will likely face a higher percentage rate, mandatory reserve and volume cap than mainstream merchants—not because the gateway exists, but because the underwriter sees the category. Get your claims language reviewed before you apply anywhere. A gateway list is not a promise of approval.
⚖️ Legal status is genuinely contested or actively changing
When the legal status of your category is genuinely contested or actively changing, the merchant account underwriting shifts from chargeback risk to legislative risk. Underwriters will ask where the product is legal, whether federal law might change the calculation, and how quickly you could pivot if a jurisdiction moves against you. They will price this uncertainty into your rate and almost certainly into a mandatory reserve. Shopify's additional gateway fee stacks on top. A processor that lists your category today may have different pricing or different criteria six months from now if the legal landscape shifts. Expect the worst terms available: higher percentage, volume cap, reserve. Build relationships with more than one acquirer if you can, because a single processor failure leaves you with no backup.
What you actually have to fix
Underwriters do not change their minds because you asked. They change them because the facts changed. For kava, these are the facts that move the decision:
Add state-by-state legal disclaimers to every product page
Kava's legal status varies by state and is actively contested. You must disclose this on product pages, not just in terms of service. Write a clear statement that kava is banned in some US states and territories, that you will not ship to those jurisdictions, and that the buyer is responsible for verifying legality in their location. Acquirers scrutinise this heavily because a single shipment to a restricted state can trigger a chargeback cascade and regulatory attention.
Obtain and display third-party lab reports for every SKU
High-risk acquirers require proof that your kava is what you claim it is. Get certificates of analysis from a reputable lab showing the identity and purity of each product you sell. Display them on product pages or as downloadable PDFs. This is the second-highest-yield fix because it shifts the perceived risk from 'unknown substance' to 'verified botanical', and it is what separates approved merchants from declined ones in this category.
Audit all marketing and health claims for drug language
Do not claim kava treats, prevents or cures any condition — anxiety, sleep, stress, pain or otherwise. That language triggers both processor decline and regulatory risk. Use structure and function language only: 'supports relaxation' is defensible; 'treats anxiety' is not. Check your email flows, blog, product descriptions, images with text, and any third-party reviews you display.
Verify your business can legally operate in your home state and every shipping state
Before applying, confirm in writing that kava sale is legal in your state of incorporation and in every state where you have customers. Some states have explicit bans; others have grey areas. Do not assume federal legality means state legality. A letter from a local attorney or a regulatory agency clarifying your state's position is stronger than your own research, and acquirers will ask for it.
What underwriting will ask you for
- A detailed product compliance audit showing that each SKU meets the laws of every state you ship to
- Lab reports or certificates of analysis for your kava products
- A written health warnings and disclaimers policy as it appears on your website and in marketing
- Business formation documents: articles of incorporation or partnership agreement
- Processing history for the past 12–24 months, if available
- Bank statements for the past 3–6 months
- A signed attestation that you understand kava's legal status and contested legality in certain jurisdictions
Getting underwritten for kava
High-risk acquiring is an entire industry that exists for businesses Stripe declines, and several of them publicly underwrite kava. 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 kava
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
- Separate the gateway from the merchant account in your mindThe Shopify integration list shows what can be plugged in technically. The processor's application is what actually evaluates you. Installing a gateway in Shopify does not skip the merchant account step. It is the setup you can do in parallel. Write down the processor's name — the company that will actually underwrite you — separately from the gateway name. That distinction will save you weeks of confusion. When you get declined, you will know whether to blame the gateway (which is rare) or the underwriting criteria (which is the reason 99 times out of 100).
- Research the processor's actual criteria, not the gateway's marketingThe gateway's website will say 'we support high-risk merchants'. The processor's underwriting criteria — the thing that matters — lives in their application form, their policies, or a conversation with their underwriting team. Find it before you apply. Call them. Ask what business types they actually underwrite, what volume they need to see, whether they want reserves, what your rate will be. Cheaper gateways often cost more once you factor in reserves, higher rates, and transaction fees. Shopify also charges an additional third-party-gateway transaction fee on top of the processor's rate — tiered by your plan. That fee exists. Budget for it.
- Prepare your application materials while applications are pendingWhile the merchant account is being underwritten, you are waiting. Use that time to collect what processors will ask for: business registration, tax ID, processing history, bank statements, identity verification. Different processors have different checklists. Some will ask for personal guarantees. Some will want to know about past declined accounts. If you have been through a payment processor decline before, have that story ready and honest. Many processors now ask about MATCH history — the card networks' list of terminated merchants — and the answer matters more than the story. If you are on it, disclose it. Lying will disqualify you faster than the truth.
- Apply to multiple processors in parallel, not sequentiallyDo not pick one gateway, apply, get declined, then pick another. Research and apply to three to five processors whose criteria match your business type, in the same week if possible. Each application goes into the processor's system, and a decline does not flag you across all of them. But time between applications is time your store makes no money. Applications take days to weeks to process, so start the stack now rather than one at a time. Keep notes on each processor's criteria, rate, timeline, and reserve requirement so you can compare approved offers.
- Plan for worse terms than Shopify Payments, and budget the cost inIf you move to a third-party gateway, expect higher transaction rates, volume caps, rolling reserves, or setup fees. These are not bugs — they are how high-risk underwriting works. The processor is taking on more chargeback risk or regulatory scrutiny, so the pricing reflects that. Shopify Payments was a flat rate with no reserve. Your new processor will likely have both a rate and a reserve — money held back against chargebacks, sometimes 10 to 25 percent of monthly volume. That is working capital you do not have. Factor it into your business plan. If you cannot operate with a reserve, that processor is not a fit, and you move to the next application.
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 kava store's critical compliance data lives in metafields: lab reports, certificates of analysis, state-by-state legality notes and age-restriction metadata. A hand migration or a CSV round-trip cannot carry file-type metafields or reference-type metafields at all, so lab PDFs and compliance documents silently detach from product pages. On a substance with active legal restrictions, missing lab proof is not a display glitch — it is a compliance failure that will trigger chargebacks and processor account review.
| What you own | How much of it | What breaks doing it by hand | What we do instead |
|---|---|---|---|
| Product images | 1,200images≈ 5 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 | 200descriptions≈ 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 | 600variants≈ 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 | 2,400metafields≈ 16 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 | 373records≈ 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 | 2,800orders≈ 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 | 45discounts≈ 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 | 53articles & 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 | 12apps≈ 12 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 processing history or your MATCH listing. If you were declined as a sole proprietor and incorporate as an LLC, the underwriter will still see your previous decline. The advantage of a new entity is structural clarity for compliance purposes, not a fresh start at the processor level. Most kava merchants do not need a new entity; they need a processor who accepts the category.
Frequently asked
Will Shopify Payments ever accept kava?
No. Stripe, the processor behind Shopify Payments, names kava explicitly in its prohibited businesses list. That policy is not changing based on individual merchant status. Your only path to Shopify is a third-party provider — a high-risk acquirer who will give you a merchant account and you will connect it to your Shopify store via an app or custom integration.
Which payment gateway will actually accept kava?
Several high-risk acquirers publicly underwrite kava: Authorize.net on a high-risk MID, PaymentCloud, Soar Payments and Easy Pay Direct are the ones most commonly referenced by merchants in this category. Which one will accept you, at what rate and reserve, depends on your compliance posture, your volume and your processing history. None of them will tell you yes or no without an underwriting review. Use the quote form to reach them directly.
What reserve should I expect if I get approved?
High-risk acquirers in this category typically hold a 10–25% rolling reserve for 180 days or longer. That means if you process $10,000 in a month, $1,000–$2,500 is held and released slowly over six months. Plan your cash flow accordingly. Some providers release it faster if you hit clean performance benchmarks, but you cannot count on that upfront.
If I migrate to a new store, will my compliance docs travel with me?
No. Lab reports, COAs and state-by-state disclaimers stored in metafields cannot be exported via Shopify's standard CSV, and file URLs from your old store will break immediately. You will need to re-upload every compliance document to your new store's metafields and re-link them to products. If you have 200 SKUs and 12 metafields of compliance data each, that is a real project — plan a week for it.
What is the difference between a payment gateway and a merchant account?
The gateway is the software bridge connecting your Shopify checkout to a payment processor — it handles the technical flow of card data. The merchant account is your commercial relationship with the processor, and it is where underwriting happens. You can have the gateway installed in Shopify and still not be approved for the merchant account. The gateway is necessary but not sufficient.
If Shopify integrates a third-party gateway, will it approve me?
No. Shopify's integration of a gateway means only that the technical connection is possible. The merchant account approval comes from the processor that owns the gateway, using their own underwriting criteria. Some of those processors are more liberal with high-risk categories than others, but none of them approve everyone. Integration and approval are separate decisions.
Will I have to pay Shopify a fee on top of the processor's rate?
Yes. Shopify charges an additional third-party-gateway transaction fee on top of what the processor charges. This fee is tiered by your plan. It is a real cost and should be factored into your rate comparison when you are deciding which processor to apply to. The processor's advertised rate is not your total rate.
Can I appeal if a processor declines my merchant account application?
You cannot appeal to force approval, but you can reapply later if your circumstances change meaningfully — higher volume, longer business history, reserves in place, or a shift in your business type toward lower-risk activity. Some merchants reapply after six months to a year. Most processors will consider a fresh application if your profile is different. Lying on the reapplication will disqualify you entirely.
If I get declined by one gateway processor, will other processors know about it?
Each processor screens applications against the card networks' MATCH file — the list of terminated merchants — but they do not automatically see declines from other processors. A decline itself is not instantly shared across the industry. However, multiple hard applications in a short time can raise flags for some processors, and if you are on MATCH, every processor will see it. Apply thoughtfully to a few good fits rather than scattering applications everywhere. If you have been declined before, disclose it in the new application.
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 →