Dispute Details
In details page the entire details of the dispute will be shown including transaction ID, Customer name, customer email, Merchant ID, Merchant name, merchant email etc . Along with this details dispute journey and documents submitted will be shown for reference.
GET https://stgsecctrl.tutelar.io/api/v1/dispute/view/:disputeId
Success Response
Failure Response
Response parameter description
documents
Object
Documents refers to the set of documents that are submitted in order to challenge the dispute. This documents field contains level_1, level_2 and level_3 each which is an array of objects, which contains 2 fields: key data type is string and _id data type is objectId.
Level
String
following the dispute raised in the panel, the client can use the edit option in the action menu to change level . The level is mainly based on the priority of the dispute raised by the acquirer bank
status
String
whenever an dispute is raised the status of the dispute will be updated in order identify whether the raised dispute is in open or closed status
verdict
String
After evaluating the raised dispute the verdict will be uploaded such as won or loss .
createdAt
DateTime
Created date and time of dispute.
updatedAt
DateTime
Updated date and time of dispute.
disputeId
String
A unique ID will be followed in order to differentiate the disputes raised dispute_uVxLt1Mh
merchantName
String
Merchant name will be updated while creating the dispute (Johnson)
merchantId
String
A unique ID will be followed in order to save the merchants vice versa and differentiate the client TUTDINEJOHN00006
merchantMobile
String
Merchant mobile number will be updated while creating the dispute 9588588573
businessName
String
Merchant business name will be uploaded while creating the dispute (Johnson Travels)
merchantEmail
String
Merchant email address will be uploaded while creating the dispute (johnson.a@ippopay.com)
transactionId
String
The transaction ID that is registered while doing the transaction will be updated Trans474765400
customerName
String
Customer name will be updated while creating the dispute (Johnsonvirat)
customerEmail
String
Customer email address will be uploaded while creating the disputevirat@gmail.com
customerMobile
String
Customer mobile number will be updated while creating the dispute 95885885739787956464
amount
Number
The transactional amount will be updated 500000
disputeAmountTdrDetails
Object
The TDR type,amount,amount type is u sing
To calculate the TDR amount from dispute Amount. disputeAmountTdrDetails has fields [ type, amountType ( Type as String )].amount data type is Number.
disputeAmountTaxDetails
Object
The TAX type, amount, amount type is using To calculate the TAX amount from dispute Amount. disputeAmountTaxDetails has fields [ type, amountType ( Type as String )].amount data type is Number.
disputeAmount
Number
Dispute amount is also known as the challenged amount that is raised by the customer 1000
paymentType
Object
Payment type is used to mention the payment type the customer is used to paying the required amount , payment type includes credit card , debit card, POS. The paymentType contains 2 fields: name date type is string and code data type is String.
transactionDate
DateTime
Transaction done date is updated 2024-04-03T00:00:00.000Z
remitterBank
String
Remitter bank is also known as the customers bank through which the transaction is made (AXIS bank )
acquirerBank
Object
Merchants bank is known as the acquirer bank { name, code } (please mention this in description ). The acquirerBank contains 2 fields: name data type is string and code data type is String.
nodalAccountNo
String
Merchants settlement account is known as the nodal account 74573478734
paymentInstrumentId
String
The payments instruments such pos and carding machine have an unique ID which is known as payment instrument ID payment_84746
gatewayOrderId
String
The Id that is registered while an order is made in the respective merchants website is called as gateway order ID , Each order have an unique order ID gateway
reasonCode
String
1065
reasonCategory
String
Service level dispute
dueDate
Number
The date provided by a client to disclose the respective dispute . the due date is applicable only (20240602)
internalDueDate
Number
Internal due date refers to the final date that a resolution need to be provided for an dispute 20240418
disputeType
String
Dispute type is used to identify what kind of dispute is raised by the customer , various types of disputes are as follows fraud , chargeback , BO ,complaint (dispute)
sendEmail
Boolean
The clients mail that is registered to receive the dispute complaint is mentioned here
disputeStatus
String
The dispute status is mentioned whether the raised dispute is open, closed or reopened
comments
Array
This comments field is an array of objects, [created_by, created_id, comment, action (Type as String)]. date data type is DateTime, _id data type is objectId.
Last updated