{"title":"Bulk-upload disputes","category":"default","creationDate":1770633540,"content":"<div class=\"notices green\">\n<p>This feature is in pilot phase. To enable this feature in your platform, reach out to your Adyen contact.<\/p>\n<\/div>\n<p>You can use the <a href=\"https:\/\/ca-test.adyen.com\/\" target=\"_blank\" rel=\"nofollow noopener noreferrer\" class=\"external-link no-image\">Customer Area<\/a> to raise multiple disputes, along with attachments of supporting information. Examples of supporting information are screenshots or photos of receipts, email communication with the merchant, or any other information the card scheme can review to make a decision on the dispute.<\/p>\n<p>To submit disputes, <a href=\"#prepare-the-zip-file\">compile dispute information in a CSV file<\/a>, package it with the necessary supporting information attachments in a <a href=\"#3-create-the-zip-file\">ZIP file<\/a>, and <a href=\"#upload-the-zip-file\">upload it to the Customer Area<\/a>.<\/p>\n<p>This feature is designed for card partners who prefer a UI-based workflow to raise disputes. If you want to have more control over the dispute process, we recommend using the  <a href=\"https:\/\/docs.adyen.com\/api-explorer\/transfers-api\/latest\/overview\" class=\"codeLabel  external-link no-image\" target=\"_blank\" rel=\"nofollow noopener noreferrer\">Raise disputes API<\/a>.<\/p>\n<h2>Requirements<\/h2>\n<p>Before you begin, take into account the following requirements, limitations, and preparations.<\/p>\n<table>\n<thead>\n<tr>\n<th style=\"text-align: left;\">Requirement<\/th>\n<th style=\"text-align: left;\">Description<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td style=\"text-align: left;\"><strong>Integration type<\/strong><\/td>\n<td style=\"text-align: left;\">Issuing<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\"><strong><a href=\"\/pt\/account\/user-roles\">Customer Area roles<\/a><\/strong><\/td>\n<td style=\"text-align: left;\">To access the <strong>Upload disputes<\/strong> menu in the Customer Area, make sure that you have the following role: <br>  <ul><li markdown=\"1\"><strong>Manage issuing disputes<\/strong><\/li><ul><\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\"><strong><a href=\"\/pt\/development-resources\/webhooks\">Webhooks<\/a><\/strong><\/td>\n<td style=\"text-align: left;\">Subscribe to the following webhook(s): <ul><li markdown=\"1\"> <a href=\"https:\/\/docs.adyen.com\/api-explorer\/dispute-webhooks\/latest\/overview\" class=\"codeLabel  external-link no-image\" target=\"_blank\" rel=\"nofollow noopener noreferrer\">Dispute webhooks<\/a><\/li><li markdown=\"1\"> <a href=\"https:\/\/docs.adyen.com\/api-explorer\/transfer-webhooks\/latest\/overview\" class=\"codeLabel  external-link no-image\" target=\"_blank\" rel=\"nofollow noopener noreferrer\">Transfer webhooks<\/a><\/li><\/ul><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<h2>Prepare the ZIP file<\/h2>\n<p>Your upload must be a single ZIP file containing:<\/p>\n<ul>\n<li>A CSV file named <code>disputes.csv<\/code> that contains information about each dispute.<\/li>\n<li>All the attachments that the csv references.<\/li>\n<\/ul>\n<p>The total uncompressed size of all the files must be less than 100 MB. Once compressed, the ZIP cannot be larger than 50 MB.<\/p>\n<h3>1. Create the disputes.csv file<\/h3>\n<p>To ensure your CSV file is formatted correctly and has the right columns, use the <a href=\"\/pt\/issuing\/raise-disputes\/bulk-upload\/disputes.csv\">disputes.csv template<\/a>. The template includes an example dispute for each dispute type.<\/p>\n<p>For each dispute you want to raise, add a row to your disputes.csv file. Provide data for all columns that pertain to the dispute <code>type<\/code>. For example, if you are raising a dispute with the <code>type<\/code> <span translate=\"no\"><strong>fraud<\/strong><\/span>, enter data in the <a href=\"#general-columns\">General columns<\/a> and the <a href=\"#columns-for-fraud\">columns for fraud<\/a>. Make sure to leave all remaining columns empty for that row.<\/p>\n<h4>General columns<\/h4>\n<p>Input data into the following columns for every dispute:<\/p>\n<table>\n<thead>\n<tr>\n<th style=\"text-align: left;\">Column Name<\/th>\n<th style=\"text-align: left;\">Description<\/th>\n<th style=\"text-align: left;\">Values required<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td style=\"text-align: left;\"><code>transactionId<\/code><\/td>\n<td style=\"text-align: left;\">The transaction ID of the <span translate=\"no\"><strong>Booked<\/strong><\/span> event for the transaction you want to dispute. This can be found in the Customer Area <strong>Transfer Details page<\/strong>, or in the <a href=\"\/pt\/platforms\/reports-and-fees\/balance-platform-accounting-report\/#report-structure\">Balance Platform Accounting Report<\/a>. <br><strong>Note<\/strong>: the transaction ID is different from the transfer ID.<\/td>\n<td style=\"text-align: left;\"><img title=\"-white_check_mark-\" alt=\"-white_check_mark-\" class=\"smileys\" src=\"\/user\/data\/smileys\/emoji\/white_check_mark.png\" \/><\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\"><code>description<\/code><\/td>\n<td style=\"text-align: left;\">Your description of the dispute. You can use this field as an internal reference. <br><strong>Maximum length<\/strong>: 50 characters.<\/td>\n<td style=\"text-align: left;\"><\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\"><code>type<\/code><\/td>\n<td style=\"text-align: left;\">The category of the dispute. This determines which other <a href=\"#type-specific-columns\">type-specific columns<\/a> you need to enter in a row. <br> <strong>Accepted values:<\/strong> <ul><li markdown=\"1\"><code>notDelivered<\/code><\/li> <li markdown=\"1\"><code>fraud<\/code><\/li> <li markdown=\"1\"><code>duplicate<\/code><\/li><\/ul><\/td>\n<td style=\"text-align: left;\"><img title=\"-white_check_mark-\" alt=\"-white_check_mark-\" class=\"smileys\" src=\"\/user\/data\/smileys\/emoji\/white_check_mark.png\" \/><\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\"><code>disputedAmount_currency<\/code><\/td>\n<td style=\"text-align: left;\">The three-character <a href=\"https:\/\/en.wikipedia.org\/wiki\/ISO_4217\" target=\"_blank\" rel=\"nofollow noopener noreferrer\" class=\"external-link no-image\">ISO 4217<\/a> currency code for the disputed amount. For example, enter <span translate=\"no\"><strong>USD<\/strong><\/span> for United States Dollars or <span translate=\"no\"><strong>EUR<\/strong><\/span> for Euro. If you leave this field empty, the original currency is used for the dispute.<\/td>\n<td style=\"text-align: left;\"><\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\"><code>disputedAmount_value<\/code><\/td>\n<td style=\"text-align: left;\">The value of the disputed amount in minor units. For example, enter <strong>12500<\/strong> for $125.00. If you leave this field empty, the full amount is used for the dispute.<\/td>\n<td style=\"text-align: left;\"><\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\"><code>attachment_fileName<\/code><\/td>\n<td style=\"text-align: left;\">The file name for the supporting information attachment, including its extension. Leave blank if there is no attachment for this dispute row. Supported file types: PDF, JPEG, TIFF. <br> <strong>Maximum length<\/strong>: 17 characters.<\/td>\n<td style=\"text-align: left;\"><\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\"><code>attachment_attachmentType<\/code><\/td>\n<td style=\"text-align: left;\">The type of information in the attachment. Required if <code>attachment_fileName<\/code> is provided. Leave blank if there is no attachment. <br> <strong>Accepted values:<\/strong> <ul><li markdown=\"1\"><code>receipt<\/code><\/li> <li markdown=\"1\"><code>correspondence<\/code><\/li> <li markdown=\"1\"><code>other<\/code><\/li><\/ul><\/td>\n<td style=\"text-align: left;\"><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<h4>Type-specific columns<\/h4>\n<p>Enter values in the columns that relate to the specific type of the dispute you are raising. Leave all other columns empty.<\/p>\n<div class=\"accordion-shortcode adl-accordion adl-accordion--max-height-transition\" data-expand=\"true\" data-ignore=\"anchorjs-link\">\n    \n    <div class=\"adl-accordion__item\" style=\"\">\n        <div tabindex=\"0\" role=\"item\" aria-expanded=\"false\" class=\"adl-accordion__header\">\n            <i class=\"adl-accordion__toggle adl-icon-chevron-down\"><\/i>\n            <div class=\"adl-accordion__title-wrapper\" data-accordion=\"#columns-for-not-delivered\">\n                                    <h4 class=\"adl-accordion__title\">Columns for notDelivered<\/h4>\n                            <\/div>\n        <\/div>\n        <div role=\"region\" class=\"adl-accordion__content\">\n            \n<p>If the <code>type<\/code> for a dispute is <span translate=\"no\"><strong>notDelivered<\/strong><\/span>, enter values in the following <code>notDeliveredInfo<\/code> columns for that row.<\/p>\n<p>Leave all other dispute type info (<span translate=\"no\"><strong>fraudInfo<\/strong><\/span>, <span translate=\"no\"><strong>duplicateInfo<\/strong><\/span>) columns empty for that row.<\/p>\n<table>\n<thead>\n<tr>\n<th style=\"text-align: left;\">Column Name<\/th>\n<th style=\"text-align: left;\">Description<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td style=\"text-align: left;\"><code>notDeliveredInfo_descriptionOfIssue<\/code><\/td>\n<td style=\"text-align: left;\">Your description of the problem. <br> <strong>Maximum length:<\/strong> 2500 characters.<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\"><code>notDeliveredInfo_whatWasNotDelivered<\/code><\/td>\n<td style=\"text-align: left;\">A type indicating what the payment was for. <br> <strong>Accepted values:<\/strong> <ul><li markdown=\"1\"><code>goods<\/code><\/li><li markdown=\"1\"><code>services<\/code><\/li><\/ul><\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\"><code>notDeliveredInfo_lastExpectedDate<\/code><\/td>\n<td style=\"text-align: left;\">The date the undelivered goods or services were expected to be delivered. Use <code>YYYY-MM-DD<\/code> format.<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\"><code>notDeliveredInfo_whoCancelled<\/code><\/td>\n<td style=\"text-align: left;\">A type indicating the party that initiated the cancellation of the transaction. <br> <strong>Accepted values:<\/strong> <ul><li markdown=\"1\"><code>merchant<\/code><\/li><li markdown=\"1\"><code>cardholder<\/code><\/li><\/ul><\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\"><code>notDeliveredInfo_dateOfCancellation<\/code><\/td>\n<td style=\"text-align: left;\">The date the undelivered goods or services were cancelled. Use <code>YYYY-MM-DD<\/code> format.<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\"><code>notDeliveredInfo_agreedDeliveryLocation<\/code><\/td>\n<td style=\"text-align: left;\">The delivery location specified by the cardholder. <br> <strong>Maximum length:<\/strong> 500 characters.<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\"><code>notDeliveredInfo_deliveredToWrongLocation<\/code><\/td>\n<td style=\"text-align: left;\">Indicates goods were delivered to the wrong location. <br> <strong>Accepted values:<\/strong> <ul><li markdown=\"1\"><code>true<\/code><\/li><li markdown=\"1\"><code>false<\/code><\/li><\/ul><\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\"><code>notDeliveredInfo_didCardholderReturn<\/code><\/td>\n<td style=\"text-align: left;\">Indicates if the cardholder returned the goods to the merchant. <br> <strong>Accepted values:<\/strong> <ul><li markdown=\"1\"><code>true<\/code><\/li><li markdown=\"1\"><code>false<\/code><\/li><\/ul><\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\"><code>notDeliveredInfo_isDeliveryLate<\/code><\/td>\n<td style=\"text-align: left;\">Indicates if the goods or services were delivered late. <br> <strong>Accepted values:<\/strong> <ul><li markdown=\"1\"><code>true<\/code><\/li><li markdown=\"1\"><code>false<\/code><\/li><\/ul><\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\"><code>notDeliveredInfo_isMerchantBankrupt<\/code><\/td>\n<td style=\"text-align: left;\">Indicates if the transaction was processed by a bankrupt merchant. <br> <strong>Accepted values:<\/strong> <ul><li markdown=\"1\"><code>true<\/code><\/li><li markdown=\"1\"><code>false<\/code><\/li><\/ul><\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\"><code>notDeliveredInfo_isNonFiatOrNft<\/code><\/td>\n<td style=\"text-align: left;\">Indicates if the transaction is non-fiat or non-fungible token (NFT) related. <br> <strong>Accepted values:<\/strong> <ul><li markdown=\"1\"><code>true<\/code><\/li><li markdown=\"1\"><code>false<\/code><\/li><\/ul><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n\n        <\/div>\n    <\/div>\n<\/div>\n\n<div class=\"accordion-shortcode adl-accordion adl-accordion--max-height-transition\" data-expand=\"true\" data-ignore=\"anchorjs-link\">\n    \n    <div class=\"adl-accordion__item\" style=\"\">\n        <div tabindex=\"0\" role=\"item\" aria-expanded=\"false\" class=\"adl-accordion__header\">\n            <i class=\"adl-accordion__toggle adl-icon-chevron-down\"><\/i>\n            <div class=\"adl-accordion__title-wrapper\" data-accordion=\"#columns-for-fraud\">\n                                    <h4 class=\"adl-accordion__title\">Columns for fraud<\/h4>\n                            <\/div>\n        <\/div>\n        <div role=\"region\" class=\"adl-accordion__content\">\n            \n<p>If the <code>type<\/code> for a dispute is <span translate=\"no\"><strong>fraud<\/strong><\/span>, enter values in the following <code>notDeliveredInfo<\/code> columns for that row.<\/p>\n<p>Leave all other dispute type info (<span translate=\"no\"><strong>notDelivered<\/strong><\/span>, <span translate=\"no\"><strong>duplicateInfo<\/strong><\/span>) columns empty for that row.<\/p>\n<table>\n<thead>\n<tr>\n<th style=\"text-align: left;\">Column Name<\/th>\n<th style=\"text-align: left;\">Description<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td style=\"text-align: left;\"><code>fraudInfo_cardDoesNotBelongToCardholder<\/code><\/td>\n<td style=\"text-align: left;\">Indicates if the card is no longer in the cardholder's possession. <br> <strong>Accepted values:<\/strong> <ul><li markdown=\"1\"><code>true<\/code><\/li><li markdown=\"1\"><code>false<\/code><\/li><\/ul><\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\"><code>fraudInfo_cardWasCounterfeited<\/code><\/td>\n<td style=\"text-align: left;\">Indicates if the card was counterfeited. <br> <strong>Accepted values:<\/strong> <ul><li markdown=\"1\"><code>true<\/code><\/li><li markdown=\"1\"><code>false<\/code><\/li><\/ul><\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\"><code>fraudInfo_descriptionOfIssue<\/code><\/td>\n<td style=\"text-align: left;\">Your description of the issue. <br> <strong>Maximum length:<\/strong> 2500 characters.<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\"><code>fraudInfo_reportOnly<\/code><\/td>\n<td style=\"text-align: left;\">Set to <span translate=\"no\"><strong>true<\/strong><\/span> if you want to submit a fraud report with no further action. If set to true, there is no request for a chargeback or fee reversal. Default is <code>false<\/code>. <br><strong>Accepted values:<\/strong> <ul><li markdown=\"1\"><code>true<\/code><\/li><li markdown=\"1\"><code>false<\/code><\/li><\/ul><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n\n        <\/div>\n    <\/div>\n<\/div>\n\n<div class=\"accordion-shortcode adl-accordion adl-accordion--max-height-transition\" data-expand=\"true\" data-ignore=\"anchorjs-link\">\n    \n    <div class=\"adl-accordion__item\" style=\"\">\n        <div tabindex=\"0\" role=\"item\" aria-expanded=\"false\" class=\"adl-accordion__header\">\n            <i class=\"adl-accordion__toggle adl-icon-chevron-down\"><\/i>\n            <div class=\"adl-accordion__title-wrapper\" data-accordion=\"#columns-for-duplicate\">\n                                    <h4 class=\"adl-accordion__title\">Columns for duplicate<\/h4>\n                            <\/div>\n        <\/div>\n        <div role=\"region\" class=\"adl-accordion__content\">\n            \n<p>If the <code>type<\/code> for a dispute is <span translate=\"no\"><strong>duplicate<\/strong><\/span>, enter values in the following <code>notDeliveredInfo<\/code> columns for that row.<\/p>\n<p>Leave all other dispute type info (<span translate=\"no\"><strong>notDeliveredInfo<\/strong><\/span>, <span translate=\"no\"><strong>fraudInfo<\/strong><\/span>) columns empty for that row.<\/p>\n<table>\n<thead>\n<tr>\n<th style=\"text-align: left;\">Column Name<\/th>\n<th style=\"text-align: left;\">Description<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td style=\"text-align: left;\"><code>duplicateInfo_duplicateTransactionId<\/code><\/td>\n<td style=\"text-align: left;\">The transaction ID of the other payment that your cardholder considers to be a duplicate. <br> <strong>Accepted values:<\/strong> <ul><li markdown=\"1\"><code>true<\/code><\/li><li markdown=\"1\"><code>false<\/code><\/li><\/ul><\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\"><code>duplicateInfo_sameCard<\/code><\/td>\n<td style=\"text-align: left;\">An indicator if the duplicate transaction occurred on the same card. <br> <strong>Accepted values:<\/strong> <ul><li markdown=\"1\"><code>true<\/code><\/li><li markdown=\"1\"><code>false<\/code><\/li><\/ul><\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\"><code>duplicateInfo_sameIssuer<\/code><\/td>\n<td style=\"text-align: left;\">An indicator if the duplicate transaction involved the same issuer. <br> <strong>Accepted values:<\/strong> <ul><li markdown=\"1\"><code>true<\/code><\/li><li markdown=\"1\"><code>false<\/code><\/li><\/ul><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n\n        <\/div>\n    <\/div>\n<\/div>\n\n<h3>2. Collect your supporting information attachments<\/h3>\n<p>For each row in your CSV file, you can include an attachment file in the root of the ZIP file to be used as supporting information, also known as evidence, for the dispute. The attachments can be a receipt, correspondence with the merchant, or anything else that the cardholder would like to include to support the cardholder's case.<\/p>\n<p>Adyen supports <span translate=\"no\"><strong>JPEG<\/strong><\/span>, <span translate=\"no\"><strong>TIFF<\/strong><\/span>, and <span translate=\"no\"><strong>PDF<\/strong><\/span> attachments. Each attachment can be up to 2 MB with a file name up to 17 characters, including its extension. You can attach 49 files per upload. The total file size, including all supporting information attachments and the CSV, must not exceed 100 MB before it is compressed.<\/p>\n<h3>3. Create the ZIP file<\/h3>\n<p>After you create your CSV and collect your supporting information attachments, compress the files into a ZIP archive. Place all files at the root of the archive. All subfolders are ignored.<\/p>\n<p><strong>Example ZIP file structure:<\/strong><\/p>\n<pre><code class=\"language-php\">Example.zip\n\u251c\u2500 disputes.csv\n\u251c\u2500 evidence_1.jpg\n\u251c\u2500 evidence_2.pdf\n\u251c\u2500 evidence_3.jpg\n\u2514\u2500 evidence_4.tiff<\/code><\/pre>\n<p>Before you compress the files, check that they do not exceed 100 MB in total. Then, compress the files into a ZIP archive and make sure the ZIP file does not exceed 50 MB.<\/p>\n<h2>Upload the ZIP file<\/h2>\n<p>When your ZIP file is ready, you can upload it in the Customer Area.<\/p>\n<ol>\n<li>Log in to your <a href=\"https:\/\/ca-test.adyen.com\/\" target=\"_blank\" rel=\"nofollow noopener noreferrer\" class=\"external-link no-image\">Customer Area<\/a>.<\/li>\n<li>Go to <strong>Financial products<\/strong> &gt; <strong>Issuing disputes<\/strong>.<\/li>\n<li>Select <strong>Bulk Uploads<\/strong>.<\/li>\n<li>On the upload page, drag and drop your ZIP file or select <strong>Browse files<\/strong> to choose it from your computer.<\/li>\n<li>Select <strong>Submit<\/strong>.<\/li>\n<\/ol>\n<p>If there are no issues with the file type and size you upload, Adyen  processes the disputes. You can submit up to ten uploads per day. If you receive an error, check your Zipped file, and try to upload your file again.<\/p>\n<p>Adyen processes each dispute in your upload individually. To track the result of each dispute, use  <a href=\"https:\/\/docs.adyen.com\/api-explorer\/dispute-webhooks\/latest\/overview\" class=\"codeLabel  external-link no-image\" target=\"_blank\" rel=\"nofollow noopener noreferrer\">Dispute webhooks<\/a>. For more information about tracking disputes, see <a href=\"\/pt\/issuing\/raise-disputes\/#associating-ids-throughout-the-dispute-lifecycle\">Associating IDs throughout the dispute lifecycle<\/a>.<\/p>\n<h2>See also<\/h2>\n<ul>\n<li><a href=\"\/pt\/issuing\/raise-disputes\/manage-disputes\">Manage disputes via API<\/a><\/li>\n<li><a href=\"\/pt\/issuing\/raise-disputes\">How to raise disputes<\/a><\/li>\n<li><a href=\"\/pt\/issuing\/raise-disputes#dispute-reasons-and-their-types\">Dispute reasons and their types<\/a><\/li>\n<li><a href=\"\/pt\/issuing\/webhook-types#dispute-webhooks\">Dispute webhooks<\/a><\/li>\n<\/ul>","url":"https:\/\/docs.adyen.com\/pt\/issuing\/raise-disputes\/bulk-upload","articleFields":{"description":"Learn how to use the Customer Area to upload multiple disputes and their supporting information.","robots":"noindex,nofollow","parameters":{"directoryPath":"\/issuing"},"feedback_component":true,"filters_component":false,"decision_tree":"[]","page_id":"a2ab1d58-1640-48d6-ba0e-054a691d3bb1","last_edit_on":"09-02-2026 11:39"},"algolia":{"url":"https:\/\/docs.adyen.com\/pt\/issuing\/raise-disputes\/bulk-upload","title":"Bulk-upload disputes","content":"\nThis feature is in pilot phase. To enable this feature in your platform, reach out to your Adyen contact.\n\nYou can use the Customer Area to raise multiple disputes, along with attachments of supporting information. Examples of supporting information are screenshots or photos of receipts, email communication with the merchant, or any other information the card scheme can review to make a decision on the dispute.\nTo submit disputes, compile dispute information in a CSV file, package it with the necessary supporting information attachments in a ZIP file, and upload it to the Customer Area.\nThis feature is designed for card partners who prefer a UI-based workflow to raise disputes. If you want to have more control over the dispute process, we recommend using the  Raise disputes API.\nRequirements\nBefore you begin, take into account the following requirements, limitations, and preparations.\n\n\n\nRequirement\nDescription\n\n\n\n\nIntegration type\nIssuing\n\n\nCustomer Area roles\nTo access the Upload disputes menu in the Customer Area, make sure that you have the following role:   Manage issuing disputes\n\n\nWebhooks\nSubscribe to the following webhook(s):  Dispute webhooks Transfer webhooks\n\n\n\nPrepare the ZIP file\nYour upload must be a single ZIP file containing:\n\nA CSV file named disputes.csv that contains information about each dispute.\nAll the attachments that the csv references.\n\nThe total uncompressed size of all the files must be less than 100 MB. Once compressed, the ZIP cannot be larger than 50 MB.\n1. Create the disputes.csv file\nTo ensure your CSV file is formatted correctly and has the right columns, use the disputes.csv template. The template includes an example dispute for each dispute type.\nFor each dispute you want to raise, add a row to your disputes.csv file. Provide data for all columns that pertain to the dispute type. For example, if you are raising a dispute with the type fraud, enter data in the General columns and the columns for fraud. Make sure to leave all remaining columns empty for that row.\nGeneral columns\nInput data into the following columns for every dispute:\n\n\n\nColumn Name\nDescription\nValues required\n\n\n\n\ntransactionId\nThe transaction ID of the Booked event for the transaction you want to dispute. This can be found in the Customer Area Transfer Details page, or in the Balance Platform Accounting Report. Note: the transaction ID is different from the transfer ID.\n\n\n\ndescription\nYour description of the dispute. You can use this field as an internal reference. Maximum length: 50 characters.\n\n\n\ntype\nThe category of the dispute. This determines which other type-specific columns you need to enter in a row.  Accepted values: notDelivered fraud duplicate\n\n\n\ndisputedAmount_currency\nThe three-character ISO 4217 currency code for the disputed amount. For example, enter USD for United States Dollars or EUR for Euro. If you leave this field empty, the original currency is used for the dispute.\n\n\n\ndisputedAmount_value\nThe value of the disputed amount in minor units. For example, enter 12500 for $125.00. If you leave this field empty, the full amount is used for the dispute.\n\n\n\nattachment_fileName\nThe file name for the supporting information attachment, including its extension. Leave blank if there is no attachment for this dispute row. Supported file types: PDF, JPEG, TIFF.  Maximum length: 17 characters.\n\n\n\nattachment_attachmentType\nThe type of information in the attachment. Required if attachment_fileName is provided. Leave blank if there is no attachment.  Accepted values: receipt correspondence other\n\n\n\n\nType-specific columns\nEnter values in the columns that relate to the specific type of the dispute you are raising. Leave all other columns empty.\n\n    \n    \n        \n            \n            \n                                    Columns for notDelivered\n                            \n        \n        \n            \nIf the type for a dispute is notDelivered, enter values in the following notDeliveredInfo columns for that row.\nLeave all other dispute type info (fraudInfo, duplicateInfo) columns empty for that row.\n\n\n\nColumn Name\nDescription\n\n\n\n\nnotDeliveredInfo_descriptionOfIssue\nYour description of the problem.  Maximum length: 2500 characters.\n\n\nnotDeliveredInfo_whatWasNotDelivered\nA type indicating what the payment was for.  Accepted values: goodsservices\n\n\nnotDeliveredInfo_lastExpectedDate\nThe date the undelivered goods or services were expected to be delivered. Use YYYY-MM-DD format.\n\n\nnotDeliveredInfo_whoCancelled\nA type indicating the party that initiated the cancellation of the transaction.  Accepted values: merchantcardholder\n\n\nnotDeliveredInfo_dateOfCancellation\nThe date the undelivered goods or services were cancelled. Use YYYY-MM-DD format.\n\n\nnotDeliveredInfo_agreedDeliveryLocation\nThe delivery location specified by the cardholder.  Maximum length: 500 characters.\n\n\nnotDeliveredInfo_deliveredToWrongLocation\nIndicates goods were delivered to the wrong location.  Accepted values: truefalse\n\n\nnotDeliveredInfo_didCardholderReturn\nIndicates if the cardholder returned the goods to the merchant.  Accepted values: truefalse\n\n\nnotDeliveredInfo_isDeliveryLate\nIndicates if the goods or services were delivered late.  Accepted values: truefalse\n\n\nnotDeliveredInfo_isMerchantBankrupt\nIndicates if the transaction was processed by a bankrupt merchant.  Accepted values: truefalse\n\n\nnotDeliveredInfo_isNonFiatOrNft\nIndicates if the transaction is non-fiat or non-fungible token (NFT) related.  Accepted values: truefalse\n\n\n\n\n        \n    \n\n\n\n    \n    \n        \n            \n            \n                                    Columns for fraud\n                            \n        \n        \n            \nIf the type for a dispute is fraud, enter values in the following notDeliveredInfo columns for that row.\nLeave all other dispute type info (notDelivered, duplicateInfo) columns empty for that row.\n\n\n\nColumn Name\nDescription\n\n\n\n\nfraudInfo_cardDoesNotBelongToCardholder\nIndicates if the card is no longer in the cardholder's possession.  Accepted values: truefalse\n\n\nfraudInfo_cardWasCounterfeited\nIndicates if the card was counterfeited.  Accepted values: truefalse\n\n\nfraudInfo_descriptionOfIssue\nYour description of the issue.  Maximum length: 2500 characters.\n\n\nfraudInfo_reportOnly\nSet to true if you want to submit a fraud report with no further action. If set to true, there is no request for a chargeback or fee reversal. Default is false. Accepted values: truefalse\n\n\n\n\n        \n    \n\n\n\n    \n    \n        \n            \n            \n                                    Columns for duplicate\n                            \n        \n        \n            \nIf the type for a dispute is duplicate, enter values in the following notDeliveredInfo columns for that row.\nLeave all other dispute type info (notDeliveredInfo, fraudInfo) columns empty for that row.\n\n\n\nColumn Name\nDescription\n\n\n\n\nduplicateInfo_duplicateTransactionId\nThe transaction ID of the other payment that your cardholder considers to be a duplicate.  Accepted values: truefalse\n\n\nduplicateInfo_sameCard\nAn indicator if the duplicate transaction occurred on the same card.  Accepted values: truefalse\n\n\nduplicateInfo_sameIssuer\nAn indicator if the duplicate transaction involved the same issuer.  Accepted values: truefalse\n\n\n\n\n        \n    \n\n\n2. Collect your supporting information attachments\nFor each row in your CSV file, you can include an attachment file in the root of the ZIP file to be used as supporting information, also known as evidence, for the dispute. The attachments can be a receipt, correspondence with the merchant, or anything else that the cardholder would like to include to support the cardholder's case.\nAdyen supports JPEG, TIFF, and PDF attachments. Each attachment can be up to 2 MB with a file name up to 17 characters, including its extension. You can attach 49 files per upload. The total file size, including all supporting information attachments and the CSV, must not exceed 100 MB before it is compressed.\n3. Create the ZIP file\nAfter you create your CSV and collect your supporting information attachments, compress the files into a ZIP archive. Place all files at the root of the archive. All subfolders are ignored.\nExample ZIP file structure:\nExample.zip\n\u251c\u2500 disputes.csv\n\u251c\u2500 evidence_1.jpg\n\u251c\u2500 evidence_2.pdf\n\u251c\u2500 evidence_3.jpg\n\u2514\u2500 evidence_4.tiff\nBefore you compress the files, check that they do not exceed 100 MB in total. Then, compress the files into a ZIP archive and make sure the ZIP file does not exceed 50 MB.\nUpload the ZIP file\nWhen your ZIP file is ready, you can upload it in the Customer Area.\n\nLog in to your Customer Area.\nGo to Financial products &gt; Issuing disputes.\nSelect Bulk Uploads.\nOn the upload page, drag and drop your ZIP file or select Browse files to choose it from your computer.\nSelect Submit.\n\nIf there are no issues with the file type and size you upload, Adyen  processes the disputes. You can submit up to ten uploads per day. If you receive an error, check your Zipped file, and try to upload your file again.\nAdyen processes each dispute in your upload individually. To track the result of each dispute, use  Dispute webhooks. For more information about tracking disputes, see Associating IDs throughout the dispute lifecycle.\nSee also\n\nManage disputes via API\nHow to raise disputes\nDispute reasons and their types\nDispute webhooks\n","type":"page","locale":"pt","boost":17,"hierarchy":{"lvl0":"Home","lvl1":"Adyen Issuing","lvl2":"Raise disputes for transactions made with an Adyen-issued card","lvl3":"Bulk-upload disputes"},"hierarchy_url":{"lvl0":"https:\/\/docs.adyen.com\/pt","lvl1":"https:\/\/docs.adyen.com\/pt\/issuing","lvl2":"https:\/\/docs.adyen.com\/pt\/issuing\/raise-disputes","lvl3":"\/pt\/issuing\/raise-disputes\/bulk-upload"},"levels":4,"category":"Issuing","category_color":"green","tags":["Bulk-upload","disputes"]},"articleFiles":{"disputes.csv":"<p alt=\"\">disputes.csv<\/p>"}}
