For a voter, the Top Awards payment journey is intentionally simple: choose a nominee, select the number of votes, enter a phone number and approve the M-PESA prompt. Behind that short experience, however, the platform performs several checks to ensure that a vote is only credited when there is a valid confirmed payment behind it.
A payment request is not yet a vote
The first important distinction is between initiating a payment and completing one. When a supporter starts an STK Push, the platform creates a payment record and waits for the payment provider to return the outcome.
If the supporter cancels the prompt, enters an incorrect PIN, lacks sufficient balance or the transaction otherwise fails, the request does not become a verified vote.
Confirmation is the trigger
Votes are credited after the provider reports a successful transaction. This approach prevents the system from treating an uncompleted payment request as if money had actually been received.
It also creates a clear point of reconciliation: a confirmed provider transaction can be matched to the platform payment record and the vote quantity credited to the relevant nomination.
Unique references help prevent duplication
Payment providers may send status updates more than once, particularly when networks retry callbacks. A secure voting platform therefore cannot assume that every incoming callback represents a brand-new payment.
Top Awards uses unique references and idempotent processing so that a repeated confirmation for the same transaction does not create a second set of votes. The original payment remains the single source of truth.
Financial records and vote records remain connected
Keeping payment and vote data connected makes it possible to audit what happened after the fact. Administrators can trace a vote to its payment transaction, review the provider reference and see whether the payment was paid, failed or left pending.
This is particularly important when a voter reports that money was deducted but the vote did not appear immediately. Support teams can investigate the transaction without relying only on screenshots or memory.
Revenue sharing follows confirmed value
Where an edition enables nominee revenue sharing, earnings are calculated from verified paid transactions rather than from attempted payments. The nominee wallet therefore reflects confirmed financial activity, while failed and pending transactions do not create earnings.
Wallet entries and withdrawal requests are recorded separately so that financial activity remains auditable after the voting event itself.
Visibility is different from integrity
An edition may choose to hide public vote totals or rankings while voting is active. That does not mean votes are untracked. Public visibility is a presentation choice; the underlying verification and transaction records continue to operate regardless of what the visitor can see on the front end.
Why this matters to both nominees and voters
Nominees need confidence that campaign performance is based on completed support. Voters need confidence that a successful payment can be associated with the nominee they intended to support. Administrators need records that can be reconciled if a dispute arises.
Those needs are different, but they depend on the same principle: every verified vote should be explainable. The platform's payment and audit trail is designed to make that possible without making the public voting experience unnecessarily complicated.