MyEZToll
POST/api/partner/v1/disputes

Report a dispute

Report a dispute opened on one of your charges.

The charge must be reported first, or sent inline as charge. We collect the evidence in the background (202) and send dispute.evidence_ready or dispute.evidence_failed. Sending the same stripeDisputeId again updates status and deadline. An ACH-return reason comes back at once as not_applicable with recommendation: accept.

Authorization

X-Api-Key header

Send your partner key on every request. An owner key acts for its one owner; an integration token also needs the owner's id in the X-Owner-Id header.

Body

application/json
stripeDisputeIdstringrequired

Your Stripe dispute id (du_…).

chargeIdstring

The disputed charge

chargeobject
reasonstringrequired

Stripe's reason: fraudulent, product_not_received, duplicate, …

networkReasonCodestring
amountnumber

Defaults to the charge amount.

currencystring
statusstring

A Stripe dispute status; default needs_response.

evidenceDueBystring <date-time>

Response

200 · application/json
successbooleanrequired
dataobject
idstring
stripeDisputeIdstring
chargeIdstring
reasonstring
networkReasonCodestringnullable
amountnumber
currencystring
statusstring

Stripe vocabulary.

evidenceDueBystring <date-time>nullable
evidenceStatusstring
Allowed values:collectingreadyfailednot_applicable
recommendationstringnullable
Allowed values:contestacceptnull
recommendationReasonstringnullable
Allowed values:genuine_duplicatebank_instrument_reasonnull
evidenceobject

Stripe evidence fields by Stripe's own names (product_description, customer_name, service_date, access_activity_log, uncategorized_text, duplicate_charge_explanation, …). Text fields are strings; file fields (receipt, service_documentation, customer_signature, customer_communication, uncategorized_file, duplicate_charge_documentation) are { "fileId": "…" }.

filesDisputeFile[]
warningsstring[]
submittedAtUtcstring <date-time>nullable
createdAtUtcstring <date-time>
updatedAtUtcstring <date-time>
errorstringnullable

Status codes

200Updated.
202Recorded; evidence is being collected.
400Validation error.
401Missing, unknown or revoked API key.
409This dispute id is already registered (ours, or another partner's).
422The charge was never reported — POST /charges first, or send it inline.