Why I built Remitz
I have spent fifteen years in remittance — building, integrating and running the systems that move money across borders. Long enough to have seen the same thing happen to a lot of good operators.
They get authorised. They have the licence, the capital, the compliance officer, the corridors they know better than anyone. And then the technology becomes the thing that decides whether the business works. Either they spend two years and a fortune building a platform, or they rent one from a vendor who wants to sit between them and their own customers — holding the provider relationships, owning the rails, and quietly becoming impossible to leave.
I started Remitz in 2020 because there was a third option and nobody was selling it.
Your licence, your providers
Remitz gives you the platform. You keep everything else.
You hold the authorisation. Remitz is not authorised or regulated by the FCA, and it does not need to be — supplying software is not a regulated activity. Your permission is yours, and no part of your regulatory standing depends on us.
You contract your own providers. Payout, banking, FX, identity verification — you sign those agreements directly, on your commercial terms. We integrate them. We do not resell them, and we do not take a margin on your payments.
We never touch client money. Funds move between your accounts and your providers'. Safeguarding is yours, which is exactly where the Payment Services Regulations put it.
That model is less profitable for us than the alternative. It is also the only version I would have wanted to buy.
About the company behind Remitz
Remitz is a trading name of Kreativ Web Solutions Limited (CRN 12691280), incorporated in England and Wales in 2020. Kreativ builds software for more than one industry, so if you look us up you will find work outside payments. I would rather say that here than have you discover it in a footer.
What it means in practice: Remitz is built by an engineering company, not a payments consultancy that outsourced its platform. The people who wrote the code are the people who answer when something breaks.
