The Compliance Failures That Close Merchant Accounts
What gets a merchant terminated by a crypto payment provider, why the notice is short, and how to avoid being in that position.
Priya Raman · 2 min read
A licensed payment provider can terminate a merchant with little notice, and the reasons are rarely explained in detail. Here is what actually triggers it. Comparing against crypto acquiring for businesses is the quickest way to see what is missing from the operation described here.
Selling something outside the agreed category
The onboarding described one business. The transactions describe another.
This is the most common cause. A merchant adds a product line, or a customer segment, that falls into a category the provider’s licence or banking arrangement does not permit.
The fix is to tell the provider before adding it, not after. Providers can usually accommodate an expansion discussed in advance and cannot accommodate one discovered in transaction monitoring.
Transaction patterns inconsistent with the stated business
Average order values far above what was described. Volume concentrated in a small number of very large payments when a consumer business was described. Sudden growth without explanation.
None of these are wrong in themselves. All of them prompt a review, and a review that receives no explanation escalates.
Tell your provider when something changes. A large contract, a seasonal spike, a new market. One email prevents the review entirely.
Payments from screened addresses, repeatedly
A single flagged payment is routine. A pattern suggests the customer base is not what was described.
This is largely outside your control and it is worth knowing that it accumulates. If your category attracts it, discuss it with the provider at onboarding rather than letting it appear as a trend. Merchants meet a variant of this, and a payment processor for high-risk e-commerce handles it on the receiving side.
Refunds to destinations other than the origin
This reads as potential laundering regardless of the underlying reason, because it is the mechanism used for it.
A firm policy of refunding only to origin protects you from the fraud and from the appearance of facilitating it.
Acting as a payment service for others
Processing payments that are not for your own goods and services. This is a regulated activity requiring its own licence, and doing it through a merchant account breaches the agreement.
It happens innocently: a merchant collects payments on behalf of a partner, or invoices for a group company. It is still a problem and it is worth checking whether your arrangement does this.
What termination looks like
Notice of anywhere from immediate to thirty days. Settlement of the outstanding balance, sometimes after a hold period. And an entry in industry databases that makes the next provider harder to obtain.
That last part is the expensive consequence, and it is why the first termination matters more than the lost provider.
Staying on the right side
Describe the business accurately at onboarding, including the awkward parts. Providers decline some businesses and that is better than being terminated later.
Tell them about changes before they happen.
Keep a refund policy that never sends funds to a new destination.
And read the acceptable use terms once, properly, because the categories they exclude are specific and most merchants have never looked. If you want to see these protections operating rather than described, a provider you can actually reach is bound by them.
Move any remaining funds to a wallet with a newly generated seed phrase before anything else. Then revoke token approvals, and report the incident to your local authorities and the exchange involved. Do not pay anyone who promises to "recover" your coins. That is a second scam, aimed at victims of the first.