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 setupCalifornia · Systems
Last reviewed
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.
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.
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.
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.
Run a standard sale end to end and confirm it appears identically in POS totals, settlement report and the deposit.
Test all three separately. Partial refunds are the most commonly broken path and the hardest to fix retrospectively.
Disconnect the device or the network and confirm the counter has a documented fallback that does not create an unrecorded sale.
If you deliver, test the pre-dispatch funding path, driver-side confirmation and the cancelled-order refund separately from the counter flow.
Close a full day with the new tender live and reconcile POS totals to the deposit before extending to other sites.
Illustrative example
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.
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
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 setupAlready 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 setupAccount 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 accountTurned 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 applicationIt 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.
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.
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.
Where this pos and payment integrations page sits in the wider California and national picture.
Bordering states first, because supply chains, banking relationships and cross-border customer traffic usually follow them. Comparable markets are shown when a neighbouring state has no guide yet.
Bordering state
A mature, oversupplied adult-use market where years of price compression have made every basis point of payment cost matter more than it does elsewhere.
Bordering state
A tourism-heavy adult-use market where Las Vegas visitor volume, cash-intensive retail and licensed consumption lounges shape payment planning more than population size does.
Bordering state
A dual medical and adult-use market administered by the Arizona Department of Health Services, with many operators running both programmes from the same establishment.
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.