Enrichment by business model
The evidence that moves outcomes for SaaS and e-commerce disputes: subscription fields, customer activity logs, order products, and fulfillment tracking.
The evidence that wins a dispute depends on what you sell. A SaaS charge has no tracking number, so the case rests on proving the customer signed up, used the service, and knew the billing terms. A physical-goods charge turns on what was ordered and where it was delivered. Everything below is sent to the same endpoint:
PATCH https://api.chargeflow.io/public/2025-04-01/disputes/{disputeId}Use the Chargeflow dispute ID (dispute.id) from the dispute.created webhook as the path parameter. See Enrich a dispute for upsert semantics and the array merge behavior that applies to products[] and fulfillments[].
Find your evidence set
Customer communication
Whatever you sell, a record of your interactions with the customer strengthens the response: conversations where you provided shipping updates, where the customer acknowledged the service, asked for a refund, or where you offered a resolution before the dispute was filed.
- Structured messages: use the Customer communication endpoint to send helpdesk conversations programmatically.
- File upload: use the Upload evidence endpoint with
evidenceUploadCategory: "customer_communication"to attach a screenshot.
How to send this data
| Data | Endpoint |
|---|---|
| Order, products, fulfillments, transaction context | PATCH /public/2025-04-01/disputes/{disputeId} |
| Subscription record | POST /public/2025-04-01/disputes/{disputeId}/subscription (required: source_id, created_at, start_date, frequency, frequency_count) |
| Activity logs | POST /public/2025-04-01/disputes/{disputeId}/user_events_log |
| Communication records | POST /public/2025-04-01/customer-communication |
Confirm it landed
Each call returns the updated dispute, and the record then appears on that dispute in the Chargeflow dashboard. To re-check later, read the dispute back with GET /public/2025-04-01/disputes/{disputeId}: that response is the authoritative view of what Chargeflow stored.