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.
Endpionts:
Production: https://transactions.transactional.unico.app/api/public/v1. We
To see all possible statuses, refer to the Enumerated section.
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.
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"
Requestor's information.
Identification key type for the requestor.
"cpf"
Identification key value for the requestor.
"USER_CPF"
Name of the requestor.
"USER_NAME"
Reason for the chargeback request.
"REQUEST_REASON"
General observations about the request.
"GENERAL_OBSERVATIONS"
Documents related to the chargeback. Up to 3 items are allowed, and each document must be Base64 encoded. Only PDF files are accepted.
File name or description.
"FILE_NAME"
Base64 encoded PDF file.
"JVBERi0xLjQKMSAwI=="
Chargeback request successful.
Generated chargeback 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}.
Chargeback status retrieved successfully.
Chargeback ID.
"8263a268-5388-492a-bca2-28e1ff4a69f0"
Current status of the chargeback.
"waiting"