Service Endpoint

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

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.

What makes good evidence

The card schemes accept PDF, JPEG and TIFF. Send what answers the reason code: for "not received" a signed proof of delivery or a service log with the cardholder's details; for "fraud" the AVS/CVV and 3-D Secure results plus anything tying the cardholder to the order; for "not as described" the product page and your correspondence with the customer; for "credit not processed" the refund receipt or your refund policy as shown at checkout. One clear document beats ten. Upload before the deadline in ActionDueUtc - evidence that arrives after it cannot be used.

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
fileItemTypeId No byte The document type from your file-type list, or 0 for none
fileName Yes string The file name including its extension (.pdf, .jpg, .tif)
base64Content Yes string The file content, base64 encoded

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,
	"fileItemTypeId": 0,
	"fileName": "proof-of-delivery-2005843394.pdf",
	"base64Content": "JVBERi0xLjQKJcOkw7zDtsOfCjIgMCBvYmoKPDwvTGVuZ3RoIDMgMCBSL0ZpbHRlci9GbGF0ZURlY29kZT4+..."
}

Response example

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

Login first to get the credentials token.
Recommendation

After the evidence, tell us whether to defend or accept.
Get Dispute

Check the deadline before you upload.