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

Engagement scope - proposed scope

Wise Clone Development Company: How to Choose One

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

Show me where a corridor is defined

  • If the answer is "the destination country field on a transfer", then the rail, fee logic and rules for every route live in conditionals scattered through the code, and adding corridor two is engineering rather than configuration.

Does screening run before or after settlement?

  • Before, or it is not compliance - it is reporting. Recalling a completed cross-border payment ranges from difficult to impossible, so a suspicious transfer has to be held rather than chased.

Can you verify a business, not just a person?

  • KYB is a different process from KYC - ownership structure, incorporation documents, beneficial owners. Businesses are the higher-value customers in cross-border, and a KYC-only platform cannot take them.

Reconcile a settlement that arrived late

  • Cross-border settlement is not instant and sometimes not same-day. Ask how a transfer in flight is represented and how reconciliation handles a delayed or partial settlement, because both happen routinely.

Log in as support and try to approve a flagged transfer

  • Role separation is a control, not an org chart. The person under pressure to keep a customer happy should not be the person clearing a risk flag, and the platform should enforce that rather than trust it.

Where is fee logic configured?

  • If fees are hardcoded rather than set per corridor and per flow, every pricing experiment is a deployment - and in a thin-margin business you will want to run many.

Is any of the source encrypted?

  • Ask directly, and about licence callbacks. In a regulated money business a vendor kill switch is a concentration risk your compliance function will have to disclose.

What is not included?

  • Ours is published as the Enterprise tier and includes the plain statement that we supply no licence, no correspondent relationship and no liquidity.

A proposed launch process, without time promises

Define the first service area

  • Where you operate, what you charge inside it, and any limits such as cash-on-delivery ceilings. The first zone usually becomes the template for the ones that follow.

Apply your branding

  • Name, logo, colour scheme and invoice layout applied across the storefront and apps. Which parts are configuration and which are build work is confirmed in the written scope.

Set the commercial rules

  • Commission or subscription structure, discount responsibilities, delivery pricing per zone, tax rules and payout preferences, recorded in the written scope.

Connect your own accounts

  • Payment gateways, store listings, maps and notification services stay under your own accounts, with access arranged before build work starts.

Red Flags That Mean Walk Away

If you hear any of these, stop

  • "We'll sort your licensing" Software vendors do not obtain money transmission licences. A firm blurring that line is either overselling or does not understand the regulatory perimeter - and in this category both are disqualifying.
  • "A corridor is just the destination country" Then rail selection, fee logic and per-route rules have nowhere to live, and your second corridor is a rewrite rather than a configuration change.
  • "We screen transactions in a nightly batch" By which time the money has gone. Screening has to precede settlement, because a cross-border payment that has landed is very hard to bring back.
  • "KYB is basically KYC with extra fields" It is not - ownership structures, incorporation documents and beneficial owners are a different problem. A team that conflates them has not onboarded a business customer.

What We Do Not Supply

Stated plainly, because in cross-border the boundary between software and permission decides which corridors you can serve at all.

We do not supply money transmission licences

  • Cross-border movement is regulated on both ends of every corridor. Whether you hold the required permissions, or operate under a licensed partner, is entirely yours - and a licence covering one corridor does not cover another. This determines your product before any configuration does.

We do not supply correspondent relationships

  • SEPA, SWIFT-alternative rails and a correspondent network are supported by the platform. Being onboarded by those partners, passing their due diligence on you, and the terms you negotiate are yours - and those terms are your actual cost per corridor.

We do not supply liquidity

  • Pre-funding nostro accounts in destination currencies so transfers settle quickly is a treasury function requiring real working capital, held per corridor. It is frequently the largest commitment in a remittance plan and no software provides it.

Advanced finance modules are Enterprise scope

  • Crypto rails, forward contracts and hedging tooling are named on the hub as premium layers. If your corridors carry FX exposure between quote and settlement that you intend to hedge, scope this early rather than after launch.
  • A vendor precise about this boundary is more useful than one implying they can shorten a regulatory timeline or open a corridor for you. Nobody can do either.

More pages on this build

Five pages describing this proposed build. You are on Development Company.

A partner who knows where software ends

Named fintech deployments, corridors modelled properly, screening before settlement, and a plain statement that we supply no licence, no correspondent and no liquidity.

Omnistu is an independent software development project. We are not affiliated with, connected to, sponsored by, or endorsed by Wise .

Discuss this scope by message

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

team@omnistu.com