Pricing mistakes in remittance are rarely big decisions gone wrong. They are small edits gone wrong: a slipped decimal point on a rate, a fee slab saved over the wrong range, a promotion that was meant to end on Sunday and ran until Wednesday. Customers see the result before anyone in the office does. This guide is for pricing, treasury and compliance leads who change fees, rates and limits every week and want each change to land exactly as intended.
The principle: every change shows its effect before it is saved, and every change is kept with who made it and why.
RemitSo, a white label remittance platform, applies this to fees, exchange rates and AML limits across releases 2026.09.2, 2026.09.3 and 2026.10.6. Your team still sets the prices and the policies. The platform makes sure what you meant is what customers get.
See what customers will pay before you save
| Area | The review shows | Safety catch |
|---|---|---|
| Fees | What customers would pay at each step of a rule's slabs, and anything worth knowing | Nothing is saved until the review is confirmed |
| Exchange rates | Every pair you changed, in one review | A buy or sell rate moving more than 5% must be typed a second time (the limit can be changed per installation); a zero or mistyped rate is refused |
| AML limits | What each change means for customers, including any change that lets them send more than today | If a colleague changed the same rule while your page was open, the save is refused and nothing is saved |
A save changes only what you changed. On the rates page, that means a manual save can no longer put an older rate back over the newer one your rate feed has just written.
A history that answers "what did it say that day?"
Disputes and audits ask the same question: what was the price, or the limit, on the day of this transfer? Without a proper history, the answer is a search through raw logs.
- Fees: every change records who made it, what it was, what it became and the reason.
- Exchange rates: every change to a standard rate sits in one history with who made it.
- AML rules: every rule, exception, policy, tier and raised customer limit that changed, with the reason, filtered by rule, kind, person and date.
Promotions that start and stop on time
A weekend promotion is only a promotion if it ends on Sunday. Since 2026.10.6, a fee rule or slab scheduled for a date starts and stops on that date by the clock, instead of waiting for an unrelated save to notice. Scheduled exchange rate rules work the same way.
Useful test: list every promotion you ran last quarter with its planned end date, then check the first and last transfer priced under it. Any gap is money you gave away or customers you disappointed.
What the customer sees is what they pay
- Payment method charges and limits apply at checkout. A charge set on a payment method is added to the customer's total, and an amount the method does not accept is refused with a message naming the limit.
- Quotes refuse instead of quietly adjusting. If a customer's app asks for a currency, payout method, partner or amount that is not offered, the quote is refused and the field is named, instead of being priced on something else.
- Stale prices are flagged. A standard rate that stops moving raises an alert, and fees left unreviewed for too long raise a prompt. Scout shows both.
Watch out: before switching on payment method charges, check that your customer apps show the chosen method's total and limits. Otherwise customers meet the charge for the first time at checkout.
Separate pricing for each brand you run
Many operators run more than one brand: a main app and a second brand for a specific community or channel. Since 2026.10.6, a fee rule, an exchange rate rule, a way to pay, a receiving account and an AML rule can each be pinned to one app. A brand running as its own app can have fees, rates, payment methods and limits of its own. What a customer has sent still counts across every app, so limits cannot be avoided by switching brands. Rules that name no app work exactly as before.
Exchange rate rules go further: a special rate by customer group, platform, payout country or partner, or any mix, either fixed or following the standard rate at a set distance.
Move whole rule sets as files
Fee rules, exchange rates and AML rules can each be exported as a file and imported back, for example to copy a tested set from staging to production. An import never removes anything the file leaves out. Importing is its own permission, because a file changes more in one action than a person editing a page can.
Doing it with RemitSo
Fees, rates and limits are part of every RemitSo installation. See the admin features, how pricing is shown to customers in the customer app, each change in the release notes, or book a demo.
Frequently asked questions
Can a fee change go live without anyone checking it?
No. Every change to fee slabs or a payment method's terms shows a review of what customers would pay before it is saved.
What stops a mistyped exchange rate?
A zero or invalid rate is refused, and a rate that moves more than 5% must be typed a second time. The limit can be changed per installation.
Can each of our brands have its own fees?
Yes. Fee rules, exchange rate rules, ways to pay, receiving accounts and AML rules can each be pinned to one app.
Can we see what a fee was on a past date?
Yes. Every fee change is kept with who made it, what it was, what it became and why.
Do scheduled promotions end on time?
Yes. Rules and slabs scheduled for a date start and stop on that date by the clock.