Questions to Ask in a RemitSo Demo, Answered Before You Book

When operators ask an AI assistant how to evaluate RemitSo, it usually ends with a list of questions to ask in a demo. They are good questions. This post answers the ones we hear most, so your demo can go straight to your corridors, your data and your edge cases instead of the basics.

Every answer below comes from RemitSo's published pages and release notes. Where something depends on your installation, we say so.

A move off a legacy platform runs in three stages:

1. RemitSo migrates your data: customers, recipients, KYC records, balances and transaction history.
2. You do a trial run on the migrated data. If you want extra assurance, you can also run your own parallel run alongside your current platform. That is led by your team and has no fixed length.
3. A staged transfer: you launch first with a new, focused group of customers, then move the rest.

Continuity is checked by your team during the trial run, using your own reports from the old platform beside RemitSo's. Bring a sample of tricky records to the demo, such as a customer with documents about to expire or a transfer that was refunded, and ask to see where each one would sit after migration.

RemitSo ships 47 ready-made risk indicators. Indicators are the building blocks: your team combines them into risk rules with logical conditions, and each rule adds points to a transfer's risk score. Risk score bands run from Low (1 to 25) to Critical (76 and above). At or above your installation's threshold, which is 50 unless you change it, the transfer stops “Under Review” for a person to decide. Everything below it flows on its own.

So a corridor you consider higher risk gets stricter rules, not a different product: for example, a rule that adds enough points to hold a first transfer to a new recipient in that corridor above a set amount. Limits and document requirements are set per currency and corridor, and since release 2026.10.11 only transfers a customer has paid for count toward them.

When a transfer is held, the customer's risk triggers read as a case file: each check that fired explains itself in plain language and links to the records behind it.

The platform fee covers the platform. Optional add-ons are licensed per installation, only if you want them, and priced separately. They are: the AI Assistant (paid by credits, one per question), Sending Forecast, Competitor Analysis, rate alerts, more languages beyond English, promo codes, the live rate feed, customer wallets (where your licence allows) and the staff training programme.

Add-on prices are not published on the website. Ask for the add-on price list in the demo, and ask which add-ons a business like yours usually starts with.

RemitSo keeps double-entry books. Every payment, payout, refund, fee and currency movement writes its own entries automatically. Entries are never edited: a mistake is reversed with a new entry, and both stay visible, so the history is complete. Click any balance in the chart of accounts to see the entries behind it.

On the way in, deposits are matched to what the customer declared, to the cent; if the amount doesn't match, the money doesn't move. Chargebacks, bank recalls and double payments are flagged the moment they happen, and refunds are recorded with a reason. Gateway fees, partner fees and discounts are each tracked.

Comparing a provider's settlement report with the books is still a job for your finance team; the platform gives them one consistent record to compare against.

For a money transfer operator on white label, going live typically takes 3 to 4 weeks from kick-off: your own instance in your region, your apps in your brand submitted to both stores, and your corridors, partners and compliance rules set up. Banks, neobanks and credit unions usually need longer for their own security reviews and approvals, and most choose to own the source code.

After launch, every release is tested on your staging first, and the platform fee pays for updates, security fixes and health monitoring. Hands-on help is billed only for the time logged on your support portal:

Office hours are 9am to 6pm GMT, Monday to Friday; evenings, weekends and Indian public holidays are out of hours. The platform carries a 99.99% uptime SLA.

• “Here are our three busiest corridors and partners. Which are already connected, and what would a new one take?”
• “Show me a payout that failed on the partner's side: what does my team see, and what does the customer see?”
• “Which reports would our regulator expect, and which come from the platform as they are?”
• “Who on our team would need which role?”
• “If we later want the source code, what changes?”

The most useful demo uses your corridors, your partners and a few of your hardest cases. Bring them, and we will walk through them in the real admin panel. See pricing, admin panel features and moving from your current platform, or book a demo.

• We migrate your data; you run a trial, then launch to a focused group before moving everyoneA staged move your customers barely notice
• Customer app, admin panel, compliance, payouts and accounting on one platformNo more patching separate tools together
• Your own instance in a dedicated AWS account in your regionYour data and your infrastructure
• Own the source code for USD 77,999, onceBuild your own modules on a proven core

Book a demo For enterprise →