Tender handling
Each tender type carries its own capture, refund, and reconciliation behavior instead of being flattened into a single payment blob.
Platform
Money movement you can reconcile.
Cannabis payments are awkward by regulation, not by choice. The platform treats tender types, banking rails, and the ledger as first-class so the day's close actually ties out.
Multiple tender types
Cash, external card, store credit, and gift cards are modeled distinctly, because reconciling them is a different job for each.
A real ledger
Financial movement is recorded in a double-entry ledger rather than inferred after the fact from a pile of transactions.
Bank connectivity
Account linking through established banking rails, so deposits and settlements can be matched against the register.
STORE PERFORMANCELast 7 days
- Net sales$48,210+12.4%
- Avg basket$71.40+3.1%
- Discount load8.2%−1.6%
M
T
W
T
F
S
S
Illustrative. Demos run in a dedicated environment with our team.
In detail
What payments covers
Double-entry ledger
Sales, refunds, drawer movements, and settlements post to a ledger with a deterministic financial core, so balances are derived rather than guessed.
Cash reconciliation
Drawer counts, drops, and variance tie back to the shift and employee that produced them.
Bank account linking
Connect accounts through Plaid to match settlement activity against recorded sales.
Idempotent money paths
Payment operations are idempotent by construction, so a retried request does not become a second charge.
Store credit and gift cards
Balances are tracked as real liabilities with their own audit trail, not as ad-hoc discounts.
Connected
Works with the rest of the platform.
These are the areas this capability touches most directly.
See it running on real workflows.
Demos are run by our team in a dedicated demo environment, walked through live on a call — so you see the parts that matter to your operation, not a generic tour.