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 setupNew York · Diagnostics
Last reviewed
In New York the most common payment problems are the problems of a young market: caps set for a smaller business than you have become, reserves that bite in a slow month, refund paths that were never tested on delivery orders, and documentation that drifted out of sync with the state record while everyone was busy opening.
None of these are dramatic on their own. They become dramatic when two arrive together — a cap hit during a promotion, or a hold in the same week as a tax date. The fixes are mostly about anticipating the combination.
Caps set at onboarding are sized to the business you were, not the one you are after a good month. Hitting one mid-month means tender stops working while customers are still arriving.
Track monthly volume against the cap weekly. A cap you can see coming is a phone call; a cap you hit is an outage.
Establish who raises a cap, what evidence they need and how long it takes, before you need it.
Any store that can trade cash-only for a week without stress is insulated from cap and outage events.
Reserves modelled on a strong month become painful in a quiet one, and New York's seasonality and local competition can produce sharp swings. Pull the clause, model it against your worst month, and if the arrangement is unsustainable at that level, raise it with a documented performance history rather than a complaint.
Cancelled and returned delivery orders are where refund policy usually breaks in New York, because the tender was collected against an order and there is no till to reverse it at. Define the path in writing before launch: who authorises, through which channel, within what window, and how it appears in reconciliation.
Fast-growing operators change addresses, add owners and restructure entities, and the payment file quietly goes stale. This is the most common cause of a sudden documentation request escalating into a review. Reconcile against the state cannabis regulator's record quarterly and send corrections proactively.
Illustrative example
A New York retailer ran a promotion that pushed monthly volume 40% above plan and hit the tender cap on day 19. Tender stopped, the store reverted to cash mid-promotion, and the cap review took eleven days. After the incident the operator set a weekly run-rate check against the cap and agreed a written review path with the provider — the next growth month was a scheduled conversation rather than an outage.
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 applicationMost often a volume cap. Caps are sized at onboarding and rarely adjust automatically, so a growth month can exhaust one before month end. Track volume against your cap weekly and agree a written review path with your provider before you need it.
Against the order, through a defined channel, with named authorisers and a stated window — decided and documented before launch. Test a pre-dispatch cancellation and a doorstep refusal separately, because they behave differently and only one of them resembles a counter refund.
Usually because the information you hold no longer matches the state licence record: an address, an owner, an entity name. Reconcile quarterly against the regulator's record and send corrections proactively; unexplained mismatches are read as risk rather than admin.
Where this common payment problems page sits in the wider New York 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 densely populated adult-use market fragmented by municipal opt-outs, with heavy cross-border demand from New York and Pennsylvania residents.
Bordering state
One of the largest medical-only patient bases in the country, served by vertically integrated grower-processors, with adult-use legislation a recurring but unresolved question.
Bordering state
A dense, high-income adult-use market with equity-linked licensing and a potency-based tax that makes accurate product-level reporting unusually important.
Bordering state
A mature, competitive adult-use market with host community agreements, high store density near borders and steady margin compression.
Tell us what happened and when. We will tell you whether it is a cap, a clause or a documentation issue, and what to do in the next 48 hours.