How Ta'ab works for your organisation
Ta'ab gives the people you serve one card, or one code in the Ta'ab app, that carries the passes you give them: a bus pass, a ticket, a meal plan, a membership. You decide what each pass is and what it costs. You sell it the way you already take payment. You accept it at your door with a phone. Ta'ab keeps the record of who holds what, and of every time it was used or refused.
What Ta'ab does, and what you do
| Ta'ab | You |
|---|---|
| Gives each person a Ta'ab ID, and a card or a code in the app | Decide who gets a pass, what it is and what it costs |
| Holds the passes you issue, and the ones from other organisations you agree to accept | Sell passes and keep the money: cash at your counter, or your own card payments |
| Says yes or no at your door, and records every answer | Scan at the door with a phone, or from your own system |
| Shows you who used what, and when, with reports to download | Decide what to do with what the reports tell you |
Ta'ab never takes payments. You collect the money for every pass, the way you do today.
People without a phone or a bank account
A Ta'ab card works the moment it is handed over: no app, no login, no bank account. You can sell one at your counter and put a pass on it straight away.
The slip that comes with the card carries a claim code. Whenever the holder likes, they enter it in the Ta'ab app, and the card and its passes are in their own wallet. A card nobody has claimed works just the same, but if it is lost, nobody can prove it was theirs, so the slip matters.
Bus companies
- What riders carry: a Ta'ab card bought at your counter, or the code in the Ta'ab app.
- What you sell them: a ticket for one trip, or a pass for a period. The T-Pass is one monthly pass that riders use on every bus company that takes it.
- At the door: the conductor taps the card or scans the code.
- One pass, one rider: an unlimited pass is refused a second time on your buses within 10 minutes, so one card can't carry two people.
- If you sell through MOHBEL ticketing, it works with Ta'ab. Riders link their card to their ticketing account and use it to reserve a seat and board, and a bus that loses signal still boards riders with a pass, sending their rides once the signal is back.
- Reports: every ride on a shared pass, by bus company, for settling who carried whom.
Schools
- What students carry: a Ta'ab card as their student ID, or the code in the Ta'ab app.
- What you give them: a meal plan (a number of meals), the school bus, library membership, attendance. Every use is recorded against the student.
- In the cafeteria or at the gate: staff scan with a phone.
- Your roster: import your class list. Each student gets a code to claim their wallet; students without a phone get a card instead.
- A cafeteria that already sells credit can keep each student's balance in Ta'ab: your cashier takes the cash and records it, and your cafeteria's till spends it.
Employers
- Give your whole staff a bus pass in one go, honoured by the bus companies you agree with. Pay the operators from the usage report; Ta'ab moves no money between you.
- Staff ID: the same Ta'ab card or app code.
Venues and events
- Sell tickets and memberships your way, put them in the holder's Ta'ab wallet from your own system, and scan at the door.
Each organisation sees only its own
A school sees its students and the passes it gave them. A bus company sees its riders and their rides with it. Neither sees what the person does with the other. People keep their Ta'ab ID, card and passes when they leave you; you stop seeing them.
What it takes to start
- Try it in the sandbox, sandbox.taab.mohbel.com. You're in at once, with test accounts and test cards, and nothing in it is real.
- Add a pass to your catalog, give it to a test account, and scan it with a phone at
/scan. - Apply to go live at taab.mohbel.com/institutions/request. Ta'ab reviews every application.
- If you have your own system, connect it through the partner API: see the developer docs.
What you need at the door: an Android phone with NFC to tap cards (any phone with a camera can scan the app's code), or your own system calling the API.