How to Compare Cannabis Payment Processors Without Guesswork

The short answer

Comparing cannabis payment proposals on headline price is the fastest way to pick the wrong one. Compare them on the rail, the sponsoring institution, the funding and reserve terms, the total cost per transaction at your real basket size, and the exit terms. Those five factors determine whether an arrangement is cheap, durable or neither.

Put every proposal into the same table before you talk to anyone again. Providers describe the same mechanics with different vocabulary, and the table forces the comparison to be like for like.

The comparison grid

Fill one row per proposal, and leave a cell blank rather than guessing. Blank cells are the finding.

• Rail and method, named specifically, plus the sponsoring institution behind it.
• All-in cost per transaction modelled on your own average ticket and monthly volume.
• Funding schedule, including weekends, holidays and post-spike behaviour.
• Reserve percentage, hold period, cap and review criteria.
• Integration depth with your POS and who supports it.
• Term length, early termination cost, hardware ownership and data export on exit.
• What historically causes this arrangement to end, in the provider's own words.

Modelling cost honestly

Convert every pricing structure into cost per transaction and cost per hundred dollars of sales at two or three realistic basket sizes. A structure that looks competitive at a large ticket can be expensive at a small one, and dispensary baskets vary widely by daypart and promotion.

Include the non-obvious lines: monthly and gateway fees, hardware, PCI or compliance charges, batch fees, chargeback handling, and the working-capital cost of the reserve and funding delay. The last item is frequently larger than the difference in headline rate.

Build the model in a simple spreadsheet you control, not one the provider hands you. Enter your own twelve months of volume by week if you have it, and stress-test a slow month and a promotional spike separately, since reserve and funding terms often behave differently at the extremes.

Reference checks and red flags

Ask for two operator references in your state and licence type, and ask them one question: what happened the last time something went wrong. Then weigh the answers against the written terms rather than the sales narrative.

• Red flag: unwillingness to name the rail or the sponsoring institution.
• Red flag: acceptance described as guaranteed or risk-free.
• Red flag: pricing that cannot be reduced to cost per transaction.
• Red flag: reluctance to provide any reference at all, even under a confidentiality agreement.
• Green flag: a clear, unembarrassed answer about what would end the arrangement.
• Green flag: proactive disclosure of past incidents and how they were resolved.

Questions to put in writing before signing

Verbal assurances during a sales call do not survive a dispute later. Convert the important questions into a short written request and keep the reply, whether it comes as an email, an addendum or a term in the agreement itself.

A provider that answers plainly and in writing is telling you something about how they will behave when a real problem arises. Hesitation at this stage is data, not an accident.

• What specific events trigger a reserve increase or an account review.
• Who owns the hardware, and what happens to it at contract end.
• How quickly transaction history and settlement records can be exported on request.
• Whether pricing can change unilaterally, and with how much notice.

Common mistakes underwriters and operators both make

Operators frequently sign based on the lowest quoted rate without modelling the reserve and funding delay, then discover the effective cost of capital is far higher than the rate suggested. Underwriters, on their side, often flag applications where volume estimates on the application do not match bank statements, which slows or kills approval regardless of how good the pricing comparison looked.

The remedy for both sides is the same discipline: numbers that tie out, assumptions written down, and a habit of asking what could go wrong before it does.

Turning the comparison into a decision

Once the grid and the cost model are complete, resist the temptation to average the scores into a single number. Some factors, such as an unwillingness to name the sponsoring institution, should function as disqualifiers regardless of how attractive the pricing looks elsewhere on the sheet.

Present the finished comparison to whoever signs the contract in the same table format used throughout the process, with blank cells and red flags visible rather than smoothed over. A decision made from a messy but honest table is more durable than one made from a clean but incomplete summary.