Exchange Rate Rules That Win and Keep Customers: First-Transfer Offers, VIP Rates and App-Only Pricing

A standard rate treats every customer the same. That is the right default, but it is a blunt tool for growth. The customer deciding whether to try you for the first time, the regular who sends every fortnight, and the sender you would rather see in your app than on your website are worth different things to you. Exchange rate rules let you price for each of them deliberately, and keep everyone else on the standard rate.

This guide is for founders, growth leads and pricing teams at money transfer businesses. It covers how rate rules work, five practical uses, a playbook table, and the habits that stop offers quietly eating margin.

RemitSo is one way to run this. Its Exchange Rate Rules give special rates by customer group, platform, payout country or partner, as fixed rates or adjustments that follow the standard rate. Your team still decides who deserves a better rate, for how long, and whether it paid off.

Start with the standard rate: the sell rate per currency pair and amount band that every customer gets unless something says otherwise. For how standard rates are entered and checked, see managing exchange rates without mistakes.

A rule says who gets something different. The useful dimensions are:

• Customer group: new customers, VIPs, or any group you run.
• Platform: customers sending from the web, iOS or Android.
• Payout country: transfers paid out in one country.
• Payout partner: transfers paid out by one partner, for example where your cost is lower.
• Any mix: new customers on Android sending to Kenya, for instance.

Everyone a rule does not cover keeps the standard rate. Where a rule gives nothing for a particular pair, its customers keep the standard rate on that pair too. That default matters: a rule should be an exception you chose, not a second price list to maintain.

Every rule gives one of two things per pair.

• A fixed rate stays exactly where you set it, whatever the market does. It can carry its own amount bands.
• An adjustment is added to the standard rate every time the standard rate moves, so it never goes stale.

The difference shows up the moment the market moves. The figures below are illustrative, using an AUD to NGN pair with a buy rate of 931 and a standard sell rate of 911, a spread of 20 and a margin of 2.148% (spread divided by buy rate).

The adjustment keeps the offer worth the same 5 naira to the customer and keeps your margin roughly where you planned it. The fixed rate becomes more generous as the market falls, until you are paying customers to send. Fixed rates still have a place, for a short campaign with a published headline rate, or for a VIP who has been promised a specific figure, but they need a stop date and someone watching them.

The first transfer is the hardest to win. A customer who has never used you is comparing rates, trusting a new brand with family money, and going through an ID check for the first time. A slightly better rate on that first transfer gives them a concrete reason to finish.

The cleanest way to run this is a rule for a New Customer group, with two mechanics working for you:

• Customers move from New to Default after their first completed transfer. The offer ends itself. Nobody has to remember to take it away, and nobody gets it twice.
• Visitors who are not signed in are quoted as the New group. The rate a prospect sees on your website calculator or in the app before signing up is the offer rate, so the promise in your marketing matches the quote.

Make it an adjustment, such as "the standard rate plus 5" on your priority pairs, so it tracks the market. Keep the uplift small enough that a customer who stays on your standard rate afterwards does not feel the drop as a betrayal. And make sure the first transfer itself is easy to finish: an offer will not rescue a confusing ID check. See rescuing stalled onboarding.

Your best senders are the customers competitors most want. A rate rule for a VIP group rewards them without discounting everyone else.

• Write down the criteria: regular sending over several months, larger typical amounts, low support and compliance friction. A VIP list nobody can explain becomes favouritism.
• Prefer an adjustment: "standard plus 3" holds its value as markets move. Use a fixed rate only where you have agreed a specific figure, and review it often.
• Use amount bands where size is the point: if VIP status is about larger transfers, bands keep the best rate for the largest amounts.
• Review membership: customers who stopped sending six months ago should not keep the rate by default.

Customers on your app are usually cheaper to serve and easier to keep: push notifications, faster sign-in and a send-again button bring them back. A platform rule giving iOS and Android customers a slightly better rate than the web is a direct, measurable nudge.

Keep the web on the standard rate, put a small adjustment on iOS and Android, and say so plainly on the website: "better rates in our app". Measure the share of transfers sent from the app before and after, not just app downloads.

A new corridor has no reputation. A rule for transfers paid out in that country, with a start date and a planned stop, gives early customers a reason to try it and gives your marketing a clear message.

Set the rule to start on launch day so it is ready before the corridor opens, and stop it when the launch period ends. If one payout partner in the corridor costs you less, a rule by partner can pass part of that saving to customers on that delivery method only.

As rules multiply, two controls keep them understandable.

Exceptions

An exception takes specific customers or routes back out of a rule; they are quoted as though the rule did not exist. Use them for a corridor where the margin is already thin, a customer under compliance review, or a payout method that is costly to serve.

The most specific rule wins

Where two rules cover the same route, the more specific one applies. A rule for new customers on Android sending to Ghana overrides a general new-customer rule for that route. Design rules from general to specific so this works for you, and check the list of routes each rule covers before switching it on. A route here is a way to pay, a way to be paid and a customer group together. If a route you expected is missing, the rule is not doing what you think.

• Default to adjustments: they follow the standard rate, so an offer cannot drift into a loss on its own.
• Exclude thin corridors: use exceptions where the standard margin cannot absorb an uplift.
• Give every promotion a stop: a rule with no end becomes a permanent price cut nobody approved.
• Review monthly: list every active rule, its routes, its type and the result against the number you wrote down. Stop the ones that did not work.
• Remember fees: a better rate and a fee waiver on the same transfer can double the discount. Look at total income per transfer, not the rate alone. For the broader approach, see FX spread strategy.

Rules apply automatically to everyone they cover. A promo code applies only when a customer enters it at checkout. Use a rule when the audience is defined by who they are or how they send. Use a code when you want to track a specific campaign, partner channel or influencer, or limit uses per customer. The two answer different questions; for the choice between money off and a better rate, see money off versus a better FX rate.

The figures are illustrative. An operator sending from Australia wants more first transfers, more app use and a strong launch for a new corridor.

1. Week 1: a New Customer rule, "standard plus 5" on AUD to NGN and two other pairs. The website calculator now shows the offer to visitors, and customers move to Default after their first completed transfer.
2. Week 2: a platform rule, "standard plus 2" for iOS and Android. The web stays standard. The rule's route list confirms both app platforms are covered.
3. Week 4: a payout-country rule for the new corridor, starting on launch day with a stop eight weeks later. One delivery method with thin margin is added as an exception.
4. Week 6: reading the route lists, the team sees new customers on the app touched by two rules. Rather than leave the outcome to chance, they add a combined rule for new customers on iOS and Android, so the most specific rule states exactly what those customers get.
5. Week 12: the monthly review shows the first-transfer offer worked, the app share rose, and the corridor offer brought customers who mostly stopped when it ended. The corridor rule is not renewed.

RemitSo's Exchange Rate Rules sit alongside standard rates on one Exchange Rates page in the admin panel. See the admin features.

• Rules by group, platform, payout country or partner, or any mix, so each offer reaches exactly the customers you intend; everyone else keeps the standard rate.
• Fixed or adjustment per pair: a fixed rate (with optional amount bands) stays where you set it; an adjustment is added to the standard rate every time it moves, so offers never go stale.
• A first-transfer offer that ends itself: new customers move from the New group to Default after their first completed transfer, and visitors not signed in are quoted as the New group.
• Start dates and stopping: a rule can start on a date and be stopped, so launches and campaigns run on time.
• Exceptions: take customers or routes back out of a rule; they are quoted as though it did not exist.
• Routes covered, most specific wins: each rule lists the routes it covers now, and where a more specific rule also covers a route, that rule applies.
• Nothing changes by accident: creating a rule changes nobody's rate until it is given one.
• Promo codes, an optional add-on: a code at checkout for money off or a better rate, with limits, dates and uses per customer.

Your team still decides who belongs in each group, sets the uplift, writes down what success looks like and reviews the results. To see rules in the console, book a demo.