Service Endpoint

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

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.

Reading the history

Each event is one step the scheme reported: the dispute being raised, our defense being submitted, the issuer escalating to pre-arbitration, the final ruling. Initiator says which side moved (issuer or acquirer). The current state of the case is always the first event; GetDispute gives the same state together with the deadline.

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
disputeId Yes int The dispute id (Id) returned by SearchDisputes

Response Fields

Parameter Type Description
Array of event objects, newest first. On an unknown or foreign id the call fails with 'Dispute not found.'
Stage string The lifecycle stage the event belongs to (chargeback, chargebackResponse, preArbitration, ...)
Status string The status the dispute moved to with this event
EventDateUtc string ISO-8601 UTC. When the network reported the event
Initiator string Who moved the case: issuer or acquirer
Details string The scheme's comment on the event, when there is one

Request example

Code Example
{
	"disputeId": 1043
}

Response example

Code Example
{
  "d": [
    {
      "Stage": "chargebackResponse",
      "Status": "awaitingResponse",
      "EventDateUtc": "2026-09-12T14:03:10.0000000Z",
      "Initiator": "acquirer",
      "Details": "Defense submitted with 2 documents"
    },
    {
      "Stage": "chargeback",
      "Status": "evidenceSubmitted",
      "EventDateUtc": "2026-09-10T08:41:55.0000000Z",
      "Initiator": "acquirer",
      "Details": null
    },
    {
      "Stage": "chargeback",
      "Status": "received",
      "EventDateUtc": "2026-09-01T09:12:44.0000000Z",
      "Initiator": "issuer",
      "Details": "Reason 13.1 Merchandise/Services Not Received"
    }
  ]
}
Authentication

Login first to get the credentials token.
Get Dispute

The current state and the deadline.
Search Disputes

List the disputes raised against you.