The Chargeback API is a communication channel between the platform and merchants that have disputes assigned to them. lets merchants:

• list disputes assigned to them
• view dispute details
• view dispute history and audit trail
• contest(submit a challenge) or accept a dispute
• Upload supporting documents (evidence)
• download or list previously upload documents

The API is designed for secure, auditable exchanges and supports pagination, filtering, role-based access.

• Merchant - can access disputes that are assigned to their merchant account. Can contest, accept, upload documents
• Platform - internal use: assign disputes, change statuses, resolve disputes
• Auditor - read-only access for compliance teams (optional)

• Dispute Won = Merchant won the dispute and any chargeback debit is reversed
• Dispute Lost = Merchant lost the dispute and the chargeback amount will be debited from merchant
• Dispute Partially Won = Merchant lost the dispute, but the chargeback amount will not fully be debited from merchant
• Needs Response = Merchant must sent de document or accept the chargeback
• In Review = Reponse being validaded by Getnet Network

• documentation_reproved = PagoNxt staff determined that the uploaded documents cannot be used as evidence
• merchant_notified = The merchant has been notified that a response is needed
• verification_required = There are no pending issues on the merchant's side, as the necessary documents have been provided
• chargeback_accepted = There are no pending issues on the merchant's side, as the chargeback has been accepted

• retrieval_request = retriveal request occurs when the card issuer requests additional information about transaction before initiating a chageback.
• retrieval_fulfillment = The merchant's response to retrieval request. It includes all documents, notes submitted to satisfy the issuer's inquiry
• first_chargeback = A first chargeback (also know as initial chargeback) occurs when the issuer or cardholder disputes a transaction and funds can be debited from merchant
• second_representment = The second presentment (also called as represetnment) is the merchant's formal response to first chargeback. The merchant submits evidence to the acquirer, who forwards it to the issuer for review. If accepted the chargeback is reversed if rejected it may proceed to pre-arbitration
• pre_arbitration = Occurs when the issuer disagrees with the merchant's second presentment. It's the issuer's opportunity to reopen dispute before escalating it to the card network arbitration.
• arbitration_chargeback = final stage of the dispute process, where the card network makes a biding decision. At this point both parties have submitted evidence, and the network rules in favor either the issuer or the merchant. This decision is final and non-reversible

To obtain API credentials, please contact your Account Manager for guidance. Your Account Manager will provide the necessary instructions andd assist you with the onboarding and credential gerenation process including your client_id, client_secret.

1. The merchant (or platform client) authenticats usign OAuth 2.0 - client credentials flow
2. The platform issues a Bearer access token with specific scope
3. Every subsequent request to the API must include the Authorization header with token

1. Obtain an access token from /oauth2/access_token
2. Use the token in all subsequent API call as Authorization: Bearer <access_token>
3. Token expires after 1 hour. Use refresh token if available

• All endpoijnts require HTTPS (TLS 1.2+).
• Access is controlled by OAuth2 scopes and merchant ownership
• Evidences files are stored encrypted at rest
• All actions are logged for audit
• Compliance with PCI-DSS, GDPR and LGPD standards