Your business account
Your Paga business account is where every payment you collect arrives, and where every payout, airtime purchase and bill payment is paid from. Check its balance and history at any time.
What arrives in your account
- Checkout, transfers, USSD and Paga Wallet
- Direct Debit charges
- Payments to you as a biller
- Subsidiary Accounts that settle to you
What’s paid from your account
- Money transfers
- Airtime and data
- Bill payments
- Fees
These endpoints use the Business API, with your principal and credentials headers and a hash, as in Authentication. They cover every transaction on your business account, however it was made.
1. Check your balance
Check availableBalance before a payout run: it’s what you can actually spend. totalBalance can include money that isn’t available yet.
POST /paga-webservices/business-rest/secured/accountBalance
principal: YOUR_PUBLIC_KEY
credentials: YOUR_SECRET_KEY
hash: sha512(referenceNumber + hashKey)
Content-Type: application/json{
"referenceNumber": "BAL-2026-0042"
}{
"referenceNumber": "BAL-2026-0042",
"responseCode": 0,
"totalBalance": "100000.0",
"availableBalance": 95000.0,
"currency": "NGN"
}Response fields (5)
| Field | Meaning |
|---|---|
availableBalance | What you can spend now. Use this before sending money |
totalBalance | Your full balance, including anything not yet available |
currency | NGN |
responseCode | 0 means success. Look up any other code in the Business API error codes |
referenceNumber | Your reference |
2. Get your transaction history
Every transaction on your business account between two dates: money in, money out and fees. Use it to reconcile your records with Paga’s.
POST /paga-webservices/business-rest/secured/transactionHistory
principal: YOUR_PUBLIC_KEY
credentials: YOUR_SECRET_KEY
hash: sha512(referenceNumber + hashKey)
Content-Type: application/json{
"referenceNumber": "HIS-2026-0042",
"startDateUTC": "2026-11-01T00:00:00",
"endDateUTC": "2026-11-04T00:00:00"
}Request and response fields
| Field | Meaning |
|---|---|
startDateUTC, endDateUTC | Request. The range, in UTC |
items[].referenceNumber | The transaction’s reference |
items[].status | The transaction’s status |
items[].amount | Amount |
items[].fee | Fee |
items[].balance | Your balance after the transaction |
items[].dateUTC | When it happened, in milliseconds since 1970 (UTC) |
Returns up to 10,000 of your most recent transactions in the range. For a busy account, request shorter ranges, such as one day at a time.
No code needed: download it from the business portal. Your finance team can download your transaction history as a CSV file for spreadsheets, or as a PDF statement. In the business portal, go to Transaction history and select Export, or open Account statement.
3. Get your recent transactions
Your last 5 transactions, without choosing a date range. Useful for a dashboard, or to confirm something has just arrived.
POST /paga-webservices/business-rest/secured/recentTransactionHistory
principal: YOUR_PUBLIC_KEY
credentials: YOUR_SECRET_KEY
hash: sha512(referenceNumber + hashKey)
Content-Type: application/json{
"referenceNumber": "REC-2026-0042",
"locale": "en"
}{
"referenceNumber": "REC-2026-0042",
"responseCode": 0,
"message": "Success",
"recordCount": 5,
"currency": "NGN",
"items": [
{
"itemNumber": 1,
"dateUTC": "2026-11-07T09:14:22",
"description": "Deposit to bank: Access Bank ******8830",
"amount": 5000.0,
"status": "SUCCESSFUL",
"transactionId": "RP658",
"referenceNumber": "PAY-2026-0311"
}
]
}Request and response fields
| Field | Meaning |
|---|---|
referenceNumber | Request. Your unique reference for this request. The only value in the hash |
locale | Request, optional. Language for messages, such as en |
accountPrincipal, accountCredentials | Request, optional. Only when checking a Paga user’s account on their behalf. Leave out to check your own business account |
recordCount | How many transactions were returned, up to 5 |
currency | The currency of the amounts |
items[].itemNumber | The item’s position, starting at 1 |
items[].dateUTC | When the transaction happened, in UTC |
items[].description | What the transaction was |
items[].amount | The transaction amount |
items[].status | The transaction’s status |
items[].transactionId | Paga’s short ID for the transaction |
items[].referenceNumber | Your original reference, if the transaction was made through the API. Transactions made elsewhere, such as at an agent, may not have one |
responseCode | 0 means success. Look up any other code in the Business API error codes |
Returns your last 5 transactions. For anything further back, or a specific period, use your transaction history.
Reconciling your account
Balance and history cover everything
Collections, payouts, biller payments and fees all appear, whichever API or channel they came through.
Checking a single payout?
Use “Check the transaction status” in Money transfer, Airtime and data or Bill payment. It covers Business API transactions from the last 48 hours.
Checking a single collection?
Use the status check on that payment method’s page, such as Dynamic virtual account.
Reconcile daily
Pull yesterday’s history each morning by API, or download it as CSV or PDF from the business portal (Transaction history → Export, or Account statement), and match it against your records by reference number.
Need help? We’re here 24/7
Talk to our support team any time, or ask questions in the developer community.
Updated about 7 hours ago

