Who These Deployment Options Are Built For
Evaluating multiple vendors before deciding? See the White-Label International Remittance Providers 2026 guide for an eight-criterion evaluation framework, and the remittance management software guide for the processing, settlement and reconciliation side.
Consider Enterprise when standard-plan scope does not cover your integration, infrastructure or operational needs. Review the requirements before choosing a deployment model:
- Tier-1 MTOs with complex operational or integration requirements
- Bank fintech arms running regulated remittance as a discrete business line under their banking group's risk framework
- Established MTOs scaling internationally who need multi-country operations, FX treasury, and regulatory reporting across jurisdictions
- Fintech groups that require data-residency control, dedicated-tenant isolation, or regulatory separation from other customers
- Agent-heavy networks requiring centrally managed agent, commission, settlement and compliance workflows, validated against the proposed network scope
What You Get That the Standard Plans Do Not
Enterprise is an agreed implementation scope with specific infrastructure, service and commercial terms—not a promise that every requested feature is already included.
Dedicated or Isolated Infrastructure
Enterprise infrastructure is scoped around isolation, data-location and operational requirements. Confirm hosting, backups, support access, encryption, retention and responsibility boundaries for the proposed deployment in writing.
Enterprise SLA
Enterprise includes a written SLA. Availability targets, response times, monitoring coverage, escalation, service credits if agreed, and support contacts must be specified in your contract. This page does not promise standard response targets.
Custom Integration Support
Bring your banking, compliance, reporting, CRM and accounting integration requirements to scoping. Supported interfaces, data flows, security, testing and any custom development are confirmed before quotation; inclusion is not automatic.
Deeper White-Label Control
Agree white-label scope for domains, app-store publishing, communications, receipts and staff interfaces. Bespoke interface work and additional publishing support may require a separate quotation.
Regulatory and Audit Support
Prepare a technology due-diligence pack with your team. Agree the documentation and assistance required:
- Architecture and data-flow documentation for your vendor files
- Security questionnaire responses — agree questionnaire scope and supporting evidence with your team
- Audit support — agree platform walkthroughs and audit assistance in the service scope
- Incident notification — agree notification triggers, recipients and timing in your contract
Security and Compliance Posture
Remitz is software. Your firm holds the authorisation and the regulatory obligations — our role is to supply the technology, while your reviewers assess the proposed deployment against your requirements.
Deployment controls to verify
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.
Use the platform and security review to prepare your questions. The public status page is a monitoring reference, not proof of every component or an uptime commitment.
Supporting your obligations
Keep technology-provider oversight with your firm. Request architecture, data flows, access-control evidence, recovery arrangements and exit provisions for your assessment.
No ISO 27001 certification is claimed here. Request current security-assessment and penetration-testing evidence and confirm any gaps before committing.
Safeguarding of customer funds
Safeguarding is your obligation, not ours. Remitz does not hold customer funds or provide safeguarding accounts. You arrange appropriate accounts and safeguarding with your providers. Software failure can still disrupt operations, so continuity and recovery planning remain important.
What to validate: the ledger, provider balances, settlement records, reports and audit exports available in your implementation. Your finance team must establish whether these records support its reconciliation process.
What it does not do: Remitz does not currently provide a purpose-built safeguarding reconciliation module or automated safeguarding attestation reporting. If your permission requires daily safeguarding reconciliation, that process sits with your finance function, using validated records and appropriate controls.
Enterprise Compliance Requirements
Compliance technology supports your programme; it does not replace it. Validate the workflows and provider coverage needed for your operation:
- KYC, sanctions and PEP checks through your chosen providers, including coverage and refresh arrangements.
- Transaction-monitoring rules, review holds and escalation responsibilities.
- Enhanced due diligence, risk reviews and available evidence records.
- Reports and exports your team needs, with filing and regulatory decisions remaining your responsibility.
Deployment Models
| Model | Best For | Trade-offs |
|---|---|---|
| Multi-Tenant SaaS | Scale-up and established MTOs | Shared infrastructure; confirm suitability, scope and service terms |
| Dedicated Tenant | Tier-1 MTOs, banks, regulated groups | Confirm tenant isolation, configuration and acceptance evidence |
| Fully Dedicated Deployment | Data-residency-sensitive operators, very large banks | Confirm infrastructure boundaries, responsibilities, cost and schedule |
Self-Hosted + Source Code
Self-Hosted + Source Code is quoted individually. Run the platform on your own hosting with source code access; agree licence rights, deployment and support in writing. Scope is driven by:
- Annual transaction volume and peak throughput
- Deployment model (multi-tenant, dedicated tenant, fully dedicated)
- Number of corridors and payout-partner configurations
- Custom integration scope (internal banking, BI, CRM, compliance tools)
- Support and SLA tier
- Contract duration, renewal and exit terms
Confirm all Remitz fees and service terms in the quotation. Provider charges are paid separately under your own contracts.
For pricing context across all tiers, see the pricing page.
Ask about relevant customer references during evaluation. Any introduction or disclosure requires the customer's permission.
The Evaluation Process
Agree an evaluation schedule around your decision-makers, evidence needs and technical scope:
- Discovery call — your profile, authorisation stage, corridors, volume projections, deployment preferences
- Scoping workshop — architectural fit, integration scope, compliance alignment
- Security and compliance due diligence — we complete your questionnaires and walk your team through the platform under NDA
- Commercial scoping — tailored pricing proposal, SLA, and contract structure
- Technical proof-of-concept (optional) — in your sandbox before contract
- Contract and onboarding plan
Start the Conversation
Enterprise engagements start with a scoping call. The quickest route is to book a 15-minute call and mention your enterprise profile — or explore the sandbox first. We will discuss the information needed to scope your requirements.