Fuliza Is Eating Your E-Commerce Profits: How to Block Risky Payment Methods Without Losing Good Customers

The Double-Edged Overdraft

Fuliza M-Pesa is a lifesaver for millions of Kenyans who need a small bridge to pay for goods. But for e-commerce merchants, Fuliza-funded transactions carry an elevated risk of reversal. When a customer's overdraft limit is maxed out, or they fail to repay, Safaricom can claw back the payment from your till—sometimes days after you've already shipped the product.

This is a delicate problem. You don't want to block Fuliza entirely, because many good, loyal customers rely on it. But you also can't absorb an open-ended reversal risk. Here's the Stonehenge Digital approach to fine-tuning your risk tolerance.

How to Detect a Fuliza Transaction at the API Level

The Safaricom Daraja API does not explicitly flag an STK Push as "Fuliza-funded." However, there are proxy signals you can use:

1. Transaction Metadata Analysis: Some M-Pesa callback data includes an "AccountReference" or "TransactionType" that indirectly indicates the funding source. You need to work with a developer who understands the undocumented fields.
2. Post-Transaction Bulk Query: After payment, you can periodically query the Safaricom Transaction Status API. In some cases, reversals are flagged as "ReversalPending" within a short window. You can programmatically hold the order for 1 hour if this flag exists.
3. Customer Behavior Pattern: Frequent small reversals from a specific phone number or a specific user agent? Your system can assign a "risk score" to that customer and automatically flag their next order for manual verification.

The Selective Block Strategy

Instead of blocking all Fuliza transactions, you implement conditional risk management:

• Low-Risk Orders (KES <1,500, returning customers with good history): Allow Fuliza. The reversal risk is modest, and the customer relationship is valuable.
• Medium-Risk Orders (KES 1,500 - 10,000, new customers): Add a "M-Pesa STK Push (Standard)" option, but also offer a "M-Pesa Express Checkout" or "Lipa Na M-Pesa B2C" as an alternative that encourages upfront settlement. You can also add a small notice: "For orders over KES 5,000, we may require a 2-hour settlement period before dispatch."
• High-Risk Orders (KES 10,000+, or flagged accounts): Disable STK Push entirely and require a direct bank transfer or a Pesalink payment. Or, use a payment gateway that offers card payments with 3D Secure (which eliminates chargeback risk from issuer fraud).

The Communication Challenge

Never say "We don't accept Fuliza." That alienates customers. Instead, phrase it as "For your security, we require an additional verification step for larger orders." Shift the narrative to protection, not restriction.

Fuliza risk can be managed, not eliminated. With smart API integration, you can minimize reversals while preserving the customer experience.

I Need Fraud-Reduced M-Pesa Integration →