---
title: "Transaction Search"
method: POST
path: "/pws/pws_mc_txn_search/"
tags: ["Chargeback"]
---

# Transaction Search

`POST /pws/pws_mc_txn_search/`

This resource is used to query for transaction data

An issuer uses this endpoint to search for information about an original transaction. An issuer may use this information to take an action on the original transaction, such as creating a claim

## Request body

- MasterComTxnSearchModel
  - `api_call_unique_identifier` string, required — Unique number that must be passed at each API request. Identifier to make each API request unique
  - `client_id` integer, required — Unique identifier for the client which Paymentology will provide at outset
  - `user_id` string — User Id of the Customer who triggered the API request.
  - `remarks` string — Remarks for API request
  - `acquirerRefNumber` string — CONDITIONAL: Acquirer Reference Number. If provided bankNetRefNumber may not be used. This field is required and applicable if primaryAccountNum is not provided.
  - `bankNetRefNumber` string — CONDITIONAL: Banknet Reference Number. If provided acquirerRefNumber may not be used.
  - `primaryNumber` integer — CONDITIONAL: Public token or pan number.If length is equal to 16 digit or greater than 16 digit,it will be considered as pan number. If less than 16 digit it will be considered as public token . This field is required and applicable if acquirerRefNum is not provided
  - `transAmountFrom` number — Transaction amount lower limit value to be searched. Format : Numeric
  - `transAmountTo` number — Transaction amount upper limit value to be searched. Format : Numeric
  - `referenceSetId` integer — Unique identifier for clearing summary (settlement). This field will be used if authorisation or clearing is internal Format : Numeric
  - `tranStartDate` string — Transaction Date min search range. The search range is a maximum of 30 days, and searches can be completed for up to 730 days of history. Format : Date (yyyy-MM-dd)
  - `tranEndDate` string — Transaction Date max search range. The search range is a maximum of 30 days, and searches can be completed for up to 730 days of history. Format : Date (yyyy-MM-dd)

## Response `200`

Successful Response

- MasterComTxnSearchResponseModel
  - `header` ResponseHeaderMCTSR
    - `error_id` integer — error id
    - `error_desc` string — error message
  - `body` AuthorizationSummary[]
    - `originalMessageTypeIdentifier` string
    - `banknetDate` string
    - `transactionAmountUsd` string
    - `primaryAccountNumber` string
    - `processingCode` string
    - `transactionAmountLocal` string
    - `authorizationDateAndTime` string
    - `authenticationId` string
    - `cardAcceptorName` string
    - `cardAcceptorCity` string
    - `cardAcceptorState` string
    - `currencyCode` string
    - `chipPresent` string
    - `transactionId` string
    - `track1` string
    - `track2` string
    - `clearingSummary` ClearingSummary[]
      - `primaryAccountNumber` string
      - `transactionAmountLocal` string
      - `dateAndTimeLocal` string
      - `cardDataInputCapability` string
      - `cardholderAuthenticationCapability` string
      - `cardPresent` string
      - `acquirerReferenceNumber` string
      - `cardAcceptorName` string
      - `currencyCode` string
      - `installmentPaymentDataBrazil` string
      - `transactionId` string
      - `settlementIndicator` string
      - `tlementIndicator` ClearingSummary — recursive

## Other responses

- `404` — Webservices does not exist
- `500` — Internal Server error

---

[API](https://skmtc.net/paymentology/apis/payapi-docs.md) · [All operations](https://skmtc.net/paymentology/apis/payapi-docs/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/paymentology/payapi-docs/revisions/a675891b0365/schema)