Market specifications

Do you want to know more information about Tanzania's market? Go to the Expand Your Reach in Africa’s eCommerce Market article.

Country reference

`country` code	`currency` code	`amount` decimals	`document` name	`document` format	`document` required?
`TZ`	`TZS`	2	National Identity Card	Unique 20 digit national ID number	Yes

Alternative Payment Method supported

`payment_method_id`	Name	`payment_method_type`	Allowed Flows	Logo
`MW` / All telecom companies `VC` / Vodacom	Mobile Money	`WALLET`	`DIRECT`

Alternative Payment Method

Mobile Money

Mobile Money is a widely used payment method in Africa that enables people to send and receive money through their mobile phones. Users need to register for an account, provide identification, and deposit money through authorized agents or channels.

Mobile Money platforms are operated mainly by telecommunications companies and they have enabled financial inclusion by providing banking services to unbanked or underbanked individuals.

Customize payment options

The payment method ID may vary based on the specific user experience you intend to provide.

Offer all telecom companies. To offer all available telecommunications options, complete "payment_method_id": "MW".
Provide a specific network. To specify a particular telecommunications company, input the corresponding ID. For example, if you intend to utilize the Vodacom network, use "payment_method_id": "VC".

📘
Choosing the right network option
To use a specific network feature effectively, make sure to know the user's telecommunications company. If you're unsure, use the generic one to prevent any potential misunderstandings so that all companies are supported.

To find all the available payment options, refer to the Alternative Payment Method supported section.

Capabilities

	Mobile Money
Max. expiration time supported	5 days
Notification delay	Depending on provider
Refunds	Yes
Flow	`DIRECT`
Supported wallets	Airtel, Tigo, mPesa, Vodacom, Zantel, Halopesa, Ezy-pesa, TTCL.

UX Flow

Flow might slightly differ depending on the provider.

Alternative flow

Request Parameters

Property	Type	Description	Mandatory?
`amount`	Number	Amount to be charged.	Yes
`currency`	String	`TZ` Transaction currency in ISO 4217.	Yes
`country`	String	`TZS` Transaction country in ISO 3166.	Yes
`payment_method_id`	String	`MW` ID of the selected payment method.	Yes
`payment_method_flow`	String	`DIRECT`	Yes
`payer.name`	String	Name of the payer.	Yes
`payer.email`	String	Email of the payer.	Yes
`payer.phone`	String	Phone number of the payer.	Yes
`payer.document`	Number	Document of the payer.	Yes
`order_id`	Number	ID of the capture given by the merchant in their system. Think of it as an external ID of the capture.	No
`notification_url`	String	Notifications will be sent in every change of status of a payment to the `notification_url` specified by the merchant.	No

Examples

{
    "amount": 1000,
    "currency": "TZS",
    "country": "TZ",
    "payment_method_id": "MW",
    "payment_method_flow": "DIRECT",
    "payer": {
        "name": "Jane Doe",
        "email": "[email protected]",
        "phone": "254746488970",
        "document": "12345678901234567890",
        "address": {
            "country": "TZ",
            "state": "Dar es Salaam",
            "city": "Dar es Salaam",
            "zip_code": "8858",
            "street": "Main St.",
            "number": "540"
        }
    },
    "order_id": "34545sk3483kqw0",
    "description": "Tshirt",
    "notification_url": "http://merchantsite.com/notification/new",
    "callback_url": "http://merchantsite.com/success_page"
}

{
    "id": "D-4-74fb9f36-eced-4433-4e32-2a77e90de8c6",
    "amount": 1000,
    "currency": "TZS",
    "payment_method_id": "MW",
    "payment_method_type": "BANK_TRANSFER",
    "payment_method_flow": "DIRECT",
    "country": "TZ",
    "bank_transfer": {},
    "ticket": {},
    "created_date": "2023-01-23T19:21:58.000+0000",
    "status": "PENDING",
    "status_detail": "The payment is pending.",
    "status_code": "100",
    "order_id": "34545sk3483kqw0",
    "notification_url": "http://merchant.com/notification/new"
}