Issuin icon

Raise a dispute for a duplicate charge

Learn how to raise a dispute for a duplicate charge made either on a single card, or on two Adyen-issued cards.

If a cardholder notices duplicate charges for the purchase of goods or services, they can submit a duplicate charge dispute to receive a chargeback for the transaction.

Requirements

Before you begin, take into account the requirements, limitations, and preparations described under Raise disputes.

1. Raise a duplicate charge dispute

  1. Find the transaction IDs for which you want to raise a dispute for a duplicate charge transaction made to the Adyen-issued card(s).
    You can find a transaction ID in one of the following locations:

  2. Make a POST /disputes request, specifying the following parameters:

    Parameter Type Required Description
    description string Your reference for the dispute. The description appears in dispute webhooks for your information. Do not include any personally-identifiable information (PII) in this field. Maximum length: 50 characters.
    duplicateInfo object -white_check_mark- Additional information for raising a dispute of type duplicate. Required for disputes of type duplicate.
    duplicateInfo.duplicateTransactionId string -white_check_mark- The transaction id associated with the duplicate charge for which you are disputing. The disputed transaction must be in the same amount as the duplicate transaction.
    duplicateInfo.sameCard boolean -white_check_mark- The duplicate charge was made on the same card. Possible values: true, false.
    duplicateInfo.sameIssuer boolean The issuer associated with each charge is the same. Possible values: true, false.
    transactionId string -white_check_mark- The unique reference of the transaction for which you are raising the dispute.
    type string -white_check_mark- The type of the dispute. When raising a dispute for a duplicate charge, the value must be duplicate.

  3. Make a note of the dispute id in the response. You need this ID to provide supporting information as an attachment, update the dispute, submit the dispute for a duplicate charge, close the dispute, and follow the lifecycle of the dispute.

    The response includes the following additional parameters:

    Parameter Type Description
    arn string The unique Acquirer Reference Number (arn) generated by the card scheme for each capture. You can use the arn to trace the transaction through its lifecycle.
    id string The unique identifier of the raised dispute.
    status string The current status of the dispute. You can update a dispute to submitted or closed. Possible values: draft, submitted, closed, won, chargeback, secondChargeback.

    Adyen sends a balancePlatform.dispute.created webhook to your server for the dispute with a status of draft.

2. Upload attachments (optional)

We recommend that your cardholder upload supporting documentation, such as receipts, communication with a merchant, or any additional documents that would help the card scheme when they are reviewing the dispute.

When you present the screen to cardholders to upload attachments, make sure they know which file types we support (JPEG, PDF, TIFF).

  1. Base64-encode any attachments the cardholder provides for upload with their dispute.

  2. Make a POST /disputes/{disputeId}/attachments request, specifying the disputeId as a path parameter and the following request parameters.

    Parameter name Type Required Description
    attachmentType string -white_check_mark- The type of information contained in the attachment.
    Possible values:
    • receipt
    • correspondence
    • other
    fileName string -white_check_mark- The name of the attachment, including its filename extension. Minimum length: four characters, Maximum length: 17 characters, including the extension type.
    Supported filename extensions:
    • jpeg
    • pdf
    • tiff
    Examples:
    • airfare24_03.jpeg
    • hotel24_0315.jpeg
    content string -white_check_mark- The content of the image. An attachment must be Base64-encoded data, with a maximum file size of 2 MB.

  3. In the response, note the attachmentId. You need the ID if you want to later get the attachment, or delete the attachment.

    Parameter name Type Description
    attachmentId string The unique identifier of the attachment.

3. Review the dispute

You should allow your cardholder to review their dispute. This allows the cardholder time to make sure they have captured all information correctly. The cardholder can then confirm they want you to submit the dispute to the card scheme on their behalf, or decide to make edits to their dispute.

  1. Make a GET /disputes/{id} request, specifying the dispute id as a request parameter.

  2. Present the details of the dispute to your cardholder.

4. Edit dispute details (optional)

If the cardholder wants to make any changes to the information they provided in their dispute, you can make a request to update the dispute.

  1. To update information in your dispute, make a PATCH /disputes/{id} request, specifying the dispute id as a path parameter, and supplying updated information in the following request parameters:

    You do not have to provide the complete dispute object in your PATCH request.

    Parameter Type Description
    duplicateInfo object The object containing additional information for raising a dispute of type duplicate. Required for disputes of type duplicate.
    duplicateInfo.duplicateTransactionId boolean The transaction id associated with the duplicate charge for which you are disputing. The disputed transaction must be in the same amount as the duplicate transaction.
    duplicateInfo.sameCard boolean The duplicate charge was made on the same card. Possible values: true, false.
    duplicateInfo.sameIssuer boolean The issuer associated with each charge is the same. Possible values: true, false.

  2. Present the updated dispute details from the response to your cardholder.

5. Submit the dispute

If your cardholder is satisfied with the information they provided for the dispute, they can confirm they want you to submit the dispute to the card scheme for review and a chargeback, if successful.

When you submit a dispute to the card scheme, you can no longer update the dispute, upload or delete attachments, or close the dispute.

  1. Make a PATCH /disputes/{id} request, specifying the dispute id as a path parameter, and include status with a value of submitted as a request parameter.

    A successful response includes the dispute object, with an updated status of submitted. Adyen also sends your system a balancePlatform.dispute.updated webhook with the updated status.

  2. Notify the cardholder that their dispute has been submitted.

6. Process webhooks for status changes

  1. Process balancePlatform.dispute.updated webhooks, looking for changes in the status of your raised dispute.

  2. If the status of a dispute changes to chargeback or secondChargeback, inspect balancePlatform.transfer.created webhooks for the matching Acquirer Reference Number (arn), and reconcile balances for the cardholder's balance account.

    • Lifecycle of a raised dispute describes in more detail how status changes for disputes are communicated to your system through Adyen webhooks, and how balance mutations are recorded in the Balance Platform Accounting Report.
    • Associating IDs throughout the dispute lifecycle describes the various IDs you should refer to when correlating original transactions, acquirer reference numbers, and dispute IDs to your raised disputes.

See also