{"title":"Raise disputes for transactions made with an Adyen-issued card","category":"default","creationDate":1776961628,"content":"<p>As a platform that issues cards through Adyen, you must be able to raise disputes on behalf of your cardholders.<\/p>\n<p>These are situations when you need to raise a dispute:<\/p>\n<ul>\n<li>The cardholder disagrees with a transaction charged to their Adyen-issued card.<br>If a merchant refuses to make a refund directly to your cardholder, the cardholder can raise a dispute for a chargeback through your UI.<\/li>\n<li>The cardholder reports fraudulent transactions.<br>If a cardholder realizes their card was lost or stolen, and transactions were charged to their card, you should close their card immediately and report those fraudulent transactions to the card scheme.<\/li>\n<\/ul>\n<p>To raise disputes for Adyen to submit to card schemes you can do one of the following:<\/p>\n<ul>\n<li>Provide a UI for your cardholders to ask for their money back and to report fraudulent transactions and lost cards using the  <a href=\"https:\/\/docs.adyen.com\/api-explorer\/transfers-api\/latest\/overview\" class=\" external-link no-image\" target=\"_blank\" rel=\"nofollow noopener noreferrer\">Raise disputes API<\/a><\/li>\n<li>Package dispute details and supporting information into a zip file and <a href=\"\/pt\/issuing\/raise-disputes\/bulk-upload\">upload them through the Customer Area (pilot feature)<\/a>.<\/li>\n<\/ul>\n<p>You can raise a dispute for any <a href=\"\/pt\/issuing\/payment-stages#captured\">captured payment<\/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;\"><strong><a href=\"\/pt\/issuing\">Issuing Integration<\/a><\/strong><\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\"><strong><a href=\"\/pt\/issuing\/manage-access\/webservice-roles\">API credential roles<\/a><\/strong><\/td>\n<td style=\"text-align: left;\">Make sure that you have the following webservice role:<ul><li><strong>Bank disputes webservice role<\/strong><\/li><\/ul><\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\"><strong><a href=\"\/pt\/account\/user-roles#financial-products\">Customer Area roles<\/a><\/strong><\/td>\n<td style=\"text-align: left;\">Make sure that you have the following role to view disputes: <ul><li><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><strong>Dispute webhooks<\/strong><\/li><li><strong>Transfer webhooks<\/strong><\/li><\/ul><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<h2>How it works<\/h2>\n<ol>\n<li>Locate the transactionId for which your cardholder wants to raise a dispute for a chargeback or for a report of fraudulent activity.<br \/>\nIf you suspect your cardholder's card has been lost or stolen, make sure to <a href=\"\/pt\/issuing\/manage-cards#close-card\">close the card<\/a>.<\/li>\n<li>Raise a dispute for one of the following dispute types:\n<ul>\n<li><span translate=\"no\"><strong>duplicate<\/strong><\/span> - The transaction was a duplicate charge.<\/li>\n<li><span translate=\"no\"><strong>fraud<\/strong><\/span> - The transaction was fraudulent.<\/li>\n<li><span translate=\"no\"><strong>notDelivered<\/strong><\/span> - Goods or services were not delivered.<\/li>\n<\/ul><\/li>\n<li>Optionally provide supporting information for the dispute as attachments.<\/li>\n<li>Present the information in the raised dispute to your cardholder for review.<\/li>\n<li>Update the status of the cardholder's dispute to <span translate=\"no\"><strong>submitted<\/strong><\/span> or <span translate=\"no\"><strong>closed<\/strong><\/span>.<br \/>\nIf you are raising disputes in the Customer Area, this step is not required.<\/li>\n<li>Watch dispute webhooks for status changes to the submitted dispute, or view the status of disputes in the Customer Area.<\/li>\n<li>Watch transfer webhooks for the movement of funds due to a chargeback or second chargeback, or view them in the Balance Platform Accounting Report.<\/li>\n<\/ol>\n<h2>Dispute reasons and their types<\/h2>\n<p>Cardholders have a maximum limit of 35 disputes that they can raise over the course of their possession of their card. Cardholders can raise a dispute for one of the following dispute reasons.<\/p>\n<table>\n<thead>\n<tr>\n<th style=\"text-align: left;\">Dispute reason<\/th>\n<th style=\"text-align: left;\">Dispute type<\/th>\n<th style=\"text-align: left;\">Timeline<\/th>\n<th style=\"text-align: left;\">Information<\/th>\n<th style=\"text-align: left;\">Suggested attachments<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td style=\"text-align: left;\">Transaction was a duplicate charge<\/td>\n<td style=\"text-align: left;\"><span translate=\"no\"><strong>duplicate<\/strong><\/span><\/td>\n<td style=\"text-align: left;\">120 days from the date of the authorized transaction.<\/td>\n<td style=\"text-align: left;\"><ul><li>The transaction ID for the duplicate charge the cardholder disputes.<br>The transaction amount must be the same for both transactions.<\/li><li>Was the duplicate charge made on the same card?<\/li><li>Were the charges made on a card (or cards) issued by the same issuer?<br>All charges must have been made on cards issued by Adyen.<\/li><\/ul><\/td>\n<td style=\"text-align: left;\"><ul><li>receipts<\/li><li>card statements<\/li><\/ul><\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\">Transaction was fraudulent<\/td>\n<td style=\"text-align: left;\"><span translate=\"no\"><strong>fraud<\/strong><\/span><\/td>\n<td style=\"text-align: left;\">120 days from the date of the authorized transaction.<\/td>\n<td style=\"text-align: left;\"><ul><li>Description of the issue<\/li><li>Is the cardholder in possession of the card?<\/li><li>Was the card counterfeit?<\/li><li>Is this dispute a fraud report only, with no expectation of a chargeback?<\/li><\/ul><\/td>\n<td style=\"text-align: left;\"><ul><li>receipts<\/li><li>card statements<\/li><li>correspondence with the merchant<\/li><\/ul><\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\">Goods or services were not delivered<\/td>\n<td style=\"text-align: left;\"><span translate=\"no\"><strong>notDelivered<\/strong><\/span><\/td>\n<td style=\"text-align: left;\">120 days from the date that goods or services should have been delivered.<\/td>\n<td style=\"text-align: left;\"><ul><li>What was not delivered? One of the following:<ul><li><span translate=\"no\"><strong>goods<\/strong><\/span><\/li><li><span translate=\"no\"><strong>services<\/strong><\/span><\/li><\/ul><\/li><li>Description of the issue<\/li><li>Last expected date?<\/li><\/td>\n<td style=\"text-align: left;\"><ul><li>receipts<\/li><li>card statements<\/li><li>correspondence with the merchant<\/li><\/ul><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<h2>Lifecycle of a raised dispute<\/h2>\n<p>A dispute has the following lifecycle, which you can follow through status changes in dispute webhooks. When you raise a dispute on behalf of a cardholder, Adyen creates an ID for the dispute, and informs your system with a  <a href=\"https:\/\/docs.adyen.com\/api-explorer\/dispute-webhooks\/latest\/post\/balancePlatform.dispute.created\" class=\"codeLabel  external-link no-image\" target=\"_blank\" rel=\"nofollow noopener noreferrer\">balancePlatform.dispute.created<\/a> webhook. The initial status of a raised dispute is <span translate=\"no\"><strong>draft<\/strong><\/span>. However, if you <a href=\"\/pt\/issuing\/raise-disputes\/bulk-upload\">raised the dispute by uploading a file in the Customer Area<\/a>, Adyen automatically updates the status to <span translate=\"no\"><strong>submitted<\/strong><\/span> once it is processed.<\/p>\n<p>While the status of the dispute is <span translate=\"no\"><strong>draft<\/strong><\/span>, your cardholder may change the status of the dispute to <span translate=\"no\"><strong>closed<\/strong><\/span> for any reason.<\/p>\n<p>When your cardholder is satisfied with the information for the dispute, they must change the status of the dispute to <span translate=\"no\"><strong>submitted<\/strong><\/span>. Adyen then packages the dispute and sends it to the card scheme for review.<\/p>\n<p>Whenever there is a change of status for a raised dispute, Adyen informs your system with a  <a href=\"https:\/\/docs.adyen.com\/api-explorer\/dispute-webhooks\/latest\/post\/balancePlatform.dispute.updated\" class=\"codeLabel  external-link no-image\" target=\"_blank\" rel=\"nofollow noopener noreferrer\">balancePlatform.dispute.updated<\/a> webhook.<\/p>\n<p><img alt=\"Lifecycle of a raised dispute\" src=\"\/user\/pages\/docs\/07.issuing\/25.raise-disputes\/raised-dispute-lifecycle.svg?decoding=auto&amp;fetchpriority=auto\" \/><\/p>\n<table>\n<thead>\n<tr>\n<th style=\"text-align: left;\">Dispute status<\/th>\n<th style=\"text-align: left;\">Description<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td style=\"text-align: left;\"><span translate=\"no\"><strong>draft<\/strong><\/span><\/td>\n<td style=\"text-align: left;\">A dispute ID was created for the raised dispute, but the <code>status<\/code> of the dispute has not been set to <span translate=\"no\"><strong>submitted<\/strong><\/span> or <span translate=\"no\"><strong>closed<\/strong><\/span>.<\/br><\/br>You can still edit a dispute with a <span translate=\"no\"><strong>draft<\/strong><\/span> status.<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\"><span translate=\"no\"><strong>closed<\/strong><\/span><\/td>\n<td style=\"text-align: left;\">The status of the raised dispute is <span translate=\"no\"><strong>closed<\/strong><\/span>.<\/br><\/br>You cannot edit, reopen, or submit a closed dispute.<br\/><br\/> Possible reasons for a closed status are:<ul><li>You have closed the dispute<\/li><li>The timeframe allowed to submit a dispute has passed<\/li><li>Adyen deems your dispute ineligible for chargeback<\/li><li>The card scheme rejected your dispute request<\/li><\/ul><\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\"><span translate=\"no\"><strong>submitted<\/strong><\/span><\/td>\n<td style=\"text-align: left;\">The cardholder reviewed and submitted the dispute to Adyen to process with the card scheme.<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\"><span translate=\"no\"><strong>chargeback<\/strong><\/span><\/td>\n<td style=\"text-align: left;\">The funds were returned to your dispute account.<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\"><span translate=\"no\"><strong>won<\/strong><\/span><\/td>\n<td style=\"text-align: left;\">The acquirer can no longer challenge the dispute.<br\/>The timeline for challenging a dispute is different for each card scheme:<ul><li>Mastercard - 45 days after the date of chargeback<\/li><li>Visa - 30 days after the date of chargeback<\/li><\/ul><\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\"><span translate=\"no\"><strong>secondPresentment<\/strong><\/span><\/td>\n<td style=\"text-align: left;\">The funds have been returned to the acquirer.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<h3>Associating IDs throughout the dispute lifecycle:<\/h3>\n<p>Adyen informs your system of any updates to the status of your raised disputes with  <a href=\"https:\/\/docs.adyen.com\/api-explorer\/dispute-webhooks\/latest\/post\/balancePlatform.dispute.updated\" class=\"codeLabel  external-link no-image\" target=\"_blank\" rel=\"nofollow noopener noreferrer\">balancePlatform.dispute.updated<\/a> webhooks. You can follow the dispute throughout its lifecycle by paying attention to the  <a href=\"https:\/\/docs.adyen.com\/api-explorer\/dispute-webhooks\/latest\/post\/balancePlatform.dispute.updated#{param-type}-data-status\" class=\"codeLabel  external-link no-image\" target=\"_blank\" rel=\"nofollow noopener noreferrer\">status<\/a> of the dispute and by correlating the <code>transactionId<\/code>, the dispute ID, and the Acquirer Reference Number (<code>arn<\/code>).<\/p>\n<ul>\n<li> <a href=\"https:\/\/docs.adyen.com\/api-explorer\/dispute-webhooks\/latest\/post\/balancePlatform.dispute.updated#{param-type}-data-arn\" class=\"codeLabel  external-link no-image\" target=\"_blank\" rel=\"nofollow noopener noreferrer\">arn<\/a>: The Acquirer Reference Number (<code>arn<\/code>) is a unique number assigned to a card transaction when it goes from the merchant's bank (acquirer) through the card scheme at the cardholder's bank (issuer).<\/li>\n<li> <a href=\"https:\/\/docs.adyen.com\/api-explorer\/dispute-webhooks\/latest\/post\/balancePlatform.dispute.updated#{param-type}-data-id\" class=\"codeLabel  external-link no-image\" target=\"_blank\" rel=\"nofollow noopener noreferrer\">id<\/a>: Unique ID for the dispute that Adyen creates when you raise a dispute for a card transaction.<\/li>\n<li> <a href=\"https:\/\/docs.adyen.com\/api-explorer\/dispute-webhooks\/latest\/post\/balancePlatform.dispute.updated#{param-type}-data-transactionId\" class=\"codeLabel  external-link no-image\" target=\"_blank\" rel=\"nofollow noopener noreferrer\">transactionId<\/a>: The Adyen event ID for the capture that you use to raise the dispute.<\/li>\n<\/ul>\n<p>Additionally, if the <code>status<\/code> of your dispute is <span translate=\"no\"><strong>chargeback<\/strong><\/span> or <span translate=\"no\"><strong>secondPresentment<\/strong><\/span>, there is a balance mutation on the Disputes balance account.<\/p>\n<p>When there is a balance mutation, Adyen informs your system with a  <a href=\"https:\/\/docs.adyen.com\/api-explorer\/transfer-webhooks\/latest\/post\/balancePlatform.transfer.created\" class=\"codeLabel  external-link no-image\" target=\"_blank\" rel=\"nofollow noopener noreferrer\">balancePlatform.transfer.created<\/a> webhook with the following <code>category<\/code>, <code>type<\/code>, and <code>status<\/code> event mapping:<\/p>\n<table>\n<thead>\n<tr>\n<th style=\"text-align: left;\">Event<\/th>\n<th style=\"text-align: left;\"> <a href=\"https:\/\/docs.adyen.com\/api-explorer\/transfer-webhooks\/latest\/post\/balancePlatform.transfer.created#request-data-category\" class=\"codeLabel  external-link no-image\" target=\"_blank\" rel=\"nofollow noopener noreferrer\">category<\/a><\/th>\n<th style=\"text-align: left;\"> <a href=\"https:\/\/docs.adyen.com\/api-explorer\/transfer-webhooks\/latest\/post\/balancePlatform.transfer.created#request-data-type\" class=\"codeLabel  external-link no-image\" target=\"_blank\" rel=\"nofollow noopener noreferrer\">type<\/a><\/th>\n<th style=\"text-align: left;\"> <a href=\"https:\/\/docs.adyen.com\/api-explorer\/transfer-webhooks\/latest\/post\/balancePlatform.transfer.created#request-data-status\" class=\"codeLabel  external-link no-image\" target=\"_blank\" rel=\"nofollow noopener noreferrer\">status<\/a><\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td style=\"text-align: left;\"><span translate=\"no\"><strong>chargeback<\/strong><\/span><\/td>\n<td style=\"text-align: left;\"><span translate=\"no\"><strong>issuedCard<\/strong><\/span><\/td>\n<td style=\"text-align: left;\"><span translate=\"no\"><strong>chargeback<\/strong><\/span><\/td>\n<td style=\"text-align: left;\"><span translate=\"no\"><strong>chargeback<\/strong><\/span><\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\"><span translate=\"no\"><strong>secondPresentment<\/strong><\/span><\/td>\n<td style=\"text-align: left;\"><span translate=\"no\"><strong>issuedCard<\/strong><\/span><\/td>\n<td style=\"text-align: left;\"><span translate=\"no\"><strong>secondChargeback<\/strong><\/span><\/td>\n<td style=\"text-align: left;\"><span translate=\"no\"><strong>secondChargeback<\/strong><\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>This event mapping for a <span translate=\"no\"><strong>chargeback<\/strong><\/span> or <span translate=\"no\"><strong>secondPresentment<\/strong><\/span> is also reflected in the <a href=\"\/pt\/issuing\/report-types\/balance-platform-accounting-report\">Balance Platform Accounting Report<\/a>. The ARN is the common link between the original transaction, the raised dispute, and the <span translate=\"no\"><strong>chargeback<\/strong>\/<strong>secondChargeback<\/strong><\/span> transfer events. You can locate the ARN in the  <a href=\"https:\/\/docs.adyen.com\/api-explorer\/transfer-webhooks\/latest\/post\/balancePlatform.transfer.created#request-data-reference\" class=\"codeLabel  external-link no-image\" target=\"_blank\" rel=\"nofollow noopener noreferrer\">reference<\/a> parameter of the  <a href=\"https:\/\/docs.adyen.com\/api-explorer\/transfer-webhooks\/latest\/post\/balancePlatform.transfer.created\" class=\"codeLabel  external-link no-image\" target=\"_blank\" rel=\"nofollow noopener noreferrer\">balancePlatform.transfer.created<\/a> webhook Adyen sends to your server.<\/p>","url":"https:\/\/docs.adyen.com\/pt\/issuing\/raise-disputes","articleFields":{"description":"Learn about the types of disputes you can raise and how to track a dispute's status throughout its lifecycle.","next_steps":[{"title":"Raise a dispute for a duplicate charge","description":"Learn how to raise a dispute for a duplicate transaction charge.","url":"\/issuing\/raise-disputes\/duplicate","required":true},{"title":"Raise a dispute for fraud","description":"Learn how to raise a dispute for fraudulent activity.","url":"\/issuing\/raise-disputes\/fraud","required":true},{"title":"Raise a dispute for non-delivery","description":"Learn how to raise a dispute for non-delivery of goods or services.","url":"\/issuing\/raise-disputes\/not-delivered","required":true},{"title":"Upload and manage attachments","description":"Learn how to add attachments as supporting information for your dispute.","url":"\/issuing\/raise-disputes\/attach-supporting-information","required":false}],"parameters":{"directoryPath":"\/issuing"}},"algolia":{"url":"https:\/\/docs.adyen.com\/pt\/issuing\/raise-disputes","title":"Raise disputes for transactions made with an Adyen-issued card","content":"As a platform that issues cards through Adyen, you must be able to raise disputes on behalf of your cardholders.\nThese are situations when you need to raise a dispute:\n\nThe cardholder disagrees with a transaction charged to their Adyen-issued card.If a merchant refuses to make a refund directly to your cardholder, the cardholder can raise a dispute for a chargeback through your UI.\nThe cardholder reports fraudulent transactions.If a cardholder realizes their card was lost or stolen, and transactions were charged to their card, you should close their card immediately and report those fraudulent transactions to the card scheme.\n\nTo raise disputes for Adyen to submit to card schemes you can do one of the following:\n\nProvide a UI for your cardholders to ask for their money back and to report fraudulent transactions and lost cards using the  Raise disputes API\nPackage dispute details and supporting information into a zip file and upload them through the Customer Area (pilot feature).\n\nYou can raise a dispute for any captured payment.\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 Integration\n\n\nAPI credential roles\nMake sure that you have the following webservice role:Bank disputes webservice role\n\n\nCustomer Area roles\nMake sure that you have the following role to view disputes: Manage issuing disputes\n\n\nWebhooks\nSubscribe to the following webhook(s): Dispute webhooksTransfer webhooks\n\n\n\nHow it works\n\nLocate the transactionId for which your cardholder wants to raise a dispute for a chargeback or for a report of fraudulent activity.\nIf you suspect your cardholder's card has been lost or stolen, make sure to close the card.\nRaise a dispute for one of the following dispute types:\n\nduplicate - The transaction was a duplicate charge.\nfraud - The transaction was fraudulent.\nnotDelivered - Goods or services were not delivered.\n\nOptionally provide supporting information for the dispute as attachments.\nPresent the information in the raised dispute to your cardholder for review.\nUpdate the status of the cardholder's dispute to submitted or closed.\nIf you are raising disputes in the Customer Area, this step is not required.\nWatch dispute webhooks for status changes to the submitted dispute, or view the status of disputes in the Customer Area.\nWatch transfer webhooks for the movement of funds due to a chargeback or second chargeback, or view them in the Balance Platform Accounting Report.\n\nDispute reasons and their types\nCardholders have a maximum limit of 35 disputes that they can raise over the course of their possession of their card. Cardholders can raise a dispute for one of the following dispute reasons.\n\n\n\nDispute reason\nDispute type\nTimeline\nInformation\nSuggested attachments\n\n\n\n\nTransaction was a duplicate charge\nduplicate\n120 days from the date of the authorized transaction.\nThe transaction ID for the duplicate charge the cardholder disputes.The transaction amount must be the same for both transactions.Was the duplicate charge made on the same card?Were the charges made on a card (or cards) issued by the same issuer?All charges must have been made on cards issued by Adyen.\nreceiptscard statements\n\n\nTransaction was fraudulent\nfraud\n120 days from the date of the authorized transaction.\nDescription of the issueIs the cardholder in possession of the card?Was the card counterfeit?Is this dispute a fraud report only, with no expectation of a chargeback?\nreceiptscard statementscorrespondence with the merchant\n\n\nGoods or services were not delivered\nnotDelivered\n120 days from the date that goods or services should have been delivered.\nWhat was not delivered? One of the following:goodsservicesDescription of the issueLast expected date?\nreceiptscard statementscorrespondence with the merchant\n\n\n\nLifecycle of a raised dispute\nA dispute has the following lifecycle, which you can follow through status changes in dispute webhooks. When you raise a dispute on behalf of a cardholder, Adyen creates an ID for the dispute, and informs your system with a  balancePlatform.dispute.created webhook. The initial status of a raised dispute is draft. However, if you raised the dispute by uploading a file in the Customer Area, Adyen automatically updates the status to submitted once it is processed.\nWhile the status of the dispute is draft, your cardholder may change the status of the dispute to closed for any reason.\nWhen your cardholder is satisfied with the information for the dispute, they must change the status of the dispute to submitted. Adyen then packages the dispute and sends it to the card scheme for review.\nWhenever there is a change of status for a raised dispute, Adyen informs your system with a  balancePlatform.dispute.updated webhook.\n\n\n\n\nDispute status\nDescription\n\n\n\n\ndraft\nA dispute ID was created for the raised dispute, but the status of the dispute has not been set to submitted or closed.You can still edit a dispute with a draft status.\n\n\nclosed\nThe status of the raised dispute is closed.You cannot edit, reopen, or submit a closed dispute. Possible reasons for a closed status are:You have closed the disputeThe timeframe allowed to submit a dispute has passedAdyen deems your dispute ineligible for chargebackThe card scheme rejected your dispute request\n\n\nsubmitted\nThe cardholder reviewed and submitted the dispute to Adyen to process with the card scheme.\n\n\nchargeback\nThe funds were returned to your dispute account.\n\n\nwon\nThe acquirer can no longer challenge the dispute.The timeline for challenging a dispute is different for each card scheme:Mastercard - 45 days after the date of chargebackVisa - 30 days after the date of chargeback\n\n\nsecondPresentment\nThe funds have been returned to the acquirer.\n\n\n\nAssociating IDs throughout the dispute lifecycle:\nAdyen informs your system of any updates to the status of your raised disputes with  balancePlatform.dispute.updated webhooks. You can follow the dispute throughout its lifecycle by paying attention to the  status of the dispute and by correlating the transactionId, the dispute ID, and the Acquirer Reference Number (arn).\n\n arn: The Acquirer Reference Number (arn) is a unique number assigned to a card transaction when it goes from the merchant's bank (acquirer) through the card scheme at the cardholder's bank (issuer).\n id: Unique ID for the dispute that Adyen creates when you raise a dispute for a card transaction.\n transactionId: The Adyen event ID for the capture that you use to raise the dispute.\n\nAdditionally, if the status of your dispute is chargeback or secondPresentment, there is a balance mutation on the Disputes balance account.\nWhen there is a balance mutation, Adyen informs your system with a  balancePlatform.transfer.created webhook with the following category, type, and status event mapping:\n\n\n\nEvent\n category\n type\n status\n\n\n\n\nchargeback\nissuedCard\nchargeback\nchargeback\n\n\nsecondPresentment\nissuedCard\nsecondChargeback\nsecondChargeback\n\n\n\nThis event mapping for a chargeback or secondPresentment is also reflected in the Balance Platform Accounting Report. The ARN is the common link between the original transaction, the raised dispute, and the chargeback\/secondChargeback transfer events. You can locate the ARN in the  reference parameter of the  balancePlatform.transfer.created webhook Adyen sends to your server.","type":"page","locale":"pt","boost":18,"hierarchy":{"lvl0":"Home","lvl1":"Adyen Issuing","lvl2":"Raise disputes for transactions made with an Adyen-issued card"},"hierarchy_url":{"lvl0":"https:\/\/docs.adyen.com\/pt","lvl1":"https:\/\/docs.adyen.com\/pt\/issuing","lvl2":"\/pt\/issuing\/raise-disputes"},"levels":3,"category":"Issuing","category_color":"green","tags":["Raise","disputes","transactions","Adyen-issued"]},"articleFiles":{"raised-dispute-lifecycle.svg":"<img alt=\"\" src=\"https:\/\/docs.adyen.com\/user\/pages\/docs\/07.issuing\/25.raise-disputes\/raised-dispute-lifecycle.svg?decoding=auto&amp;fetchpriority=auto\" \/>"}}