White Label Remittance Software Features: Corridor by Corridor
A money transfer business is really a set of routes, and no two routes share a payout partner, a settlement clock, a fee or a rulebook. Software that flattens them works for the launch route and breaks on the next. This is the platform underneath the money transfer clones, listed by the people who use it. The licenses and partners behind each route stay yours.
Request a Live Demo →See PricingFeature 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
- Virtual card issuing and physical card requests, run with your issuing partner
- Payment links, money requests with due dates and bill splitting
- Invoices, a client list and PDF exports for freelancers
- MFA, trusted devices, biometric login and sign-in history
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
- Daily or monthly spend limits on each card
- Staff invited with permissions set by role
- Sign-off chains before money leaves the account
- Cash-flow views, statements and PDF or CSV reports
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
- Real-time monitoring with a review queue
- AML/CFT cases with approve, reject or escalate
- Suspicious activity and filing workflows, with the filings yours
- An audit trail on every decision and approval
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
- User tiers, account status and feature flags
- Brand name, logo, colors and policy rules
- Scoped API keys with rotation and usage tracking
- Webhooks with OAuth 2.0 and delivery logs
The fifth role is the agent, who works in a separate scoped view. Keeping these apart is a control in its own right: whoever answers a customer cannot clear that customer's held transfer, and every admin action lands in the log.
Rented Platform vs One-Time Script vs Miracuves Platform
Three routes to your own transfer brand. Where they split is ownership, corridor handling and how the compliance team gets to work.
| What decides it | Rented or hosted platform | Miracuves platform | One-time payments script |
|---|---|---|---|
| How you pay | A setup fee, then monthly or per-transaction charges | $12,999 once, with no per-transfer fee to us | A single purchase, often license-checked |
| Who holds the code | The vendor, on the vendor's servers | You, complete and unencrypted, with no license callback | You, though frequently partly encrypted |
| Customer records | Stored with the vendor | In your own database, on your cloud | On your server |
| Corridors | Added when the vendor's roadmap gets there | Each one configured with its own rail, fee logic and rules | Usually one rail, often SWIFT, for every route |
| FX pricing | Set within the vendor's limits | Your spread, shown to the sender before confirming | A rate table someone edits by hand |
| Verification | The vendor's workflows; your license is still required | KYC and KYB queues with verification rules and an audit trail | Basic KYC at best, rarely KYB |
| Monitoring | Whatever the plan tier includes | Real-time review queue that can hold a transfer | Reports pulled after the money has gone |
| Business tools | Often reserved for higher tiers | Invoicing, payroll, bulk payouts and sign-off chains | Send-only in most cases |
| Partner access | Limited to what the vendor exposes | APIs, webhooks, OAuth and scoped keys in the base build | No API, or one nobody documented |
| Licenses and partners | Yours | Yours | Yours |
Look at the last row before any other. No route in this table gives you permission to move money: licenses, payout partners and pre-funded liquidity are yours on all three. What changes is who keeps the code and the records, and whether a new corridor is a setting or a rebuild.
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 sender sees the price first
The rate engine takes the feed you choose, adds your spread and shows the result with the fee before anyone taps confirm. Senders who abandon their bank usually do so because they learned the rate too late, so showing it up front is the core of what you sell.
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.
A reviewer decides, and the decision is kept
Held transfers appear in the monitoring queue, where compliance staff approve, reject or escalate them and the audit trail records who did what. That reviewer sits in a separate role on purpose, away from the people keeping customers happy.
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 the base build because a money transfer operator gets hurt in a specific way without it.
| Capability | What goes wrong without it |
|---|---|
| A rail setting per corridor | Pushing every route over one expensive rail eats the margin. Picking the cheapest rail that still meets each route's speed needs the corridor to exist as its own record, not a country dropdown. |
| Rate and fee shown before confirming | A sender who sees the true cost only after paying feels misled and leaves. Without an up-front quote there is little reason to switch from a bank. |
| Spread set from the console | The spread is usually your biggest earner and it rarely matches across routes. If it lives in code, every price change waits for a release. |
| KYB next to KYC | Companies tend to send larger and more often, and checking a company is a different job from checking a person. With KYC alone you turn them away. |
| Checks before settlement | A held transfer costs the sender a short wait. A suspicious transfer that has already landed abroad can cost far more, and often cannot be reversed. |
| A live review queue | A report read the next morning arrives too late to act on. A queue that can hold a transfer is the kind of monitoring supervisors usually expect. |
| A separate compliance role | The person judging a flagged payment should not be the one under pressure to please that customer. Splitting the roles is a control, not paperwork. |
| Payment links and requests | Businesses need money coming in as well as going out. A platform that only sends meets half of what they ask for. |
| Payroll and bulk payouts | A company paying dozens of contractors abroad will not key them in one at a time. Batch upload with sign-off is the reason it signs up. |
| Revenue split by corridor | On thin, route-specific margins a single blended total hides the routes that lose money every month. |
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.
What Is Not Included in the Base Package
Every feature above comes with the $12,999 build. The items below are either add-ons or yours to arrange, and in money transfer that second group decides whether you are allowed to open at all.
Add-on scope, or yours to arrange
- Money transmitter, e-money or payment licensesMoney 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 partnersConnectors 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 fundsPre-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; Miracuves never holds customer funds.
- Named KYC, sanctions and monitoring vendorsThe queues and hooks ship. Wiring in the specific identity, sanctions-screening or monitoring provider your license calls for is integrated to scope and quoted separately.
- Your compliance program and staffThe 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.
- Hardening for live moneyYou start from working code that is hardened around your own deployment before launch, including the edge protection, rather than a turnkey production system.
- Advanced modules and multi-brandForward contracts, hedging tools, crypto and L2 routing, per-corridor rule packs and running several brands are add-ons. One installation runs one operator brand. Enterprise rollouts take 15+ days.
- PCI DSS, ISO 27001 and SOC 2No certificate is held and none is claimed. Controls are built to OWASP ASVS 5.0.0 with a control map to PCI DSS and ISO 27001, but certification is issued to the operating entity after its own audit.
Licenses and payout partners are the two that shape your product. A corridor you have no right or partner to serve cannot be fixed in configuration, so map them first and features second.
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.
Frequently Asked Questions
How does the platform handle different corridors?
Does the sender see the exchange rate before paying?
Can businesses and freelancers use it, not only individual senders?
When does screening happen, and who provides it?
Do I need a money transmitter license to run it?
Do payout rails and live FX work out of the box?
Send a transfer that breaks a rule
Ask for that demo. Watch the transfer stop in the queue, sign in as compliance to clear it, and read the record it leaves.
Explore White Label Remittance Software
Own the code, the corridors and the customer records.
Multi-currency wallets, an FX rate engine, corridor rules, KYC, KYB and AML queues and an operator console, deployed on your cloud in six days, with the licenses and partners kept in your hands.
Talk to Us →Miracuves is an independent software development company. 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.
We supply software, not permission to operate. Obtaining the money transmitter, e-money or payment licenses on both ends of every corridor you serve, or operating under a licensed partner, is your responsibility, as are your correspondent and payout partners, safeguarding of customer funds, KYC, AML and sanctions screening, and reporting to each regulator. We do not advise on any of it.
The entire design and codebase is built by our own team. The product contains no code, design, graphics, or content originating from any third-party money transfer website or application. All third-party names and marks belong to their respective owners.
