BFSI Loyalty Program Software for South Africa

A consultant working a branch catchment in Johannesburg, Cape Town, Durban or Polokwane books transactional accounts, personal loans, vehicle and asset finance, and SME facilities. The rule engine takes those figures straight from core banking, deducts anything that defaults early, and opens the slab as soon as the month's booked value clears the threshold. The approved rand then settles to the consultant's own bank account by instant EFT, usually the same day.

Three things decide the band: how many policies were written, what premium they carry, and how many were still paying at month thirteen. Life, short-term, health and funeral-cover intermediaries are scored the same way, and the evaluation reads the policy admin system rather than anything the intermediary types in. What a band is worth is yours to set, whether that is cash to a bank account, a convention or club place, or a non-cash award, and it stays inside the conduct rules your compliance team applies.

The bank account is captured at sign-up and checked against the member's South African ID number and the account-holder name the bank holds. After that an approved amount leaves by instant EFT or PayShap. Caps run per day, per account and per programme, the bank statement reconciles without anyone touching it, and the member follows progress in the app instead of ringing the scheme desk.

Yes. Aggregators and the merchant agents beneath them earn on card turnover, deposits taken, prepaid and airtime sales, and new accounts opened, whether the outlet trades at Warwick Junction, around the Bree taxi rank, or on a forecourt out on the N3. Each aggregator keeps its own hierarchy, its own verification requirements and its own message stream, while the rule engine settles commission and bonus to every registered account underneath it.

Early defaults are clawed back, ageing is checked before anything is released, and AI anomaly scoring picks up a sudden spike in volume or the same supporting document submitted twice. High-value amounts need more than one approver. Anything flagged waits in a review queue. Because the rules live on the server and never on the handset, a genuine member is not slowed down and still sees the rand arrive on schedule.

Disbursements, policy issuance and premium receipts arrive over REST API or a scheduled SFTP drop from your core banking or policy admin system. Each record is scored against whichever slabs are live at the time, and a qualifying one triggers the payout. The sync runs both ways, so settled amounts are written back to the source system for your accounting and audit teams to reconcile.

A board can be cut by province, by metro or by branch cluster, ranking consultants, brokers and tied agents on booked volume and conversion anywhere from Gauteng to the Western Cape to KwaZulu-Natal. Band badges sit on the member's app profile. Challenges run alongside them for funeral-cover drives, SME-lending sprints and the usual month-end push, and who qualifies for each one is set in the portal.

Every audience gets its own stream. Scheme alerts, persistency reminders, recognition notices and volume updates go out over WhatsApp Business API and SMS, and a member can reply to ask where a slab or a payment stands. Sends are scheduled per campaign in the automation engine, run on opt-in, and go out in English, isiZulu, isiXhosa, Afrikaans or Sesotho depending on what the member chose.

Payout run-rate in rand as it happens, how fast slabs are being reached, the persistency curve, engagement broken out by province, and whatever the fraud rules have flagged. Finance gets programme cost against budget on the same screen. Ask 1Voice for the top five consultants on personal loans this month and it answers in plain language, and every figure drills down to the individual transaction for audit.

Yes. The app is built for entry-level Android handsets and keeps working with no signal at all, holding captured activity on the device and syncing it the moment coverage returns, which matters on long rural routes and in the township pockets where reception falls away. Member records and consent capture are handled in line with POPIA, and an SMS fallback still reaches a member whose data has run out.