Send documentation

The Chargebacks API allows Localpayment clients to upload dispute documentation to pending chargebacks received, so that Localpayment can submit these documents to the relevant issuers for processing.

If a chargeback is received a notification is sent via our callback notification service. After we have notified your server you will have 7 days to send the proper documentation to dispute the chargeback

Dispute file requirements

• Each chargeback dispute must be fully contained within a single file.

Chargeback -> Send documentation to dispute a Chargeback

POST https://api.stage.localpayment.com /api/chargeback/documentation/:externalId

Send documentation to start a chargeback

Path Parameters

Name	Type	Description
externalId *	String	Mandatory. The same externalId specified when the order was created. Each ID should be unique and meaningful to you and your system.

Headers

Name	Type	Description
Authorization*	String	Mandatory. JWT token in format Bearer eyJ0... . For more information about authentication, please refer to Authentication token.

Request Body

Name	Type	Description
files*	form-data	Mandatory. Attach the documentation that refers to the charbacked operation. You

200: OK A chargeback has been started

{
    "externalId": "1652301353",
    "internalId": "5a76070b-cd60-4f4a-9186-044d76a9d4fd",
    "status": {
        "code": "101",
        "description": "DOC_RECEIVED",
        "detail": "Dispute documentation received"
    }
}

401: Unauthorized The period to respond to a chargeback has expired

Request

curl --location \
--request POST '{{api_base_url}}/api/chargeback/documentation/1668019382' \
--header 'Authorization: Bearer {{token}}' \
--form 'files=@"/path/to/file"'

Status Ok

Notification sample

In Dispute notification

{
  "transactionType": "ChargeBack",
  "data": {
    "externalId": "1668802354",
    "internalId": "3b95aeb9-c22e-4301-909e-d160e1dcebed",
    "accountNumber": "032.032.00000001",
    "transactionType": "ChargeBack",
    "comment": "ChargeBack transaction originated by: 7fd9c89a-4f6e-4912-b478-890b86429df7",
    "status": {
      "code": "102",
      "description": "INDISPUTE",
      "detail": "Dispute documentation was sent to the acquire"
    },
    "dateCreated": "2022-11-22T20:18:50Z",
    "dateProcessed": "2022-11-22T20:20:09Z"
  }
}