Money Transfer Software FAQ — Your Questions Answered

No. Remitz is a technology provider. We provide the white-label software, the hosting and the integrations; you hold the FCA authorisation — or operate under an appropriate regulatory arrangement — and contract directly with your own payment, payout and KYC providers. This is deliberate: holding those relationships yourself is what keeps your pricing, your margins and your commercial terms your own.

Remitz supplies branded customer and back-office software for remittance operators, with plan-dependent mobile capability, agent workflows and provider connections. You retain your licence, accounts, funds and compliance programme. Agree modules and implementation work in your scope.

No. Remitz supplies supporting technology, not regulatory approval or a compliance programme. Agree identity checks, screening, monitoring, reviews and reports against the available workflows. Your team retains policies, decisions and regulatory submissions.

Typical implementation is 15–30 days once authorisation is in place and providers are ready with API credentials, subject to configuration and testing. The agreed schedule depends on your scope.

Remitz pricing is £79/month for the non-operational SPI applicant environment (no setup fee), £299/month plus £1,500 setup for Starter, and £799/month plus £2,000 setup for Growth. Enterprise pricing and setup are quoted. Third-party provider fees are separate. See the pricing page for scope and exclusions.

Growth includes iOS/Android capability at £799/month plus £2,000 setup. Confirm the build, supported devices, authentication, notifications, branding and publishing scope. Other-plan requirements and custom work are quoted; developer-account and provider fees are separate.

Methods depend on your contracted payment and payout services and the agreed connectors. Review card or bank funding separately from bank, mobile-wallet or cash-pickup payouts. Airtime top-up is a separate service, not a remittance payout method.

Bring your verification and screening providers and required checks to scoping. Confirm connector compatibility, sanctions/PEP coverage, monitoring and provider fees. Additional services or providers may require development.

Yes — that is how Remitz is designed to work. You choose your providers and hold the commercial relationship with each of them. Existing compatible connectors can reduce implementation work. Confirm supported services, credentials and testing during scoping; new providers require feasibility review and may involve separately quoted development.

Yes. You arrange payout, KYC, payment, SMS, email and other required provider accounts and contracts, then supply credentials. Remitz connects supported services and does not provide those accounts or hold customer funds.

Agree the required currencies, margins, fees and providers for each corridor. Starter includes up to 5 corridors; Growth has no software-plan corridor limit. Provider coverage, permissions, new services and development still need confirmation.

Agent-network functionality is scoped with Enterprise. Review hierarchy, transactions, commissions, pre-funding records, permissions and reports against your needs. Ledger balances do not supply agent bank accounts.

For managed deployments, Remitz provides hosting and technical maintenance under the agreed service terms. Confirm monitoring, backup and restore arrangements, update windows and responsibilities in the contract. Self-hosted requirements are scoped separately.

Bring expected transaction volumes and peak-load requirements to scoping. Capacity, load testing, infrastructure changes and any associated fees are agreed for your deployment; there is no unlimited-capacity assurance.

Remitz provides founder-led implementation and technical support. Agree channels, coverage, escalation and response commitments in your service terms. Enterprise service levels are specified in writing.

Security requirements are assessed for the proposed deployment. Ask for evidence of encryption, administrative MFA, role permissions, audit coverage and retention, data locations, monitoring and recovery tests. Confirm supported controls and service levels in writing rather than assuming every deployment has the same configuration. See the platform and security review.

No. Remitz does not hold customer funds or supply safeguarding accounts. Your firm arranges appropriate accounts, controls and reconciliation. Validate available ledger records and exports with your finance team; they are not a purpose-built safeguarding reconciliation or attestation service. Confirm requirements for your permission with the regulator and advisers.

Continuity needs a documented plan covering service interruption, recovery, data export and exit assistance. Raise self-hosting or source-code requirements during scoping; availability, licence rights and support responsibilities require a separate written agreement.

Discuss self-hosting and source-code requirements during Enterprise scoping. Availability, licensing, deployment work, ongoing support and responsibility for patching, monitoring, backups and recovery must be agreed in writing; they are not standard-plan inclusions.