A structured buyer's framework covering every feature category — consumer, back-office, compliance, technical, and commercial — that money transfer operators must verify before committing to a remittance platform.
Choosing the right remittance platform is one of the highest-stakes decisions any money transfer operator will make — and the remittance platform features checklist for MTOs is the structured framework that separates sound evaluations from costly mistakes. This guide covers every feature dimension an MTO must verify before signing a contract: consumer UX, back-office operations, AML compliance, technical infrastructure, payout network depth, and commercial terms that compound over years.
In This Article
The most expensive mistake in fintech is not launching — it is launching on the wrong infrastructure and discovering the problem two years later. MTOs that select platforms without a structured feature evaluation frequently encounter the same cluster of problems: compliance gaps that trigger regulatory notices, rigid architecture that cannot support new corridors, and commercial models that punish growth with rising fees.
Platform migration is far more disruptive than initial selection. Customer data must be transferred, integrations rebuilt, staff retrained, and — in regulated jurisdictions — regulators sometimes notified of material operational changes. Analysts who study MTO operations consistently note that migration projects run 18 to 36 months and routinely exceed initial cost estimates by two to three times.
A remittance platform is the end-to-end technology system that powers money transfer operations — encompassing the consumer-facing application, back-office management tools, compliance and AML engine, payment rail integrations, and the commercial agreement that determines how the vendor shares in (or stays out of) your revenue.
The checklist that follows is structured by functional area. Work through each section with your evaluation team before issuing any RFP or entering sandbox testing. Every item maps to a genuine operational or regulatory risk. None of them are optional in a market that requires FCA, FINTRAC, FinCEN, or AUSTRAC compliance.
Consumer experience determines conversion rates, repeat transactions, and word-of-mouth referrals. In competitive remittance corridors, switching costs for senders are low — a slow, friction-heavy app loses customers to the next provider within one transfer cycle. Every item in this section is a direct driver of revenue retention.
A platform's consumer layer is visible — but the back-office is where an MTO's operational efficiency is actually won or lost. Understaffed compliance teams, manual FX rate adjustments, and poor reporting capability compound into operational cost overruns that erode margin as transaction volumes grow.
| Feature Area | What to Verify | Minimum Acceptable Standard | RemitSo |
|---|---|---|---|
| Agent & Branch Management | Multi-level agent hierarchy, commission tracking, branch-level P&L | Unlimited agent tiers, real-time commission ledger | Included |
| Transaction Management Dashboard | Real-time status, manual override, exception queue, bulk processing | Sub-second refresh, searchable by 10+ fields | Included |
| FX Rate & Spread Management | Live rate feeds, manual spread override per corridor, margin floor controls | Per-corridor rate overrides with audit trail | Included |
| Customer Management + Risk Tiering | Customer risk profiles, tiered limits, EDD flag workflow | Automated tier assignment with manual override | Included |
| Reporting & Analytics | Corridor performance, agent productivity, AML exception volumes, custom report builder | Scheduled exports, real-time dashboards | Included |
| Role-Based Access Control | Granular permissions by function, principle of least privilege, action audit log | RBAC + ABAC hybrid, full audit trail | RBAC + ABAC |
Figure 1: Back-office feature checklist — minimum acceptable standards and RemitSo verified capability.
Role-based access control deserves particular scrutiny. Platforms that implement only broad role categories — "admin," "agent," "viewer" — create compliance exposure. A proper implementation supports attribute-based access control (ABAC) in addition to role-based access (RBAC), allowing permissions to be conditioned on customer risk tier, corridor, transaction value, and time-of-day. This is increasingly expected in FCA and FinCEN examinations.
Compliance capability is not a feature set — it is the licence-preservation infrastructure of your business. MTOs have lost operating licences not because their compliance teams were negligent, but because the platform they chose could not surface the indicators that regulators expected to see actioned. Every item in this section is a non-negotiable. Weakness in any one creates regulatory exposure.
Figure 2: Six compliance checklist failures that have directly contributed to MTO licence suspensions and enforcement actions. Verify each against your shortlisted platform before committing.
The full compliance checklist for any serious evaluation must also include: tiered EDD workflows from standard through full Enhanced Due Diligence, PEP screening against current lists, automated regulatory report generation, and documented escalation paths for every alert type. For a deeper treatment of AML requirements specifically, see the FATF guidance on technology-based AML/CFT solutions.
Infrastructure decisions made at platform selection create ceilings on future growth. A platform that cannot sustain throughput at scale, cannot offer contractual uptime guarantees, or relies on proprietary closed-source components will constrain an MTO's options at exactly the moment volume demands more flexibility.
Figure 3: RemitSo verified technical performance benchmarks. Use these figures as the baseline when evaluating competing platforms' infrastructure claims.
When evaluating technical infrastructure, use the following checklist framework — and require vendors to substantiate every claim with documentation, not marketing copy:
Corridor coverage at launch is rarely the corridor coverage an MTO needs at month 18. Remittance businesses evolve — new diaspora communities, new partnership opportunities, new regulatory clearances open new markets. A platform's payout network architecture determines whether expansion requires a new vendor or a configuration change.
The core of most corridors. Verify support for local clearing rails — not just SWIFT. Real-time payment rails matter for recipient experience: UPI and IMPS in India, Instant Payment Service in the UK, NPP in Australia. SWIFT is fine for business payments but slow and expensive for consumer remittance.
Mobile wallet payout has overtaken cash in several corridors — particularly Sub-Saharan Africa, Pakistan, and the Philippines. The platform must have live, maintained integrations — not "available on request" partnerships — for the wallets dominant in your target corridors.
Cash payout remains essential in corridors where banking penetration is low and in rural distribution. Verify the density and geographic spread of the cash agent network in each target corridor — not just headline country coverage but sub-national reach. An agent network covering only capital cities is not a cash payout capability for rural Bangladesh or Ethiopia.
Platform features determine what you can do. Commercial terms determine how much of the revenue you keep. For MTOs that expect to grow, the pricing model compounds — positively or negatively — with every transaction you process. Reviewing the white-label remittance software comparison makes the long-term impact of commercial model differences concrete.
Figure 4: Long-term commercial impact comparison — flat-fee licensing vs revenue-share pricing model. At $10M annual transfer volume with a 1.5% average fee, a 20% revenue share costs $30,000/year extra — growing proportionally with every corridor you open.
Beyond pricing model, the commercial terms checklist must cover:
A structured evaluation process compresses decision-making time while reducing the risk of overlooking critical gaps. The five-phase framework below applies to both greenfield selection and migration decisions. Budget 4–8 weeks total. Compressed timelines beyond this are possible — but only if each phase has a designated decision-owner with authority to advance or eliminate vendors.
Figure 5: Five-phase platform evaluation framework for MTOs — from RFP definition through reference verification. Each phase should produce a documented output before the next phase begins.
For a comprehensive treatment of how different platform vendors compare against this process, see the remittance software comparison guide, which benchmarks the leading platforms across all five evaluation dimensions.
RemitSo is a white-label remittance software platform built by Prymera Consulting — not a money transfer operator. That distinction matters: the technology is the product, not a side operation to a payments business. Every feature in this checklist maps directly to verified RemitSo production capability.
RemitSo's consumer layer is built on Flutter 3.23.2 — a production-grade cross-platform framework that delivers native-quality performance on both iOS and Android from a single codebase. The web transfer portal shares the same back-end API layer as the mobile apps. KYC onboarding completes in 15 seconds — combining automated document OCR, liveness detection, and real-time sanctions pre-check. Push notifications, SMS, and email are all supported with multi-language capability.
The RemitSo back-office provides multi-tier agent and branch management, real-time FX rate and spread management with per-corridor override capability, a full customer management module with automated risk tiering, and a reporting suite with scheduled exports and live dashboards. Access control is implemented as a hybrid RBAC + ABAC model — permissions can be conditioned on customer risk tier, corridor, and transaction value.
RemitSo's AML engine monitors 55+ transaction indicators, calibrated per corridor. Sanctions screening runs against 40,000+ records from 8+ consolidated lists — OFAC, UN, EU, HMT, DFAT, and regional authorities — with phonetic and fuzzy matching. KYC/eKYC is tiered from standard through full Enhanced Due Diligence. SAR and STR case management includes end-to-end audit trail. IFTI and regulatory report generation is automated. Travel Rule compliance and business entity screening with beneficial ownership verification are both included. 97% of transactions clear AML checks automatically — reducing manual review queues to a manageable exception volume.
RemitSo is deployed on AWS — Lambda for compute, S3 for storage, SQS and SNS for messaging, and SES for communications. The contractual uptime SLA is 99.99%. API response time at P95 is under 120ms. Peak TPS capacity is 5,000+. Security certifications are current: ISO/IEC 27001:2022 and PCI-DSS. The entire open source stack is MIT, Apache 2.0, or BSD licensed — no GPL or AGPL components. The backend is PHP 8.3 on Laravel 12. The database layer is PostgreSQL 17 with Redis caching. All platform functions are accessible via documented APIs.
RemitSo supports 100+ payout countries. Mobile wallet integrations include GCash, JazzCash, EasyPaisa, M-Pesa, and OPay — all live, not "available on request." Bank transfer rails include UPI, IMPS, and NEFT for India corridors, alongside SWIFT and correspondent banking for international reach. Cash agent network access is available for corridors requiring physical distribution.
RemitSo operates on a flat-fee model — no revenue share on any tier. Clients keep 100% of their FX spreads. The platform is fully white-label: your brand, your domain, your app store listing. Source code ownership is available as a one-time perpetual licence. PaaS monthly tiers run from $99/month to $499/month. The full feature breakdown is at RemitSo platform features.
RemitSo is built for MTOs who want compliance-grade infrastructure, full brand ownership, and a vendor that earns retention through product quality — not revenue-share lock-in. Here is what you get from day one.
A production-grade remittance platform must cover five functional areas: consumer-facing features (mobile app, web portal, KYC onboarding, transaction tracking, multi-language support), back-office operations (agent management, FX rate management, customer risk tiering, role-based access control, analytics), compliance and AML (sanctions screening, transaction monitoring, SAR case management, Travel Rule, automated regulatory reporting), technical infrastructure (API-first architecture, 99.99% uptime SLA, sub-200ms API response, ISO 27001 and PCI-DSS certification), and payout network (multi-corridor bank rails, mobile wallet integrations, cash agent access). Any platform missing material capability in any of these five areas represents a gap that will become operationally or regulatorily significant as transaction volumes grow. The evaluation checklist in this guide maps each feature to the specific risk it addresses.
Six compliance features are non-negotiable for any licensed MTO: real-time sanctions screening with fuzzy matching against 40,000+ records from consolidated lists (OFAC, UN, EU, HMT, DFAT minimum); corridor-calibrated transaction monitoring with at least 50 indicators; tiered KYC/eKYC from standard through full Enhanced Due Diligence; SAR and STR case management with a full end-to-end audit trail; automated regulatory report generation (IFTI for AUSTRAC, CTR for FINTRAC, SARs for FinCEN/FCA); and Travel Rule compliance for jurisdictions where it is enforced (UK, EU, USA, Canada, Australia). Beyond these six, business entity screening with beneficial ownership verification is becoming a practical requirement as regulators increase scrutiny of corporate sender accounts. Platforms missing any of these capabilities are already non-compliant in one or more major licensed jurisdictions.
A production-grade remittance platform should commit to sub-200ms API response time at P95 — meaning 95% of API calls complete in under 200ms under normal load conditions. The benchmark for platforms targeting enterprise-volume MTOs is sub-120ms at P95. For context, a transaction initiation sequence in a well-optimised app involves 4–6 API calls: rate fetch, beneficiary lookup, compliance pre-check, transaction creation, confirmation, and notification. If each call averages 300ms, the visible end-to-end flow takes 1.8–2.2 seconds — which is perceptible friction in a consumer experience. Require vendors to provide load-test evidence at 2–5x your expected peak TPS, not average response times from a low-traffic sandbox environment. RemitSo's verified API response time is under 120ms at P95.
For any MTO with a growth plan, a flat-fee platform is almost always the correct commercial choice. Revenue-share models are structured so that your platform cost grows proportionally with your revenue — which means the platform vendor extracts a permanent share of every gain you make from better FX rates, higher volumes, or new corridors. A flat-fee model gives you a fixed, predictable cost baseline while allowing your revenue to grow without a corresponding platform tax. At $5M annual transfer volume with a 1.5% average fee and a 20% revenue share, the platform cost is $15,000 per year. At $50M volume, that becomes $150,000 per year for the same platform service. A flat-fee platform at $499/month costs $5,988/year regardless of volume. The economics decisively favour flat-fee at any meaningful scale. RemitSo operates exclusively on a flat-fee model — no revenue share at any tier.
White-label remittance software is a fully built, tested, and production-ready remittance platform that an MTO deploys under its own brand — replacing all vendor branding with the MTO's own logo, colour scheme, domain name, and app store identity. The MTO's customers see and interact with the MTO's brand throughout the entire transaction lifecycle, with no visible reference to the underlying software vendor. White-label licensing is distinct from source code ownership: under a white-label licence, the software remains owned by the vendor but deployed under your brand. Under a source code licence, the MTO owns the codebase outright and can modify, extend, or migrate it independently. Both models are available from RemitSo — white-label PaaS from $7,499 one-time plus a monthly support tier, or a perpetual source code licence for full IP ownership.
A rigorous platform evaluation should take 4–8 weeks from initial RFP to final decision. The five-phase framework in this guide allocates approximately one week to each phase: requirements definition and RFP distribution (Week 1), vendor RFP response review and shortlisting (Week 2), sandbox testing with your technical and compliance teams (Weeks 3–4), compliance architecture review with your MLCO (Week 5), and commercial negotiation with reference checks running in parallel (Weeks 6–8). Evaluations compressed below four weeks tend to skip sandbox testing or compliance review — which are exactly the phases where platform gaps are discovered. Conversely, evaluations that run beyond eight weeks usually indicate an internal decision-making process issue, not a vendor complexity issue. Assign a single decision-owner with authority to advance or eliminate vendors at each phase gate.
Sandbox testing is the evaluation phase in which the prospective MTO gets access to a fully functional test environment — mirroring the production platform — and runs real test scenarios against it. This is distinct from a sales demonstration, which is a scripted walkthrough of pre-selected features. In a genuine sandbox, the MTO's technical team can call APIs directly, the compliance team can trigger monitoring scenarios and review alert outputs, and the operations team can process end-to-end test transactions through back-office workflows. Sandbox quality is a reliable proxy for production quality: vendors that cannot provide a stable, complete sandbox environment typically have production environments with similar gaps. Require access to a sandbox that includes your target corridors, realistic FX data, and a compliance exception workflow — not just a rate-retrieval and transaction-initiation demo. A vendor that refuses or delays sandbox access during evaluation is a material red flag.
RemitSo scores across all five checklist categories with verified production figures. Consumer-facing: Flutter 3.23.2 native mobile apps, full web portal, 15-second KYC onboarding, multi-language support. Back-office: multi-tier agent management, per-corridor FX spread controls, automated risk tiering, RBAC + ABAC access control. Compliance: 55+ AML monitoring indicators, 40,000+ record sanctions screening with fuzzy matching across 8+ consolidated lists, tiered EDD, SAR case management with audit trail, Travel Rule compliance, automated IFTI and regulatory reporting, 97% auto-clearance rate. Technical: 99.99% uptime SLA, sub-120ms API response at P95, 5,000+ TPS capacity, ISO/IEC 27001:2022 and PCI-DSS certified, AWS infrastructure, MIT/Apache/BSD-only open source stack. Payout: 100+ countries, live mobile wallet integrations including GCash, JazzCash, EasyPaisa, M-Pesa, and OPay. Commercial: flat-fee only — no revenue share, full white-label, source code ownership available. The full feature breakdown is available at the RemitSo platform features page.
