Fetch List of Disputes


To fetch the list of disputes by specifying the date range, limit, offset and Status (“ACTION_REQUIRED”, “UNDER_REVIEW”, “WON”, “LOST”).

EnvironmentHttp MethodAPI
SandboxGEThttps://api-preprod.phonepe.com/apis/pg-sandbox/v1/disputes?from=<epoch-timestamp>&to=<epoch-timestamp>&offset=<integer>&limit=<integer>&status=<statusTobeFetched>
ProductionGEThttps://api.phonepe.com/apis/pg/v1/disputes?from=<epoch-timestamp>&to=<epoch-timestamp>&offset=<integer>&limit=<integer>&status=<statusTobeFetched>
Request Headers
Header NameHeader Value
Content-Typeapplication/json
AuthorizationO-Bearer <access_token>
Path Parameters
Path Parameter NameTypeDescription
fromLongStart date period (Epoch timestamp)
(in milliseconds)
Note : Required Parameter
toLongEnd date period (Epoch timestamp)
(in milliseconds)
Note : Required Parameter
offsetLongThe starting point of the records
limitLongThe number of record merchant want to fetch
Note: Max value 100
statusEnumStatus for which merchant want to fetch the list of disputes
Note : Required Parameter

ℹ️ Dispute List API Date Range!


The Dispute List API supports responses for disputes within the specified date range, defined by the from (epoch date) and to (epoch date) parameters.

{
    "disputes": [
        {
            "merchantId": "merchantId",
            "disputeId": "D23456",
            "merchantOrderId": "MO2321",
            "orderId": "OMO241",
            "transactionId": "OM123",
            "transactionCompletedAt": <epoch-timestamp>,
            "transactionAmount": 1000,
            "disputeAmount": 1000,
            "refundAmount": 0,
            "contestAmount": 0,
            "status": "ACTION_REQUIRED",
            "stage": "CHARGEBACK",
            "createdAt": <epoch-timestamp>,
            "updatedAt": <epoch-timestamp>
        },
        {
            "merchantId": "merchantId",
            "disputeId": "D5674",
            "merchantOrderId": "MO2324",
            "orderId": "OMO241",
            "transactionId": "OM456",
            "transactionCompletedAt": <epoch-timestamp>,
            "transactionAmount": 1000,
            "disputeAmount": 1000,
            "refundAmount": 0,
            "contestAmount": 0,
            "status": "ACTION_REQUIRED",
            "stage": "ARBITRATION",
            "createdAt": <epoch-timestamp>,
            "updatedAt": <epoch-timestamp>
        }
    ],
    "nextOffset" : 2,
    "totalCount" :  2
}
Response Parameters
Parameter NameTypeDescription
disputesLISTList of dispute object
merchantIdStringUnique MerchantID assigned to the merchant by PhonePe
Note: merchantId length will be less than 38 characters.
disputeIdStringUnique DisputeId assigned to a dispute
merchantOrderIdStringUnique merchant order id generated by merchant
orderIdStringPhonePe generated order Id
transactionIdStringUnique transaction id generated by phonepe
transactionCompletedAtLongEpoch timestamp of the transaction completion time
(in milliseconds)
transactionAmountLongAmount of the transaction
disputeAmountLongAmount for which dispute is raised, will be lesser than or equal to transactionAmount
refundAmountLongAfter the status of dispute moved to LOST or WON, The amount that is given back to the customer
contestAmountLongAmount for which merchant does the contest
statusENUMStatus of the dispute
Note: The value could be
“ACTION_REQUIRED”, “UNDER_REVIEW”, “WON” or “LOST”
stageENUMStage of the dispute 

Note: The value could be
“CHARGEBACK” or “PRE_ARBITRATION”
createdAtLongEpoch timestamp, Creation date of the dispute
(in milliseconds)
updatedAtLongEpoch timestamp, Last updated date of a dispute
(in milliseconds)
nextOffsetIntegerNext offset in the filter list to pick the document
totalCountIntegerTotal record under the filter
Error Scenarios
Error ScenarioResponse CodeResponse
Input invalid limit or offset is negative
OR
limit > 100
OR
offset is greater than total count
400{
   “message”: “Invalid pagination parameters”,
   “code”: “INVALID_PAGINATION_PARAMS”
}
from >= to400{
   “message”: “Time range Invalid”,
   “code”: “INVALID_TIME_RANGE”
}
from (or) to is null400{
   “message”: “From or to cannot be null”,
   “code”: “INVALID_VALUE_OF_FROM_OR_TO”
}

Is this article helpful?