---
title: "Provide evidence for FRAUD"
method: POST
path: "/v1/disputes/{ratepay_dispute_id}/evidences/fraud"
---

# Provide evidence for FRAUD

`POST /v1/disputes/{ratepay_dispute_id}/evidences/fraud`

## Request

- Base URL: `https://api-integration.ratepay.com/dispute/management`
- URL: `https://api-integration.ratepay.com/dispute/management/v1/disputes/{ratepay_dispute_id}/evidences/fraud`
- Auth: HTTP bearer

Endpoint to provide evidence for the FRAUD request for information.

A valid JWT token is required in order to perform requests against this API.
See [Ratepay Authentication API](/apis/authentication/openapi/authentication_api) specification.

## Path parameters

- `ratepay_dispute_id` string, required: Ratepay dispute ID

## Headers

- `Authorization` string, required

## Request body `multipart/form-data`

- FraudContent
  - `evidence` FullEvidence, required
    - `ratepay_transaction_id` string, required: Ratepay transaction ID.
    - `case_details` string: All details available to the shop regarding the return of goods. This information is required if no delivery information or additional evidence has been provided.
    - `delivery_information` DeliveryInformation[]: List of objects containing delivery details. This information is required if no case details or additional evidence has been provided.
      - `carrier_name` 'DHL' | 'UPS' | 'POST_AUSTRIA' | 'DPD' | 'SWISS_POST' | 'GLS' | 'ASENDIA' | 'HERMES_LOGISTICS' | 'FEDEX' | 'OTHER_WITH_TRACKING' | 'OTHER_WITHOUT_TRACKING', required: Name of the shipping carrier used by the shop for the capture.
      - `tracking_number` string, required: Tracking number for order delivery. This field is optional for carrier_name: 'OTHER_WITHOUT_TRACKING'
      - `status` 'PENDING' | 'DELIVERED' | 'RETURNED' | 'LOST': Current status of delivery.
      - `date` string, date: Date when goods were delivered. Must be in the format YYYY-MM-DD, in accordance with [ISO 8601](https://en.wikipedia.org/wiki/ISO_8601).
      - `address` string: Delivery address. Country code in accordance with [ISO-639-1](https://en.wikipedia.org/wiki/List_of_ISO_639-1_codes)
      - `note` string: Name of the delivery note file to be uploaded. The value will be used as a key to the binary file in the request. The delivery note is required only in case of multiple captures, if the captures did not contain item information.
  - `additional_evidence` string, binary: File with additional evidence. Allowed types are '.zip', '.pdf', '.jpg', '.png', '.gif', '.txt'. Maximum file size is 10 MB.
  - `file1` string, binary: Information about the items included in the shipment. Key name must correspond to the actual value of the `evidence` field. Allowed types are '.zip', '.pdf', '.jpg', '.png', '.gif', '.txt'. Maximum file size is 10 MB.

## Response `201`

Evidence was created.

## Other responses

- `404`: Incorrect path parameters or invalid URL.
- `409`: Unable to process request.
- `422`: Unable to process request.

---

[API](https://skmtc.dev/ratepay/apis/dispute-openapi-specification.md) - [All operations](https://skmtc.dev/ratepay/apis/dispute-openapi-specification/llms.txt) - [OpenAPI document](https://skmtc.dev/ratepay/apis/dispute-openapi-specification/revisions/bfa4739d0187?raw)