Accept Chargeback Process
Overview
This document describes the complete workflow for accepting chargebacks using the Justt API. The accept chargeback process allows merchants to acknowledge the validity of a customer's chargeback claim and allow funds to be returned without disputing the claim.
Prerequisites
- Valid Justt API Bearer token for authentication
- Chargeback must have an open status
- Payment processor must support chargeback acceptance
- Optional: reference-account-id header for multi-merchant accounts
Process Flow
1. Receive Chargeback Notification
Chargebacks can be discovered through:
- Webhook notifications (recommended for real-time processing)
- API polling using the GET /chargebacks endpoint
2. Accept the Chargeback
Endpoint: POST /chargebacks/:id/accept
Important Notes:
- This action is irreversible - once accepted, the chargeback cannot be disputed
- The process is asynchronous - acceptance happens in the background
- You'll receive an internal ID to track the acceptance status
3. Monitor Acceptance Status
Endpoint: GET /chargebacks/:id/accept
4. Status Values
| Status | Description |
|---|---|
| created | Acceptance request has been created but not yet processed |
| inProgress | Acceptance is being processed with the payment processor |
| succeeded | Chargeback has been successfully accepted |
| failed | Acceptance failed (see error field for details) |
Monitoring Options
Option A: Status Polling
- Poll the GET /chargebacks/:id/accept endpoint
- Use exponential backoff strategy
- Check status until "succeeded" or "failed"
Option B: Webhook Notifications
- Configure webhook endpoint to receive real-time updates
- Process chargeback acceptance events automatically
- More efficient than polling
Error Handling
Common Error Scenarios
-
400 Bad Request
- Invalid chargeback ID format
- Chargeback not eligible for acceptance
- Missing required parameters
-
404 Not Found
- Chargeback doesn't exist
- No access to the specified chargeback
-
500 Internal Server Error
- PSP communication failure
- Temporary service unavailability
Best Practices
- Always validate chargeback status before attempting acceptance
- Implement retry logic with exponential backoff for failed requests
- Use webhooks when possible for real-time status updates
Multi-Merchant Account Support
If your account encompasses multiple merchants, include the reference-account-id header in all requests.
Updated 9 months ago