Preparing Your M-Pesa Merchant Setup for Billing

WayaDesk / M-Pesa payments

Merchant setup determines how the internet business receives and identifies payments. Before integration, establish who controls the receiving account and which provider configuration is authorised for the intended payment workflow.

Start with the receiving account

Confirm the business payment destination and the account-reference rules. A phone number advertised for support is not automatically the receiving account. Keep licence purchases from WayaDesk distinct from payments your own customers make for internet service.

Prepare the integration privately

The application’s payment connection needs the appropriate configured credentials and public endpoint arrangement. Store secrets through the supported private settings process. Do not paste API secrets, passkeys or customer PINs into public pages, example screenshots or ordinary sales enquiries.

• Confirm the account and intended transaction flow with its authorised administrator.
• Prepare the required HTTPS customer and callback deployment.
• Agree a controlled live payment test with the actual operator.

Understand a readiness check

LinkDesk’s guided Daraja OAuth check is a no-charge configuration check. It does not send a customer payment prompt or prove that a completed live transaction will activate access. A full acceptance test must exercise the stages that the business intends to use.

Record what was verified

Keep a setup record containing non-secret identifiers, the responsible person and the completed acceptance checks. If another site already uses the merchant account, preserve its working arrangements while evaluating the new integration. Existing success elsewhere is useful context, not proof that this installation has been connected.