Service Endpoint

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

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.

Defend or accept

defend asks us to contest the chargeback with the evidence on the ticket. If the network rules in your favour the funds come back; if it rules against you the case may move to pre-arbitration, where further fees apply. accept closes the case in the cardholder's favour and stops any further fees - the right call when the customer is right, when the evidence is thin, or when the amount is below what a defense costs you. Use the note to explain your reasoning; it is read by the person deciding. Accepting liability and submitting the defense are not exposed on this API - they are done by our team on the same ticket, and their reply reaches you there (Support.svc/GetTicketMessages).

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. The dispute must still be open
recommendation Yes string defend or accept
note No string Your reasoning, or anything the decision maker should know - up to a few paragraphs

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.'
Number string Not used by this call

Request example

Code Example
{
	"disputeId": 1043,
	"recommendation": "defend",
	"note": "Delivered and signed for on 3 Sep; tracking and the signed POD are attached to the ticket."
}

Response example

Code Example
{
  "d": {
    "Code": 0,
    "IsSuccess": true,
    "Key": "Success",
    "Message": null,
    "Number": null
  }
}
Authentication

Login first to get the credentials token.
Upload Evidence

Attach the documents before you recommend.
Dispute Events

Follow the case after our decision.