Skip to content
/
Public Keys

Blu Penguin Merchant API v1 (v1)

Please find complete documentation from https://docs.transaction-monitor.io/.

Download OpenAPI description
blupenguin_openapi_v1.json
blupenguin_openapi_v1.yaml
Languages
Servers
Mock server
https://docs.transaction-monitor.io/_mock/blupenguin_openapi_v1/
Blu Penguin Merchant API sandbox
https://api.sandbox.transaction-monitor.io/
Blu Penguin Merchant API production
https://api.transaction-monitor.io/

Payouts

OperationsWebhooks

Deposits

OperationsWebhooks

Refunds

OperationsWebhooks

Payment Page

Operations

Wallet balances

Operations

Toolkit

Operations

Predict Correspondent

Request

Security
bearerAuth
Bodyapplication/jsonrequired
msisdnstring(FlexibleMsisdnValue)required

The phone number (MSISDN) to predict the correspondent of. Must contain the country code.

The input will be sanitized by:

  • removing the leading + sign
  • removing all whitespace
  • removing non-numeric characters
Example: "+260 763-456789"
curl -i -X POST \
  https://docs.transaction-monitor.io/_mock/blupenguin_openapi_v1/v1/predict-correspondent \
  -H 'Authorization: Bearer <YOUR_JWT_HERE>' \
  -H 'Content-Type: application/json' \
  -d '{
    "msisdn": "+260 763-456789"
  }'

Responses

Correspondent prediction was successful

Bodyapplication/json
countrystring(Country)required

The country in which the MMO operates.

Format is ISO 3166-1 alpha-3, three character country code in upper case. Read more from Wikipedia.

Example: "ZMB"
operatorstringrequired

The name of the MMO associated with the specified MSISDN.

Example: "MTN"
correspondentstring(Correspondent)required

The correspondent code refers to the specific MMO that the specified phone number (MSISDN) has an active mobile money wallet with.

You can find all the supported correspondents listed here.

The active configuration endpoint provides the list of correspondents configured for your account.

You can use the predict correspondent enpoint to predict the correct correspondent to use based on the phone number (MSISDN).

Example: "MTN_MOMO_ZMB"
msisdnstring(PredictedMsisdnValue)required

The correctly formatted phone number (MSISDN) from your original request that is in a valid format for the rest of the Blu Penguin Merchant API.

Example: "260763456789"
Response
application/json
{
  "country": "ZMB",
  "operator": "MTN",
  "correspondent": "MTN_MOMO_ZMB",
  "msisdn": "260763456789"
}

Public Keys

Request

Security
bearerAuth
curl -i -X GET \
  https://docs.transaction-monitor.io/_mock/blupenguin_openapi_v1/public-key/http \
  -H 'Authorization: Bearer <YOUR_JWT_HERE>'

Responses

If a request has been processed by Blu Penguin successfully.

Bodyapplication/jsonArray [
idstringrequired

The ID of the public key.

keystringrequired

The public key to use when verifying the signature in a callback sent by Blu Penguin.

]
Response
application/json
[
  {
    "id": "HTTP_EC_P256_KEY:1",
    "key": "-----BEGIN PUBLIC KEY-----\nMFkwEwYHKoZIzj0CAQYIKoZIzj0DAQcDQgAEYZe9jhnaZKw9ykMBe2IwRg6AgVMx\n2JRE3RMIdf4YazZTaQaUO19uDI5UO0QsTG699UeI+emd63/GY1PyOpf1rw==\n-----END PUBLIC KEY-----\n"
  }
]