Add a Document

post

https://prod.emea.api.fiservapps.com/sandbox/exp/v1/disputes/{disputeId}/document

This endpoint can be used to attach additional documents to the Dispute Case. One document per API call is allowed.

Recent Requests

Time	Status	User Agent
Retrieving recent requests…

Loading…

Path Params

disputeId

int64

required

19000101000000 to 99991231999999

Unique case identifier assigned to the dispute.

Body Params

evidence

file

required

Evidence such as photographs or emails, to prove a link between the person receiving the merchandise or services and the cardholder, or to prove that the cardholder disputing the transaction is in possession of the merchandise and/or is using the services. Supported formats: JPG, JPEG, TIF, TIFF, PDF, DOCX, DOC. Maximum supported file size is 5MB.

templateCategoryCode

string

required

length between 3 and 3

The category of the letter template/attachment attached to the chargeback case.

documentNote

string

length between 0 and 2000

Additional internal notes for the attachment purpose.

tcn

string

required

Transaction Control Number (used to control concurrent actions and avoid change clashes)

networkFormType

string

enum

required

Indicates the name of the network form that is associated with the letter or attachment and belongs to the card scheme. Valid values are VISA_NETWORK_FORM, MASTERCARD_NETWORK_FORM and JCB_NETWORK_FORM.

Allowed:

Headers

Institution-Number

string

length between 8 and 8

Institution number (8-digit number) associated with the merchant. This information defines the acquirer for the merchant. If a consumer is granted access to this API for multiple institutions, this field must be populated. If access is for only one institution, the API will automatically determine this value, making it optional for the client.

Message-Signature

string

required

Optional security header. Used to ensure the request has not been tampered with during transmission. The Message-Signature is the Base64 encoded HMAC hash (SHA256 algorithm with the API Secret as the key.) For more information, refer to the supporting documentation on the Developer Portal.

Responses

Language

Credentials

Header

URL

Loading…

Response

Click Try It! to start a request and see the response here! Or choose an example:

application/json

201Document attached successfully to the Case Id.

400Bad request

401Unauthorised

403Forbidden

404Not found

500Internal server error

API Products

Point of Sale

Developer

Resources