M-PESA casino payments Kenya: what payment teams should verify

Next research pages

Which M-PESA business rails are documented?

Safaricom documents several business channels: business-to-consumer, business-to-business, bulk payments and collection through a shortcode. These descriptions identify the types of business functionality presented in Safaricom's materials; they do not confirm that every rail is available to every business or that any rail supports gambling transactions.

Safaricom's Daraja API list includes customer-to-business, business-to-customer, transaction-query and account-balance functions. The list can help a technical or commercial team frame questions about collection, disbursement and transaction visibility. It should not be read as evidence that a specific operator has implemented any of these functions.

• B2C business channel
• B2B business channel
• Bulk payments
• Collection through a shortcode
• Customer-to-business API function
• Business-to-customer API function
• Transaction-query API function
• Account-balance API function

What Safaricom states about KYC and unlicensed gambling

Safaricom's M-PESA B2B terms state that account activation follows KYC vetting and the provision of required KYC documents. This is a statement about Safaricom's documented business-account process, not legal advice and not a finding about the status of any particular operator.

The same Safaricom B2B terms prohibit use connected to unlicensed gaming or unlicensed gambling. The supplied evidence does not identify which operators meet that condition, confirm a licence for any operator, or establish that a particular deposit, collection or payout route is available.

For a specific operator, teams should obtain and assess the operator's own business identity, payment arrangement and relevant licensing information through appropriate verification channels. This page does not infer those facts from general M-PESA documentation.

• Confirm what KYC documents Safaricom requires for the relevant business arrangement.
• Check how the proposed use is treated under the applicable Safaricom terms.
• Verify the specific operator separately rather than relying on general M-PESA channel documentation.
• Record unresolved acceptance, licensing and transaction-flow questions before implementation.

Questions to verify with a specific operator

General M-PESA documentation does not establish that a named casino or betting operator accepts M-PESA, supports a particular business rail, or offers a particular transaction type. Those points require operator-specific evidence and should not be inferred from the existence of B2C, B2B, collection or API documentation.

A payment, compliance or commercial review can ask the operator to identify the relevant M-PESA business arrangement, the transaction direction being offered and the entity responsible for the payment relationship. The review should also clarify how the operator addresses the unlicensed-gambling restriction stated in Safaricom's B2B terms.

Safaricom advises customers to keep their M-PESA PIN secret and verify suspicious requests. Teams documenting operational procedures should preserve that warning in user-facing and internal controls without requesting or exposing a customer's PIN.

• Which documented M-PESA business channel or API function is being used?
• Is the arrangement customer-to-business, business-to-customer, or another documented flow?
• What entity is the contracting business and what KYC process applies?
• What evidence supports the operator's eligibility under the relevant Safaricom terms?
• How are suspicious requests handled without disclosing an M-PESA PIN?

What this page does not establish

The supplied evidence does not establish fees, limits, processing speed, withdrawal support, operator acceptance, customer eligibility, licensing status or availability for a particular gambling business. It also does not establish that a general M-PESA business rail is a payment approval for gambling activity.

Accordingly, this page is a research aid rather than a recommendation or approval. A specific commercial decision should rely on current operator and provider documentation that addresses the exact entity, flow and intended use.