Endpoints that allow merchants to view customer payment disputes. 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. Additionally, the API integrates standard dispute reason codes and human-readable descriptions, offeringa customisable approach to dispute resolution that facilitates effective dispute management.
Revolut Disputes API is one of 46 APIs that Revolut publishes on the APIs.io network, described by a machine-readable OpenAPI specification.
Tagged areas include Disputes. The published artifact set on APIs.io includes an OpenAPI specification.
This API exposes
5 operations
across 5 paths,
and defines 30 schemas.
It is described by OpenAPI 3.0.1, at version 1.0.
Requests are made against 2 base URLs: https://b2b.revolut.com/api/1.0, https://sandbox-b2b.revolut.com/api/1.0.
5 operations5 paths30 schemas2 GET3 POST
Metadata
The identity and technical contract details declared by the specification.
Specification
OpenAPI 3.0.1
API Version
1.0
Base URL
https://b2b.revolut.com/api/1.0
Authentication
HTTP Bearer
Resource Areas
1
Authentication & Security 1
Revolut Disputes API declares
1 security scheme
for authenticating requests.
It accepts HTTP bearer tokens (AccessToken).
AccessToken — Each Business API request must contain an authorization header in the following format to make a call: Bearer . The access token will be obtained the first tim…
Paths & Operations 5
Across 5 paths, the API surfaces 5 operations — 2 GET, 3 POST. Each is listed below with its method, path, parameters, and response codes.
Disputes 5
Endpoints that allow merchants to view customer payment disputes. It provides a robust framework with high-level states (e.g., won, lost, needsresponse, underreview) and detailed…
The contract defines 30 schemas that model the data the API accepts and returns. The most detailed are Dispute (11 properties), Dispute-Payment (7 properties), Dispute-Payment-Method-Sepa-Direct-Debit (4 properties), Dispute-Payment-Method-Card (3 properties). Each schema is shown below with its type and property counts.
Dispute-Payment-Method
object
Payment method used for the original payment. Use the type field to determine the specific payment method variant.
Disputes
array
An array containing a list of disputes.
Sepa-Direct-Debit-Debtor-Name
string
The full name of the debtor as provided in the mandate.
Sepa-Direct-Debit-Debtor-Iban-Last-Four
string
The last four digits of the debtor's IBAN.
Card-Last-Four
string
The last four digits of the payment card number.
Dispute-Payment-Amount
integer
Amount of the original payment expressed in minor currency units, according to the [ISO 4217 standard](https://en.wikipedia.org/wiki/ISO4217). For example, 703…
Dispute
object
11 properties
Currency
string
[ISO 4217](https://en.wikipedia.org/wiki/ISO4217) currency code in upper case. :::info For more information about the supported currencies, see: [Help Center](…
Dispute-Payment-Method-Apple-Tap-To-Pay
object
Object containing details of a payment made via Apple Tap to Pay.
1 property1 required
Error-v2
object
3 properties
Dispute-Payment-Created-At
string
[ISO 8601](https://en.wikipedia.org/wiki/ISO8601) date and time when the original disputed payment was created.
Dispute-Evidence-Creation
object
1 property1 required
Dispute-Payment-Order-Id
string
The ID of the order linked to the original disputed payment.
Dispute-Payment-Method-Google-Pay
object
Object containing details of a card used via Google Pay.
3 properties1 required
Dispute-Payment-Method-Revolut-Pay-Account
object
Object containing details of a payment made via Revolut Pay account.
1 property1 required
Dispute-Payment-Method-Type
string
Type of the payment method used for the original payment. Available values: | Payment method type | Description | | --------------------- | ----------- | | app…
Dispute-Payment
object
Object containing the details of the original payment associated with the dispute.
7 properties
Dispute-Payment-Method-Revolut-Pay-Card
object
Object containing details of a card used via Revolut Pay.
3 properties1 required
Dispute-Challenge-Reason
string
The reason for challenging the dispute.
Dispute-Payment-Id
string
The ID of the original payment that was disputed.
Dispute-Challenge-Comment
string
Additional explanation or comment for the challenge, if needed.
Dispute-Challenge
object
3 properties2 required
Dispute-Payment-Method-Card
object
Object containing details of the card used for the payment.
3 properties1 required
Dispute-Payment-Method-Apple-Pay
object
Object containing details of a card used via Apple Pay.
3 properties1 required
Dispute-Payment-Method-Sepa-Direct-Debit
object
Object containing details of a SEPA Direct Debit payment.
4 properties1 required
Card-Brand-v2
string
The brand of the payment card.
Dispute-Payment-Arn
string
Acquirer Reference Number (ARN) of the original payment. :::note Only returned for payments made by a card. :::
Sepa-Direct-Debit-Mandate-Reference
string
The unique mandate reference generated by Revolut. Include this in pre-debit notifications sent to your customers.
Dispute-Challenge-Evidences
array
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…
Dispute-Evidence
object
1 property1 required
Specification
The full machine-readable OpenAPI contract behind this narrative.
