Roadmap & What's Not Here

This page exists because it's worse to publish confident-looking documentation for a method that doesn't exist than to just say so plainly. Everything below is genuinely absent from @lumierelabs/daraja's current source not renamed, not hiding under a different method name.

Not implemented in the current version

General B2C Payment Request (CommandID: "BusinessPayment" / "SalaryPayment" / "PromotionPayment" disbursing to a customer MSISDN) what's actually shipped is B2C Account Top Up, which moves funds between your own organization's accounts, not out to a customer. - General B2B Payment Request (moving money from your shortcode to another business's shortcode) what's shipped is B2B Hakikisha, a name/tariff lookup only. It doesn't move money. - Account Balance (CommandID: "AccountBalance") querying your own shortcode's available balance. - Transaction Status (CommandID: "TransactionStatusQuery") checking the status of a previously initiated B2C/B2B transaction by TransactionID. - Reversal (CommandID: "TransactionReversal") reversing a completed transaction.

If your integration needs any of these today, you'll need to call Daraja directly for that specific flow (they follow the same OAuth Bearer pattern as everything else this SDK wraps see Authentication for the token lifecycle you'd replicate) or track the package's changelog for when they land.

What is implemented

For contrast, everything documented elsewhere in these docs is real, tested, working code in the current version:

If you're contributing to @lumierelabs/daraja and want to close one of the gaps above, the existing endpoint clients (particularly B2C Account Top Up, which already handles the SecurityCredential/Initiator pattern that Account Balance, Transaction Status, and Reversal all also need) are the closest reference implementation to follow for request validation style and error codes.

Roadmap & What's Not Here

What is implemented

On this page