NEXUS Back Office Rwanda (RWF) Maker-checker: 4 pending PH

Transaction Operations

Search, reverse, refund and resolve duplicate transactions - every action posts a compensating entry
Patrick Habimana - Platform Admin Reversals require checker
1,204 transactions match - showing 6
TransactionTimeTypeFromToChannel AmountStatusActions
TX-09188211:42P2P transferAline UwaseEric Mugisha AppRWF 25,000 Completed
TX-09187711:38Escrow captureAline UwaseKigali Electronics WebRWF 189,000 In escrow
TX-09187111:30CICO cash-inAgent SB-4471Grace Umutoni AgentRWF 60,000 Completed
TX-09186411:19Bill paymentSamuel NsengimanaEUCL CashPower USSD *182#RWF 10,000 Pending Trace
TX-09186011:12P2P transferW-4471W-9902 AppRWF 480,000 Held (FRE) Case
TX-091712YesterdayRefundKigali ElectronicsJosiane Uwimana Web- RWF 98,500 Reversed View

Duplicate detection - resolution queue

3 unresolved
Idempotency conflict (409): the same idempotency key was seen with a matching payload within the dedup window. Confirm whether these are a genuine double-charge to reverse, or distinct transactions to keep.
GroupOriginalSuspected duplicateParty AmountGapResolution
DUP-2201TX-091801 TX-091802Eric Mugisha RWF 15,0002 s Reverse duplicate / Keep both
DUP-2198TX-091644 TX-091649Simba Supermart RWF 4,8006 s Reverse duplicate / Keep both
DUP-2195TX-091590 TX-091598Grace Umutoni RWF 32,50044 s Reverse duplicate / Keep both

Transaction Operations

Nothing matched: today, cash-out, over RWF 5,000,000

Nothing matched those filters

Three filters are stacked and the value floor is above the Tier 2 daily cap, so no single cash-out could match it. Drop the floor or widen the date.

Transaction Operations

This transaction has already been reversed
TRF-2026-771204 was reversed at 11:02 by m.habimana. Reversing it again would create money out of nothing, so the platform refuses. A reversal is not idempotent by accident; it is guarded on purpose.
Error returned409 ALREADY_REVERSED
Original transactionTRF-2026-771204, RWF 50,105
Reversal entryREV-2026-771204, posted 11:02 today
Reversed bym.habimana, confirmed by t.nkusi
Reason on the reversalCustomer reported a mistaken recipient
Net effect nowZero. The customer has their RWF 50,105 back.
Your attemptRefused. Nothing was written.
EntryPostedDebitCreditState
TRF-2026-77120419 Jul 09:14Aline Uwase RWF 50,105Eric Mugisha RWF 50,000 Reversed
REV-2026-77120419 Jul 11:02Eric Mugisha RWF 50,000Aline Uwase RWF 50,105 Posted
Both entries stay visible. The original is not deleted or marked void; it is marked reversed and the reversal sits beside it. Anyone reading the account later sees what happened rather than a gap.
Open the fraud case instead

Transaction Operations

Your reversal is with a checker
Nothing has moved. A reversal takes money back off somebody, so it needs a second operator. Until then this is a request with your reason attached.
RequestREV-REQ-2026-0884
TransactionCSH-2026-880194, RWF 40,000 cash-out at Agent 4471
Requested byj.mukama, today 15:22
ReasonCustomer states the cash-out was not authorised; fraud case FRD-2026-2218 open
Effect if confirmedRWF 40,000 back to the customer, agent float debited
The agentTold, and their float is held pending the decision
Waiting onAny operator with the transaction checker role
Why the agent float is held rather than debited now. If the reversal is not confirmed, the agent should not have lost anything. Holding is reversible; debiting is a second correction.