Chargeback

Latest known stage of one dispute raised by a cardholder against a payment of the account. A disputed payment has one chargeback. The dashboard shows chargebacks on the Disputes page.

type Chargeback {
  id: ID!
  accountId: ID!
  checkoutId: ID!
  paymentMethod: String!
  transactionType: String!
  postingDate: String!
  origTransactionDate: String!
  origTransactionCurrency: String!
  origTransactionAmount: Int!
  cbkCurrency: String!
  cbkAmount: Int!
  providerReferenceId: String!
  internalId: String!
  arn: String
  reasonCode: String
  reasonDescription: String
  workByDate: String
  disputeStatus: DisputeStatus!
  disputeDate: String
  disputeLanguage: String
  cardScheme: CardBrand
  representmentStatus: RepresentmentStatus
  createdAt: String!
  updatedAt: String
}

Fields

Chargeback.id ● ID! non-null scalar

Identifier of the chargeback (UUID). Pass it as id to chargeback, and as chargebackId to chargebackEvents, dispute and the dispute mutations.

Chargeback.accountId ● ID! non-null scalar

Account the disputed payment belongs to.

Chargeback.checkoutId ● ID! non-null scalar

ID of the disputed payment: the ID that charge takes. The dashboard shows it as Payment ID.

Chargeback.paymentMethod ● String! non-null scalar

Payment method code of the disputed payment, for example card or bizum. A string, not an enum.

Chargeback.transactionType ● String! non-null scalar

Latest stage the acquirer reported for this dispute. The dashboard shows it as Dispute stage. One of 1st Chargeback, 1st Chargeback reversal, 1st Chargeback Allocation, Re-presentment, Re-presentment reversal, Retrieval request, Retrieval request reversal, Pre-arbitration, Arbitration, Resolved chargeback, Resolved chargeback reversal, Reimbursement or Reimbursement reversal.

Chargeback.postingDate ● String! non-null scalar

When the acquirer posted the latest stage, ISO 8601. It moves forward with each new stage. The dashboard shows it as Posting date.

Chargeback.origTransactionDate ● String! non-null scalar

When the disputed payment was made, ISO 8601. The dashboard shows it as Original transaction date.

Chargeback.origTransactionCurrency ● String! non-null scalar

Currency of the original payment, as an ISO 4217 code.

Chargeback.origTransactionAmount ● Int! non-null scalar

Amount of the original payment in origTransactionCurrency, in cents: 1050 is 10.50. The dashboard shows it as Original transaction amount.

Chargeback.cbkCurrency ● String! non-null scalar

Currency of the disputed amount, as an ISO 4217 code. It is the card issuer's currency and can differ from origTransactionCurrency.

Chargeback.cbkAmount ● Int! non-null scalar

Disputed amount in cbkCurrency, in cents: 1050 is 10.50. The dashboard shows it as Disputed amount. On a formal chargeback this amount is taken from the payouts. On an inquiry (WARNING_NEEDS_RESPONSE) nothing is taken. It can be less than the original payment.

Chargeback.providerReferenceId ● String! non-null scalar

Reference of the original payment at the acquirer. The dashboard shows it as Provider reference ID.

Chargeback.internalId ● String! non-null scalar

Merchant identifier of the account at the acquirer that processed the payment. It does not identify the dispute.

Chargeback.arn ● String scalar

Acquirer Reference Number: the card network reference of the payment, the same in every stage of the dispute. Null when there is none, for example for Bizum.

Chargeback.reasonCode ● String scalar

Reason code the issuer raised the dispute under. Null when the acquirer sent none.

Chargeback.reasonDescription ● String scalar

Text form of reasonCode. The dashboard shows it as Reason.

Chargeback.workByDate ● String scalar

Response deadline the acquirer stated for this stage, ISO 8601. The dashboard shows it as Response deadline. It names a calendar day in UTC, and a response is accepted until that day ends (UTC). Missing the deadline on a NEEDS_RESPONSE dispute loses it: the status becomes EXPIRED. The deadline stays on a dispute that lapses, so a closed case can still carry one. But a later stage can replace the deadline and clear it, and older cases can have none. So presence on an ended case is not guaranteed, and absence does not mean that the acquirer stated no deadline. A date here does **not** mean that a response can be filed. Only NEEDS_RESPONSE accepts a response; see disputeStatus. A WARNING_NEEDS_RESPONSE chargeback carries the deadline of the inquiry, but an inquiry accepts no response. An EXPIRED chargeback keeps the deadline it missed, as history. LOST tells nothing about the deadline: a case lost on the merits was answered on time, and a case lost through a later stage has the deadline cleared.

Chargeback.disputeStatus ● DisputeStatus! non-null enum

Where the dispute stands according to the acquirer. See DisputeStatus for each value and its dashboard label.

Chargeback.disputeDate ● String scalar

When the response was filed with submitRepresentment, ISO 8601. Null if no response was filed. The dashboard shows it as Dispute date.

Chargeback.disputeLanguage ● String scalar

Two-letter code of the language the response must be written in, en or es. The dashboard shows it as Response language.

Chargeback.cardScheme ● CardBrand enum

Card scheme of the disputed payment. Null when it is not known.

Chargeback.representmentStatus ● RepresentmentStatus enum

State of the response: DRAFT after the first saveDispute, SUBMITTED after submitRepresentment. Null until the first saveDispute. The dashboard shows a NEEDS_RESPONSE dispute with a SUBMITTED response as Response filed.

Chargeback.createdAt ● String! non-null scalar

When this chargeback was first recorded, ISO 8601. The Disputes page shows it as Date and lists chargebacks by it, newest first.

Chargeback.updatedAt ● String scalar

When the chargeback last changed, ISO 8601. Null if it never changed.

Returned By

chargeback query ● submitRepresentment mutation

Member Of

ChargebacksConnection object