PSPs > API Reference > Endpoints > Dispute

Dispute

Jump to Response

POST api.ravelin.com/psp/dispute

dispute object

One of the following:

Show definition

amount integer optional

The amount under dispute, in the currency's basic units.

arn string optional

The Acquirer Reference Number (ARN) is the acquirer's reference for the disputed transaction. It must match the ARN provided on the disputed transaction.

category string optional

Category mapped to the one given by the cardholder for disputing the transaction.

currency string optional

The currency of the amount of this dispute, as an ISO 4217 currency code.

disputeId string required

A unique reference for the dispute.

disputeTime integer optional

Time at which the dispute was created, used for reporting. A unix timestamp preferably as an integer count of milliseconds since 1970-01-01T00:00 UTC (nanoseconds are also accepted).

gateway string optional

The gateway responsible for processing the disputed transaction.

gatewayReference string optional

If the transactionId for the disputed transaction is not available then you must provide the gateway reference associated with the transaction.

liabilityShifted boolean optional

Whether liability for this dispute was shifted to the issuer. See Liability Shift.

outcome string optional

Outcome of the dispute. Use ACCEPTED for disputes you have accepted and decided not to defend, WON for disputes you have successfully defended, EXPIRED for disputes that have timed out and LOST for disputes ruled in favour of the cardholder. Omit outcome if the dispute is still open.

reason string optional

Reason given by the cardholder for disputing the transaction.

stage string required

Stage of the dispute. A dispute with the stage EARLY_FRAUD_WARNING or REQUEST_FOR_INFORMATION is not considered a chargeback for reporting purposes. See our Sending Disputes guide to learn more.

transactionId string optional

Identifier for the disputed transaction. Must match the transactionId provided on the disputed transaction.

timestamp integer required

A unix timestamp preferably as an integer count of milliseconds since 1970-01-01T00:00 UTC (nanoseconds are also accepted).

POST https://api.ravelin.com/psp/dispute HTTP/1.1
Authorization: token ...
Content-Type: application/json

{
  "dispute": {
    "amount": 1337,
    "arn": "string",
    "currency": "GBP",
    "disputeId": "string",
    "disputeTime": 1512828988826,
    "gateway": "braintree",
    "gatewayReference": "string",
    "liabilityShifted": true,
    "outcome": "LOST",
    "reason": "fraud",
    "stage": "CHARGEBACK",
    "transactionId": "string",
    "property1": null,
    "property2": null
  },
  "timestamp": 1667387532297,
  "property1": null,
  "property2": null
}

Response

status integer optional

HTTP response status code.

timestamp integer optional

UNIX timestamp when Ravelin finished handling the request

HTTP/1.1 200 OK
Content-Type: application/json

{
  "status": 200,
  "timestamp": 1667387532297
}

Feedback

Was this page helpful?