The bank refused your acquiring application: why it happens and what to do next

A refused acquiring application rarely comes with an explanation. The letter usually contains a single line about internal policy, and there is no way to tell from it what exactly the bank did not like. Below are the reasons that come up most often, and what to do while the talks are still going.

Why applications get refused

The line of business is on a stop list. Every acquirer keeps a list of industries it will not take. The lists are unpublished and differ from bank to bank, so a refusal from one says nothing about the next. Typical entries: online courses and info products, consulting, services without a fixed catalogue, and anything adjacent to gambling or crypto.

No trading history. A young company with no turnover is a statistical blank for the bank. There is nothing to estimate the dispute rate from, and that rate is what decides how much the bank stands to lose. A refusal here is not about you — it is about the absence of data.

A high average ticket at low frequency. Ten payments a month at ₽200,000 look considerably worse to a risk model than a thousand at ₽2,000: a single dispute burns a whole month of revenue.

The website fails the review. The formal requirement people trip over most: the site must carry company details, a public offer, a product description with prices, refund terms and contacts. A missing block produces a refusal that reads exactly like a refusal over the industry.

Non-residency or a foreign jurisdiction. Russian acquiring is all but closed to a foreign legal entity, and no amount of paperwork gets around it.

What follows is the step-by-step part; if you need to accept payments today, the takemypay dashboard issues a test key right away.

What actually helps in talks with a bank

Three things, in order of effect:

1. Bring the site up to the formal requirements. This is the cheapest fix and it removes the most common reason.
2. Come back with turnover. Even three months of history through any other payment channel change the conversation: the risk model finally has data.
3. Apply to several banks in parallel. Stop lists differ, and one refusal tells you nothing about the next acquirer.

What does not help: re-registering the same business under a new legal entity, and describing the activity in vague terms. The bank sees the first through related parties and the second through payment purposes.

How to take payments while the bank talks are ongoing

This is where a payment gateway comes in — an intermediary that already holds the acquiring contract, so you integrate with it rather than with a bank directly. The difference is in the requirements: the gateway needs to review the project, not to open a full merchant outlet.

With takemypay it looks like this:

• sign-up through a link in an email, with no password and no document pack up front;
• the API key is issued immediately and works in test mode, so the whole integration can be built and verified before real money is on the table;
• payment methods are SBP, Mir cards, Visa/Mastercard and crypto, and the payer picks one on the checkout page;
• roubles are converted to dollars at the moment of payment, and payouts go out in USDT TRC20.

The method most projects switch on first is accepting payments over SBP: it has no disputes in the usual sense and the money arrives almost instantly — for a business without history that matters more than the percentage.

The price of this route is a fee above the banking one: 18% against the 2–3% of direct acquiring. That is what it costs to have the intermediary carry the risk. For a business that has just been refused, the choice is usually not between 18% and 3% but between 18% and nothing at all. How the amount on your balance follows from the amount paid, and when you can withdraw it, is covered in the breakdown of the fee and payouts.

What to do today

If you need payments running now, the order is: connect a gateway and start selling, fix the website and build up turnover in parallel, then go back to the bank three or four months later with numbers. Direct acquiring is granted far more readily after that — and you move onto it, keeping the gateway as a backup channel.

The technical side is one POST and one webhook, a couple of hours of work. Start from the quick start. Before taking real money, budget for verifying the webhook signature: without it, anyone can send you a payment notification.

Frequently asked questions

Why does the bank not explain the reason for the refusal?

The criteria of a risk model are a trade secret: published, they would turn into a guide for getting around them. So the letter refers to internal policy, and the reason has to be inferred from the usual grounds — industry, absence of turnover, average ticket, formal website requirements.

Does one bank’s refusal mean every bank will refuse?

No. Industry stop lists differ between acquirers and are never published, so it is worth applying to several banks in parallel. A refusal describes the risk policy of that particular bank, not your business.

Would re-registering under a new legal entity help?

No. The bank sees related parties, and the line of business does not change with the company details. The same goes for describing the activity vaguely: it is read off the payment purposes, and a mismatch with what was declared becomes a reason for refusal in itself.

What if the website is not ready for the bank’s requirements yet?

Bringing it up to the formal requirements is the cheapest step and the most common cause of refusal: you need company details, a public offer, a product description with prices, refund terms and contacts. Payments can run through a gateway while the site is being finished.

Can I go back to a bank after working through a gateway?

Yes, and that is the usual path. Three or four months of turnover give the risk model the data it was missing, and direct acquiring is granted far more readily afterwards. It is worth keeping the gateway as a backup channel — for the day the bank suspends service.