How a Remitz Launch Works — Demo to Go-Live
A launch is shared work: Remitz configures and tests the software; you arrange authorisation, providers and credentials. These ten steps show the responsibilities to agree before setting a date.
- Book a demo (us · 15 minutes)
You see the platform and get a straight answer on whether Remitz fits — from the founder, not a sales team. - Requirements discussion (us + you)
Corridors, authorisation status, expected volumes, target launch date — and which third-party providers you will need. - Commercial agreement (you)
Plan, setup fee and contract terms.
- Branding (us)
Branding across the channels and communications agreed for your plan, including mobile publishing where scoped. - Configuration (us)
Corridors, fees, FX margins, user roles, agent structure and commission rules, configured to how you actually operate.
- You provide API credentials (you + your providers)
Payout, KYC, payment gateway, SMS and email. Remitz does not supply these accounts — you hold the commercial relationship with each provider, and your credentials stay yours. - Integration configuration (us)
We configure supported provider connections using your credentials. New services or connectors require separate scoping, development where needed and testing.
- Testing (us + you)
Agree acceptance tests for enabled corridors, provider responses, review steps, failures and reconciliation records. - Training (us)
Your operations, compliance and finance teams, on the back office, reporting and agent management. - Go live (you)
First real transaction, under your own licence and your own brand.
What actually determines your launch date
Existing compatible integrations can reduce implementation work. Confirm supported services, any new development and the testing needed for your operation before agreeing a schedule.
Provider readiness is one dependency. Your providers control account approval and credential issuance. Internal decisions, migration, additional development and testing can also affect the schedule.
Typical implementation is 15–30 days once authorisation is in place and providers are ready with API credentials, subject to configuration and testing. Agree a schedule for your actual scope; it is not a promise of approval or third-party readiness.
Frequently Asked Questions
What would your timeline look like?
Bring your provider list, required workflows and intended launch date. We can identify the questions to resolve and the evidence needed for a realistic implementation plan.
