Payment integration
Let customers pay your KES invoices from their phone. They approve an M-Pesa prompt, and Invoice Crowd confirms the payment with M-Pesa before recording it.
From setup to paid
Connect your M-Pesa account once and every invoice can offer it. Each payment is confirmed with M-Pesa before it reaches your books.
Each business profile uses its own M-Pesa account, in Live or Sandbox mode.
Enter your consumer key, consumer secret, shortcode, pass key and transaction type, then choose Live or Sandbox. Secrets are saved securely and never shown again.
Customers pay into your own M-Pesa account, on your existing M-Pesa pricing. M-Pesa appears on invoices in Kenyan shillings (KES).
Customers see only the payment options that suit their invoice.
Your customer chooses M-Pesa on the invoice and approves the STK Push prompt on their phone. Invoice Crowd confirms the result with M-Pesa and applies it to that invoice.
If a response is slow to arrive, Invoice Crowd waits for M-Pesa's answer rather than sending a second prompt, so customers aren't asked to pay twice.
An invoice is marked paid once M-Pesa confirms the payment.
Invoice Crowd checks the result with M-Pesa and matches the checkout request, the invoice and the KES amount before marking the invoice paid.
Make a refund in your M-Pesa account, then record it with Refund on the invoice. The invoice, its credit note and your books stay in step.
At a glance
Get paid online, keep every payment matched to its invoice, and keep your books in step without extra work.
Customers approve an M-Pesa STK Push prompt on their phone, straight from the invoice.
M-Pesa appears on your invoices in Kenyan shillings.
A slow response never triggers a second prompt, so customers aren't asked to pay twice.
Add your consumer key, shortcode and pass key, choose Live or Sandbox, and you're ready to take payments.
An invoice is marked paid once M-Pesa confirms the payment for the exact KES amount.
Payments go to your own M-Pesa account, on your existing M-Pesa pricing.
Try the whole flow in Sandbox, then switch to Live when you're ready.
Each payment gets its own receipt PDF, attached to the customer's payment confirmation email.
If an invoice changes after checkout starts, the payment waits in Payments Needing Review for you to apply, keep as credit or refund.
Refund in your M-Pesa account, then record it with Refund on the invoice, so the invoice and your books agree.
Add a gateway fee for M-Pesa if you choose, shown to the customer as Gateway Fees on the invoice.
Switch on other gateways alongside M-Pesa and customers choose the one they prefer.
Questions
Yes. Customers pay your KES invoices by approving an M-Pesa STK Push prompt on their phone, and Invoice Crowd confirms the result with M-Pesa before recording the payment.
Your M-Pesa consumer key and consumer secret, shortcode, pass key and transaction type, plus a choice of Live or Sandbox mode. M-Pesa is included on paid plans; the free plan includes PayPal.
Your customer chooses M-Pesa on the invoice and receives an STK Push prompt on their phone. Once they approve it, Invoice Crowd confirms the payment with M-Pesa and records it against the invoice.
Invoice Crowd checks the result with M-Pesa and matches the checkout request, the invoice and the KES amount before marking the invoice paid. If a confirmed payment can't be applied, for example because the balance changed, it waits in Payments Needing Review for you to decide.
M-Pesa sets its transaction fees, exchange costs and payout timing under your M-Pesa agreement, separate from your Invoice Crowd plan. You can pass a processing fee on to customers with the gateway fee setting.
Make the refund in your M-Pesa account, then record it with Refund on the invoice in Invoice Crowd. The invoice, its credit note and your books stay in step.
Connect M-Pesa in Sandbox mode, pay a sample invoice, then switch to Live when you're ready.
