reference_number you supplied in that request and the API returns the current status of the transaction. This is the primary way to confirm delivery when your webhook endpoint does not receive a notification — for example, during a network interruption or when a transfer is still processing.
Endpoint
Authentication
Pass your bearer JWT in theAuthorization header. Obtain a token from Generate Token.
Request body
The unique reference number you provided when calling Funds Transfer. This is your own identifier for the transaction — not Shogun’s internal
transaction_id.Request example
Responses
200 — Status retrieved
Error — Reference not found
Response fields
Your reference number, echoed back from the original funds transfer request.
Shogun’s internal transaction identifier.
Transfer amount in NGN.
intra or inter, as specified in the original transfer request.Current status of the transaction. Possible values:
pending— the transfer is still being processed by the bank or NIPsuccessful— the funds have been successfully delivered to the beneficiaryfailed— the transfer was not completed; no funds were debited, or a debit has been reversed
The narration provided in the original transfer request.
ISO 8601 timestamp of when the transfer was initiated.
ISO 8601 timestamp of the most recent status update.
Inter-bank transfers via NIP typically settle within seconds, but may remain
pending for up to a few minutes during peak periods. If you poll for status, use an exponential backoff strategy — for example, check after 5 s, then 15 s, then 60 s — rather than polling in a tight loop. For production workloads, configure a webhook to receive real-time delivery notifications instead of relying solely on polling.