E-Commerce Chargeback Representment Builder

$2.50 USDC per call · Business, finance and compliance · POST /api/v1/fight-chargeback · Id chargeback-fighter

Tells a merchant whether to fight or accept a card dispute: scores win probability against the network rubric for the reason code (Visa, Mastercard, Amex, Discover), runs deterministic Visa CE3.0 eligibility and invalid-dispute checks, computes expected recovery net of the contest fee and days to the deadline, and returns a processor-ready submission (summary under 4,000 characters, evidence fields in dispute-form order, missing items marked NOT AVAILABLE). Uses only supplied evidence and never fabricates it. Not legal advice; the issuer decides.

What you get

A lost chargeback costs the order value plus a $15-$100 dispute fee and counts toward network monitoring thresholds. A dispute-response specialist or service typically charges 15-25% of recovered revenue; this returns the fight-or-accept call and a submission-ready response per dispute.

Call it

Send the JSON body below to https://agents.writerslogic.com/api/v1/fight-chargeback. An unpaid request answers 402 with the price and how to pay; a request that fails with a 5xx status is not charged.

curl -i -X POST https://agents.writerslogic.com/api/v1/fight-chargeback \
  -H 'content-type: application/json' \
  -d '{"network":"visa","reasonCode":"13.1","disputeDate":"2026-10-20","orderDetails":{"orderId":"SHOP-10442","amount":189,"currency":"USD","transactionDate":"2026-09-28","items":[{"name":"Trail running shoes, size 10","quantity":1,"unitPrice":189}],"shippingAddress":"42 Elm St, Austin, TX 78701","productType":"physical"},"evidence":{"trackingNumber":"1Z999AA10123456784","carrier":"UPS","deliveryConfirmation":"Delivered 2026-10-02 14:12, left at front door, 42 Elm St Austin TX","deliveryDate":"2026-10-02","avsResult":"Y (full match)","cvvResult":"M (match)","customerCommunications":"2026-10-03 customer email: '\''Got the shoes, they run a bit small.'\''"}}'

Input

Field	Type	Required	Description
`network`	string; one of "visa", "mastercard", "amex", "discover"	yes
`reasonCode`	string	yes	e.g. 10.4, 13.1, 13.3 (Visa); 4837, 4853, 4855 (Mastercard).
`disputeDate`	string	no
`disputeFeeUsd`	number; 0..10000	no	Fee your processor charges to contest the dispute and does not return on a loss; used to net the expected value.
`responseDeadline`	string	no	Deadline shown in your processor's dispute dashboard (YYYY-MM-DD); days remaining are computed from it.
`orderDetails`	object	yes
`evidence`	object	yes

Example request body

{
  "network": "visa",
  "reasonCode": "13.1",
  "disputeDate": "2026-10-20",
  "orderDetails": {
    "orderId": "SHOP-10442",
    "amount": 189,
    "currency": "USD",
    "transactionDate": "2026-09-28",
    "items": [
      {
        "name": "Trail running shoes, size 10",
        "quantity": 1,
        "unitPrice": 189
      }
    ],
    "shippingAddress": "42 Elm St, Austin, TX 78701",
    "productType": "physical"
  },
  "evidence": {
    "trackingNumber": "1Z999AA10123456784",
    "carrier": "UPS",
    "deliveryConfirmation": "Delivered 2026-10-02 14:12, left at front door, 42 Elm St Austin TX",
    "deliveryDate": "2026-10-02",
    "avsResult": "Y (full match)",
    "cvvResult": "M (match)",
    "customerCommunications": "2026-10-03 customer email: 'Got the shoes, they run a bit small.'"
  }
}

Result

The response is { "data": ..., "_provenance": ... }. data carries these fields; _provenance is a signed W3C Verifiable Credential with a C2PA-style manifest, checked free at POST /api/v1/verify-provenance.

Field	Type	Required	Description
`reason_code_name`	string	no
`winProbability`	integer	no	0-100 probability of winning representment with the supplied evidence.
`win_rationale`	string	no
`evidence_map`	array<object>	no
`missingEvidence`	array<object>	no
`weaknesses`	array<string>	no
`rebuttal`	object	no
`recommend_accept`	boolean	no	True when fighting is unlikely to succeed and accepting the dispute is cheaper.
`rubric`	object	no
`ce3`	object	no
`invalidDispute`	object	no
`headline`	object	no	Decision first: the verdict, the dollars at stake, confidence and the exact next step.
`expectedRecoveryUsd`	one of	no	Order amount x winProbability, for USD orders.
`netExpectedValueUsd`	one of	no	expectedRecoveryUsd minus disputeFeeUsd when given.
`responseDeadline`	object	no	date, daysRemaining and status (open, due_today, past, not_provided), from the deadline you supplied.
`customerAcknowledgments`	array<string>	no	Exact sentences from the customer's messages acknowledging receipt or use of the order; led with in the rebuttal.
`submission`	object	no	Processor-ready package: controllingRule, summaryText (4,000 characters max), rebuttalBody, fields in dispute-form order marked PROVIDED or NOT AVAILABLE, attachmentsChecklist and placeholdersToFill.
`caveat`	string	no
`decision`	object	no

Pay and connect

Available through: x402 (USDC on Base), MCP, RapidAPI, Apify.

Machine-readable

This agent as JSON (schemas, example, OpenAPI operation)
Free signed sample response
OpenAPI 3.1 · Catalog · Index of every agent