Why none of this is behind a form
The person who needs a security summary is usually a compliance officer building a vendor file, not a buyer looking for a sales call. Asking them for an email address before they can read it helps us and hinders them. The linked overviews are available to read. They are not a complete due-diligence pack or proof that a particular deployment meets your requirements.
For evaluating the platform
- Implementation guide — the ten steps from demo to go-live, who owns each one, and what actually determines your launch date.
- Platform walkthrough — eleven customer-web and back-office examples, with limitations explained beside the screenshots.
- Feature guide — what the platform does, module by module.
- Pricing and total cost of ownership — all four tiers, setup fees, and a three-year cost comparison.
For security and compliance review
- Architecture and security overview — how the platform is built, where it runs, the controls to verify, and what Remitz deliberately does not do.
- Live status page — the monitored service view, not a guarantee for every platform component.
- Enterprise deployment and SLA terms — hosting scope, support commitments and technical evidence to agree.
- Frequently asked questions — the compliance, security and continuity answers in one place.
For choosing your providers
- Integration catalogue — provider options and the connector scope to validate.
- Connector detail pages — provider relationships, credentials and implementation questions.
- Vendor evaluation scorecard — seven criteria, what good looks like, and what to ask any vendor including us.
Background reading
- Launching a money transfer business in the UK
- Choosing a white-label provider — an eight-criterion framework and a ten-question RFI set you can send to any vendor.
- All articles — FCA compliance, licensing, agent networks and build-versus-buy.
Need something that is not here?
If your due-diligence questionnaire asks for something this library does not cover, ask us directly and we will answer it in writing. A written answer is faster than a meeting, and it is what your file needs anyway.
