RemitSo News

What's New in RemitSo: One Person, One Allowance, Fairer Limits and Safer Payouts

The latest releases, what each changes for your team, and what you need to do about it

RemitSo shipped fifteen releases between 7 October and 8 November 2026: 2026.09.5, 2026.10.1 to 2026.10.11, and 2026.11.1 to 2026.11.3. None of the October releases needed downtime, and each newer one says plainly what to prepare. Most change things for the better without anyone lifting a finger. A few need a decision: a permission to grant, an alert to subscribe to, or an optional add-on to switch on. This round-up is for compliance, operations, finance and product leads who want to know which is which.

RemitSo, a white label remittance platform, gives every client their own deployment, and releases are tested on your staging first. Every release has a business note that says what changed, whether it needs downtime and what to do after. New permissions and alerts reach nobody until someone grants them and subscribes, so the "what to do" column below matters.

01 · AT A GLANCE

The latest releases, and what each needs from you

What changed, whether it is included, and what to do
AreaWhat changedIncluded or add-onWhat to doRelease
Duplicate customersRecords that belong to one person are found, linked and treated as one, so a second registration is not a second allowance. A Possible Duplicate Customers desk holds the pairs that need an investigatorIncludedReview risk rules built on the retired indicator, grant six permissions, subscribe three alerts, and run the backfill. Decide when to switch the hold on: it is off until you do2026.11.2
SMS codesEvery sign-in, two-step and mobile verification code sent by SMS is recorded with the provider's delivery answer in plain words; two-step sign-in by SMS sends its codeIncludedGrant the new permission; add the SMS provider's token where you want delivery reports2026.11.3
Sanctions and contact changesA wrong sanction list version can be withdrawn, and everyone last checked against it is screened again. Customers who confirm a new mobile number or email sign in with itIncludedBefore upgrading, check that no staff account still in use is marked inactive2026.11.1
Limits and checksOnly transfers a customer has paid for count toward sending limits, document requirements and risk checksIncludedNothing to switch on. Tell compliance and support, so they know an abandoned transfer no longer holds the next one back2026.10.11
Risk indicatorsA new indicator catches unpaid transfers crossing a limit together; 47 indicators in allIncludedIndicators act through your risk rules. Decide whether to add it to one2026.10.11
SanctionsLists load all at once and are checked against what was published; re-screening carries on past long names. Earlier: whole-name matching, a fast ledger, each list watched on its ownIncludedNone. Keep someone subscribed to the sanctions alerts2026.10.3 to 2026.10.11
Payout desksDesks scoped more tightly; a receipt at payout; new filtersIncludedCheck that each desk's role still covers what it needs2026.10.11
Competitor AnalysisYour price beside each competitor's for the same corridor, payout method and amount, all fees includedOptional add-onAsk RemitSo for the licence; decide who may show competitors to customers2026.10.11
AI AssistantAsk the console why a transfer is stuck or whose side a failure is on; PDF reports; or connect your own assistantOptional add-onLicence, credits, and five permissions to grant2026.09.5, 2026.10.9
Sending ForecastWhich customers are likely to send next, who is overdue, who has lapsedOptional add-onAsk for it; RemitSo scores it on your past transfers first. Grant Browse the Sending Forecast2026.10.9, 2026.10.10
PayoutsFailed only when the partner refuses; faults on our side stop in Error with the reason; nothing left in ProcessingIncludedBrief the payout team on Error and on confirming with the partner before Retry2026.10.5, 2026.10.8
Fees and transactionsEvery fee change previewed and kept; one transactions list; background exports; previewed bulk payout updates; pricing per appIncludedNone2026.10.6
DashboardOne payment currency at a time; revenue on delivered transfers only; transfers counted from the day payment clearedIncludedGrant each of the eight sections to the roles that need it2026.10.4, 2026.10.10
Customer appsWhen money should arrive, PDF receipts, transfer search, feedback, confirmed mobile numbersIncludedDecide who answers feedback on the Feedback page2026.10.3, 2026.10.5
02 · 2026.11.1 TO 2026.11.3

One person, one allowance, and codes you can see arrive

Some customers sign up twice: a new email, a second phone, a slightly different spelling. Until release 2026.11.2, each registration had its own sending limit and its own document tiers, so a second account was a second allowance. Now RemitSo finds records that share an identity document, a name and date of birth, or a payment account, links them, and treats them as one person. Sending limits, document tiers, the sending block, the watch list, sanctions screening and the Compliance Dashboard read the person, not each record.

Pairs that need a human decision wait on a new Possible Duplicate Customers desk. An investigator compares the two records and links them as one person, dismisses the pair, or records that they are different people. Records with strong evidence can also be held from quoting or sending until someone decides. That hold is off until your installation switches it on, so plan the switch with compliance and support.

Release 2026.11.3 answers a question support teams hear every day: "I never got the code." Every sign-in code, two-step code and mobile number verification sent by SMS is now recorded with the SMS provider's delivery answer, in plain words, so the team can see whether the message arrived before asking the customer to try again. Release 2026.11.1 lets a sanction list version that turns out to be wrong be withdrawn: every installation replaces it and screens again the people last checked against it.

Customers start transfers they never pay for. They check a rate, change their mind, or start again with a different amount. Until this release, an unpaid transfer could still count toward the customer's sending limit, the documents they were asked for and the risk checks run on them. From 2026.10.11, only transfers the customer has paid for count.

An example, with illustrative figures. Your AML rule asks for proof of address once a customer's total over 90 days passes 3,000. A customer has paid for 1,800 this quarter. On Monday they start a 1,500 transfer, then abandon it. On Tuesday they start a 1,000 transfer.

The same customer, before and after 2026.10.11 (illustrative figures)
Counted toward the 90-day totalTotalWhat the customer sees
Before1,800 paid + 1,500 abandoned + 1,000 new4,300Asked for proof of address over money that never moved
After1,800 paid + 1,000 new2,800Sends as normal

That removes a source of needless document requests and support tickets. It also opens a gap someone could try to use: start several unpaid transfers together, each one under the limit, and pay for them all at once. So the same release adds a risk indicator that catches unpaid transfers crossing a limit together. If the same customer started three transfers of 1,200 at the same time, together crossing the 3,000 limit, the indicator fires. That brings RemitSo to 47 ready-made risk indicators, which you combine into your own rules. Risky transfers wait for a person; everything else flows on its own.

What to do: ask your compliance lead to look at the new indicator in Risk Mitigation and decide which rule it belongs in. An indicator on its own does not hold anything.

04 · 2026.10.11

Sanctions loading and payout desks

Sanction lists now load all at once and are checked against what was published, so what you screen against is what the publisher put out. Re-screening carries on past long names instead of stopping at them, so everyone on your books is screened after each load. RemitSo screens every sender and recipient against 8 lists, reloaded every night, and nothing is blocked by a match on its own: a person decides.

Payout desks are scoped more tightly, so each desk sees what it needs. Desks can give a receipt at payout and have new filters. If your cash pickup or agent staff use payout desks, check their roles after the upgrade.

Earlier October releases already made sanctions matching smarter, with fewer false matches from real-world name variations. The screening ledger opens in well under a second, and each sanctions list is watched on its own, with the late list named in the alert. Read the sanctions screening guide.

05 · COMPETITOR ANALYSIS

Competitor Analysis: your price beside the market

Competitor Analysis arrives in 2026.10.11 as a licensed module, an optional add-on. It prices your transfer live with your own quote engine and sets it beside each competitor's newest recorded price for the same corridor, payout method and amount. Prices are ranked by what the recipient gets per unit paid, every fee included, so a strong headline rate with a fee on top no longer looks better than it is.

Competitor prices come from a rate provider over an API, a file import, or typed in by your team from a competitor's calculator. Recorded prices are never edited, only retracted with a reason. It never changes your rates by itself: your pricing team decides. Read the full guide.

06 · AI ASSISTANT

An AI Assistant in the console

An optional add-on. Operators ask the console a question in plain words, such as "why is this transfer stuck?" or "is the partner down, or is it us?", and get an answer from their own data, limited to what they may see. Email addresses, phone numbers and long numbers typed into a question are removed before it is sent. It can prepare a PDF report on a transfer, a customer's standing or a partner's health. Each question spends one AI credit, and a failed question spends none. Teams can also connect their own assistant with a personal token. Read the full guide.

07 · SENDING FORECAST

See which customers will send next

An optional add-on. Every night the Sending Forecast reads each customer's paid transfers from the last six months and works out their rhythm. Tiles show who is overdue, due today, due within 7, 10 and 30 days, and who has lapsed. Slow senders are listed as occasional rather than guessed at. It is switched off until you ask, and RemitSo scores it against your past transfers first. It never contacts customers itself. Read the full guide.

08 · PAYOUTS

Payouts that tell the truth

A payout is now failed, and the customer told, only when the payout partner refuses it. A fault on our side, an outage, a timeout or an unreadable answer stops the payout in Error, with the reason and whose side it is on. Where the partner may already hold the money, Retry asks your team to confirm with the partner first, so nobody pays twice. No payout is left in Processing, and a refused payout update says why. Read the full guide.

09 · FEES, TRANSACTIONS, DASHBOARD

Fees, transactions and the dashboard

  • Every fee change is previewed, showing what customers pay at each step, and kept with who, before, after and why.
  • Fees, rate rules, ways to pay and AML rules can be pinned to one app, so each brand can be priced on its own.
  • One transactions list with full filters on every desk. Exports build in the background, masked as the screen is, up to 100,000 rows.
  • Bulk payout updates, up to 500 rows, are previewed row by row before anything changes.
  • Disabling a payment interface or an app now really stops it.

The dashboard reports money one payment currency at a time and never converts between them. Revenue is your fee less any coupon discount, plus the FX margin, on delivered transfers only, so it agrees with your books. Transfer counts and amounts count from the day the payment cleared. The highest-risk customers match the Compliance Dashboard, and each of the eight sections has its own permission. Read the guide to changing fees, rates and limits safely.

10 · FOR YOUR CUSTOMERS

What your customers notice

  • Apps can show when money should arrive, and give a PDF receipt in the customer's language.
  • Customers can search their transfer list.
  • Customers can send feedback with a rating, a topic and a message; your team answers it on a Feedback page.
  • A changed mobile number must be confirmed by code.
  • A customer at a sending limit is told what they can still send. From 2026.10.11, that figure no longer includes transfers they abandoned.
11 · WITH REMITSO

How releases reach you with RemitSo

Releases are numbered by date and tested on your staging first. Every environment shows exactly which release it runs, under Environment Overview. Each release has a business note that says what changed, whether it needs downtime, and what to do after, including any new permissions and alerts. Optional add-ons are switched on per client by a licence; without it nothing changes. Read every release in the release notes, see the admin features and customer app features, or book a demo.

FAQ

Frequently asked questions

Did any of these releases need downtime?

No. 2026.09.5 and every release from 2026.10.1 to 2026.10.11 went in with no downtime.

Do we need to do anything after 2026.10.11?

Nothing has to be switched on for paid-only limits or the sanctions loading changes. Your compliance lead should decide which risk rule the new indicator belongs in, and you should check payout desk roles. Competitor Analysis is only there if you license it.

Which of these are optional add-ons?

Competitor Analysis, the AI Assistant and the Sending Forecast. Each is licensed separately and switched on per client. Everything else in this round-up is part of the platform.

Why are new permissions and alerts not working after an upgrade?

New permissions and alerts reach nobody until someone grants them and subscribes to them. The release note for each release lists what to grant.

How are releases numbered?

By date: 2026.10.11 is the eleventh release of October 2026. Every environment shows exactly which release it runs.

Built by people who have helped MSBs for years.

47 ready-made risk indicators, drawn from what they see every day, combined into your own rules.

  • 47 ready-made risk indicators
  • Your own rules
  • 8 sanctions lists
  • A person decides
Book a demo

See RemitSo running with your corridors.

  • 30 minutes with our team, on video
  • The real admin panel and customer apps
  • The right way to buy it for you, explained with pricing
  • Your compliance and launch questions answered

We use these details to arrange your demo and reply to you. See our Privacy policy.

Loading the form…

Video