Vodacom M-Pesa (DRC)
VODACOM_MPESA collects through Vodacom’s M-Pesa Open API for the Democratic
Republic of the Congo: a customer-to-business request is pushed to the payer’s
M-Pesa wallet, and the payer approves it on their handset.
The backend country catalog offers it for the Democratic Republic of the
Congo (CD) only.
What the integration needs
Documented for support and upgrade planning, not as an instruction to set these another way.
Requests go to Vodacom’s production Open API host for DRC. There is no sandbox
switch — a session key is fetched, encrypted with the public key, and used to
authorize each request.
How a payment would complete
1
Session
Centipid Billing fetches a session key and encrypts it with the configured
public key.
2
Request
A customer-to-business payment is pushed to the payer’s normalized DRC
M-Pesa number for the merchant code.
3
Authorization
The payer approves the prompt on their handset.
4
Confirmation
Vodacom’s response description is recorded against the transaction, and the
payment settled from the outcome.
Troubleshooting
For the gateways that are configurable today, see
Payment gateways, and for their fields, the
credential reference.
