Switching Cannabis Payment Providers: A Migration Plan That Protects Sales

The short answer

The risk in switching providers is not the new arrangement, it is the gap between the two. A migration that protects revenue runs both setups in parallel for a defined window, moves volume deliberately, and does not cancel the outgoing arrangement until settlements, reserves and hardware are fully resolved.

Plan for four to eight weeks end to end. Boarding, hardware logistics and integration testing rarely compress well, and rushing them is how a store ends up cash-only on a weekend.

The migration sequence

Work the phases in order, and do not start the next one until the previous one has produced evidence rather than assurances.

• Prepare: assemble licences, ownership documents, statements and traceability reports in one pack.
• Board: complete underwriting with the incoming provider and get the funding and reserve terms in writing.
• Integrate: connect to the POS in a test environment and run split tenders, refunds, voids and offline behaviour.
• Pilot: move one register or one location for a full week, including a busy day and a close.
• Cut over: shift remaining volume, keeping the outgoing method live as a fallback.
• Close out: reconcile final settlements, recover the reserve on the contracted schedule, return hardware and export all data.

The clauses that cause trouble at exit

Read the outgoing agreement before you announce anything. Auto-renewal windows, early termination fees, hardware ownership, and post-termination reserve holds are the four terms that most often turn a clean switch into a dispute.

Send written notice exactly as the contract specifies, keep the acknowledgement, and diarise the reserve release date. Reserves are commonly held for a period after termination, and the release will not chase you.

Where a contract allows for cure periods or dispute resolution before termination takes effect, read those clauses too. Missing a procedural step can extend the relationship, and the associated fees, well beyond the date you intended to leave.

If the contract is silent or ambiguous on any of these four points, ask the outgoing provider in writing before giving notice, not after. A written clarification obtained before termination is far easier to enforce than a dispute raised once the relationship has already ended.

Protecting staff and customers through the change

Most lost sales during a migration come from staff uncertainty at the counter, not from technology. Brief the team on the new flow, print a one-page fallback procedure, and keep signage current so customers know which tenders work today.

• Reconcile daily during the pilot and the first two weeks after cut-over.
• Export full transaction history from the outgoing provider before access ends.
• Keep the old method available until the first clean settlement cycle on the new one.

Staff training checklist for cut-over week

A migration that is technically sound can still lose sales if the person at the counter cannot explain to a customer why the payment screen looks different. Build a short training session rather than an email, and run it close enough to cut-over that staff remember it.

Include a role-play of the most common failure mode: a card declining for an unrelated reason on the very first day of the new system, which staff may otherwise blame on the switch itself.

• Walk through the new tender flow on the actual hardware, not a slide deck.
• Give staff a one-line explanation to offer customers if a transaction looks unfamiliar.
• Post the fallback tender option clearly at every register during the transition.
• Debrief staff at the end of day one, two and seven to catch friction early.

Recordkeeping that survives an audit or a dispute

Migrations generate a lot of paperwork in a short window, and it is precisely the documentation most likely to matter later if a reserve dispute or a compliance question arises. Keep everything in one folder, not scattered across email threads.

At minimum, retain the boarding approval, the written funding and reserve terms, termination notice and acknowledgement, final settlement statement, and hardware return confirmation. Five years of retention is a reasonable default absent other guidance, and this is general information, not legal advice.

Communicating the change to customers

Customers rarely care which provider sits behind a payment method, but they notice when a familiar tender disappears without warning. A short notice at the register and on receipts for the two weeks before cut-over reduces confusion and the number of transactions that fail simply because a customer tried an old habit.

Keep the messaging factual: which tenders are changing, when, and what to expect if something does not work as usual. Overpromising a seamless transition sets up a worse reaction if any friction does occur during the pilot week.