Cross border payments challenges: the five that stall remittance growth

Growth has stalled. Marketing says the product loses people at KYC. Product says marketing buys the wrong installs. Operations says nobody warned them about the campaign. Finance says the numbers do not reconcile. Every team blames a different cause, and every team is partly right.

The cross border payments challenges written about most are the industry-level ones: cost, speed, access and transparency. They matter. Target 10.c of the UN Sustainable Development Goals aims to cut average remittance costs to less than 3% of the amount sent by 2030, and to eliminate corridors costing more than 5%. That keeps pressure on every operator's pricing.

But the problems that stall an individual money transfer business are usually closer to home. Here are the five that recur, with what each looks like, why it happens, what to fix first and who should own it.

Cross border payments challenges at a glance

The five challenges, one by one

Each challenge below follows the same pattern: the symptom a leadership team can see, the cause underneath it, the first fix worth funding and the team that should own it.

1. Verification leakage

Symptom. Registrations climb month on month. First transfers stay flat. People download and never verify.

Cause. Document capture fails on older Android phones. Liveness checks time out on weak connections. Senders referred to manual review wait with no message and give up. Often nobody reports on the verification queue at all, so the loss is invisible.

First fix. Instrument every step: KYC started, document submitted, liveness passed, referred, approved, first transfer. Then read the drop by device, corridor and acquisition source. The method is set out in our KYC drop-off audit.

Owner. Product, with operations for the review queue. The verification rules themselves stay with compliance. Improving the screens never means weakening the checks.

Licensing and AML questions go to a qualified adviser. We handle advertising and marketing compliance.

2. Acquisition waste

Symptom. Cost per install is stable or falling. Cost per first send is unknown or rising. Three platforms claim the same conversion.

Cause. Campaigns optimise toward installs or registrations because those are the events the platforms receive. The algorithms then find people who install and never send. Platform-reported conversions are taken on trust instead of being checked against transfer records.

First fix. Send post-KYC events and first transfers back to the ad platforms. Reconcile platform conversions against your own records and report the gap. Measure cost per first send by corridor. Your cost per install is lying to you explains why the headline number misleads.

Owner. Growth, with engineering for server-side events.

We argue against more spend until the funnel holds. Month one looks slower that way.

3. One-and-done senders

Symptom. A large share of senders make one transfer and are never seen again. Reactivation is a monthly email blast.

Cause. Nothing gives the sender a reason to reopen the app. Rate improvements and fee changes are never communicated. Seasonal occasions such as Eid, Christmas and school-fee months pass without a message. Dormant senders are treated as one list.

First fix. Build triggers, not calendars: a message after the first transfer, a rate alert for the sender's corridor, a reminder near the sender's usual send date, a two-tap repeat transfer. Our guide to customer retention for remittance apps covers the second-transfer windows in detail.

Owner. Lifecycle or CRM marketing, with product for the repeat-send flow.

Send frequency is where the business is.

4. Corridor concentration

Symptom. One corridor carries most of the revenue. A pricing move by a competitor on that route, or a payout partner problem, hits the whole business.

Cause. Corridors were added by opportunity rather than evidence. Budget is split evenly across unequal corridors, or kept where it has always been. Nobody can say which corridor makes money after acquisition costs.

First fix. Score each live and candidate corridor on demand, competition, pricing visibility, payout reliability, channel opportunity, marketing economics and strategic fit. Grade them: priority, test, monitor or low priority. That is the work of corridor and market research, and it answers "we do not know which corridor to focus on" with evidence instead of opinion.

Owner. Leadership, because corridor mix is a strategy decision, not a campaign setting.

5. Platform ceilings

Symptom. Marketing wants corridor-specific rates, a referral offer or a faster repeat send. The answer is "the platform cannot do that". Reconciliation takes two people most of a week.

Cause. Rates live in a spreadsheet. Payout partners are chased by email. Agent balances sit in a monthly workbook. Every change is manual, so every change is slow and risky.

First fix. Start with reconciliation and rate management, not a full rebuild. Rates with an audit trail and reconciliation that surfaces only exceptions remove most of the manual load. A remittance management system is usually built module by module, and it usually starts there. No software on its own makes a business licensed or AML compliant.

Owner. Operations and engineering, with finance for the ledger.

The cross-cutting constraint: compliance-safe messaging

Every fix above runs into the same wall if the copy is wrong. Ads rejected for financial services policy. Claims such as "zero fees" or "instant" that the product cannot substantiate on every corridor. Compliance teams who see campaigns for the first time the day before launch.

The fix is procedural. Agree the claims library with compliance before anyone writes. A workable library has 4 parts:

• Fee wording, including how the FX margin is described when the transfer fee is zero.
• Speed wording by corridor and payout method, since cash pickup and bank deposit rarely arrive at the same time.
• Regulatory status lines, in the exact form compliance has approved.
• Banned phrases, such as "guaranteed", "risk-free" or "instant" where delivery is not instant on every corridor.

Then write inside it. Compliance blocks less when it is asked first. The same library feeds ads, landing pages, app store listings and support macros, so a claim is approved once rather than argued four times.

Where these challenges show up in your numbers

Growth stalls partly because each team reads a different number. One shared metric set settles most arguments.

This sequence, measurement first and verification second, is how our conversion rate optimisation services are ordered.

Where to start

Pick the challenge with the clearest symptom in your own numbers. For most app-led operators, that is verification leakage, because it wastes every pound spent above it. Agree the metric definitions first, then name an owner for each of the five.

Start with the glossary, so every team reads the same numbers. When you want the leaks sized by monthly cost, Book a Growth Audit. Two weeks, a fixed fee, and a roadmap you keep whether or not the work continues.