Disputes Report
Introduction
This report provides details on disputed operations (e.g., RDR, chargebacks, representment, compliance, pre-arbitration, arbitration).
Recommended columns
-
cardCountry string(2)
Card country (format ISO_3166-1_alpha-2)
Example: US
-
cardFullName string
Cardholder's full name (as described on the payment method)
Example: JOHN SNOW
-
cardNumber string(12-19)
First six and last 4 digits of holder’s card number
Example: 411111XXXXXX1234
-
cardType string
Type of the card
Example: VISA
-
chargebackCode string(1-255)
Chargeback reason code
Example: 4807
-
chargebackReason string
Chargeback reason
Example: No cardholder authorization
-
customerEmail string
Shopper's email.
Example: john.snow@example.com
-
customerIpCountry string
The shopper’s IP country
Example: FR
-
disputeAmount float
Amount of the chargeback
Example: 105.45
-
disputeDate datetime
Chargeback date
Example: 2023-06-01 06:38:38
-
disputeNature string
Stage of the chargeback
RDR
RDR Reversal
First chargeback
First chargeback reversal
Representment
Representment reversal
Pre-compliance issuer
Pre-compliance acquirer
Compliance
Pre-arbitration
ArbitrationExample: Representment
-
ftEntryDate datetime
Processing time of the FT File containing the FT record
Example: 2023-06-01 06:38:38
-
ftFraudReason string
Fraudulent transaction fraud reason
Example: [01] Stolen fraud
-
identifier string(1-32)
Your processing account technical identifier
Example: YOUR_IDENTIFIER
-
operationAmount float
Amount of the operation in the transaction currency. The point is used as decimal separator
Example: 105.45
-
operationCurrency string(3)
Transaction currency code (ISO 4217 format)
Example: EUR
-
operationDate datetime
Transaction date (YYYY-MM-DD hh:mm:ss)
Example: 2020-01-01 10:02:00
-
operationId string(1-32)
Unique Payplug operation ID
Example: A1123456
-
operationNature string
Type of the operation : authorization, capture, payment, refund, credit, void, capture, dispute, tax, miscellaneous operation, guarantee release, guarantee withheld, adjustment debit, adjustment credit
Example: payment
-
orderId string(1-40)
Unique ID associated to an order in the merchant’s database (as specified in the merchant’s initial submission/POST request)
Example: 1234
-
ruleIds string
Rule IDs applied by fraud rule engine
Example: 32204,32272,22644,22638
-
settlementCurrency string(3)
Currency of settlements for this merchant account
Example: EUR
-
threeDSecureApplied no ; yes
Flag to indicate whether or not the transaction has been processed with 3-D Secure
Example: yes
-
threeDSecureAuthenticationStatus string
Authentication status:
- Y = authentication successful
- N = not authenticated
- U = unavailable
- A = attempted
- C = cardholder challenge required
- R = rejected
- empty = no 3-D SecureExample: Y
Additional columns
-
alias string
Alias generated by Payplug for Card On File operations: subscription, one-click
Example: A1-fc5bafe3-8c12-4314-95c7-2e15ec3220e0
-
aliasMode string
Indicates the Card On File type (subscription or one-click)
Example: oneclick
-
archivingReference string
Retrieval reference number
Example: 271770264051
-
arn string
Acquirer Reference Number.
Unique 23-digit numbers assigned to credit or debit card transactions. It is used to trace a transaction from the acquirer’s bank to the cardholder’s bank.Example: 41234567890123456789000
-
authentication string
Cardholder authentication mechanism
Example: 00
-
authorizationNumber string
Authorisation number (POS Terminals only)
Example: 497730
-
authorizationType string
Defines the type of authorization: final auth, pre-auth, card verification
Example: final auth
-
avsCode string(1)
The Address Verification System result code. See the Address Verification System result codes section
Example: A
-
avsCode string(1)
The Address Verification System result code. See the Address Verification System result codes section
Example: A
-
avsMessage string(1, 255)
The Address Verification System result message. See the Address Verification System result codes section
Example: Partial Match - Address match; Zip/Postal Code does not match
-
avsMessage string(1, 255)
The Address Verification System result message. See the Address Verification System result codes section
Example: Partial Match - Address match; Zip/Postal Code does not match
-
bankCaptureNumber string(1-50)
Bank collection number (POS only)
Example: 1417
-
bankCaptureNumber string(1-50)
Bank collection number (POS only)
Example: 1417
-
billingAddress string(1-50)
Billing address as specified by the merchant in the original payment request
Example: 110 avenue de France
-
billingAddress string(1-50)
Billing address as specified by the merchant in the original payment request
Example: 110 avenue de France
-
billingCity string
Billing city as specified by the merchant in the original payment request
Example: Paris
-
billingCountry string
Billing country (ISO_3166-1_alpha-2) as specified by the merchant in the original payment request
Example: FR
-
billingFirstName string(1-15)
First name part of the billing address as specified by the merchant in the original payment request
Example: John
-
billingLastName string(1-15)
Last name part of the billing address as specified by the merchant in the original payment request
Example: Doe
-
billingMobilePhone string(1-32)
Billing mobile phone number in international format as specified by the merchant in the original payment request
Example: 0623456789
-
billingPhone string(1-32)
Billing phone number in international format as specified by the merchant in the original payment request
Example: 0123456789
-
billingState string
Billing state as specified by the merchant in the original payment request
Example: ARA
-
billingTitle string
Title used for the billing address name (mr, miss, mrs)
Example: mr, miss, mrs
-
billingZipCode string(1-9)
Billing zip code as specified by the merchant in the original payment request
Example: 75013
-
cardBank string
Cardholder's bank
Example: BPCE
-
cardProduct string
Product type (consumer/corporate)
Example: consumer
-
cardServiceType string
Card service type associated to card : debit,credit,enterprise,pre-paid
Example: credit
-
clientIdentifier string
Merchant acquiring identifier delivered by Payplug
Example: Payplug IDENTIFIER
-
contractNumber string
Merchant acquiring identifier delivered by Payplug
Example: 5907654
-
customerId string
Shopper’s uid in the merchant application
Example: 8188965
-
description string
A short description of the operation. Don’t hesitate to ask your Payment Manager for some advice on this topic
Example: My_Company
-
descriptor string
Descriptor displayed on the cardholder bank statement. Data coming from information provided during merchant’s onboarding
Example: myshop.com
-
disputeCurrency string
Dispute currency code (ISO 4217 format)
Example: EUR
-
exchangeRate string
Exchange rate used to calculate the fee in the settlement currency
Example: 9.8973
-
execCode string(4)
The operation result code. (See the complete list of execution code)
Example: 4001
-
execCodeMessage string
The operation result code. (See the complete list of execution code)
Example: Transaction declined by the banking network
-
extraData string
Free field sent during the processing request
Example: referrer=myshop.com;order=premium
-
financialAccount string(10)
Label of the financial account which is used for the transactions funding
Example: F010300
-
financialStatus string
Financial status of the operation : Being processed, collected, Paid, Advanced, Charged
Example: charged
-
idClient string
Client ID
Example: 4154
-
idClientsGroup string
Clientgroup ID
Example: 2724
-
metadata string(1-255)
Additional data that can be sent in a payment request . Metadata can contain specific tags that will be used by Payplug fraud engine to trigger general or merchant specific rules (Commercial agrement may be required prior to Tag usage)
Example: METADATA-MYWEBSITE
-
network string
Scheme used for the authentication, authorization and clearing
Example: Visa
-
nfc string
Near Field contact. Contactless transaction flag (POS only)
Example: yes
-
operationOrigin string
Indicates the origin of the transaction (DIRECTLINK, FORM, EXTRANET, BATCH, REDIRECTION, POS, DIRECT_SUBMIT, VAD_INTERNAL, PRT_RECEIVER, MULTIBANCO_MEPS, HOSTED_FIELD, POS_INTERNATIONAL)
Example: DIRECTLINK
-
originOperationAmount float
Amount of the initial operation in the operation currency. The point is used as decimal separator
Example: 59.23
-
originOperationCurrency string(3)
Currency of the initial transaction (ISO 4217 format)
Example: EUR
-
originOperationDate datetime
Date of the initial operation (YYYY-MM-DD hh:mm).
Example: 2023-06-23 21:03:00
-
originOperationId string(1-32)
Operation ID of the initial operation eg : for a capture, you will have the operation ID of the authorization which have been capture . For a refund , you will have the operation ID of the payment
Example: A1123456
-
paymentMethodType string
Payment method used for the tarnsaction: przelewy, giropay, sofort, cb_visa_mastercard, sepa_direct_debit , multibanco, bancontact, ideal
Example: cb_visa_mastercard
-
posBrand string
Equipement brand (POS only)
Example: INGENICO
-
posIdsa string
Acceptor System Identifier (POS only)
Example: 00000884
-
posItp string
Terminal application identification at point of acceptance (POS only)
Example: 168550250805
-
posModel string
Terminal model (POS only)
Example: iUN CB-Cless
-
posRank integer(3)
Payment terminal rank (for POS transactions only)
Example: 001
-
posSerialNumber string(12)
Payment terminal serial number (for POS transactions only)
Example: 5536667
-
posShortName string
POI Short Name (POS only)
Example: 1st_Floor
-
processingAccount string
Unique id of your processing account
Example: C019000
-
recurringSequence integer
Recurring sequence
Example: 22
-
refundDate datetime
Refund date
Example: 2023-06-01 06:38:38
-
refundTransferReference string
Refund transfer reference
Example: 20230519.150.20231696812900000
-
refundTransferStatus string
Refund transfer status (Pending, Failed, Succeeded).
Example: Pending
-
refundedBy string
Operation ID of the operations which have refunded the transaction
Example: A1123456
-
ruleApplied string
Rule applied by fraud rule engine
Example: P10,C9,C10,C11,C12,C14
-
ruleDescription string(1-125)
Rule description
Example:
-
saleReferenceIdentification string
A reference sent by the cash desk. Corresponds to the Order ID in the Dalenys Dashboard. (POS only)
Example: 102234
-
saleReferenceNumber string
ID of the Transaction generated by the cash desk. Corresponds to the Sale ID in the Dalenys Dashboard. (POS only)
Example: 1689518630000
-
schedule string
Payment schedule ID(instalment number - number of instalments)
Example: 2-3
-
scheduleId integer
PID of the schedule which is ithe ID of the first instalment
Example: A1123456
-
scheduleRetry string
Payment schedule information (retry number - number of retries)
Example: 2-6
-
schemeFee float
Fees charged by the card schemes (CB or Visa or Mastercard) in settlement currency
Example: -9.12
-
schemeTransactionId string(1-55)
Scheme transaction ID, retrieved in response to the authorization request
Example: 11034331402111290210
-
shipToAddress string
The shipping address where the purchased goods should be delivered
Example: 55 rue de la liberté
-
shipToCity string
The city of the shipping address
Example: Caen
-
shipToCompanyName string
The company name indicated in the shipping address
Example: Company Abc
-
shipToCountry string
The shipping country (ISO_3166-1_alpha-2 format)
Example: US
-
shipToFirstName string
The first name indicated in the shipping address
Example: James
-
shipToLastName string
The last name indicated in the shipping address
Example: Cook
-
shipToMobilePhone string
The mobile phone number indicated in the shipping address
Example: 0671788877
-
shipToPhone string
The phone number indicated in the shipping address
Example: 0112223432
-
shipToState string
The state indicated in the shipping address
Example: OCC
-
shipToTitle string
The title associated to the name indicated in the shipping address
Example: Mrs
-
shipToZipCode string
The zip code indicated in the shipping address
Example: 1-4 | 1-3 | 2-3
-
subMerchantCountry string
Country of the submerchant (for marketplaces and Payment Faciliators only)
Example: FR
-
subMerchantDoBusinessAs string
Commercial name of the submerchant (for marketplaces and Payment Faciliators only)
Example: My company
-
subMerchantExternalId string
Sub-merchants external ID as received in the transaction request. (for Marketplaces and Payment Facilitators only)
Example: 123456
-
subMerchantMcc string
Merchant Category Code of the submerchant (for marketplaces and Payment Faciliators only)
Example: 5691
-
subMerchantName string
Legal name of the submerchant (for marketplaces and Payment Faciliators only)
Example: My_SubMerchantName
-
subMerchantStatus string
The status of the Submerchant (Enabled / Disabled)
Example: ENABLED
-
tags string
Tags set by the Payplug’s rule engine
Example: TO BE CHECKED=High amount&TO BE CHECKED=Multiple cards
-
threeDSecureChallengeStatus string
3D Secure challenge status
- Y = successful
- N = failure
- U = ACS not reachable
- null = in case of frictionlessExample: Y
-
threeDSecureECI string
Electronic Commerce Indicator
Example: 06
-
threeDSecureFee float
Fees per authentification request on transactions authenticated through the security protocol 3D Secure
Example: -0.02
-
threeDSecureMode string
3D Secure mode : sca, frictionless
Example: sca
-
threeDSecurePreference string
3D Secure preference
- none (no preference)
- frictionless
- sca
- scamandateExample: frictionless
-
threeDSecureSignatureStatus string
3D Secure signature status : yes, no
Example: yes
-
threeDSecureVersion string
3D Secure version
Example: 2
-
tradename string
Trade name of your company
Example: MY_COMPANY
-
transferDate datetime
Date on which Payplug initiate the transfer of funds to your account
Example: 2023-06-01 06:38:38
-
transferReference string(1-32)
ID of the wire transfer. This reference should appear on your bank statement. May be used for financial reconciliation purposes
Example: 20230519.150.20231696812900000
-
voidedBy string
Operation ID of the operations which have voided the transaction
Example: A1123456
Available filters
- identifier
- disputeNature
- disputeDate
- chargebackCode
- orderId
- operationId
- operationNature
- operationDate - Specific format for filter : 2024-01-01 00:00:00.000000
- cardType
- cardCountry
- customerEmail
- threeDSecureApplied
- threeDSecureAuthenticationStatus
- ftEntryDate
- idClient
- idClientGroup
- processingAccount