Chargebacks

When a customer disputes a payment, NoChurn gathers the evidence it already has, drafts a reply and waits for a person to review it. When the card network sends an early fraud warning, NoChurn shows it so you can refund before it becomes a dispute.

Which providers

Provider	Disputes in NoChurn
Stripe, Braintree, Razorpay	Evidence gathered and a reply drafted; sent to the provider after review. Stripe also sends early fraud warnings
Paddle, Lemon Squeezy, Polar	The merchant of record answers disputes; NoChurn shows them read only
Chargebee, Recurly, Maxio, Zuora	Disputes stay with the payment gateway behind them; when that gateway is a connected Stripe account, NoChurn handles them as above
Mollie, GoCardless	No API to contest: chargebacks show read only
App Store, Google Play	Refund requests: NoChurn prepares the answer from your data

Details per provider: Integrations.

How a dispute is handled

1. Opened. The dispute arrives from the provider with its deadline. Admins are told by email when it opens and again 72 hours before the deadline (Slack is optional).
2. Evidence. NoChurn collects what it has on the customer, each piece with its source: the cancel flow and what the customer chose, the emails sent, usage, conversations from your help desk (quoted as is, never rewritten), and your policies. PATCH /v1/disputes/{id}/evidence includes, excludes, reorders or adds a note; POST /v1/disputes/{id}/evidence_files attaches a PDF, JPEG or PNG (5 MB each, as many files as the provider accepts).
3. Draft. The AI drafts the reply from the included evidence only, and must cite it. POST /v1/disputes/{id}/draft drafts again; PATCH /v1/disputes/{id}/draft edits or approves it (any edit sends it back to draft).
4. Review and send. A person sends it: POST /v1/disputes/{id}/submit, final, admin or owner, with confirm: true. After that nothing can change. If a reply was already sent another way (for example from the provider’s dashboard), NoChurn does not send a second one and answers 409 dispute_already_submitted.
5. Or accept. POST /v1/disputes/{id}/accept (final, admin or owner, confirm: true) when contesting is not worth it.

NoChurn also estimates the chance of winning (0 to 100, with its factors), which a person can override (PATCH /v1/disputes/{id}/win_score). It can suggest accepting a dispute when contesting is likely to cost more than it brings back, compared with your contest cost (disputes_settings.contest_cost_cents, no default value: without it, NoChurn never suggests accepting). NoChurn never accepts a dispute on its own.

Automatic sending

Off by default. When you turn it on (disputes_settings.auto_submit on PATCH /v1/account, owner or admin), NoChurn sends only a reply a person has approved, auto_submit_hours_before the deadline, and only when the chance of winning reaches auto_submit_min_score.

Early fraud warnings

GET /v1/fraud_warnings lists them (Stripe). POST /v1/fraud_warnings/{id}/refund refunds the payment before a dispute (final, admin or owner, confirm: true); by default it also cancels the customer’s subscriptions (cancel_subscription_on_fraud_refund). POST /v1/fraud_warnings/{id}/dismiss keeps the payment. Automatic refunds are off by default (auto_refund_fraud_warnings).

Numbers

GET /v1/disputes/summary counts the disputes by state, with the amount won (disputes won only) and a win rate that always comes with the number of decided disputes, null until one is decided.