Why I'm writing this
The last of these was May. Two months on, the honest thing is to show the work rather than the roadmap. Same rule as always: shipped, in sandbox, with the reasoning — not a wishlist. Everything below runs on the sandbox today. There is still no production and no paying customers; production launch comes post-funding. What changed is how much of the platform is now real to use.
The headline
Four things shipped across June and July that widen what Danipa is — from a payments core into a set of businesses a merchant, an artist, or a person can actually run on.
1. Danipa Sites — a real website, not just a CMS
Danipa Content was a headless CMS. Danipa Sites turns it into a hosted website product. Pick from 15 industry templates (restaurant, salon, travel, fitness, law, couture, and more), set your colours, logo, and copy, and publish to your own address on danipa.com — all from the same dashboard you run payments in, no developer and no second login.
The architecture is the point: one renderer serves every tenant's site, chosen by hostname, with the whole site stored as data rather than code. Adding a site is a record and a domain — nothing to host or maintain, and a fix ships to everyone at once. Thirteen sample sites are live on the sandbox today. Billing is in Canadian dollars or Cedis over MoMo, on the same invoice as everything else. Details on /platforms/content.
2. Danipa Stage — an artists suite, with a Fan CRM they own
Musicians and creators got their own package: a site template, managed hosting, and — the piece that compounds — a Fan CRM they own. It's a new module inside the fintech service: an owned fan list, segments ("superfans by spend", "fans in Accra"), and broadcasts over email and SMS. The load-bearing decision was consent: a fan's consent is enforced at compose time, so an artist can't broadcast to someone who didn't opt in. Own the data, reuse the send layer.
The whole flow — public fan signup → segment → broadcast — is drivable from the merchant dashboard, and it's live on sandbox for our pilot artist.
3. Danipa Wellness — global, and yours
Every clinical thing we build — Health, Pharmacy, Agri — is Ghana-first, because regulated healthcare is country-specific. Wellness is deliberately the opposite: global. It's a consumer layer — a personal wellness log, goals, phone health sync on iOS and Android, and insights over time — available anywhere, with a companion mobile app.
The honest boundaries matter here: it doesn't diagnose or treat, and it never shares anything to a clinic on its own. When it counts, and only with your consent, it hands your picture to a clinician through a bridge that health-side rejects without an active consent on file. Self-care that connects to real care, on your say-so. See /platforms/wellness.
4. More ways for merchants to get paid — and settle up
Two merchant capabilities went from design to running on sandbox:
- Booking Inquiries — a full inquiry → quote → deposit → in-house contract
e-sign → earnings flow, for the businesses that sell an appointment or a booking rather than a shelf item. (The e-sign has an audit trail; it isn't an eIDAS-qualified signature, and we say so.)
- Co-owners on one account — bring a business partner onto a single account
instead of juggling separate logins. The ownership backend is live; the dashboard experience is still maturing, and we're honest about that too.
The polish work
Beyond the headliners, the two months went into making money movement real and the platform honest:
- Merchant refunds, end to end. Full and partial refunds through Stripe
Connect, gated behind step-up MFA, with a reason you pick from a list (a free-text reason used to trip Stripe's API — now it can't). We ran a real refund end-to-end on a sandbox charge and fixed three bugs the live run surfaced that tests hadn't.
- Paid modules that actually charge. Enabling a paid module now takes payment
at enablement and sets up a recurring subscription — a Stripe card for CAD, an MTN MoMo pre-approval mandate for GHS — verified moving test money on both rails. Free modules stay free.
- Content grew to 10 template packs, up from 5.
- Passkey enrolment in settings — you can register a local authenticator from
the dashboard instead of being forced through a QR dance.
- Notifications you can audit. Every send now lands in one central log, so the
admin view reflects what actually went out.
- We audited the website against our own code. Every public claim was checked
against origin/develop and the live sandbox, and anything the code didn't back got cut or corrected — then a second pass tried to disprove each fix. Honesty is a feature; we treat it like one.
What it all adds up to
A year ago Danipa was a payments integration. Today a merchant can run their storefront, their website, their bookings, and their billing on it; an artist can run their site and their fanbase; a person anywhere can run their wellness on it. Same identity, same ledger, same secure core underneath — and now two payment rails: MTN Mobile Money across Africa, and Stripe wherever Stripe is supported. (More on that in Two Rails, One API.)
It's all sandbox today, tested against real provider integrations before anything gets promoted. If you want to look inside, the architecture page walks the pillars; the platforms overview walks the eight. If you want to use it, the merchant sandbox and developer sandbox are open.