California · Systems

POS and Payment Integrations for California Cannabis Businesses

Last reviewed

The short answer

In California the integration question is rarely 'does this payment method exist' — it is 'is it certified against the exact version of the POS we are running, and does it leave our reporting intact'. California operators run a wide mix of POS platforms, often with delivery modules and multi-site configurations bolted on, and certification is version-specific far more often than vendors imply.

The second California-specific factor is delivery. A large share of California retail volume moves through delivery, and delivery changes the payment question entirely: tender is usually collected before dispatch or at the door under a different workflow than the counter, and refunds have to be handled against an order rather than a till.

Certification is version-specific

Ask for certification against your POS version number, not the product name. An integration that works on the current release may be untested on the build you are actually running, especially for multi-site California operators who stagger upgrades across stores. Get the answer in writing and ask when it was last re-tested.

  • Record your exact POS version per site before starting any integration conversation
  • Ask who owns support when the payment device fails but the POS is fine
  • Ask what a POS upgrade does to the integration and how much notice you get
  • Confirm whether the integration is native or a middleware layer, and who maintains it

Protecting California traceability and tax reporting

Your reporting obligations do not change because tender changed. The sale must still carry its line items, excise treatment and customer type, and it must still flow into your traceability reporting the same way. Validate this by comparing a week of reports before and after the change, not by trusting the vendor's description.

Confirm current requirements with the Department of Cannabis Control and the CDTFA directly — payment vendors are not authoritative on California reporting mechanics.

The pre-launch test list

Every integration failure we see in California is one of a short list of untested paths. Run all of them on real transactions during a quiet hour, and have a named person sign off each one before the tender goes live across the floor.

  1. 01

    Full sale and settlement

    Run a standard sale end to end and confirm it appears identically in POS totals, settlement report and the deposit.

  2. 02

    Refund, partial refund and void

    Test all three separately. Partial refunds are the most commonly broken path and the hardest to fix retrospectively.

  3. 03

    Offline and outage behaviour

    Disconnect the device or the network and confirm the counter has a documented fallback that does not create an unrecorded sale.

  4. 04

    Delivery order flow

    If you deliver, test the pre-dispatch funding path, driver-side confirmation and the cancelled-order refund separately from the counter flow.

  5. 05

    End-of-day reconciliation

    Close a full day with the new tender live and reconcile POS totals to the deposit before extending to other sites.

Illustrative example

Worked example: a three-site California operator staggering rollout

An operator with two storefronts and a delivery hub ran the new tender at the lowest-volume store for two weeks before touching the others. That store surfaced a partial-refund failure that would have hit every site: refunds against multi-item baskets reconciled correctly in the POS but posted as full reversals in settlement. Fixing it once at one store cost a week; discovering it across three sites during a holiday weekend would have cost considerably more.

  • Pilot site chosen for low volume, not convenience
  • Two-week soak period with daily reconciliation before extending
  • Delivery workflow tested as a separate project from the counter

Illustrative scenario built from patterns we see in this market. It is not a specific customer, and the figures are indicative rather than a promise of any result.

Where you are today

Four ways operators start with us on a California cannabis, hemp or CBD business

New or pre-revenue business

Not processing yet. We map which payment methods your license type and products can realistically support, what each costs, and what your application file needs before you open.

Plan your payment setup

Operating and looking to switch

Already processing but paying too much, funding too slowly, or working around a system that does not fit. Send statements and we return a line-by-line read plus alternatives.

Review my current setup

Recently shut down or restricted

Account terminated, frozen, capped or moved to reserve. We help you interpret the notice, pursue held funds, and rebuild with fewer single points of failure.

Get help with a complex account

Declined during underwriting

Turned down on application. We read the decline reason, identify what was missing or mismatched in the file — licence, ownership, product mix, banking — and rebuild the submission before it goes back out.

Review a declined application

Frequently asked questions

Will a payment integration break my California traceability reporting?+

It should not, provided the tender writes into the existing sale record rather than creating a parallel one. Prove it by comparing a full week of reporting output before and after go-live, and confirm current reporting requirements with the Department of Cannabis Control rather than with the payment vendor.

How long does a California cannabis POS integration take?+

Plan in weeks, not days, and expect most of the time to go on underwriting and certification rather than technical work. Multi-site California operators should add a pilot period at one location before extending, which typically adds two weeks and removes most of the risk.

Does delivery need a different payment setup than the counter?+

Usually yes. Delivery tender is generally collected against an order before dispatch or under a separate door workflow, and refunds attach to the order rather than a till. Treat it as a second integration with its own test list, even if the same provider supplies both.

Related guides, questions and references

Where this pos and payment integrations page sits in the wider California and national picture.

QuestionWhich POS systems support cannabis paymentsMost dedicated cannabis point-of-sale platforms — the systems built for licensed retail with state track-and-trace reporting — support at least one integrated electronic payment method, usually through partner integrations rather than their own acquiring. What matters is not whether a POS 'supports payments' in general, but whether your specific payment method, provider and hardware are certified for your POS version and state.Open State guidePOS and payment integrations in IllinoisIntegration work in Illinois lives or dies on whether tax components survive the change.Open ArticleTraceability Sync and Payments: Keeping Sales Data ConsistentThree systems record every dispensary sale: the point of sale, the payment settlement report, and the state traceability system.Open Servicehow we handle payment integrationsPayments wired into the systems that already run your business.Open Comparisonhow we compare with POSaBITSells cannabis point of sale and payments together, so comparisons usually turn on whether you want your POS vendor and your payment provider to be the same company.Open QuestionSeed-to-sale and payment reportingMetrc is a state track-and-trace system for plants, packages and sales events — it does not process payments. Payments integrate indirectly: the point-of-sale records the sale and reports the required data to Metrc, while the payment provider settles the money and reports separately. Reconciliation happens in the POS and accounting layer, matching Metrc-reported sales to settlement deposits.Open

Planning an integration in California?

Send your POS platform and version, site count and whether delivery is in scope. We will tell you what is certified against your build, what to test, and what sequence keeps the rollout boring.