Approval rates are never one number. Break them down by issuing country and the average splits into two populations: markets where the card goes through on the first attempt, and markets where a third or more of first attempts come back declined. Those two groups are not caused by your integration. They are caused by rules sitting in four different places, and only one of them is yours to change.
The issuer decides, and it decides on geography
A card authorisation is approved or refused by the issuing bank, not by your acquirer and not by your payment provider. The issuer sees the amount, the currency, the merchant category code, the merchant country and a cross border flag. For a card issued in a market where the regulator has restricted retail leveraged trading, that combination is enough for a policy decline. Some issuers block the category outright. Others allow it but treat cross border plus a high risk category as a fraud signal and decline on score. The response codes look similar and rarely tell you which of the two happened, which is why reading decline codes at the issuer level is worth doing before you change anything else.
A related and separate problem: the country on the card does not match the country on the customer file. That mismatch raises the risk score at the issuer and can also breach your own acquirer's onboarding terms if the mismatch is systematic. It is worth understanding how BIN country mismatches are read before you assume a fraud filter is broken.
Currency control markets are a different problem entirely
In several large markets, the block is not a risk score. It is law. Countries operating capital controls restrict residents from sending funds abroad for margin trading, sometimes with an annual allowance for other purposes and an explicit exclusion for speculative accounts. Where that is the position, a declined card is the system working as designed, and there is no provider, no gateway, no retry strategy and no alternative rail that makes it lawful. A firm that routes around a national capital control is not solving a payments problem, it is creating a legal one, for itself and for the client.
The same logic applies to markets where retail CFD trading is prohibited or where only locally licensed firms may solicit residents. If your licence does not permit you to serve that country, the payment failure is a symptom, and fixing the payment is the wrong response. Firms in that position need their own legal advice on market access, not a new processor.
This is descriptive, not advice. Capital controls, marketing rules and licensing perimeters differ by country and change. Take local legal advice before accepting clients or payments from any market you are unsure about.
Where your firm is registered changes the answer
The merchant side of the transaction carries its own geography. Card schemes classify certain merchant categories as high risk and apply extra monitoring, and acquirers layer their own country lists on top. A merchant registered in a jurisdiction on the FATF list of countries under increased monitoring gets enhanced due diligence applied to it by counterparties as a matter of policy, which shows up as slower onboarding, tighter limits and more refusals at the correspondent layer rather than at the card layer. The mechanism behind that is set out in our piece on the effect of a grey listing, and the effect compounds with correspondent banking de-risking, where the bank that clears your settlement currency withdraws from a whole country rather than judging you individually.
The map, in categories
| Refusal type | Where it sits | Can the firm change it |
|---|---|---|
| Category policy decline | Issuing bank rules | No. Route to a non card rail if lawful |
| Cross border fraud score | Issuer risk model | Partly. Local acquiring, correct descriptor, 3DS data |
| Capital control | National law | No. Do not attempt to |
| Licensing perimeter | Your own permissions | Only by licensing, or by not serving the market |
| Correspondent de-risking | Settlement banks | Partly. Jurisdiction, substance, banking mix |
| Scheme high risk monitoring | Card schemes and acquirer | Yes. Dispute ratios and coding discipline |
What genuinely lifts approvals
Two things move the number in markets you are lawfully allowed to serve. The first is local acquiring: a card processed domestically, in the local currency, through an acquirer licensed in that country, is not a cross border transaction from the issuer's point of view, and the fraud score drops accordingly. The second is leaving cards behind where cards are not the local habit. Bank transfer rails, instant domestic payment systems and wallets carry the majority of online payments in several regions, and adding them tends to move total conversion more than any retry logic. Our overview of local payment methods covers which rail dominates which region.
Retries are the smallest lever and the most abused one. A soft decline can be retried on a schedule. A hard decline, a category block or a stolen card response must not be, because the schemes police excessive reattempts and the penalty lands on your account, not the client's.
Read the split before you buy anything
Before signing a second processor because approvals look bad, produce the breakdown by issuing country, by rail and by decline reason for a full month. Most firms discover the average was dragged down by three or four countries, two of which they should not be accepting at all under their licence. That report should come out of your own systems rather than a provider dashboard, which is one of the reasons the payments view inside the Broker CRM is built around reason codes and country, not just totals. The decision to add a rail is then an evidence based one, and it makes the difference between a genuine gap and a legal wall obvious.
"When approval rates split by country and nothing else changed, stop debugging your checkout. You are looking at somebody else's rulebook."
— Roman Onta, Executive Director, SINGUARD
Key Takeaways
- The issuing bank refuses most cross border trading deposits, on category and geography, not on anything your checkout did.
- In capital control markets and outside your licensing perimeter, a decline is the law working, and routing around it creates legal exposure.
- Merchant side geography matters too: FATF listings and correspondent de-risking push refusals up before a card is ever presented.
- Local acquiring and local rails lift approvals in markets you may lawfully serve, far more than retry logic does.
Frequently Asked Questions
Why do deposits fail from one country but work from another?
Because the issuing bank applies country level policy to the merchant category and to cross border transactions. The same card scheme and the same checkout can be approved in one market and policy declined in another. Some markets also apply capital controls that prohibit the transfer outright.
Can a different payment provider fix country declines?
Sometimes. A provider with local acquiring in that country converts a cross border transaction into a domestic one and usually improves approvals. It cannot fix a national capital control or a licensing restriction, and no provider should be asked to.
Does a FATF grey listing stop payments?
Not directly. It obliges counterparties to apply enhanced due diligence to firms connected to that jurisdiction, which shows up as slower onboarding, lower limits and more refusals at the banking and correspondent layer rather than at the point of sale.
About the Author
Roman Onta is an Executive Director at SINGUARD. He builds the Prop Firm CRM, the Broker CRM, Scalegram and CopySignals side by side with his brother Alex Onta, and he helped on the design of eTrader, the division Alex built and leads. His ground is worldwide payment processing, AML compliance and the corporate structures brokers are built on, work the two of them carry together, shaped by executive roles in the UAE and international corporates. He lives and works in Dubai for most of the year. Meet the executive duo leading Singuard's five divisions.