7 Payment Problems That Keep Showing Up
Different companies, different markets, same seven issues. Here's each one and how to plan for it.
After 100 posts and the client conversations behind them, the same problems keep coming back. The companies are different. So are the markets, the volumes and the providers. The issues aren't.
Here are the seven that show up most, why they keep happening, and how to plan for each one. Each links to a fuller breakdown if you want to go deeper.
1. Picking a provider on price
The rate is the easiest number to put side by side, so it tends to decide the selection. What it doesn't show is how the provider holds funds, when it applies reserves, which markets it can process in locally, and whether anyone answers when something breaks. Those show up after the contract is signed.
Companies that have already scaled look past the rate. They judge providers on structure and capability: whether the setup fits how they operate now, and whether it will help or get in the way as they grow.
Plan for it: Score fit, capabilities and terms before you compare rates.
Go deeper: The Rate Isn't The Only Score
2. Assuming your processor works the same everywhere
A provider's name travels across borders. Its entity requirements, product set and supported payment methods often don't. Stripe's US account, for example, requires a US business entity, which surprises foreign companies that already use Stripe at home.
This usually comes out mid-launch, when onboarding stalls or a payment method local customers expect isn't available in that market.
Plan for it: Confirm entity, onboarding and method support for each market first.
Go deeper: Can You Use Stripe US Without a US Entity?
3. Treating cross-border fees as fixed
When you process cards outside your customer's country, cross-border card fees apply to every transaction, and FX costs often come with them. Many companies book this as the cost of selling internationally and stop looking at it.
There's more than one way out. A local entity lets you process domestically. Some providers can process locally in certain markets without one. A merchant of record sells through its own local entity on your behalf, in exchange for its fee. Each route removes cross-border fees differently, and each brings its own costs, so the answer comes from pricing them side by side.
Plan for it: Price the routes: local entity, local acquiring, or MoR. Each has its own costs.
4. Letting the US bank account stall market entry
Foreign-owned companies often get the US entity formed quickly, then stall at the bank. Owner verification, branch-visit expectations, online bank eligibility limits and EIN delays for non-US founders all slow it down.
The account is where revenue lands, so the whole launch ends up waiting on the slowest gate. Treating banking as the step after formation is what turns it into the bottleneck.
Plan for it: Start banking and EIN work alongside entity formation, not after it.
5. Paying beneficiaries your way, not theirs
Payout methods are often chosen for the payer's convenience. Beneficiaries in each region bring their own constraints and preferences: local rails, wallets, and currencies they trust.
When the method doesn't fit, it shows up as support tickets, workarounds and beneficiaries leaving for a platform that pays them the way they want. Their needs should drive the provider choice, not the other way around.
Plan for it: Map beneficiary needs by region before choosing a payout provider.
6. Handling chargebacks after they land
Most teams start working on chargebacks once they arrive. By then, the only choices left are fighting or accepting.
The leverage sits earlier. A clear billing descriptor, customer support that resolves issues before a customer calls their bank, and evidence gathered before it's needed all cut disputes down before they reach your team.
Plan for it: Build the defense before the dispute, not during it.
Go deeper: Build Your Defense Before It's Needed
7. Leaving the decline rate unowned
Approval rates sit between finance, payments, product and engineering, so nobody owns them. Declines don't appear as a line item, which makes the lost revenue easy to miss.
Some of it is recoverable: fraud rules set too tight, retries timed badly, and cross-border declines from issuers. None of it gets fixed until one person is accountable for the number.
Plan for it: Give one person the decline rate and a monthly one-page report.
Go deeper: Who Owns Your Decline Rate?
The Takeaway
None of these are exotic. They persist because payments decisions tend to get made once, at launch or at contract signing, and then rarely get revisited while the business, the markets and the providers keep changing.
The expensive problems usually aren't new ones. They're the ones nobody went back to check.
Comments