Why we built Khlas pay and what we want payments to feel like

Khlas pay didn't start in a boardroom. It started behind the till of a small shop in Morocco, where one of our co-founders watched a customer abandon a sale because the card terminal couldn't connect again.

The problem we kept hearing

Over six months we sat with bakers, software studios, online resellers and salon owners. The complaints rhymed: opaque percentage fees, settlement delays that hurt cash flow, and customer support lines that felt designed to discourage you from calling.

A different default

Khlas pay treats instant bank transfer as the default, not the alternative. The money moves directly between accounts, the price per transaction is flat, and the merchant sees the funds before the customer leaves the page or the counter.

What comes next

Over the coming months we'll roll out plugins for more storefronts, deeper reconciliation tools, and a payout API that lets you move money out as easily as you move it in. If you'd like a closer look, our team is one demo booking away.

Previous
Previous

A developer's tour of the Khlaspay REST API

Next
Next

Five Reasons Why Moroccan Businesses Lose Customers At Checkout