This FAQ covers how a cannabis ecommerce checkout should surface payment rules, tender availability by fulfillment type, minimums, and abandonment metrics before the final payment step.

Why should payment options appear before checkout?

Cannabis payment availability changes with the store, fulfillment type, order total, delivery zone, and processor status. When those constraints stay hidden until the final step, the customer has already built a cart, and your analytics record the abandonment as preventable.

Where should payment information be shown?

Put it on the menu, on the product page where it matters, in the cart, and on the checkout start screen. By the time the customer reaches the final payment step, that step should be confirming the tender they already chose rather than teaching them the rules.

How should payment availability be modeled?

Use a tender matrix keyed by store and fulfillment type. Each row carries a payment method and its availability, the order minimum and maximum, whether prepayment is required, a customer-facing label, and a fallback instruction.

store_id
fulfillment_type
payment_method
is_available
min_order_value
max_order_value
requires_prepayment
display_label
fallback_instruction

What should the customer-facing copy include?

Say which payment methods you accept, and call out the common ones you do not (credit cards are the usual source of confusion). List any restrictions tied to fulfillment type, the order minimum, and when payment is due, whether that is online, at pickup, or at delivery.

Pickup: Cash, debit at pickup, and pay-by-bank where available. Credit cards not accepted.
Delivery: Prepayment may be required. Available tender depends on delivery address and order total.

What checkout metrics should be tracked?

The ones that catch real problems are payment-step arrival and abandonment, failed payment rate, and the rate at which carts get blocked by the order minimum. Cart start, checkout start, and tender selection give you the funnel context. Break abandonment out by fulfillment type, and segment everything by store and device.

payment_step_abandonment = payment_step_exits / payment_step_arrivals
failed_payment_rate = failed_payment_attempts / payment_attempts
minimum_failure_rate = carts_blocked_by_minimum / checkout_starts

Which policy controls should exist?

  • Fulfillment-specific tender rules. Pickup, delivery, curbside, and express lanes can have different payment availability.
  • Real-time processor status. When a tender rail goes down, the menu and checkout drop it or mark it unavailable.
  • Order minimum visibility. Show the minimum before the customer starts building a cart, and update it as the cart changes.
  • Prepayment rule. State whether prepayment is required before you collect personal information you would otherwise not need.
  • Fallback instruction. If the selected tender fails, the checkout should explain the next available payment option.

How should payment filters work?

If your platform supports payment-method filtering, drive it off the tender matrix instead of static marketing copy. A filter set to a given payment method should return only the stores, fulfillment types, and carts that can actually use it.

What is the implementation rule?

Do not render a payment option unless the current store, fulfillment type, cart total, delivery zone, and processor status all satisfy the tender matrix. When a common tender is not accepted, say so before checkout starts.