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

Engagement scope - proposed scope

Choosing a White Label Money Transfer Software Provider

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

Typical scoping questions

Who owns the source and the customer records?

  • Ask for the repository and the database by name, and whether any file is encrypted or phones home for a license check. Here the full source arrives unencrypted with no callback, and every sender record sits in your database.

What happens the day you stop paying?

  • On a rented platform the service, and often your customer list, stops with the invoice. On a platform you own, nothing switches off: you keep running on your own cloud and pay your hosting. Get the answer in writing.

Whose licenses does each corridor run under?

  • Money transmission is regulated at both ends of every route. The answer should be yours or a licensed partner's, named per corridor. A vendor that implies its software brings permission to operate is selling something it cannot hold.

Where does customer money sit?

  • With the bank you arrange, safeguarded under your license. Never with us: the software never holds customer funds and we never take custody of them. Treat any provider who offers to hold the float as a regulatory problem, not a convenience.

Show me where a corridor is defined

  • If it turns out to be the destination field on a transfer, the rail, fees and rules for each route are scattered through conditionals in the code. Then the second corridor is an engineering project rather than an afternoon in the console.

Does screening sit before settlement or after it?

  • It has to come first. A cross-border payment that has already landed is hard and sometimes impossible to recall, so a suspicious transfer must be held at the gate rather than investigated once it has gone.

Reconcile a settlement that arrived late

  • Settlement across borders is rarely instant and not always same-day. Ask to see how a transfer in flight is shown, and what reconciliation does with a payout that lands late or in part, because both are routine.

What is not included?

  • A quote with no exclusions has not been costed. Ours names them plainly: no license, no correspondent relationship, no liquidity, no custody of funds, and no specific screening vendor without Enterprise scope.

The Six-Step Delivery Process

From signature to a running platform, with the owner of each step named.

Map corridors to permissions

  • We list the routes you plan to open, the license or licensed partner covering each end, the correspondent and payout partners already signed, and whether retail senders, businesses or both come first. Nearly every later decision follows from this map.

Stand up the cloud and the ledger

  • Your cloud account is provisioned, the Node.js services go live, PostgreSQL is loaded with the wallet and ledger schema, and monitoring, backups, recovery, the domain and TLS are switched on.

Set the compliance rules

  • KYC and KYB requirements for each jurisdiction, verification enforced centrally, AML and fraud thresholds, monitoring rules, and a compliance role kept apart from support. We prove the separation by trying to break it.

Apply your brand and your teams

  • Your name, logo and colors across the apps, web and console, your custom domain, organization and team structures with role-based invitations, and the business finance modules if you serve companies.

Red Flags That Mean Walk Away

Six lines that should close the meeting, whichever provider says them, ourselves included.

Hear one of these and leave

  • "We'll take care of your licensing" No software seller can obtain a money transmission license for you. Whoever blurs that line is overselling or does not know where the regulatory perimeter sits, and either one rules them out.
  • "Keep customer balances with us" A software vendor holding your customers' money is acting as an unlicensed custodian. Funds belong with the bank you arrange, under your license, and nowhere else.
  • "The platform is certified, so you are covered" Certification is issued to the operating entity after its own audit. Software can be built to the controls an assessor checks, but it cannot carry the certificate for you.
  • "A corridor is just a destination country" Then rails, fees and route rules have nowhere to live, and adding the second corridor means rewriting code rather than changing a setting.

What a Money Transfer Platform Has to Get Right

Five properties no screenshot reveals, and every live corridor depends on.

Where the Software Stops

Written down before you buy, because in cross-border money the line between software and permission decides which corridors you may serve at all.

No money transmission license comes with it

  • Moving money across a border is regulated at both ends of every corridor. Holding the money transmitter, e-money or payment license, or working under a licensed partner, is wholly your responsibility, and a license covering one corridor does not cover another. That fact shapes your product before any setting does.

No correspondent or payout relationships

  • The platform supports SEPA, SWIFT-alternative rails and a correspondent network. Getting onboarded by those partners, clearing their due diligence on you and negotiating terms is yours to do, and those terms are your true cost on each corridor.

No liquidity and no custody of funds

  • Pre-funding destination accounts so transfers settle quickly is a treasury job that needs real working capital on every corridor, often the biggest line in a remittance plan. No software supplies it, and the software never holds customer money.

Specific compliance vendors are Enterprise scope

  • KYC, KYB, AML and fraud workflows are in an initial scope. Wiring in a particular identity, sanctions-screening or transaction-monitoring provider, which your license or partner will often dictate, is quoted on its own.

Advanced finance modules are Enterprise scope

  • Crypto rails, forward contracts and hedging tools are premium add-ons. If your corridors leave FX exposure open between quote and settlement and you plan to hedge it, scope that at the start rather than after go-live.
  • A provider exact about these limits is worth more than one hinting it can shorten a regulator's timeline or open a corridor on your behalf. No one can do either.

Operators Who Launched With Us

Two named fintech clients, quoted word for word as they appear on the hub. We show no aggregate rating, no star score and no paraphrase in their place.

A founder who needed a faster path to market than a from-scratch build, and who evaluated on operational depth - admin control and multi-currency flows - rather than on frontend polish.

A Finance Platform - Chosen on Backend Structure

  • An operator who reviewed several vendors and chose on product maturity, citing accounts, transactions, business modules and Banking Core readiness rather than the interface.
  • What decided it: product maturity behind the interface. In cross-border that is the right thing to evaluate, because the interface is the part every vendor gets right.
  • "We reviewed multiple vendors before choosing Omnistu, and the difference was clear in the product maturity... what really gave us confidence was the backend structure - accounts, transactions, business modules, and the Banking Core readiness. It felt like a product built for serious execution, not just demos." Randy Andres , Product Lead, Finance Platform
  • The words above are the clients' own, with no rating widget and no review markup added. Both judged the back office first, admin control and backend structure ahead of the app, and that is the order we would suggest you judge any provider in.

Pick the provider that names its limits

Named fintech clients, corridors modeled as real objects, screening ahead of settlement, and a written statement that no license, correspondent, liquidity or customer money comes from us.

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.

Discuss this scope by message

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

team@omnistu.com