> For the complete documentation index, see [llms.txt](https://developer.ellypayapp.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.ellypayapp.com/utility-functions.md).

# Utility Functions

- [Balance Inquiry](https://developer.ellypayapp.com/utility-functions/balance-inquiry.md): The API allows the merchant to check the balance(s) for the different currencies they might hold.
- [Payment Options](https://developer.ellypayapp.com/utility-functions/payment-options.md): Before any transaction request is performed, it's recommended that the payment options available to the merchant account are known. This endpoint returns that list.
- [Payout Bank Codes](https://developer.ellypayapp.com/utility-functions/payout-bank-codes.md): For all countries/currencies where EllyPay supports bank payouts, there's need to specify the unique code for the bank to which the funds are to be sent. These codes are available via the API
- [Transaction Status Verification](https://developer.ellypayapp.com/utility-functions/transaction-status-verification.md): In some situations, the merchant might wish to confirm the status of the transaction. This document resource describes the process of retrieving the transaction details (status inclusive)
- [Handling Notifications/Callbacks](https://developer.ellypayapp.com/utility-functions/handling-notifications-callbacks.md): Whenever the status of the transaction changes (to processing, failure or success), we notify your service via callbacks. Below are the hints to take note of as regards these payment notifications.
- [Callback Events](https://developer.ellypayapp.com/utility-functions/handling-notifications-callbacks/callback-events.md): Every callback payload has a parameter named event and its purpose is to communicate the reason for the callback. The section below describes the various values the parameter can take.