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 setupMichigan · Diagnostics
Last reviewed
Michigan's payment problems cluster around volume. High transaction counts and thin margins mean a small per-sale defect becomes a large monthly number fast, and a tender outage during a rush costs more here than in a lower-count market. Most of what Michigan operators call a payment problem is really a reconciliation problem that was allowed to run for a few weeks.
The fixes are unglamorous: daily reconciliation, one workflow, written refund rules, a practised outage script, and a pre-qualified alternative provider. Operators who have those five things in place rarely have a payment emergency.
This is the most common Michigan problem and the most expensive to fix late. The gap usually comes from refunds routed inconsistently, voids handled differently by shift, or a settlement stream that nets fees before deposit in a way the POS does not model.
Fix one refund rule and one void rule across all tills and sites before you investigate anything.
Take one day, match every transaction to settlement and deposit, and identify which category is drifting.
Once you know the category, unwind the history for that category only rather than auditing everything.
Outages are a certainty, not a risk. The damage is determined by whether staff have a script. Keep a printed fallback at each till, give managers authority to switch messaging immediately, and log every incident with a duration so you have evidence at the next provider review.
Read the reserve clause first — many Michigan operators discover a hold was contractual all along. If it is risk-driven, ask which metric moved. Sharp volume growth, an unusual refund pattern or a documentation gap are the usual triggers, and each has a different remedy.
Get statements and settlement files, confirm the stop date and treatment of funds in transit in writing, then onboard an alternative in parallel. Confirm your regulatory reporting obligations with the Cannabis Regulatory Agency remain satisfied through the switch — a tender change should never disturb what a sale records.
Illustrative example
A two-site Michigan operator found a growing monthly gap between POS tender totals and deposits. The cause was a refund rule applied differently at each site: one returned refunds through the tender, the other from the drawer. Standardising the rule stopped the gap immediately, and unwinding four weeks of refunds — rather than auditing all transactions — closed the historic difference in two days.
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 applicationNearly always refunds, voids or fee netting. Standardise the refund and void rule across every till first, then reconcile one clean day end to end to identify which category is drifting, then unwind only that category historically. Auditing everything at once is slower and rarely necessary.
With a script staff have practised. Post visible cash-only messaging, keep recording every sale normally, give the manager on duty authority to act without escalation, and log the duration. Outages are inevitable; unrecorded sales and improvised messaging are not.
Check the agreement before assuming it is not. Many reserve clauses permit adjustment based on risk metrics with minimal notice. If it is contractual, your route is renegotiation with a documented history of clean performance; if it is not, you have a contract issue worth raising immediately in writing.
Where this common payment problems page sits in the wider Michigan 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 large Midwest market transitioning most existing medical dispensaries into dual medical-and-adult-use retailers, with high-volume urban stores and a new adult-use tax to reconcile.
Bordering state
A non-programme state surrounded by legal markets, where CBD retail and hemp distribution carry all of the payment demand.
Bordering state
A state with no cannabis program at all, wedged between adult-use Illinois and medical Michigan, where every dollar of Wisconsin cannabis demand that can travel does — and where hemp and CBD businesses are the only card-acceptance story that actually exists.
Bordering state
A licence-limited market with dispensary licensing at IDFPR, cultivation at the Department of Agriculture, and cross-agency coordination through the Cannabis Regulation Oversight Office.
Send the symptom — a gap, a hold, an outage pattern or a notice letter. We will tell you the likely cause and the first three things to do about it.