Transaction Retrieval and Cancellation
You can use the same
GET /transaction request as before to query multiple transactions at a time. This is useful if you want to maintain a CRM or database of transactions for POS systems to query.
GET /transaction Request
It is the same endpoint, but when querying multiple transactions you include different parameters into the URL.
These requests support filtering the results by specifying the required filter in the query string in the format:
Values need to be correctly URL encoded if they contain characters that are reserved in URL notations, for example forward slashes must be encoded as
More than one field can be specified by specifying an ampersand (&) between the fields e.g.
These requests support pagination to minimise the amount of data returned in one go. In this situation, the pagination information is returned as part the response header in the X-Pagination header in JSON format.
|FIELD||JSON NAME||DATA TYPE||DESCRIPTION|
|Total Count||Integer||The total number of pages|
|Page Size||Integer||The number of items per page|
|Current Page||Integer||The current page number|
|Total Pages||Integer||The total number of pages|
This provides details of the total number of records, the defined page size, what the current page is and the total number of pages. The page number and page size can be specified in the query string allowing you to move through the records as appropriate.
If the page size exceeds the axept Connect Cloud service’s configured page size, the requested page size will be limited to the configured page size.
|GET /transaction Response|
|Field Name||Data Type||Description|
|uti||GUID||Unique client initiate GUID to represent the transaction.|
|reference||String||Client reference assigned to the transaction and echoed back in subsequent operations.|
|status||String||The status of the transaction. This will be either:|
|transType||String||Indicates how the transaction should be processed.|
|amountTrans||Integer||Amount of the transaction in minor units not including cashback/tips etc.|
|amountGratuity||Integer||Amount of the gratuity in minor units.|
|amountCashback||Integer||Amount of the Cashback in minor units.|
|expirationDate||DateTime||UTC Date/Time the transaction will expire in ISO 8601-1:2019 format|
|createdDateTime||DateTime||UTC Date/Time the transaction was initiated by the merchant in ISO 8601-1:2019 format|
Multiple transactions are returned as a JSON Array of Objects.
Should you need to, you can Delete any transaction that is at the
Complete status by using the DELETE HTTP Method. You need to include the
uti for the specific transaction for each request.
DELETE /transaction Example
Transactions which are
InProgress are locked and cannot be deleted.