Card Payments, Done Carefully.
EupPay is in active development — a focused, honest payment integration for Kenyan merchants. We're being open about where it is and what's still being built.
At a Glance
- Domain
- euppay.com
- Category
- fintech
- Industry
- payments
Capterra and Trustpilot are full of Kenyan merchant complaints about the existing card gateways. "They take longer time to settle payment which affects business." "They interfered directly with my clients — asking my client for their card details and bank statements was emotionally draining." One DPO reviewer described chasing $25,000+ for over 60 days with the company "finding several reasons not to make the payment". KYC dies silently — IDs and business documents go in, rejection emails come back without explanation.
EupPay is a payments project we're building actively, focused on giving Kenyan merchants a clean way to accept card payments online. The hosted checkout flow, the redirect, the success and failure handling — that's the part we're putting together carefully. We're being honest: this is not yet a live, multi-rail processor. There are still questions we're waiting on from upstream providers (production base URL, webhook signature verification, the full refund spec).
If you're a merchant looking for card-on-file or M-Pesa orchestration today, we're not the answer yet — talk to us about the Laravel Payment Kit instead. If you want to be involved early — share your requirements, weigh in on the merchant dashboard, or be one of the first integrations — that's the conversation we're having now.
What's broken today
- "They're holding funds hostage with endless excuses about pending confirmation" — typical Capterra/Trustpilot complaint
- Settlement takes a week, sometimes 60+ days, with hidden per-transaction surcharges on top of MDR
- Pesapal contacting your customers directly during disputes, asking for their bank statements
- KYC dies silently — IDs and documents go in, rejections come back, no human to talk to
- Card checkout converts badly compared to M-Pesa STK Push — most Kenyan buyers click M-Pesa in seconds and abandon at the card form
- The Flutterwave 2022 ARA freeze ($55M across 62 accounts) makes founders wary of putting all volume through one aggregator
How EupPay fixes it
- A focused integration aimed at one card flow done well, not a kitchen-sink platform
- Open about what's working, what's coming, and what's still unanswered upstream
- Built by a team that owns the support relationship — when something breaks, you talk to a person, not a portal
- Designed to sit next to M-Pesa (via the Laravel Payment Kit), not compete with it
Everything you need, built in
Hosted checkout
Visa and Mastercard accepted on a hosted checkout page — your servers never touch raw card data.
Clean callback handling
Success and failure both routed cleanly back to your application; no silent edge cases.
Transaction status visibility
Look up any transaction by reference and see exactly where it stands.
Merchant dashboard (in development)
Onboarding, KYC review, and transaction monitoring — being built; not yet live.
Refunds and voids (in development)
Confirming the upstream API spec before we ship this. We won't claim it works until it actually works.
What you get out of it
- A card payment integration that won't surprise you on launch day
- A team that says what's done and what isn't
- Card on the side, M-Pesa as the main rail — not the other way around
Who it's for
- Kenyan merchants needing reliable Visa and Mastercard acceptance online for diaspora and B2B buyers
- Teams already burned by aggregators holding settlements and want a quieter operator
- SaaS billing for African customers where cards still matter for the subset who don't have M-Pesa
Common questions
Want EupPay for your business?
Webzilla Creators ships and supports EupPay for Kenyan and pan-African organisations.