{"id":28466,"date":"2025-12-15T10:00:00","date_gmt":"2025-12-15T10:00:00","guid":{"rendered":"https:\/\/spreecommerce.org\/cannabis-ecommerce\/"},"modified":"2026-03-27T17:36:35","modified_gmt":"2026-03-27T17:36:35","slug":"cannabis-ecommerce","status":"publish","type":"post","link":"https:\/\/spreecommerce.org\/cannabis-ecommerce\/","title":{"rendered":"Cannabis eCommerce: The Deplatforming-Proof Platform for Multi-State Operators"},"content":{"rendered":"\n
\n\n\n\r\n
\r\n
\r\n
\r\n \"\"\r\n <\/div>\r\n
\r\n

Key Takeaways<\/h3>\n

Cannabis operators face a unique commerce problem: mainstream platforms ban or restrict cannabis sales entirely.<\/p>\n

Shopify prohibits all THC products above 0.3%, BigCommerce restricts cannabis to CBD-only, and major payment processors \u2014 Visa, Mastercard, Stripe, PayPal \u2014 refuse cannabis transactions regardless of state legality.<\/p>\n

Self-hosted open source platforms deployed on your own infrastructure, with your own payment integrations, are the only deplatforming-proof path.<\/p>\n

This guide covers cannabis eCommerce requirements across US state licensing regimes, which platforms can serve multi-state operators, and how to architect commerce that no vendor can shut down.
\nLast verified: March 2026<\/em><\/p>\n <\/div>\r\n <\/div>\r\n <\/section>\r\n\r\n\n\n\n\n\n

Why Cannabis Commerce Is Different<\/h2>\n\n\n\n

The US cannabis market reached an estimated $44.3 billion in 2025 and is projected to approach $47 billion in 2026, making it one of the fastest-growing retail categories in the country. Multi-state operators (MSOs) like Curaleaf, Green Thumb Industries, and Trulieve now operate across dozens of states, running complex B2B wholesale distribution alongside consumer dispensary retail \u2014 often through hundreds of licensed locations.<\/p>\n\n\n\n

Cannabis commerce faces three simultaneous forces that no other retail vertical confronts.<\/p>\n\n\n\n

First<\/strong>, cannabis remains a Schedule I controlled substance under federal law. This creates permanent tension between state-legal operations and the platforms, payment processors, and financial institutions that operate under federal jurisdiction.<\/p>\n\n\n\n

Second<\/strong>, every state that legalized cannabis created its own licensing regime, compliance requirements, and seed-to-sale tracking mandates. A multi-state operator must effectively run a different business in each state.<\/p>\n\n\n\n

Third<\/strong>, eCommerce platforms and payment networks responded to this federal-state tension by either banning cannabis or imposing restrictions so severe they create ongoing deplatforming risk.<\/p>\n\n\n\n

Building on the wrong platform carries existential risk.<\/strong> When Shopify shuts down your store or Mastercard terminates payment processing, there is no grace period. Your revenue stops immediately. Customer data becomes inaccessible. Integrations with seed-to-sale tracking systems, state compliance databases, and wholesale ordering portals fail. For an MSO operating across multiple states, this is a business continuity crisis.<\/p>\n\n\n\n

For a full overview of US regulations affecting commerce (including federal controlled substance law, state licensing, and payment processing), see our US Regulated Industries Commerce Guide (coming soon).<\/p>\n\n\n\n

\n\n\n\n

What Regulations Affect Cannabis Commerce?<\/h2>\n\n\n\n

Cannabis commerce operates under a layered regulatory environment where federal prohibition, state licensing regimes, and local ordinances create a compliance environment unlike any other retail category. No single regulation governs cannabis eCommerce. Operators must handle all of these simultaneously.<\/p>\n\n\n\n

Regulation<\/th>Jurisdiction<\/th>What It Means for Cannabis Commerce<\/th>Impact<\/th><\/tr><\/thead>
Federal Controlled Substances Act<\/td>US (federal)<\/td>Cannabis remains Schedule I. Federal illegality drives platform bans, payment restrictions, and banking barriers.<\/td>\ud83d\udd34 Critical<\/td><\/tr>
State cannabis licensing<\/td>Per-state (40+ states with some form of legal cannabis)<\/td>Each state issues its own cultivation, processing, distribution, and retail licenses with specific operational requirements.<\/td>\ud83d\udd34 Critical<\/td><\/tr>
Seed-to-sale tracking mandates<\/td>Per-state (Metrc in 30+ markets)<\/td>All cannabis products must be tracked from cultivation through final sale in state-mandated systems like Metrc, BioTrack, or Leaf Data Systems.<\/td>\ud83d\udd34 Critical<\/td><\/tr>
State-by-state age verification<\/td>Per-state<\/td>All cannabis sales require age verification (21+ for adult use, varies for medical). Online orders must include identity verification.<\/td>\ud83d\udfe1 Moderate<\/td><\/tr>
Tax compliance (state + local)<\/td>Per-state + per-municipality<\/td>Cannabis excise taxes, sales taxes, and local taxes vary by jurisdiction and product type. Multi-state operators face different tax structures in every market.<\/td>\ud83d\udfe1 Moderate<\/td><\/tr>
Advertising and marketing restrictions<\/td>Per-state<\/td>Most states restrict cannabis advertising, including digital marketing, social media, and online content. eCommerce storefronts must comply.<\/td>\ud83d\udfe1 Moderate<\/td><\/tr>
SAFE Banking Act (pending)<\/td>US (federal)<\/td>If enacted, would protect financial institutions serving state-legal cannabis businesses from federal penalties \u2014 potentially opening mainstream payment processing.<\/td>\ud83d\udfe1 Moderate (future)<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

Seed-to-sale tracking<\/strong> is the linchpin regulation for cannabis eCommerce. Metrc is the dominant tracking system, operating in 30+ regulated markets. Every licensee must record the complete lifecycle of every cannabis product from cultivation to final sale.<\/p>\n\n\n\n

Your commerce platform must integrate with Metrc’s API to report inventory movements, sales transactions, and product transfers in real time. Mistakes trigger fines, inventory holds, and license suspension. Federal cannabis regulations are detailed in the Electronic Code of Federal Regulations (eCFR)<\/a>, which governs DEA and FDA enforcement.<\/p>\n\n\n\n

State licensing<\/strong> creates a unique architectural challenge. Each state license requires its own storefront, catalog, pricing structure, and compliance configuration. An MSO operating in California, Colorado, Illinois, and New York effectively runs four separate businesses, each with different regulations, tax structures, and seed-to-sale tracking requirements. Yet it still needs centralized management of operations, inventory, and reporting.<\/p>\n\n\n\n

\n\n\n\n

Why Cannabis Gets Banned from Mainstream eCommerce Platforms<\/h2>\n\n\n\n

Cannabis operators face a three-layered deplatforming risk that no amount of workarounds can eliminate: platform bans, payment processor shutdowns, and infrastructure dependencies.<\/p>\n\n\n\n

The platform ban<\/h3>\n\n\n\n

Shopify’s Acceptable Use Policy prohibits the sale of all cannabis products containing more than 0.3% THC \u2014 including flower, concentrates, edibles, vapes, and hemp-derived cannabinoids where total THC exceeds the threshold. This is not a restriction that can be negotiated. Shopify has shut down cannabis merchants without warning, giving affected businesses as little as one week to export data and migrate to a new platform.<\/p>\n\n\n\n

BigCommerce restricts cannabis to CBD-only<\/strong>, permitting hemp-derived products below 0.3% THC while excluding all THC cannabis products. For cannabis brands planning to expand from CBD into THC, BigCommerce creates a hard ceiling that forces migration at scale.<\/p>\n\n\n\n

Salesforce Commerce Cloud generally restricts cannabis merchants through its acceptable use policies, making it an unreliable foundation for cannabis commerce operations.<\/p>\n\n\n\n

The payment processor shutdown<\/h3>\n\n\n\n

Even for operators who find a platform that technically allows cannabis, the payment processing layer creates an equally severe deplatforming risk. Visa, Mastercard, Stripe, and PayPal all prohibit cannabis transactions, regardless of state legality. In December 2022, Mastercard began shutting down cannabis-linked terminals en masse. Visa followed with similar enforcement actions. Cannabis retailers regularly experience sudden processor shutdowns \u2014 losing the prior day’s revenue, having their merchant accounts terminated, and getting blacklisted from future processing.<\/p>\n\n\n\n

The payment environment for cannabis<\/strong> relies on ACH transfers (the most stable compliant method at 1-1.5% per transaction), cannabis-specific payment processors, and point-of-banking solutions. These are unavailable through Shopify Payments or BigCommerce’s standard gateway stack.<\/p>\n\n\n\n

Cannabis operators need platforms that support flexible payment provider integration. This architecture challenge mirrors data residency and cross-border compliance in GDPR and Schrems II<\/a>, where platform flexibility is critical to regulatory compliance.<\/p>\n\n\n\n

The platform dependency trap<\/h3>\n\n\n\n

The compounding risk<\/strong> is what makes cannabis deplatforming uniquely destructive. You build your store on Shopify, invest months in themes, apps, integrations, and seed-to-sale connections. Then Shopify updates its policy and shuts you down.<\/p>\n\n\n\n

Your data becomes inaccessible. Metrc integrations fail, creating compliance violations with state regulators. Customers see error pages. Wholesale buyers cannot place orders. This happens regularly to cannabis businesses in the SaaS environment.<\/p>\n\n\n\n

How platforms compare for cannabis commerce<\/h3>\n\n\n\n
Cannabis Commerce Requirement<\/th>Shopify Plus<\/th>Salesforce CC<\/th>commercetools<\/th>Self-Hosted (Spree)<\/th><\/tr><\/thead>
THC cannabis allowed<\/td>\u274c Banned<\/td>\u274c Restricted<\/td>\u26a0\ufe0f TOS may restrict<\/td>\u2705 No platform restrictions<\/td><\/tr>
Deplatforming risk<\/td>\ud83d\udd34 High<\/td>\ud83d\udd34 High<\/td>\ud83d\udfe1 Moderate (SaaS TOS)<\/td>\u2705 None \u2014 you own the platform<\/td><\/tr>
Cannabis PSP integration<\/td>\u274c Standard processors only<\/td>\u274c Standard Salesforce payments<\/td>\u26a0\ufe0f Custom integration needed<\/td>\u2705 Any processor via API<\/td><\/tr>
Metrc \/ seed-to-sale API<\/td>\u274c No native integration<\/td>\u274c No native integration<\/td>\u26a0\ufe0f Custom build possible<\/td>\u2705 Open API for any tracking system<\/td><\/tr>
Multi-state multi-store<\/td>\u26a0\ufe0f Separate stores per state<\/td>\u26a0\ufe0f Available<\/td>\u26a0\ufe0f Project-based separation<\/td>\u2705 Native multi-tenant \/ multi-store<\/td><\/tr>
State-by-state tax config<\/td>\u2705 Tax automation available<\/td>\u2705 Available<\/td>\u2705 Available<\/td>\u2705 Customizable per-jurisdiction<\/td><\/tr>
Source code audit<\/td>\u274c Proprietary<\/td>\u274c Proprietary<\/td>\u274c Proprietary<\/td>\u2705 Full source code (BSD)<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

The pattern is clear<\/strong>: platforms that dominate mainstream eCommerce either ban cannabis or create deplatforming risk. Self-hosted open source platforms, where no vendor controls your uptime or data, are the only architecturally viable path.<\/p>\n\n\n\n

\n\n\n\n

What Does Cannabis Commerce Actually Require?<\/h2>\n\n\n\n

Cannabis multi-state operators do not need a generic online store \u2014 they need a commerce platform that supports a specific combination of business models and compliance capabilities that no single SaaS platform provides natively.<\/p>\n\n\n\n

Business Requirement<\/th>Why It Matters for Cannabis MSOs<\/th>Platform Capability Needed<\/th><\/tr><\/thead>
State-by-state storefronts<\/td>Each state license requires its own storefront with state-specific catalog, pricing, and compliance configuration<\/td>Multi-tenant or multi-store with isolated tenant configurations<\/td><\/tr>
B2B wholesale ordering<\/td>Licensed dispensary-to-distributor procurement with volume pricing, net terms, and buyer-specific catalogs<\/td>B2B module with price lists, buyer organizations, and approval workflows<\/td><\/tr>
Age and license verification<\/td>All purchases require 21+ age verification; B2B requires state license validation<\/td>Customizable checkout with third-party verification API integration<\/td><\/tr>
Seed-to-sale tracking integration<\/td>State regulators require real-time product tracking from cultivation to final sale via Metrc or equivalent<\/td>Open API for integration with Metrc, BioTrack, or Leaf Data Systems<\/td><\/tr>
Cannabis-specific payment processing<\/td>Mainstream processors ban cannabis; need ACH, cannabis-specific PSPs, or point-of-banking<\/td>No payment provider lock-in \u2014 support for any PSP via API<\/td><\/tr>
Per-state tax configuration<\/td>Cannabis excise taxes, sales taxes, and local taxes differ by jurisdiction and product type<\/td>Configurable tax rules per storefront \/ per jurisdiction<\/td><\/tr>
Centralized operations management<\/td>MSOs need a single admin view across all state operations for inventory, orders, reporting, and compliance<\/td>Central admin with per-tenant\/per-store granularity<\/td><\/tr>
Full audit trail<\/td>State compliance audits require complete order and inventory history with timestamped access logs<\/td>Immutable audit logging with configurable retention policies<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

Meeting these requirements on generic platforms<\/strong> means stacking third-party plugins for multi-store management, B2B ordering, age verification, seed-to-sale integration, and payment processing. Each plugin has its own vendor, update cycle, and failure modes.<\/p>\n\n\n\n

A composable architecture eliminates this. B2B, marketplace, multi-store, multi-tenant, and compliance capabilities as built-in modules give operators a single platform handling multi-state cannabis commerce complexity.<\/p>\n\n\n\n

\n\n\n\n

How Does Spree Enterprise Serve Cannabis Commerce?<\/h2>\n\n\n\n

Spree Enterprise combines the modules MSOs need<\/strong>: multi-tenant, multi-store, B2B, and marketplace with self-hosted architecture that eliminates deplatforming risk. Because Spree is open source and self-hosted, no vendor can ban you, no TOS changes affect you, and no platform dependency creates risk.<\/p>\n\n\n\n

Cannabis Requirement<\/th>Spree Enterprise Feature<\/th>How It Works<\/th><\/tr><\/thead>
State-by-state storefronts<\/td>Native multi-tenant \/ multi-store<\/td>Each state operation runs as a separate tenant or store with its own catalog, pricing, tax configuration, and branding \u2014 managed from a single admin<\/td><\/tr>
B2B wholesale ordering<\/td>Native B2B commerce module<\/td>Price lists, buyer organizations, approval workflows, net terms, and gated catalogs for licensed dispensary buyers<\/td><\/tr>
Seed-to-sale integration<\/td>Open API (REST + GraphQL)<\/td>Connect to Metrc, BioTrack, or Leaf Data Systems via API \u2014 report inventory movements, sales, and transfers in real time<\/td><\/tr>
Cannabis payment processing<\/td>No payment provider lock-in<\/td>Integrate any PSP \u2014 including cannabis-specific processors, ACH providers, and point-of-banking solutions \u2014 without forced vendor dependencies<\/td><\/tr>
Age and license verification<\/td>Customizable checkout<\/td>Third-party verification APIs (age verification services, state license databases) integrate at the checkout level<\/td><\/tr>
Per-state compliance<\/td>Per-tenant configuration<\/td>Each state’s regulatory requirements \u2014 tax rules, product restrictions, labeling mandates, reporting formats \u2014 are configured independently per tenant<\/td><\/tr>
Centralized management<\/td>Multi-tenant admin<\/td>A single admin dashboard manages all state operations \u2014 inventory, orders, customer data, and compliance reporting \u2014 with per-state granularity<\/td><\/tr>
Full audit trail<\/td>Built-in audit logging<\/td>Every admin action, API call, and data access is logged with user identity, timestamp, and action type<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

Why Spree Enterprise specifically<\/h3>\n\n\n\n

Spree’s composable architecture<\/strong> enables cannabis MSOs to combine B2B wholesale distribution, per-state retail storefronts, and centralized operations on one platform. No separate instances needed for each business model. No third-party plugins required.<\/p>\n\n\n\n

The multi-tenant module runs dozens of state-specific storefronts on shared infrastructure, each with its own compliance configuration. The B2B module handles dispensary-to-distributor procurement with price lists, buyer organizations, and approval workflows.<\/p>\n\n\n\n

Because Spree is open source<\/strong> (BSD 3-Clause license), your team has full visibility into every line of code. For an industry under constant regulatory scrutiny, where state auditors demand evidence of how systems handle product tracking, the ability to audit your own code is a compliance advantage proprietary systems cannot match.<\/p>\n\n\n\n

The self-hosting model<\/strong> means cannabis operators own their infrastructure, data, and uptime. No Shopify policy shuts you down. No TOS update restricts your catalog. No SaaS vendor sits between you and your customers. When the SAFE Banking Act passes and mainstream payment processors open to cannabis, Spree’s open payment architecture means immediate adoption without waiting for vendor support.<\/p>\n\n\n\n

\n\n\n\n

Architecture & Deployment for Cannabis Commerce<\/h2>\n\n\n\n

Cannabis commerce architecture must account for multi-state compliance isolation, seed-to-sale system integration, and payment processor flexibility \u2014 all while maintaining centralized operational control.<\/p>\n\n\n\n

Hosting and infrastructure<\/strong> for cannabis has no GDPR or ITAR data residency mandates. The primary concern is uptime, reliability, and payment processor connectivity. AWS and GCP handle peak-demand events (4\/20, new state launches, wholesale ordering cycles) with reliable API connections to Metrc and state systems. On-premise deployment is also viable for operators seeking maximum control.<\/p>\n\n\n\n

Multi-state architecture<\/strong> uses Spree’s multi-tenant module with one tenant per state license. Each tenant gets its own storefront, catalog, pricing, tax configuration, and compliance settings. All share the underlying infrastructure, codebase, and admin tooling.<\/p>\n\n\n\n

This eliminates operational complexity of managing separate instances per state while maintaining compliance isolation. New state launches require provisioning a tenant with state-specific configuration, not deploying an entirely new instance.<\/p>\n\n\n\n

Integration architecture<\/strong> includes seed-to-sale tracking (Metrc, BioTrack, Leaf Data Systems), cannabis-specific payment processors (Hypur, CanPay, Aeropay, Paytender), age verification, and state licensing databases. Spree’s REST and GraphQL APIs provide integration without middleware or custom API work. ERP integration (QuickBooks, NetSuite) handles financial consolidation.<\/p>\n\n\n\n

Security<\/strong> for cannabis commerce requires handling sensitive customer data (purchase history tied to controlled substances). Spree’s enterprise security includes AES-256 encryption at rest, TLS 1.2+ in transit, granular RBAC, and immutable audit logging that meets state regulator expectations.<\/p>\n\n\n\n

\n\n\n\n

Cannabis Compliance Resources<\/h2>\n\n\n\n

Cannabis operations often overlap with adjacent regulatory frameworks that carry similar compliance requirements. Below are detailed guides to the regulations most relevant to cannabis commerce, plus related industry deep dives covering similar deplatforming and payment processing challenges.<\/p>\n\n\n\n

Compliance by intersection with other regulations:<\/strong><\/p>\n\n\n\n

HIPAA applies to cannabis operators handling medical cannabis patient records. If your operation involves medical cannabis sales, patient data privacy, or health practitioner verification, the Full HIPAA Compliance Guide<\/a> covers the intersection of cannabis commerce and healthcare privacy law.<\/p>\n\n\n\n

FedRAMP compliance is relevant if your cannabis business sells to state government procurement programs. Government agencies often require FedRAMP-authorized infrastructure. More details: Full HIPAA Compliance Guide<\/a>.<\/p>\n\n\n\n

Related industry deep dives sharing similar regulatory patterns:<\/strong><\/p>\n\n\n\n

Firearms and ammunition eCommerce faces platform deplatforming challenges parallel to cannabis. Firearms and Ammunition eCommerce: Building Deplatforming-Proof Commerce (coming soon) covers payment processing, platform bans, and self-hosted strategies in the regulated weapons space.<\/p>\n\n\n\n

iGaming and white-label gambling platforms encounter similar deplatforming and payment processing constraints. iGaming & White-Label Gambling Platforms (coming soon) explores how gambling operators solve comparable problems with payment networks and platform risk.<\/p>\n\n\n\n

Regional compliance frameworks:<\/strong><\/p>\n\n\n\n

US Regulated Industries Commerce Guide (coming soon) provides an overview of US federal and state frameworks affecting regulated commerce across cannabis, firearms, alcohol, and financial services.<\/p>\n\n\n\n

\n\n\n\n

Build Cannabis Commerce with Spree<\/h2>\n\n\n\n

Spree Enterprise gives cannabis operators a composable commerce platform that combines multi-tenant state-by-state storefronts, B2B wholesale ordering, and centralized operations management \u2014 with the self-hosted architecture that makes deplatforming impossible.<\/p>\n\n\n\n

Whether you are launching a new multi-state cannabis operation from scratch or migrating off a platform that has deplatformed you or restricted your growth, the Spree team can help you scope the right architecture for your market.<\/p>\n\n\n\n

Talk to the Spree Team \u2192<\/strong><\/a><\/p>\n\n\n\n

Frequently Asked Questions<\/h2>\n\n\n\n
\n
Which ecommerce platform works for cannabis?<\/strong><\/summary>\n

Self-hosted open source platforms are the only architecturally reliable option for cannabis eCommerce. Mainstream SaaS platforms (Shopify, BigCommerce, Salesforce) either ban cannabis or impose restrictions creating deplatforming risk. Self-hosted platforms like Spree eliminate this risk because you own the infrastructure and codebase. No vendor can update a TOS and shut you down. For multi-state operators, Spree’s native multi-tenant and B2B modules handle business model complexity without plugin stacking.<\/p>\n<\/details>\n\n\n

Can I sell cannabis on Shopify?<\/strong><\/summary>\n

No. Shopify’s Acceptable Use Policy prohibits the sale of all cannabis products containing more than 0.3% THC (including flower, concentrates, edibles, vapes, and cannabinoids above the threshold). Shopify allows compliant hemp-derived CBD products within federal limits, but THC cannabis (the core product for dispensaries) is banned. Shopify has shut down cannabis merchants without warning, giving operators as little as one week to migrate.<\/p>\n<\/details>\n\n\n

Can I sell cannabis on BigCommerce?<\/strong><\/summary>\n

BigCommerce restricts cannabis to CBD-only, permitting hemp-derived products below 0.3% THC. All THC cannabis products are excluded. For cannabis brands planning to expand from CBD into THC (the natural growth path as states legalize adult use), BigCommerce creates a hard ceiling. It forces migration when it’s most disruptive: at scale.<\/p>\n<\/details>\n\n\n

What regulations apply to cannabis ecommerce?<\/strong><\/summary>\n

Cannabis eCommerce must handle federal controlled substance law (cannabis remains Schedule I), state cannabis licensing (each state has its own regime), seed-to-sale tracking mandates (Metrc in 30+ markets), age verification requirements, per-jurisdiction tax compliance, and advertising restrictions. Multi-state operators must comply with all applicable regulations in every state simultaneously, making cannabis one of the most regulation-dense eCommerce categories.<\/p>\n<\/details>\n\n\n

How much does cannabis ecommerce cost?<\/strong><\/summary>\n

Cannabis eCommerce on Spree Enterprise typically costs $50,000\u2013$150,000 first-year for multi-state operations (covering platform license, hosting, seed-to-sale integration, payment setup, state configuration). Ongoing costs scale with infrastructure and state count, not revenue. SaaS platforms either ban cannabis or charge per-transaction fees plus expensive workarounds. Self-hosted platforms eliminate per-transaction fees. Your costs are infrastructure and development, not revenue sharing.<\/p>\n<\/details>\n\n\n

What payment processors work for cannabis?<\/strong><\/summary>\n

Mainstream payment processors (Visa, Mastercard, Stripe, PayPal) prohibit cannabis transactions regardless of state legality. Cannabis operators rely on ACH transfer providers (the most stable method at 1-1.5% per transaction), cannabis-specific processors (Hypur, CanPay, Aeropay, Paytender), and point-of-banking solutions. Integration requires open payment architecture, not locked processors. Spree Enterprise supports any payment processor via API, including specialized cannabis processors that mainstream SaaS platforms don’t integrate.<\/p>\n<\/details>\n\n\n

Will the SAFE Banking Act change cannabis ecommerce?<\/strong><\/summary>\n

The SAFE Banking Act passed the Senate Banking Committee with bipartisan support in 2025, but full passage remains pending. If enacted, it would protect financial institutions serving state-legal cannabis businesses from federal penalties, potentially opening mainstream payment processing to cannabis commerce. However, platform deplatforming risk remains even with SAFE Banking. Shopify’s cannabis ban is a platform policy decision, not a banking regulation issue. Self-hosted platforms let you adopt mainstream payment processing immediately without waiting for SaaS vendor policy changes.<\/p>\n<\/details>\n\n