openapi: 3.0.1
info:
version: '1.0'
title: Business Accounting Disputes API
description: "As a Revolut Business customer with a Business Account, you can use the Business API to automate your own business processes.\nSave time, reduce your costs, and avoid errors by using the Business API. \n\n:::tip[Before you get started]\nTo learn more about the Business API and its features, check the [**user guides**](https://developer.revolut.com/docs/guides/manage-accounts/introduction).\n\nYou can reach them at any time from the main navigation bar **→ Guides → Business**.\n:::\n\nYou can view accounts, manage counterparties, make payments or currency exchanges without manual effort in the Web UI:\n\n- Accounting: [Account management](https://developer.revolut.com/docs/api/business#get-account), [Accounting settings](https://developer.revolut.com/docs/api/business#tag-accounting), [Expense management](https://developer.revolut.com/docs/api/business#get-expense), [Transactions](https://developer.revolut.com/docs/api/business#get-transactions) \n- Payments: \n - [Counterparty management](https://developer.revolut.com/docs/api/business#get-counterparties)\n - Payment management: [Payment drafts](https://developer.revolut.com/docs/api/business#delete-payment-draft), [Payout links](https://developer.revolut.com/docs/api/business#get-payout-link), [Transfers](https://developer.revolut.com/docs/api/business#tag-transfers)\n - [Foreign exchange](https://developer.revolut.com/docs/api/business#tag-foreign-exchange)\n- Business team: [Card management](https://developer.revolut.com/docs/api/business#delete-card), [Card invitation management](https://developer.revolut.com/docs/api/business#update-card-invitation), [Team member management](https://developer.revolut.com/docs/api/business#delete-team-member)\n- Developer tools: [Sandbox simulations](https://developer.revolut.com/docs/api/business#tag-simulations), [Webhook management](https://developer.revolut.com/docs/api/business#tag-webhooks-v2)\n\nTo see the reference for the specific endpoints and operations of this API, browse the menu on the left.\n\n### Test the Business API\n\nYou can test the Business API in Postman by forking this collection:\n\n[](https://www.postman.com/revolut-api/workspace/revolut-developers/overview)"
contact: {}
servers:
- url: https://b2b.revolut.com/api/1.0
description: Production server (uses live data)
- url: https://sandbox-b2b.revolut.com/api/1.0
description: Sandbox server (uses test data)
tags:
- name: Disputes
description: "Endpoints that allow merchants to view customer payment disputes.\n\n It provides a robust framework with high-level states (e.g., `won`, `lost`, `needs_response`, `under_review`) and detailed substates (e.g., `lost_expired`, `pre_arbitration`, `won_pre_arbitration`, etc.) to accurately track the dispute lifecycle.\n\n Additionally, the API integrates standard dispute reason codes and human-readable descriptions, offering a customisable approach to dispute resolution that facilitates effective dispute management."
paths:
/api/disputes:
parameters:
- $ref: '#/components/parameters/Authorization'
- $ref: '#/components/parameters/Revolut-Api-Version'
get:
summary: Retrieve a dispute list
operationId: retrieveDisputeList
servers:
- description: Production server (uses live data)
url: https://merchant.revolut.com
description: "Retrieve a list of disputes associated with your merchant account. \n\n:::note\nThis endpoint is only available in **Production** environment.\n:::\n\nYou can also use the query parameters for:\n \n | Filtering | Pagination |\n | --------- | ---------- |\n | Filter the diputes that you want to retrieve, for example, only retrieve the disputes that have a specific state. <br/><br/>Parameters used for filtering:<br/><ul><li>`from_created_date`</li><li>`to_created_date`</li><li>`payment_id`</li><li>`state`</li></ul> | View the disputes without loading all of them at once, for example, return a specified number of disputes per page. <br/><br/>Parameters used for pagination: <br/><ul><li>`limit`</li><li>`from_created_date` or `to_created_date`</li></ul> |"
parameters:
- $ref: '#/components/parameters/Limit'
- $ref: '#/components/parameters/From-Created-Date'
- $ref: '#/components/parameters/To-Created-Date'
- $ref: '#/components/parameters/Dispute-State-Query'
- $ref: '#/components/parameters/Payment-Id-Query'
responses:
'200':
description: List of disputes retrieved
content:
application/json:
schema:
$ref: '#/components/schemas/Disputes'
examples:
dispute_list:
$ref: '#/components/examples/Res-Dispute-List'
'400':
description: Bad Request
content:
application/json:
schema:
$ref: '#/components/schemas/Error-v2'
example:
code: validation
message: limit must be between 1 and 500
timestamp: 1601296792533
'401':
description: Unauthorized
content:
application/json:
schema:
$ref: '#/components/schemas/Error-v2'
example:
code: unauthenticated
message: Authentication failed
timestamp: 1721049596461
security:
- Api-Key: []
tags:
- Disputes
/api/disputes/{dispute_id}:
parameters:
- $ref: '#/components/parameters/Authorization'
- $ref: '#/components/parameters/Revolut-Api-Version'
- $ref: '#/components/parameters/Dispute-Id'
get:
summary: Retrieve a dispute
operationId: retrieveDispute
servers:
- description: Production server (uses live data)
url: https://merchant.revolut.com
description: 'Retrieve the details of a specific dispute by its ID.
:::note
This endpoint is only available in **Production** environment.
:::'
responses:
'200':
description: Successful response
content:
application/json:
schema:
$ref: '#/components/schemas/Dispute'
examples:
card_dispute:
$ref: '#/components/examples/Res-Dispute-Card'
sepa_direct_debit_dispute:
$ref: '#/components/examples/Res-Dispute-Sepa-Direct-Debit'
'400':
description: Bad Request
content:
application/json:
schema:
$ref: '#/components/schemas/Error-v2'
example:
code: bad_request
message: Missing Revolut-Api-Version header
timestamp: 1601296792533
'401':
description: Unauthorized
content:
application/json:
schema:
$ref: '#/components/schemas/Error-v2'
example:
code: unauthenticated
message: Authentication failed
timestamp: 1721049596461
'404':
description: Not Found
content:
application/json:
schema:
$ref: '#/components/schemas/Error-v2'
example:
code: not_found
message: The requested resource is not found
timestamp: 1721050063886
security:
- Api-Key: []
tags:
- Disputes
/api/disputes/{dispute_id}/accept:
parameters:
- $ref: '#/components/parameters/Authorization'
- $ref: '#/components/parameters/Revolut-Api-Version'
- $ref: '#/components/parameters/Dispute-Id'
post:
summary: Accept a dispute
operationId: acceptDispute
servers:
- description: Production server (uses live data)
url: https://merchant.revolut.com
description: 'Marks a specific dispute as accepted.
After accepting a dispute, you cannot challenge it.
:::note
This endpoint is only available in **Production** environment.
:::'
responses:
'204':
description: Dispute accepted successfully
'400':
description: Bad Request
content:
application/json:
schema:
$ref: '#/components/schemas/Error-v2'
example:
code: bad_request
message: Missing Revolut-Api-Version header
timestamp: 1601296792533
'401':
description: Unauthorized
content:
application/json:
schema:
$ref: '#/components/schemas/Error-v2'
example:
code: unauthenticated
message: Authentication failed
timestamp: 1721049596461
'403':
description: Forbidden
content:
application/json:
schema:
$ref: '#/components/schemas/Error-v2'
example:
code: not_found
message: The requested operation is forbidden
timestamp: 1721050063886
'404':
description: Not Found
content:
application/json:
schema:
$ref: '#/components/schemas/Error-v2'
example:
code: not_found
message: The requested resource is not found
timestamp: 1721050063886
'422':
description: Unprocessable entity
content:
application/json:
schema:
$ref: '#/components/schemas/Error-v2'
security:
- Api-Key: []
tags:
- Disputes
/api/disputes/{dispute_id}/evidences:
parameters:
- $ref: '#/components/parameters/Authorization'
- $ref: '#/components/parameters/Revolut-Api-Version'
- $ref: '#/components/parameters/Content-Type'
- $ref: '#/components/parameters/Dispute-Id'
post:
summary: Upload evidence for a dispute
operationId: uploadDisputeEvidence
servers:
- description: Production server (uses live data)
url: https://merchant.revolut.com
description: "Allows uploading a single evidence file for a specific dispute. \n\nUse these evidences to provide proof for claims when challenging a dispute.\n\n:::warning\n**Limitations:**\n - Maximum `100` uploaded files are allowed per dispute.\n - Maximum file size: `10MB`.\n - Allowed file types: `PDF`, `PNG`, `JPEG`.\n:::\n\n:::note\nThis endpoint is only available in **Production** environment.\n:::"
requestBody:
required: true
content:
multipart/form-data:
encoding:
file:
contentType: application/pdf, image/png, image/jpeg
schema:
$ref: '#/components/schemas/Dispute-Evidence-Creation'
responses:
'201':
description: Evidence uploaded successfully
content:
application/json:
schema:
$ref: '#/components/schemas/Dispute-Evidence'
examples:
evidence_uploaded:
$ref: '#/components/examples/Res-Dispute-Evidence'
'400':
description: Bad Request
content:
application/json:
schema:
$ref: '#/components/schemas/Error-v2'
example:
code: bad_request
message: Missing Revolut-Api-Version header
timestamp: 1601296792533
'401':
description: Unauthorized
content:
application/json:
schema:
$ref: '#/components/schemas/Error-v2'
example:
code: unauthenticated
message: Authentication failed
timestamp: 1721049596461
'403':
description: Forbidden
content:
application/json:
schema:
$ref: '#/components/schemas/Error-v2'
example:
code: not_found
message: The requested operation is forbidden
timestamp: 1721050063886
'404':
description: Not Found
content:
application/json:
schema:
$ref: '#/components/schemas/Error-v2'
example:
code: not_found
message: The requested resource is not found
timestamp: 1721050063886
'422':
description: Unprocessable entity
content:
application/json:
schema:
$ref: '#/components/schemas/Error-v2'
security:
- Api-Key: []
tags:
- Disputes
/api/disputes/{dispute_id}/challenge:
parameters:
- $ref: '#/components/parameters/Authorization'
- $ref: '#/components/parameters/Revolut-Api-Version'
- $ref: '#/components/parameters/Dispute-Id'
post:
summary: Challenge a dispute
operationId: challengeDispute
servers:
- description: Production server (uses live data)
url: https://merchant.revolut.com
description: 'Allows challenging a dispute with a reason, comment and associated evidences.
Use the uploaded evidences to provide proof for the challenge.
A dispute previously accepted, cannot be challenged.
:::note
This endpoint is only available in **Production** environment.
:::'
requestBody:
required: true
content:
application/json:
schema:
$ref: '#/components/schemas/Dispute-Challenge'
examples:
challenge_min:
$ref: '#/components/examples/Req-Dispute-Challenge-Min'
challenge_with_evidence:
$ref: '#/components/examples/Req-Dispute-Challenge-With-Evidence'
responses:
'204':
description: Dispute challenged successfully
'400':
description: Bad Request
content:
application/json:
schema:
$ref: '#/components/schemas/Error-v2'
example:
code: bad_request
message: Missing Revolut-Api-Version header
timestamp: 1601296792533
'401':
description: Unauthorized
content:
application/json:
schema:
$ref: '#/components/schemas/Error-v2'
example:
code: unauthenticated
message: Authentication failed
timestamp: 1721049596461
'403':
description: Forbidden
content:
application/json:
schema:
$ref: '#/components/schemas/Error-v2'
example:
code: not_found
message: The requested operation is forbidden
timestamp: 1721050063886
'404':
description: Not Found
content:
application/json:
schema:
$ref: '#/components/schemas/Error-v2'
example:
code: not_found
message: The requested resource is not found
timestamp: 1721050063886
'422':
description: Unprocessable entity
content:
application/json:
schema:
$ref: '#/components/schemas/Error-v2'
security:
- Api-Key: []
tags:
- Disputes
components:
schemas:
Dispute-Payment-Method:
type: object
description: 'Payment method used for the original payment.
Use the `type` field to determine the specific payment method variant.'
discriminator:
propertyName: type
mapping:
apple_pay: '#/components/schemas/Dispute-Payment-Method-Apple-Pay'
apple_tap_to_pay: '#/components/schemas/Dispute-Payment-Method-Apple-Tap-To-Pay'
card: '#/components/schemas/Dispute-Payment-Method-Card'
google_pay: '#/components/schemas/Dispute-Payment-Method-Google-Pay'
revolut_pay_account: '#/components/schemas/Dispute-Payment-Method-Revolut-Pay-Account'
revolut_pay_card: '#/components/schemas/Dispute-Payment-Method-Revolut-Pay-Card'
sepa_direct_debit: '#/components/schemas/Dispute-Payment-Method-Sepa-Direct-Debit'
oneOf:
- $ref: '#/components/schemas/Dispute-Payment-Method-Apple-Pay'
- $ref: '#/components/schemas/Dispute-Payment-Method-Apple-Tap-To-Pay'
- $ref: '#/components/schemas/Dispute-Payment-Method-Card'
- $ref: '#/components/schemas/Dispute-Payment-Method-Google-Pay'
- $ref: '#/components/schemas/Dispute-Payment-Method-Revolut-Pay-Account'
- $ref: '#/components/schemas/Dispute-Payment-Method-Revolut-Pay-Card'
- $ref: '#/components/schemas/Dispute-Payment-Method-Sepa-Direct-Debit'
Disputes:
type: array
description: An array containing a list of disputes.
items:
$ref: '#/components/schemas/Dispute'
Sepa-Direct-Debit-Debtor-Name:
type: string
description: The full name of the debtor as provided in the mandate.
Sepa-Direct-Debit-Debtor-Iban-Last-Four:
type: string
description: The last four digits of the debtor's IBAN.
minLength: 4
maxLength: 4
Card-Last-Four:
type: string
minLength: 4
maxLength: 4
description: The last four digits of the payment card number.
Dispute-Payment-Amount:
type: integer
description: 'Amount of the original payment expressed in minor currency units, according to the [ISO 4217 standard](https://en.wikipedia.org/wiki/ISO_4217). For example, `7034` in `EUR` corresponds to €70.34.
:::info
Conversion between major and minor units varies by currency. For instance, `100` minor units equal £1.00 in `GBP`, whereas in `ISK` they represent 100 units. For more details, see the [ISO 4217 standard](https://en.wikipedia.org/wiki/ISO_4217).
:::'
Dispute:
type: object
properties:
id:
type: string
format: uuid
description: Unique identifier of the dispute.
state:
type: string
enum:
- needs_response
- under_review
- won
- lost
description: 'Represents the state of the dispute.
It indicates either the final outcome of the dispute or if further action is required.
| Parameter value | Description |
| --------------- | ----------- |
| `needs_response` | Indicates that the dispute requires a response or action from the merchant. |
| `under_review` | Indicates that the dispute is currently under review, and the outcome is pending. |
| `won` | Indicates that the dispute has been resolved in favor of the merchant. |
| `lost` | Indicates that the dispute has been resolved against the merchant. |'
substate:
type: string
enum:
- arbitration
- lost_accepted
- lost_arbitration
- lost_expired
- lost_pre_arbitration
- lost_representment
- new
- pre_arbitration
- representment
- won_arbitration
- won_pre_arbitration
- won_representment
- won_reversal
description: 'Provides additional granularity about the dispute state.
It details the progression of the dispute process, showing the current stage or phase.
| Parameter value | Description |
| --------------- | ----------- |
| `new` | The dispute has been recently created and is in the initial phase, awaiting further processing. |
| `lost_expired` | The dispute has been lost due to expiration, likely because the merchant did not respond within the required timeframe. |
| `pre_arbitration` | The dispute is in the pre-arbitration phase, where preliminary evidence is being gathered before a formal arbitration process. |
| `won_pre_arbitration`| The merchant secured a win during the pre-arbitration phase based on the evidence provided. |
| `lost_pre_arbitration` | The dispute was lost during the pre-arbitration phase, indicating that the preliminary review did not favor the merchant. |
| `lost_accepted` | The loss has been accepted as final, implying that no further contestation is likely or needed. |
| `arbitration` | The dispute has escalated to the arbitration stage, where a neutral third party is reviewing the evidence. |
| `won_arbitration` | The merchant won the dispute during the arbitration process. |
| `lost_arbitration` | The merchant lost the dispute during the arbitration process. |'
created_at:
type: string
format: date-time
description: '[ISO 8601](https://en.wikipedia.org/wiki/ISO_8601) date and time when the dispute was created.'
updated_at:
type: string
format: date-time
description: '[ISO 8601](https://en.wikipedia.org/wiki/ISO_8601) date and time when the dispute was last updated.'
response_due_date:
type: string
format: date-time
description: "[ISO 8601](https://en.wikipedia.org/wiki/ISO_8601) date and time until when the merchant needs to respond to the dispute.\n\nThe response time by default is 15 days after the dispute is created. If no response is provided by this date, the dispute transitions to:\n - `state: lost`\n - `substate: lost_expired` "
reason_code:
type: string
description: "Dispute reason code from the payment scheme, following standard formats defined by individual providers.\n\n:::info\nFor complete, official lists of dispute codes, see: \n- **Visa**: [Visa Core Rules and Visa Product and Service Rules](https://corporate.visa.com/content/dam/VCOM/download/about-visa/visa-rules-public.pdf) \n- **Mastercard**: [Chargeback Guide - Merchant Edition](https://www.mastercard.com/content/dam/public/mastercardcom/na/global-site/documents/chargeback-guide.pdf)\n- **American Express**: [Chargeback Codes](https://www.americanexpress.com/content/dam/amex/au/en/merchant/static/chargebackcodeguide.pdf)\n:::"
reason_description:
type: string
description: Provides a human-readable explanation for the dispute reason codes.
amount:
type: integer
description: 'Disputed amount expressed in minor currency units, according to the [ISO 4217 standard](https://en.wikipedia.org/wiki/ISO_4217). For example, `7034` in `EUR` corresponds to €70.34.
:::info
Conversion between major and minor units varies by currency. For instance, `100` minor units equal £1.00 in `GBP`, whereas in `ISK` they represent 100 units. For more details, see the [ISO 4217 standard](https://en.wikipedia.org/wiki/ISO_4217).
:::'
currency:
$ref: '#/components/schemas/Currency'
payment:
$ref: '#/components/schemas/Dispute-Payment'
Currency:
type: string
format: ISO 4217
minLength: 3
maxLength: 3
description: '[ISO 4217](https://en.wikipedia.org/wiki/ISO_4217) currency code in upper case.
:::info
For more information about the supported currencies, see: [Help Center](https://help.revolut.com/business/help/merchant-accounts/payments/in-which-currencies-can-i-accept-payments/).
:::'
Dispute-Payment-Method-Apple-Tap-To-Pay:
type: object
description: Object containing details of a payment made via Apple Tap to Pay.
properties:
type:
$ref: '#/components/schemas/Dispute-Payment-Method-Type'
required:
- type
Error-v2:
title: Error
type: object
properties:
code:
type: string
description: 'An identifier that can be used to determine what went wrong.
Error codes are not globally unique, but uniqueness is guaranteed within endpoints.'
message:
type: string
description: Some human readable text describing what went wrong.
timestamp:
type: integer
description: The [UNIX timestamp](https://www.unixtimestamp.com/) of the date and time the error happened.
Dispute-Payment-Created-At:
type: string
format: date-time
description: '[ISO 8601](https://en.wikipedia.org/wiki/ISO_8601) date and time when the original disputed payment was created.'
Dispute-Evidence-Creation:
type: object
properties:
file:
type: string
format: binary
description: 'The single evidence file to upload.
The client must ensure this part has its own `Content-Type` header specifying the media type of the file (e.g., `application/pdf`, `image/png`, `image/jpeg`).
Must be one of the allowed types: `PDF`, `PNG`, `JPEG`.'
required:
- file
Dispute-Payment-Order-Id:
type: string
format: uuid
description: The ID of the order linked to the original disputed payment.
Dispute-Payment-Method-Google-Pay:
type: object
description: Object containing details of a card used via Google Pay.
properties:
type:
$ref: '#/components/schemas/Dispute-Payment-Method-Type'
card_brand:
$ref: '#/components/schemas/Card-Brand-v2'
card_last_four:
$ref: '#/components/schemas/Card-Last-Four'
required:
- type
Dispute-Payment-Method-Revolut-Pay-Account:
type: object
description: Object containing details of a payment made via Revolut Pay account.
properties:
type:
$ref: '#/components/schemas/Dispute-Payment-Method-Type'
required:
- type
Dispute-Payment-Method-Type:
type: string
enum:
- apple_pay
- apple_tap_to_pay
- card
- google_pay
- revolut_pay_account
- revolut_pay_card
- sepa_direct_debit
description: 'Type of the payment method used for the original payment.
Available values:
| Payment method `type` | Description |
| --------------------- | ----------- |
| `apple_pay` | The customer paid the order using Apple Pay. |
| `apple_tap_to_pay` | The customer paid the order using Apple Tap to Pay. |
| `card` | The customer paid the order using their credit or debit card. |
| `google_pay` | The customer paid the order using Google Pay. |
| `revolut_pay_card` | The customer paid the order via Revolut Pay using their credit or debit card. |
| `revolut_pay_account` | The customer paid the order via Revolut Pay using their Revolut account. |
| `sepa_direct_debit` | The customer paid the order via SEPA Direct Debit. |'
Dispute-Payment:
type: object
description: Object containing the details of the original payment associated with the dispute.
properties:
id:
$ref: '#/components/schemas/Dispute-Payment-Id'
order_id:
$ref: '#/components/schemas/Dispute-Payment-Order-Id'
created_at:
$ref: '#/components/schemas/Dispute-Payment-Created-At'
arn:
$ref: '#/components/schemas/Dispute-Payment-Arn'
amount:
$ref: '#/components/schemas/Dispute-Payment-Amount'
currency:
$ref: '#/components/schemas/Currency'
payment_method:
$ref: '#/components/schemas/Dispute-Payment-Method'
Dispute-Payment-Method-Revolut-Pay-Card:
type: object
description: Object containing details of a card used via Revolut Pay.
properties:
type:
$ref: '#/components/schemas/Dispute-Payment-Method-Type'
card_brand:
$ref: '#/components/schemas/Card-Brand-v2'
card_last_four:
$ref: '#/components/schemas/Card-Last-Four'
required:
- type
Dispute-Challenge-Reason:
type: string
description: The reason for challenging the dispute.
enum:
- product_already_delivered
- refund_already_issued
- disagree_with_customers_claim
example: refund_already_issued
Dispute-Payment-Id:
type: string
format: uuid
description: The ID of the original payment that was disputed.
Dispute-Challenge-Comment:
type: string
description: Additional explanation or comment for the challenge, if needed.
example: Refund PDF attached as evidence.
maxLength: 250
Dispute-Challenge:
type: object
required:
- reason
- evidences
properties:
reason:
$ref: '#/components/schemas/Dispute-Challenge-Reason'
comment:
$ref: '#/components/schemas/Dispute-Challenge-Comment'
evidences:
$ref: '#/components/schemas/Dispute-Challenge-Evidences'
Dispute-Payment-Method-Card:
type: object
description: Object containing details of the card used for the payment.
properties:
type:
$ref: '#/components/schemas/Dispute-Payment-Method-Type'
card_brand:
$ref: '#/components/schemas/Card-Brand-v2'
card_last_four:
$ref: '#/components/schemas/Card-Last-Four'
required:
- type
Dispute-Payment-Method-Apple-Pay:
type: object
description: Object containing details of a card used via Apple Pay.
properties:
type:
$ref: '#/components/schemas/Dispute-Payment-Method-Type'
card_brand:
$ref: '#/components/schemas/Card-Brand-v2'
card_last_four:
$ref: '#/components/schemas/Card-Last-Four'
required:
- type
Dispute-Payment-Method-Sepa-Direct-Debit:
type: object
description: Object containing details of a SEPA Direct Debit payment.
properties:
type:
$ref: '#/components/schemas/Dispute-Payment-Method-Type'
debtor_iban_last_four:
$ref: '#/components/schemas/Sepa-Direct-Debit-Debtor-Iban-Last-Four'
debtor_name:
$ref: '#/components/schemas/Sepa-Direct-Debit-Debtor-Name'
mandate_reference:
$ref: '#/components/schemas/Sepa-Direct-Debit-Mandate-Reference'
required:
- type
Card-Brand-v2:
type: string
description: The brand of the payment card.
enum:
- visa
- mastercard
- american_express
Dispute-Payment-Arn:
type: string
description: 'Acquirer Reference Number (ARN) of the original payment.
:::note
Only returned for payments made by a card.
:::'
Sepa-Direct-Debit-Mandate-Reference:
type: string
description: The unique mandate reference generated by Revolut. Include this in pre-debit notifications sent to your customers.
Dispute-Challenge-Evidences:
type: array
description: 'A list of IDs of previously uploaded evidence files to associate with this challenge.
:::warning
Each evidence ID can only be used for **a single challenge**. This means, that evidences already assigned to a challenge **cannot be reused** for other challenges.
:::'
items:
type: string
format: uuid
description: ID of a previously uploaded evidence file.
minItems: 1
maxItems: 10
uniqueItems: true
example:
- 121ac27c-b00a-44d0-9120-efeeec7c912d
- 0010e98d-0653-4dbe-8a4f-70cd5e9491f2
Dispute-Evidence:
type: object
properties:
id:
type: string
format: uuid
description: The ID of the uploaded evidence.
example: ad2ca3d0-67e9-4cea-b455-e39dd319113d
required:
- id
examples:
Res-Dispute-Card:
summary: Dispute for a card payment
value:
id: fccc53e9-00e0-4847-9d54-6938e9cdd3ef
state: lost
substate: lost_accepted
created_at: '2025-03-12T07:00:00.000000Z'
updated_at: '2025-03-13T10:00:00.000000Z'
response_due_date: '2025-03-15T12:00:00.000000Z'
reason_code: '50'
reason_description: Fr
# --- truncated at 32 KB (42 KB total) ---
# Full source: https://raw.githubusercontent.com/api-evangelist/revolut/refs/heads/main/openapi/revolut-disputes-api-openapi.yml