Your API requests are authenticated using an access token. Any request that does not include a valid access token will return an error.
You can learn more about how to generate an access token here.
Endpoint to request a chargeback review for a specified transaction.
Transaction ID to be submitted for chargeback.
A valid access token. The value must be sent in the format Bearer {token}.
Chargeback request date and time in ISO 8601 format.
2023-01-05T03:00:00.000Z
Name of the requestor.
USER_NAME
Reason for the chargeback request.
REQUEST_REASON
General observations about the request.
GENERAL_OBSERVATIONS
POST /api/public/v1/credit/transactions/{transaction_id}/chargeback HTTP/1.1
Host: transactions.transactional.uat.unico.app
Authorization: text
Content-Type: application/json
Accept: */*
Content-Length: 231
{
"datetime": "2023-01-05T03:00:00.000Z",
"requestor": {
"key": "cpf",
"value": "USER_CPF"
},
"name": "USER_NAME",
"reason": "REQUEST_REASON",
"observation": "GENERAL_OBSERVATIONS",
"documents": [
{
"label": "FILE_NAME",
"data": "JVBERi0xLjQKMSAwI=="
}
]
}
{
"id": "8263a268-5388-492a-bca2-28e1ff4a69f0"
}
Endpoint to check the status of a specific chargeback for a transaction.
Transaction ID associated with the chargeback.
Chargeback ID to be retrieved.
A valid access token. The value must be sent in the format Bearer {token}.
GET /api/public/v1/credit/transactions/{transaction_id}/chargeback/{chargeback_id} HTTP/1.1
Host: transactions.transactional.uat.unico.app
Authorization: text
Accept: */*
{
"id": "8263a268-5388-492a-bca2-28e1ff4a69f0",
"status": "waiting"
}
To optimize your application's performance, you can also implement our Webhook to know when to query the Chargeback status.
Didn't find something or still need help? If you're already a client or partner, you can reach out through our Help Center.