Why Payments Customers Stay (And Why They Leave)
FX & Float Memo #2
Payment companies treat retention as a single, big problem. But it’s not. Retention in payments comes from at least five distinct forces coming together to hold the customer. Some of these are controllable, some are not. Most of the time, companies do not separate these out and measure their impact.
The common assumption made is that customers stay because they like the product and leave because they find a cheaper alternative. This logic leads payment companies to respond to customers about to churn with discounts, and to loyal customers with neglect. These responses are wrong because the underlying mental model of why customers stay or leave is flawed.
Payment retention does not work like SaaS retention. In SaaS, the product is the experience. If the experience is good, the customer renews. In payments, the product is invisible when it works. The better the product, the more invisible it is. The customer does not think about the payments provider until an issue arises. This means the forces that hold a customer in place are largely structural, rather than experiential. And the forces that push a customer out are largely triggered by specific events and not by gradual dissatisfaction with the product.
Understanding how the retention forces and churn triggers work is necessary to build a payments company that retains customers by design and does not rely on accidental (and temporary) retention.
Why customers stay
Five forces make a payments customer keep using the product. They are not equally effective or equally easy to build. Most payments companies end up relying too much on the weakest ones, which are also the easiest to build. Listing these below in the order of effectiveness -
Force 1: Integrations
This is the strongest retention force in payments, and it has nothing to do with how good the product is.
When a business integrates a payments provider through an API, it embeds that provider into its core financial infrastructure. The accounting system mappings, reporting dashboards, and reconciliation logic are all built around the data formats of the payments provider. Over time, this becomes too costly to switch, as it would mean rebuilding it all.
The switching cost is not the technical effort of plugging in a new API. That can be done in a matter of days. The switching cost is the operational overhauling needed - remapping accounting codes, rewriting reconciliation scripts, retraining the finance team, and managing the transition period with two parallel systems. This is why mid-market and enterprise payments companies with deep API integrations often have retention rates well above 95%, even when their pricing is not the most competitive.
Force 2: Settlement dependency
Businesses build their cash flow management around their payments provider’s settlement cycle. For example, a company knows that its USD collections settle in T+1 and its INR payouts settle in T+2, so it plans its working capital, supplier payments, and treasury operations around those timelines.
Switching to a new provider with different settlement timelines means adjusting the entire cash flow model. Even when you have a provider who can settle a day faster, you need to adjust all downstream processes affected by the change. And if the new provider settles a day slower, it can throw the cash cycle off and create a big cash crunch.
Force 3: Corridor coverage
Most payments companies do not cover every corridor a business needs. But once a customer has found a provider that meets their needs for a specific combination of corridors, finding a replacement means being sure the new provider can do the same.
This is not a trivial exercise. The more corridors a customer uses, the harder it is to find a single replacement. A logistics company sending payments to drivers in 12 countries needs a provider that supports all 12 destination currencies with reliable last-mile delivery in each. The new provider might cover 10 of the 12 and claim the remaining two are “coming soon.” The customer’s choice is to run two providers in parallel or wait. Most of them choose to wait.
Force 4: Compliance and onboarding
Every payments provider requires KYC and KYB documentation. For a business customer, this means collecting and submitting corporate documents, UBO records, proof of business activity, and sometimes even audited financial statements. This is a strong deterrent, especially for customers in complex industries or high-risk categories.
Once a customer is approved and is transacting, they don’t want to keep doing this verification with new providers. The deterrents are the time this verification process consumes and the risk that the new provider’s compliance team might reject them or impose restrictions that the current provider does not.
Force 5: Relationship and account management
This is the retention force that payments companies invest the most in, and the one that matters the least.
Account managers build relationships with customers, negotiate custom pricing, handle escalations and conduct periodic business reviews. While these may sound like retention activities, if a customer has decided to leave for structural reasons (such as FX markup or settlement delay in a corridor), these activities cannot stop them. A good account manager will delay the churn, but will not be able to prevent it.
Another limitation is that these activities are personal and not structural. When the account manager leaves the company, the retention efficacy leaves with them.
Why customers leave
The five forces above are what keep a customer in place. But they are not permanent. There are specific trigger events that can shake this stability and push these customers from stable to lost. This almost always happens suddenly. A customer who looked stable last quarter is switching providers this quarter, and the payments company never saw it coming.
Trigger 1: Pricing discovery or broken trust
This is the most common trigger for churn in payments. As covered in Memo #1, payment pricing comprises five components stacked together: the stated fee, the FX markup, the float, the corridor cost, and interchange. Most customers only see one of them. When the customer calculates the total cost of their payments, the stated fees plus the FX markup plus the cost of float, they feel misled.
This is why churn conversations that start with “we found a better rate” are misleading. The rate is not the cause of churn. The cause is that they discovered that the rate they were promised was not the true rate. This is a trust problem, and not a price problem.
Trigger 2: The failed transaction
In payments, reliability is a core product feature. When a payment fails, the damage it does is beyond that failed transaction. It can cascade into a supplier not being paid on time, a payroll cycle being delayed, a contract penalty being charged for missed payment, or a business relationship becoming strained.
A one-off failed transaction in a low-stakes context is forgiven. But a failed transaction that causes a real-world consequence for the customer’s business, or multiple failures over time, will trigger the switching process. These failures force customers to evaluate the risk of failure, which they had not factored into their decision on the payments provider.
This trigger is dangerous because it hits suddenly, and by then, the customer has already made up half their mind to leave. They may have even started with another provider before the payments company finds out.
Trigger 3: The compliance friction
Compliance holds are business as usual in payments. But how a company handles them determines whether the customer stays or leaves. A company that communicates proactively, resolves issues quickly, and explains clearly can maintain the relationship and keep the customer. A company that goes silent, sends templatised emails, and takes two weeks to release funds will lose that customer.
The compliance friction itself is not the trigger here. It’s how the company handles the compliance friction. Customers accept that compliance exists. But they do not want to be treated as criminals or suspects by their own payments provider.
Trigger 4: The coverage gap
If a customer’s business grows into a new corridor that the provider does not support, they need a second provider. Once they have a second provider, it’s natural that they will compare and evaluate both providers. Now, the retention forces at play, which were working in favour of the first provider, start to weaken.
The first provider also doesn’t realise this is happening until the volume starts shifting. The customer did not leave because they were unhappy with something. They left when their business outgrew their provider’s coverage, and the second provider turned out to be better than the first.
What this means
The retention forces and the churn triggers are fundamentally different. The retention forces are structural and slow. The churn triggers are events and operate fast. This is why payments companies are consistently surprised by churn. A customer appears stable for years because retention forces hold them, only for a single trigger event to overwhelm them. The customer is then gone in weeks.
This has three consequences for how payments companies should think about retention.
First, the strongest retention is built into the product, not around it. Integration depth, settlement dependency, and corridor coverage are product decisions. They are not hooks that the Customer Success team can create. The companies with the highest retention are the ones that have designed stickiness into their product.
Second, monitoring the trigger events matters more than measuring NPS or CSAT. A customer who reports high satisfaction can still leave next month if they discover their true cost or suffer a failed payment at the wrong time. The payments companies that successfully reduce churn are the ones that carefully monitor the triggers: compliance hold frequency, unusual reconciliation activity, and corridor coverage gaps relative to the customer’s growth.
Third, the weakest link in most retention strategies is the overreliance on account management to do what the product should be doing. If a customer needs an account manager to get a rate adjustment, to understand their fee, or to resolve a compliance review, the product has failed to absorb the complexity. The account manager is at best a temporary patch, and patches don’t work forever.
Every payments company has customers who look stable right now. But they are one event away from churn. The companies measuring the wrong things, like NPS and CSAT instead of trigger events, or investing in account managers instead of product stickiness, will continue to be surprised by the customers who were stable last quarter, and ‘suddenly’ left.