Chargebacks File

overview context all chargebacks that have been newly submitted or had a change in status file type csv file name \<company name> chargebacks yyyymmddhhmmss example = \<company name> chargebacks 20221110233030 company name = your companies name when uploading test files, please append " testing" at the end of the file name example = \<company name> chargebacks 20221110233030 testing frequency daily chargeback data columns column name mandatory format details example environment mandatory valid values are "production" or "testing" production chargeback date/time mandatory dd/mm/yyyy hh\ mm\ ss 31/01/2022 16 34 45 transaction date/time mandatory dd/mm/yyyy hh\ mm\ ss 31/01/2022 16 34 45 transaction id mandatory a13f1609 7854 47a6 b533 339f3ac80be8 chargeback id mandatory 1233 1223 1111 merchant registration id mandatory depends on registered country see data dictionary 12345678 000 11 22 3 merchant category code mandatory 4 digit numeric value based on iso 18245 5812 scheme mid mandatory mid used within the scheme network url mandatory merchant website url billing descriptor mandatory tim's tiles chargeback reason code mandatory reason code provided by card scheme/network see chargback reason codes in data dictionaries section for more details 30 chargeback status mandatory the status of the chargabck based on the latest event example values are "submitted", "settled" & "successfully defended" submitted / settled / successfully defended card bin mandatory first 6 digits of the card number 512345 chargeback currency mandatory 3 letter, iso 4217 currency code usd chargeback amount mandatory numeric value with no currency symbol 100 notes please adhere by the format details of each column provided the file should contain a record for every time a chargeback is newly submitted or has a status update the minimum statuses updates required for chargebacks are when the case is submitted and when it is closed as either settled or successfully defended