You can use Transactions APIs for performing operations on individual transactions. In particular, Transactions APIs enables you to:
Retrieve a list of transactions initiated from a specific card by a specific cardholder at a specific merchants etc..
Get a specific transaction record using transaction ID
Filter or retrieve a sorted list of transactions related to a specific user, performed at a specific time, specific transaction type or amount etc.
Search for transactions
nCore platform stores all transactions, which were fulfilled earlier. You can search the transactions based on the filter parameters enabled at nCore platform.
Transaction search use cases
If you are preparing some financial statistics specific to merchants, you can call the /transactions:search endpoint to filter all transactions related to a specific merchant identified by the merchant_name parameter.
If you are developing some customer relationship management system, you may have requests to get the list of transactions, conducted by a specific card. In this case, you can call the /transactions:search endpoint and use the card id query parameter to get transactions for the specific card.
If you are developing a mobile application, users may have a possibility to review their transaction history. In this case, you can call the /transactions:search endpoint and use the user_id query parameter to get transactions conducted by a specific user.
Send a POST request to /transactions:search endpoint as shown below to retrieve maximum ten transactions initiated with a specific card which are sorted by a transaction amount in ascending order.
Below you can find a file with the list of transaction status codes, which can occur:
You can receive information about transactions as they occur by configuring webhooks. Webhooks give a possibility to receive real-time notifications about API events, such as card status change, transactions etc.. Learn more about webhooks in the Webhooks section.