API Reference
Transaction Status API
Look up the settled status of any collection, withdrawal, fee, or refund by its human-readable reference — the fallback for when a webhook hasn't arrived yet, or you just want to confirm a result before continuing a flow.
Endpoint
GET
/v1/transactions/{reference}Look up a transaction by its reference (TXN-...).
API key or dashboardAuthentication
Requires the transactions:read scope on the API key used. A key only ever sees transactions belonging to its own merchant.
bash — cURL
curl https://api.infinityafrica.net/v1/transactions/TXN-4821AB \
-H "Authorization: Bearer inf_live_xxxxxxxxxxxxx"Response
json — 200 OK
{
"success": true,
"data": {
"id": "9b7e2c1a-...",
"merchant_id": "5c1f0b2a-3e21-4b9a-9c33-2f6a1d0e8b71",
"reference": "TXN-4821AB",
"provider_reference": "MOCK-SELCOM-9F3A1C2B",
"type": "collection",
"method": "STK_PUSH",
"collection_id": "2d4f8a91-...",
"disbursement_id": null,
"gross_amount": "25000.00",
"fee_amount": "375.00",
"net_amount": "24625.00",
"currency": "TZS",
"status": "successful",
"created_at": "2026-08-14T09:00:12Z"
}
}Status values
| Status | Meaning |
|---|---|
| pending | Created, not yet dispatched to a provider. |
| processing | Awaiting customer or provider confirmation. |
| successful | Settled — funds have moved. |
| failed | Declined, expired, or errored — no funds moved. |
| reversed | Settled, then reversed (e.g. a refund). |
| cancelled | Cancelled before settlement. |
404 — reference not found
Returned for an unknown reference, or one belonging to a different merchant than your API key — the two cases are indistinguishable by design, so a key can never be used to probe for another merchant's transaction references.
info
Prefer webhooks for real-time updates
Polling this endpoint works, but Webhooks push
collection.success / collection.failed the moment a transaction settles — use this endpoint to confirm a specific reference on demand, not as your primary status feed.