Feature scope - proposed scope
Wise Clone Features: Every Corridor Is Its Own Product
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
Five roles with scoped access, because a cross-border platform is operated by a compliance team as much as it is used by a customer.
Personal Sender
- Multi-currency wallets with balances per currency
- Global transfers with the rate quoted before sending
- Recipient management with saved beneficiaries
- Physical and virtual cards
Business Customer
- Business wallets and multi-currency receivables
- Invoicing and payment collection
- Payroll and bulk transfer runs
- Spend controls and expense workflows
Compliance Operator
- KYC and KYB submission review
- Verification rules enforced centrally
- Fraud and risk flags with policy enforcement
- Transaction monitoring in real time
Finance and Platform Operator
- Fee logic configuration per corridor and flow
- FX rate engine and spread control
- Settlement, reconciliation and refunds
- Wallet and platform finance visibility
How It Works, End to End
One cross-border transfer, traced through every check, every rate decision and every record it produces.
The sender is verified before they can send
- KYC for individuals, KYB for businesses, submitted and reviewed against verification rules enforced centrally rather than judged case by case. In a money-movement business this is the gate everything else depends on, so it precedes the wallet rather than following it.
The corridor selects the rail
- SEPA within its zone, SWIFT-alternative rails or the correspondent banking network elsewhere, and local payment infrastructure where available. Different routes settle at different speeds and costs, and choosing per corridor rather than uniformly is where the margin actually comes from.
Screening runs before the money moves
- AML checks and fraud controls apply to the transfer, the sender and the recipient. A transfer that trips a rule is held for review rather than sent and investigated afterwards - the order matters, because recalling a completed cross-border payment is far harder than pausing one.
A compliance operator intervenes where required
- Flagged transactions surface in transaction monitoring for approval, rejection or escalation, with the decision recorded. This is a role with its own permissions precisely so that the person reviewing risk is not the person handling the customer.
The recipient is paid, the sender is told
- Settlement completes over the chosen rail, the recipient receives funds in their currency, and the sender sees status throughout rather than after. Statements and records are generated on both sides.
Finance reconciles, and the fee logic proves out
- Settlement records, fee logic and refunds reconcile in the finance console, with revenue and analytics showing which corridors actually earned. On a business where margin is thin and per-corridor, that reporting is how you learn which routes are worth keeping.
- Steps four and five in that order are the ones that separate a remittance platform from a payments script. Screening after settlement is not compliance, it is reporting.
Every Feature Earns Its Place
Feature lists are cheap. These exist because a specific thing goes wrong in cross-border payments without them.
Half of these are compliance controls and half are corridor economics. Those two things are what cross-border payments actually is, underneath the interface.
The Technology Behind the Features
Choices made for auditability and integration rather than novelty.
Why the corridor has to be a first-class concept
- The temptation in cross-border software is to model a transfer as a source, a destination and an amount, then pick a rail at send time. That works until the second corridor, at which point everything that differs by route - the rail, the settlement time, the fee structure, the compliance expectations, the correspondent relationship - has nowhere to live except in conditionals scattered through the code. Making the corridor a modelled thing with its own rail, fee logic and rules is what lets you add Kenya without touching how the Philippines works.
- Complete source transfers to you at handover, with rebranding and white-labelling included.
Boundaries we state in writing for your build
Enterprise scope, or yours to own
- Money transmission licences Cross-border money movement is regulated in every jurisdiction on both ends of every corridor. Whether you hold the required licences, or operate under a licensed partner, is entirely yours - and it determines which corridors you may serve before any technical decision does.
- Correspondent and partner relationships The platform supports SEPA, SWIFT-alternative rails and a correspondent network. Being accepted by those partners, and the terms you get, is a commercial negotiation you own - and it is what actually determines your cost per corridor.
- Nostro funding and liquidity Pre-funding accounts in destination currencies so transfers settle quickly is a treasury function requiring real capital. No software supplies it, and it is often the largest working-capital commitment in the plan.
- Advanced finance modules Crypto rails, forward contracts and hedging tooling are named on the hub as premium monetization layers - Enterprise scope rather than base build.
More pages on this build
Five pages describing this proposed build. You are on Features.
How it earns
- Omnistu is an independent software development project. We are not affiliated with, connected to, sponsored by, or endorsed by Wise .
- Wise Clone is used descriptively. It is how the software industry refers to building a platform with functionality similar to Wise, and how clients search for it.
- Wise and all other third-party names and marks are the property of their respective owners, referenced here solely to describe the category of software offered.
Discuss this scope by message
Tell us your market and audience, and we will respond with a practical read on scope.
team@omnistu.com