Reading Your Wallet Statement: Grants, Sends, and Refunds
Your wallet balance is just a number until you can see the story behind it. That story lives in your statement — the running list of every credit and debit that moved your balance to where it is now. KibiPay's statement records four kinds of events clearly: grants, sends, receives, and refunds. This post teaches you to read each line so the balance never feels like a mystery.
Why a statement matters
A balance answers "how much do I have?" A statement answers "how did I get here?" Every entry is a discrete, timestamped event, and because KibiPay uses a double-entry ledger, the entries always add up to your current balance. If you understand the entries, you understand your money. For the accounting model underneath, see double-entry ledgers for payments.
The four entry types
Grants (credits from the platform)
A grant is money the platform adds to your wallet. The most familiar grant is the $10,000 that lands the moment you create your account — see your $10,000 demo wallet. Grants also appear when an administrator tops you up. On your statement, a grant is a credit: your balance goes up, and the line notes it came from the platform rather than another user.
Sends (debits to another party)
A send is a payment you initiated. It is a debit — your balance falls by the amount sent. The entry records who you paid (their handle or alias), how much, and over which rail the money traveled. If a send is declined for insufficient funds, no entry is created because nothing moved; we cover that in balance checks and insufficient funds.
Receives (credits from another party)
A receive is money someone sent to you. It is a credit — your balance rises. The entry shows who paid you and how much, which is exactly what you would expect after sharing your handle or QR code, as described in get paid: share your handle or QR.
Refunds (reversals)
A refund reverses an earlier payment. If a send is returned, a refund credit appears on your statement, restoring the amount. Refunds are shown as their own entry type rather than quietly editing the original, so the history stays complete and auditable — you can always see both the send and its reversal.
Anatomy of a statement line
| Field | What it tells you |
|---|---|
| Type | Grant, send, receive, or refund |
| Amount | Value moved, with direction (credit/debit) |
| Counterparty | The platform, or the other user's handle/alias |
| Rail | Which rail carried it (Mojaloop, ACH, FPS, Solana) |
| Timestamp | When it happened |
Reconciling your balance
Here is a satisfying exercise: add up every credit, subtract every debit, and you will land exactly on your current balance. That is the whole promise of a ledger — nothing is hidden, nothing is fudged. If the numbers reconcile (they will), you can trust the wallet completely. This same discipline is what real platforms use to prove their books, and it connects to how payments finally settle, covered in multi-rail settlement explained.
Statements for admins
Administrators can view statements across users, which is invaluable for running a structured demo or debugging a flow. If a payment did not appear where expected, the two statements involved tell you exactly what happened. See the admin view for how that works.
Read your own statement now
Why every entry is kept forever
KibiPay never edits or deletes a past entry. A refund does not erase the original send; it sits beside it as its own line. A correction is a new entry, not a rewrite. This append-only discipline is what makes a ledger auditable: the history is a complete, tamper-evident story rather than a mutable snapshot. If you ever wonder how a balance came to be, you can trace it entry by entry back to the opening grant. Real financial systems live and die by this property, and seeing it in the demo builds exactly the right instinct for how trustworthy books are kept.
Sign in to the KibiPay app, send a payment or two, and watch the entries appear in real time. To generate some activity worth reading, follow the two-minute walkthrough, then browse more guides on the blog.