Your operation
Branches, staff access, expected usage and customer channels.
Your requirements shape the implementation. Start with the branches, markets and providers you want to connect.
A product discussion gives us the context to prepare a relevant quote.
Discuss pricing Explore the platform ↗Branches, staff access, expected usage and customer channels.
Countries, currencies, delivery methods and fee configuration.
Collection, KYC and payout integrations, including any custom API work.
Data migration, team training and the support requirements you bring.
Pricing follows an agreed scope; it is not inferred from an unsupported package or universal corridor fee.
Outline your branches, countries, currencies, customer channels and expected usage.
Identify collection, KYC and payout integrations, migration needs, training and support requirements.
Review responsibilities, assumptions and the implementation scope before pricing is prepared.
| Input | Why it matters | What it informs |
|---|---|---|
| Branches and users | Shows the operating structure and access model | Configuration and rollout scope |
| Corridors and methods | Defines route-specific rules and delivery choices | Configuration and validation work |
| Selected providers | Establishes API, onboarding and credential dependencies | Integration scope and responsibilities |
More to discuss? Bring it to your demo.
The implementation scope depends on your operating model and provider requirements. We establish that scope before preparing a quote.
Share your sending and receiving markets, currencies, number of branches, expected usage and preferred collection, KYC and payout providers. Include any migration, training or support requirements.
Provider services may have their own fees and onboarding requirements. We clarify the responsibilities and cost assumptions for your selected integrations during scoping.
We’ll start with the workflow, then work through the scope.