Payless Control Center
DB —

Welcome back

Here's what's happening across the control center right now.

Quick actions

Recent activity

Tickets, last 30 days

New ticket

What kind of ticket do you need to raise?

SMS provider

Which provider is tried first for outbound SMS. The others stay as automatic fallback. Switching doesn't disable them.

Email accounts

Gmail accounts registered for outbound email: alerts, partner notices, or anything else that needs one. Add/Edit/Delete still go through the ticket flow below.

Enter details

Confirm before you submit

This is the current state, read straight from the database. Nothing has changed yet.

Approvals

Tickets waiting on a decision from someone with your role. You can't approve or reject your own tickets.

Reason

Raw before-state

Decision

My tickets

Everything you've submitted and its current status.

Activity log

A running record of every submit, approval, rejection, and execution across the control center.

Users

Operator accounts and their roles.

Account

Reports

Filter tickets by date, requester, operation, or status. Export the filtered set as CSV.

Float management

Live M-Pesa float balance, alert thresholds, and who gets notified when a balance runs low. Changing a threshold or recipient goes through the usual approval flow.

Working balance, last 7 days

Alerting efficiency

How well the alerting is catching and resolving low-balance episodes, computed from the same alert history as the Alerts tab.

Alert thresholds

Alert recipients

Recent alerts

Send test alert

Confirms SMS delivery is wired up. Doesn't wait for a real balance drop, and doesn't change any configuration.

Payment failures

Disbursements the gateway reported as failed, and whether a retry is allowed. Retry and fail-back go through the usual ticket approval; resolve records what was done by hand.

Needs attention now

Open right now

Not limited to the window: a failure from yesterday that is still open stays counted.

In the window

By stage

By channel and app profile

This service only hears about failures. It cannot say how many payments succeeded or are in flight, so no success rate, failure percentage or trend is shown here; that needs a denominator from the gateway or sdk5.

Failures over time

Absolute failure counts only. Nothing here knows how many payments succeeded, so there is no success rate or failure percentage to show, and a rising line can mean a channel degrading or simply more volume.

Actions

Transaction

Failure

Retry budget

Resolution

Replay request

Exactly what a retry would send to the gateway.

        

        

          
Events

          
Every delivery, retry, refusal and state change, newest first. A refusal means someone tried and the gate was shut.

          

        

      


      
      

        
Fraud review

        
Onboarding attempts flagged for manual review. Identities are masked by default. Every reveal is audited.


        

          
          
          
          
        


        

          


          

            

              
Reasons

              
Why cases were sent to review: duplicate/velocity flags plus TransUnion's own causal findings (face match, liveness, spoof, risk). There's no category field on the source data; this is our own grouping.

              

                

                

              

            

            

              
Cases over time

              
Received per day, last 14 days, by review status.

              

              

            

          


          

            
Open cases

            

            

          

        


        

          

            

              

              

              

              

              

              

                
                
              

              

                
                
              

              

              

            

            
National ID and phone match exactly. Spaces, hyphens and case are ignored, and a phone written 0712… matches its 254712… form. There's no name or partial search.

            

              
              
            

          

          

            

            

          

        


        

          

            

              

              

              

            

          

          

          

            

            

              
Concentrations

              
Devices and IPs carrying more than one identity, and national IDs seen more than once. Several names on one ID, or many identities on one device, is the shape of organised fraud. Each row opens a search for that signal; open a case from there to see its related attempts.

              

            

            

              

                
Attempts over time

                

                

                

              

              

                
Review status

                

                  

                  

                

                
Outcome

                

              

            

            

              

                
Flags

                
One attempt can fire several rules and counts under each, so these overlap and are not shares of a total.

                

              

              

                
TransUnion

                

                

                
Top reasons

                

              

            

          

        


        

          

            
Cases CSV

            
Unmasked, one row per attempt, using the Search tab's current filters. Capped at 5,000 rows.

            
            

          

          

            
Summary CSV

            
Aggregate counts only, no identities. By day & review status, by flag category, flagged vs. TransUnion-only, by outcome.

            
            

          

        

      


      
      

        

        

          

            

            

          

        


        

          
Why it was flagged

          

          

          

          

          

            TransUnion diagnostics (did not decide the outcome)
            

          

        


        

          

            
Identity

            

          

          

            
Device & network

            

          

        


        

          
Review

          

            

              

                
                
              

              

                
                
              

            

            

              
            

          

          
Review history

          

        


        

          
Related attempts

          

          

        

      


      
      

        

          
Insights

          
        


        

          

          

          
        


        

          
          
          
          
        


        
        

          

          

            
Status split

            

              

              

            

          


          

          

            
Money flow

            
Money into vs. out of the wallet ecosystem. Gate transactions only.

            

              

              

            

          

        


        
        

          

            

              
By type

              
Product/route level detail. Gate transactions only.

              

                

                

              

            

            

              
Channel popularity

              
Rolled up to network. Gate transactions only.

              

                

                

              

            

          


          

            
Transaction amount bands

            

            

          


          

            
What these mean

            
A key for finance readers. Anything not yet confirmed internally is labeled as such rather than guessed.

            

          

        


        
        

          

          

            
Revenue split

            

            

              

              

            

          

          

            
Revenue by partner

            
Our commission per partner, before tax. Gate transactions only.

            

              

              

            

          

          

            
Revenue by channel

            
Commission kept vs. paid out, per channel. Gate transactions only.

            

          

        


        
        

          
Reversals, manual credits/debits, and pending tickets raised through this app, not the real transaction volume above. Always last 14 days, independent of the date filter.

          

          

            
Last 14 days