Merchant eligibility: 12 checks for regulated businesses

For regulated business models, a single industry label rarely decides the outcome. A reliable merchant-fit review connects company structure, actual products, destination markets, website and future payment operations. These checks make open questions visible before engineering time is committed.

This article structures payment and merchant-fit review. It is not an acceptance guarantee and does not replace individual legal advice.

1. Describe the complete business model

A review needs more than a registry purpose. Value chain, customer group, average basket, fulfilment, returns, support and the legal seller of record all matter.

Ownership, beneficial owners, directors and the settlement account must match the submitted entity. Contradictions between registry, domain, contracting party and bank account create avoidable follow-up.

2. Review products and claims together

Product category, ingredients, origin and promotion belong in the same scope. A lawful product can still create issues through unsupported health claims, incomplete labelling or an unsuitable destination market.

Material catalogue changes should not happen silently after launch. A defined re-review process protects both the merchant and payment operations.

3. Model status and operations in advance

Merchant fit does not end at KYB. Order status, server-side confirmation, refunds, webhooks, reconciliation and support escalation need to be clear before go-live.

A browser redirect must not release an order by itself. The source of truth is a confirmed server-side state with stable references across order, payment and payout.

Merchant-fit checklist

Review at least these points before the next step:

• Registry, UBOs, directors and settlement account are current and consistent.
• Products, audience, delivery markets and claims are fully documented.
• Licences, laboratory reports or other evidence map to specific products.
• Legal pages, privacy, returns, shipping and support match the business model.
• Checkout, payment status, refunds and reconciliation are operationally described.
• Product, market or ownership changes trigger a re-review.

The goal is a defensible decision

A good review does not produce a blanket yes or no. It produces a documented scope: what was assessed, what evidence remains open, which conditions apply and which changes require a new review.