Software Savants

Case study

Mauritania's payment gateway

Moosyl is Mauritania's payment gateway: one integration for every major banking app. Software Savants built it, from the bank integrations and the SDKs to the merchant dashboard.

Visit moosyl.com

10K+

transactions processed

99.9%

uptime

6

banking apps

1 to 3 days

to settlement

The Moosyl merchant dashboard: revenue, completed payments, conversion rate, and transaction activity for a connected business

Six banks, six integrations, no documentation

Mauritania's economy runs on cash. As mobile banking apps like Bankily, Sedad, and Masrivi grew, businesses could see that their customers wanted to pay digitally. The problem was on the other side of the counter.

Every bank had built its own system, its own integration method, its own rules. A business that wanted to accept digital payments had to negotiate with each bank separately, build a separate integration for each one, and then maintain all of them. Banks were slow to respond. Documentation was scarce. No two integrations worked the same way.

Most businesses gave up. The ones that didn't spent months on what should have taken days.

We knew this because we lived it. We were building products for clients who needed to accept payments, and we hit every one of those walls ourselves.

One API in front of all of it

So that is what we built for Moosyl.

One gateway, six banking apps

Bankily, Masrivi, Sedad, BimBank, Click, and BCI Pay. Your customer pays with the app already on their phone. No new account, no card.

Five SDKs

Flutter, React Native, React, TypeScript, and Dart. The developer integrating you judges you in the first ten minutes, so the SDK surface matters more than the API surface.

Webhooks

Real-time payment notifications, so a merchant's system always reflects the true state.

Subscriptions and checkout sessions

Recurring billing and hosted checkout, not just one-off charges.

A sandbox

Test keys and a full test environment before anyone touches production.

A merchant dashboard

Payments, team, and revenue. No code required after setup.

Built to hold up

Building a gateway is one thing. Building one that holds up under real money is another. Payments are not a category that tolerates a bad week, so we engineered Moosyl for reliability from the start.

  • Handles 10,000+ transactions
  • 99.9% uptime on redundant systems we built in
  • Automatic settlement to merchant bank accounts in 1 to 3 business days
  • Bank-grade security on every transaction
  • Built to stay compliant with financial regulations

What this means if you're building payments

Most product studios have never shipped a single payment integration. We built the gateway underneath one, and every SDK on top of it.

We know what it takes to get a bank to answer. We know what settlement reconciliation looks like when it goes wrong. We know that the hard part of a payments product is not the happy path.

If you are building payment infrastructure, we have already made the mistakes.

Building something in payments?

If you need a team that has built payment infrastructure and shipped it, let's talk.