Guides

Transaction Report

Use our API to browse a paginated list of transaction requests.

Suggest Edits

This guide shows you how to request a report of transaction requests made by your account. You can see the data of all transaction requests, or you can filter the response for more focused data. See Transaction Report in API Reference for field definitions.

Prerequisites

  1. See Create a Sandbox Account to sign up and log in to the Maast Manager portal.

  2. Follow the steps in Get Your API Credentials to save a sandbox ID and API key.

  3. See Authentication to format the credentials and generate your API token. (Alternatively, use the credentials as-is to test this endpoint with our 'Try It!' feature.)

  4. If you have not made any transaction requests, you can follow the steps in the API: Quick Start guide to perform a basic sale transaction for this request to return.


Implement

Write a GET request to send to the /platform/reporting/transaction-requests endpoint. See the following sample code:

curl --request GET \
     --url https://api-test.maast.com/platform/reporting/transaction-requests \
     --header 'accept: application/json' \
     --header 'authorization: Basic OjllZGVjMjFhMzFjMHh5ejc4OWUzMGEzNDE2YWJjMTIz'

The above code requests data on all transactions for your account, using default sorting and no filtering.

The following sections describe several query parameters that you can add to your request to sort and filter the response. To add these parameters, append them to the request endpoint URL, preceded by ? and separated by &.

Sort

Use the following parameters to sort the data in the response:

  • order_on - Include this to sort results by a certain field. For example, to sort by transaction time, write order_on=tran_time. All available fields are listed in the data array in the response model for this request's API Reference.
  • order_by - Include this to sort the specified field by ascending order (asc) or descending order (desc).

Filter

Use the following parameters to filter the response:

  • filter - Include this to narrow results by requiring certain fields to meet specified values. You can combine multiple filters. Each filter contains three properties, packed together with commas:
    • field name - All available fields are listed in the response model of this request's API Reference.
    • filter conditional - Find supported filter conditionals in About Our APIs: Filters.
    • the value on which to filter
  • count - Include this to set the number of records in the result.
  • page - Include this to choose a page to display when there are more results than the count parameter.

🚧

When placing strings in URLs, be sure to use your development language's URL encoding methods (e.g., for hexadecimal, use %2C in lieu of a comma).


Example Request

Once configured, the code for your request will resemble the following sample code:

curl --request GET \
     --url 'https://api-test.maast.com/platform/reporting/transaction-requests?count=10&order_on=tran_time&order_by=desc&page=2&filter=amt_tran%2CGREATER%2C100' \
     --header 'accept: application/json' \
     --header 'authorization: Basic OjllZGVjMjFhMzFjMHh5ejc4OWUzMGEzNDE2YWJjMTIz'

Integrate

Once you have sent your request, you will receive a response like this from the Maast server:

{
  "code": 0,
  "message": "Success",
  "totalPages": 1,
  "totalRecords": 1,
  "data": {
    "rec_id": 1,
    "qp_id": 56789,
    "merchant_id": 212000000001,
    "tran_time": "2025-07-01T00:00:03.000Z",
    "tran_date": "2025-07-01T00:00:00.000Z",
    "request_type": "sale",
    "tran_status": "C",
    "dispute_flag": false,
    "amt_refunded": 0,
    "pg_id": "efgbe295c41611edb32402171867ecb2",
    "pg_id_linked": "d123abead4a5911e6807e0a728c0d49c0",
    "amt_tran": 100.99,
    "tran_currency": "840",
    "purchase_id": "XYZ12345",
    "cardholder_first_name": "John",
    "cardholder_last_name": "Doe",
    "card_number": "488888xxxxxx8887",
    "card_type": "VS",
    "auth_code": "T12345",
    "acq_reference_number": "8975679",
    "merch_ref_num": "Ref#1234",
    "amt_convenience_fee": 2,
    "amt_tran_fee": 2.35,
    "dba_name": "CompanyXYZ",
    "amt_funded": 100,
    "funded_currency": "840",
    "rcode": "000",
    "auth_avs_result": "X",
    "auth_cvv2_result": "M",
    "auth_tran_id": "9902KUUSCJCP5I"
  }
}

Check the code field in the request response: 0 confirms success. If the value is something other than 0, check Platform API Response Codes in Reference.

The data field shows an array of transactions and their data. The sample response above shows data for one transaction. See Transaction Report in API Reference for response field definitions.


Test and Go Live

See our Test and Go Live guide to test your API integration and to start transacting with an active production account.


Updated 12 months ago