Service Endpoint

POST https://webservices.coriunder.cloud/v2/disputes.svc/SearchDisputes

Who can call it

Every dispute call acts on the logged-in merchant resolved from the credentials token (login with userRole 20, 21 or an API user) and is scoped to that merchant. A dispute that belongs to somebody else answers "Dispute not found." rather than a permission error, so ids cannot be enumerated. Read calls accept a read-only application token.

How a dispute is handled

  1. We receive the dispute from the card network and open a support ticket for it. The ticket is the workspace: everything about the case - evidence, your recommendation, our decision and the network's verdict - is posted there.
  2. You review it with SearchDisputes and GetDispute. Headline and WhatWeNeed say what the case needs from you; ActionDueUtc says by when.
  3. You add evidence with UploadEvidence (invoices, proof of delivery, correspondence, refund receipts) and make a recommendation - defend or accept - with PostRecommendation.
  4. Our disputes team decides whether to defend or accept and submits the response to the network. The decision is posted on the ticket as a reply from us.
  5. The network rules. Stage and Status move (chargebackResponse, preArbitration, ...) until the dispute closes as won, lost, accepted or expired. GetDisputeEvents lists every step as the scheme reported it.

The deadline

ActionDueUtc is the card scheme's deadline for the current stage of the dispute. It is set by Visa or Mastercard, not by us, and it cannot be extended. A dispute that passes it without a response is closed by the network as lost. Read it on every dispute you show and act before it - as a rule of thumb send evidence at least 48 hours before the deadline so that we can review and submit the defense in time.

Request Headers

Parameter Mandatory Type Description
Content-Type Yes string application/json
applicationToken Yes string The applicationToken provided to you by support in order to access the service.
CredentialsHeaderName Yes string The value of "CredentialsToken" returned from the Authentication call.
Signature Yes string The signature created from the values sent in the body of the request - sample script
												 hash = CryptoJS.SHA256(pm.request.body.raw + pm.collectionVariables.get('salt'));
    signature = CryptoJS.enc.Base64.stringify(hash)
    pm.variables.set("Signature", "bytes-SHA256, " + signature).

Request Fields

Parameter Mandatory Type Description
filter
OnlyOpen No boolean true returns only disputes the card network has not closed yet
OnlyNeedingAction No boolean true returns only disputes still waiting for your evidence or recommendation - use it for a work queue
Stage No string Limit to one lifecycle stage: chargeback, chargebackResponse, preArbitration, preArbitrationResponse, arbitration, rapidDisputeResolution, collaboration, collaborationResponse, requestForInformation
Status No string Limit to one status, for example received, evidenceSubmitted, awaitingResponse, closedWon, closedLost
TransactionId No int Only disputes raised against this platform transaction id
sortAndPage
PageNumber No int The page to return, starting at 1
PageSize No int Results per page. Defaults to 50, capped at 200

Response Fields

Parameter Type Description
Code int Result code
IsSuccess boolean Defines whether the service call was processed successfully or not
Key string Result key ("Success", "Error", etc.)
Message string Result message - on failure the reason, for example 'Dispute not found.'
Disputes - array of dispute objects, soonest ActionDueUtc first
Id int The dispute id on the platform - use it for GetDispute, GetDisputeEvents, UploadEvidence and PostRecommendation
ProviderKey string The dispute key at the card processor
TransactionId int The platform transaction the dispute was raised against, when it was matched. Null when unmatched
ChargeKey string The processor charge key. Several disputes can share one charge - they are the same case at different stages
Arn string Acquirer Reference Number of the disputed charge
Network string visa, mastercard
Stage string Where the case is in the scheme lifecycle: chargeback, chargebackResponse, preArbitration, preArbitrationResponse, arbitration, rapidDisputeResolution, collaboration, collaborationResponse, requestForInformation
Status string received, evidenceSubmitted, evidenceRejected, defenseInitiated, defenseFailed, acceptanceInitiated, acceptanceFailed, awaitingResponse, closedWon, closedLost, closedAccepted, closedExpired, reversed, withdrawn
IsOpen boolean True while the card network has not closed the dispute
ReasonCode string The scheme reason code (for example 10.4, 4853)
ReasonCategory string Fraud, Authorization, Processing Error, Cardholder Disputes
ReasonDescription string The reason code in plain words
Amount decimal The disputed amount in major units of Currency (12.50)
Currency string ISO currency code of the disputed amount
DisputeDateUtc string ISO-8601 UTC. When the network raised the dispute
ActionDueUtc string ISO-8601 UTC. The card scheme's deadline for the current stage. A dispute that passes it without a response closes as lost - surface it prominently
NeedsMerchantAction boolean True while you can still add evidence or a recommendation
Headline string What the dispute needs from you, in plain words
WhatWeNeed string The specific ask (documents, a decision), or null
TicketId int The support ticket that is this dispute's workspace. Evidence, your recommendation and our decision all live on it - read it with Support.svc/GetTicket
TicketNumber string The ticket's display number
CreatedUtc string ISO-8601 UTC. When the platform first recorded the dispute

Request example

Code Example
{
	"filter": {
		"OnlyOpen": true,
		"OnlyNeedingAction": true,
		"Stage": null,
		"Status": null,
		"TransactionId": null
	},
	"sortAndPage": {
		"PageNumber": 1,
		"PageSize": 50
	}
}

Response example

Code Example
{
  "d": {
    "Code": 0,
    "IsSuccess": true,
    "Key": "Success",
    "Message": null,
    "Number": null,
    "Disputes": [
      {
        "Id": 1043,
        "ProviderKey": "dsp_3f9c2a7e",
        "TransactionId": 5812234,
        "ChargeKey": "chg_8b21e0d4",
        "Arn": "74567823123456789012345",
        "Network": "visa",
        "Stage": "chargeback",
        "Status": "received",
        "IsOpen": true,
        "ReasonCode": "13.1",
        "ReasonCategory": "Cardholder Disputes",
        "ReasonDescription": "Merchandise/Services Not Received",
        "Amount": 129.90,
        "Currency": "EUR",
        "DisputeDateUtc": "2026-09-01T09:12:44.0000000Z",
        "ActionDueUtc": "2026-09-21T23:59:59.0000000Z",
        "NeedsMerchantAction": true,
        "Headline": "Chargeback received - evidence needed by 21 Sep 2026",
        "WhatWeNeed": "Proof of delivery or of the service being rendered, and your recommendation",
        "TicketId": 7712,
        "TicketNumber": "T-007712",
        "CreatedUtc": "2026-09-01T09:15:02.0000000Z"
      }
    ]
  }
}
Authentication

Login first to get the credentials token.
Get Dispute

Read one dispute with its deadline and what it needs.
Upload Evidence

Add the documents that support your case.