Choose your country or region

SMS and USSD banking for customers on any phone.

Not every customer has a smartphone or data. Reach them by SMS and a USSD menu through Africa's Talking, with the same accounts and rules as your app. Everbranch builds small and medium banks their banking app and staff portal, and sends their notices and codes through Africa's Talking.

We build the Africa's Talking connector during your implementation programme, with the same connector kit as our existing connectors.

Email, SMS and push

How we connect to Africa's Talking

Africa's Talking is a communications platform for developers in Africa, with APIs for SMS, USSD, voice, airtime, WhatsApp and mobile data. Its USSD service is available in countries including Kenya, Nigeria, Uganda, Rwanda, Ghana and Zambia. A USSD session calls the business's callback URL at each step, and the business answers with the next screen.

SMS for notices

Notices from your app's events go out through your Africa's Talking account and sender IDs, with delivery reports recorded against each one.

USSD menus from the same data

Your USSD code calls our service at each step; we answer with short menus built on the same balances, accounts and limits as your app.

Your account, your short codes

Your bank holds the Africa's Talking account, USSD codes and sender IDs in each country, and we connect with credentials you issue.
Data

What moves between Africa's Talking and your app

  • Notice text and the customer's phone number for each SMS
  • Delivery reports for each message
  • USSD session steps: the code dialled, the phone number and the menu choice
  • Balances read live from your core for a USSD balance check
  • Opt-out and preference changes for each customer

Your Africa's Talking account, USSD codes, sender IDs and mobile network arrangements stay with your bank. Money stays in your core; we keep no ledger.

Use cases

What your bank can do with it

Balance checks on a basic phone

A customer dials your code, confirms who they are and sees a balance read live from your core.

Payment alerts by SMS

Customers hear about every payment by text, whether or not they have the app.

Reach rural and low-data customers

Branches and agents can point customers to a USSD code that works without data or an app store.
Why it matters

What it changes for your bank

Serve every customer, not just smartphone owners

SMS and USSD reach customers your app alone would miss.

One set of rules behind every channel

Limits, restrictions and step-up checks are enforced on our server, so a USSD menu can't do what your app wouldn't allow.

Several countries, one connection

Banks in more than one market use one connector and set the codes and senders per country.
Rollout

From first call to live

  1. Step 1: Choose channels per countryWe list where you have USSD codes and sender IDs, and which notices and menus each market needs.
  2. Step 2: Design short menusWe design USSD menus with your team: few steps, plain words, and only actions your policy allows on a basic phone.
  3. Step 3: Build and test on the sandboxWe build the connector during your programme and test sessions and SMS on Africa's Talking's sandbox and test numbers.
  4. Step 4: Launch market by marketYou go live in one country first, then add the next with its own codes and senders.
Questions

Africa's Talking: what IT teams ask

Is USSD banking available in Everbranch today?
Not yet. Today customers bank on web, iPhone and Android, with email and in-app notices. We build SMS and USSD through Africa's Talking during your implementation programme.
Which actions should a USSD menu allow?
Your bank decides. Most start with balance checks and recent transactions, then add payments under lower limits. Every action passes the same server checks as the app.
How does a customer prove who they are on USSD?
The phone number on the session is checked against the customer's record, and actions that move money ask for a PIN or code your bank sets in the programme.
Can we use Africa's Talking in more than one country?
Yes. Codes, sender IDs and settings are configured per country under your bank's account, behind one connector.
Related

M-Pesa

Customers send money to an M-Pesa wallet and see top-ups arrive, in your app. Everything runs through the M-Pesa integration your bank already has.
M-Pesa integration

Smile ID

Your customer enters an ID number and takes a selfie. Smile ID checks both against the government record, and your policy does the rest.
Smile ID integration

Twilio

Reach customers by text and WhatsApp from your banking app, using the Twilio account your bank already runs. Your notice rules and customer preferences stay the same.
Twilio integration
Pilot programme

Running Africa's Talking? Let's map it.

Tell us your version and how your teams use it. We'll show where it plugs in and what your customers get.

  • Your name and colours in the demo
  • Straight answers for risk, compliance and IT
  • No commitment