Most dispensary online menus reserve inventory without collecting payment, because card processing for cannabis is unreliable. Bank-to-bank ACH collects the full basket at checkout instead. The customer connects their bank once, in about thirty seconds, and the order arrives paid rather than reserved, so pickup becomes handover only.
Online orders are worth more per basket. An order that is only reserved is not yet worth anything.
The short version
- Most cannabis online menus reserve inventory without collecting payment.
- Unpaid reservations produce no-shows, which hold inventory and misstate demand.
- Card checkout for cannabis fails for the same classification reason it fails at the counter.
- Bank-to-bank prepay collects the full basket at checkout, so pickup becomes handover only.
The reservation problem
Ask most dispensary operators what their online ordering does and the honest answer is that it holds product. The customer browses a menu, submits an order, receives a confirmation, and pays at the counter or at the door. Nothing has actually been collected.
That gap creates a set of costs that get filed under everything except payments:
- No-shows. An order that costs nothing to place costs nothing to abandon. The product sat aside for a customer who never came.
- Inventory held against nothing. Pull, bag, and set aside labour spent on orders with no commitment behind them.
- Distorted demand data. Online order volume looks like demand, but a meaningful share of it never converts, so forecasting from it overstates the channel.
- A second transaction at pickup. The customer still queues, still pays, and the online step saved nobody time.
The channel is doing marketing work, not commerce work.
Why cannabis card checkout keeps failing online
Online card acceptance for cannabis runs into the same wall as the counter, for the same reason. A card transaction requires a merchant category code, and there is no code for state-licensed cannabis. An e-commerce gateway boarded for a cannabis business is coded as something else, and card-not-present transactions attract more scrutiny than card-present ones, not less.
Operators who have had an online gateway work for a while are usually early in the same cycle that closes counter accounts: it boards, it works, monitoring identifies the mismatch, and the account terminates with funds commonly held for around 90 days.
How bank-to-bank prepay works at online checkout
The customer builds a basket on your menu and goes to checkout. Instead of a card form, they connect their bank account once, in about thirty seconds, and confirm the exact total. The funds are captured before the order enters your queue.
The transaction settles bank-to-bank on federally regulated banking rails, next day, into your own account. There is no card network in the transaction, so there is no category to code incorrectly.
- Basket built on your existing menu or storefront.
- Checkout. Bank connects once; one confirmation on every order after that.
- Payment captured before the order is accepted into the queue.
- Order fulfilled for pickup or dispatched for delivery.
- Handover only at the counter or the door. ID and compliance checks, no transaction.
What changes when orders arrive paid
Pickup stops being a second queue. The customer arrives, is verified, and leaves with a bag. Staff time per online order drops because the transaction is not repeated in person.
No-shows become refunds rather than write-offs, and they become rare, because the commitment now exists before the pull. Inventory that is set aside is set aside against money that has moved.
Demand data becomes real. Online order volume and revenue are the same number, so the channel can actually be evaluated and forecast from.
And every sale captures a customer record, name, phone and email, held in your account rather than a marketplace's, which is what makes the built-in outreach tools worth anything.
Integrating with what you already run
Most operators are not looking to replace a menu platform or POS that works. The payment layer connects through API and existing POS and e-commerce integrations, so the storefront your customers know stays where it is and the checkout step changes underneath it.
Transactions post to your ledger automatically if you use QuickBooks, and the same platform covers SMS pay links for delivery, in-store QR, and wholesale invoicing, settling into one account.