Overview
This node, named "M-Pesa Query Customer Name," is designed to query the name of a customer associated with a mobile money wallet (M-Pesa) using their MSISDN (mobile number). It is useful for confirming the identity of the customer before proceeding with transactions, helping to reduce errors and fraud. Typical use cases include verifying the recipient's name in payment workflows or validating customer details in financial services.
Properties
| Name | Meaning |
|---|---|
| Customer MSISDN | The mobile phone number (MSISDN) of the customer whose name you want to query (e.g., 258843330333). |
| Third Party Reference | A unique reference string from your system to track this specific transaction or query. |
| Service Provider Code | The shortcode of the business or service provider where funds will be credited (e.g., 171717). |
Output
The node outputs JSON data containing the queried customer name information associated with the provided MSISDN. This typically includes the customer's registered name as stored in the M-Pesa system. The output is structured as standard JSON under the json field of the output item. There is no binary data output.
Dependencies
- Requires an API key credential for authenticating requests to the M-Pesa API.
- The node makes HTTP GET requests to the M-Pesa endpoint
/ipg/v1x/queryCustomerName/. - The base URL and service provider code are expected to be configured via credentials.
- The request includes headers specifying content type and origin.
Troubleshooting
- Invalid or missing MSISDN: Ensure the MSISDN is correctly formatted and includes the country code without spaces or special characters.
- Authentication errors: Verify that the API key credential is valid and has the necessary permissions.
- Third Party Reference duplication: Each request should have a unique third party reference to avoid conflicts.
- Service Provider Code issues: Confirm that the service provider shortcode is correct and active.
- Network or API errors: Check network connectivity and that the M-Pesa API endpoint is reachable.
Common error messages may relate to invalid parameters, authentication failure, or rate limiting. Resolving these usually involves correcting input values, renewing credentials, or retrying after some time.
Links and References
- M-Pesa API Documentation (general reference; actual endpoint docs may vary)
- n8n documentation on HTTP Request Node for understanding API calls within n8n.