Please find complete documentation from https://docs.transaction-monitor.io/.
- Predict Correspondent
Blu Penguin Merchant API v1 (v1)
- Mock serverhttps://docs.transaction-monitor.io/_mock/blupenguin_openapi_v1/active-conf
- Blu Penguin Merchant API sandboxhttps://api.sandbox.transaction-monitor.io/active-conf
- Blu Penguin Merchant API productionhttps://api.transaction-monitor.io/active-conf
- curl
- JavaScript
- Node.js
- Python
- Java
- C#
- PHP
- Go
- Ruby
- R
- Payload
curl -i -X GET \
https://docs.transaction-monitor.io/_mock/blupenguin_openapi_v1/active-conf \
-H 'Authorization: Bearer <YOUR_JWT_HERE>'If a request has been processed by Blu Penguin successfully.
Your unique alphanumeric ID in the Blu Penguin platform.
Your company name as configured in the Blu Penguin platform.
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.
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).
The currency in which the amount is specified.
Format must be the ISO 4217 three character currency code in upper case. Read more from Wikipedia.
You can find all the supported currencies that the specific correspondent supports from here.
The active configuration endpoint provides the list of correspondents configured for your account together with the currencies.
The name of the company that is shown to the customer on the SMS receipt.
{ "merchantId": "MERCHANT_INC", "merchantName": "Merchant Inc.", "countries": [ { … }, { … } ] }
- Mock serverhttps://docs.transaction-monitor.io/_mock/blupenguin_openapi_v1/v1/predict-correspondent
- Blu Penguin Merchant API sandboxhttps://api.sandbox.transaction-monitor.io/v1/predict-correspondent
- Blu Penguin Merchant API productionhttps://api.transaction-monitor.io/v1/predict-correspondent
- curl
- JavaScript
- Node.js
- Python
- Java
- C#
- PHP
- Go
- Ruby
- R
- Payload
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"
}'Correspondent prediction was successful
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.
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).
{ "country": "ZMB", "operator": "MTN", "correspondent": "MTN_MOMO_ZMB", "msisdn": "260763456789" }
- Mock serverhttps://docs.transaction-monitor.io/_mock/blupenguin_openapi_v1/public-key/http
- Blu Penguin Merchant API sandboxhttps://api.sandbox.transaction-monitor.io/public-key/http
- Blu Penguin Merchant API productionhttps://api.transaction-monitor.io/public-key/http
- curl
- JavaScript
- Node.js
- Python
- Java
- C#
- PHP
- Go
- Ruby
- R
- Payload
curl -i -X GET \
https://docs.transaction-monitor.io/_mock/blupenguin_openapi_v1/public-key/http \
-H 'Authorization: Bearer <YOUR_JWT_HERE>'[ { "id": "HTTP_EC_P256_KEY:1", "key": "-----BEGIN PUBLIC KEY-----\nMFkwEwYHKoZIzj0CAQYIKoZIzj0DAQcDQgAEYZe9jhnaZKw9ykMBe2IwRg6AgVMx\n2JRE3RMIdf4YazZTaQaUO19uDI5UO0QsTG699UeI+emd63/GY1PyOpf1rw==\n-----END PUBLIC KEY-----\n" } ]