PRODUCT ENGINEERING / CONNECTED BUSINESS SYSTEMS
Omnistu Global - Everything ConnectedStart a project

Feature scope - proposed scope

White Label Remittance Software Features: Corridor by Corridor

This page describes proposed scope for a build in this category, agreed in writing per project. Nothing here is a finished product, a fixed bundle or a fixed price.

Scope areas for this kind of build

Feature Set by Role

Your compliance and finance staff spend as many hours inside a transfer platform as your customers do, so each of the five roles gets its own screens and nothing more.

Sender and Freelancer

  • A wallet per currency, with reserved and frozen amounts visible
  • Sends abroad with the fee and rate shown before confirming
  • Saved recipients with bank details, IBAN, SWIFT and country
  • One-off, scheduled, recurring and batch transfers

Business Account

  • Company wallets that hold receivables in several currencies
  • Invoices with line items, taxes and status tracking
  • Payroll runs and employee pay records
  • Bulk payouts by file upload, with status per line

Compliance Team

  • KYC and KYB queues with verification checks
  • Tiered verification rules applied the same way to everyone
  • Hooks for the sanctions-screening provider you contract
  • User risk profiles, anomaly flags and transaction holds

Operator and Finance

  • Fee tables per corridor and per transfer type
  • The FX spread you add to each quoted rate
  • Settlement records, reconciliation and refunds
  • Revenue, volume and KPI dashboards by corridor

How It Works, End to End

Follow one transfer from sign-up to the finance report, including each check it clears and each record it leaves behind.

Verification comes before the wallet

  • A person passes KYC and a company passes KYB, and only then does a wallet open. Your tiered rules decide the outcome the same way every time, not an analyst's mood on a busy afternoon, because everything after this step relies on knowing who is sending.

The route chooses the rail

  • Each corridor carries its own rail setting: SEPA inside the euro zone, SWIFT-alternative rails, a correspondent network or local payout, reached through the partners you have signed and funded. Speed and cost differ by route, and choosing per corridor is where the margin is made.

Checks run while the money is still yours to stop

  • Fraud rules and risk scores look at the sender, the recipient and the transfer, and the screening step calls the provider your license requires. Anything that matches a rule waits in a queue. Pausing a payment is easy; pulling one back from another country is often impossible.

The recipient gets paid and the sender can see it

  • The payout partner settles over the chosen rail in the recipient's currency. Status updates reach the sender at each stage instead of at the end, and statements are produced for both parties.

Finance checks the books, corridor by corridor

  • Settlement records, fees and refunds reconcile in the operator console, and the dashboards split revenue by corridor. When each route earns a thin margin of its own, that split shows you which ones to grow and which to drop.
  • The order of steps four and five is the real difference between remittance software and a generic payments script. A check that runs after settlement only tells you what already went wrong.

Every Feature Earns Its Place

Anyone can write a long feature list. Each item here is in an initial scope because a money transfer operator gets hurt in a specific way without it.

Roughly half the rows are about controls and half are about corridor economics. Strip away the screens and that pair is what a remittance business runs on.

The Technology Behind the Features

Picked so that auditors can follow it and partners can plug into it, not to look new.

Why each corridor needs its own record

  • The easy way to build transfer software is to store a sender, a recipient and an amount, and pick a rail when the money leaves. It holds up for exactly one route. Once a second arrives, the rail, the settlement time, the fee, the checks and the partner terms that differ between them end up as special cases scattered through the code. Giving every corridor its own rail, fee logic and rules means that, once the license and partner are in place, a new route is set up from the console and the routes already live are left alone.
  • At handover you receive the full source and the documentation, rebranded to your name, and nothing stops you changing, extending or redeploying it.

Boundaries we state in writing for your build

Add-on scope, or yours to arrange

  • Money transmitter, e-money or payment licenses Money transmission is regulated at both ends of every corridor. You hold the license in each jurisdiction or work under a partner that does, and that decides which routes you can open long before any setting does. The software holds no license of any kind.
  • Correspondent, banking and payout partners Connectors are in the code, but being accepted by those partners and the terms they offer are your negotiation, and those terms set your real cost per corridor. Live rails and live FX switch on only once the agreements exist.
  • Liquidity and customer funds Pre-funding accounts in destination currencies takes real capital and is often the largest working-capital line in the plan. The bank holding customer money and its safeguarding are yours; Omnistu never holds customer funds.
  • Your compliance program and staff The platform gives you the controls and the evidence. Policies, filings to each regulator and the qualified people running them are yours, and we do not advise on licensing or compliance.

Deciding who should supply your money transfer platform?

  • The Provider page covers the questions to put to any vendor, how delivery runs, what to test on screening order and reconciliation, and a real client deployment.

Own the code, the corridors and the customer records.

Omnistu is an independent software development project. We are not affiliated with, connected to, sponsored by, or endorsed by Wise or any other money transfer, remittance or payments service.

White label remittance software describes a category of product, not any one company. Brand names appear elsewhere on this site only to describe the kind of platform being built and the terms buyers search for.

Discuss this scope by message

Tell us your market and audience, and we will respond with a practical read on scope.

team@omnistu.com