Submit Evidence

Overview

The SubmitEvidence RPC uploads supporting documentation to contest a chargeback dispute. This evidence is presented to the issuing bank during the dispute resolution process to prove the transaction was valid.

Business Use Case: When a customer disputes a charge claiming they didn't receive the product, didn't authorize the transaction, or the product was defective, you need to provide proof to defend against the chargeback. This RPC uploads delivery confirmations, receipts, customer communication, and other supporting documents.

Purpose

Why submit evidence for disputes?

Scenario
Evidence Type
Expected Outcome

Product not received

Shipping confirmation, tracking records, delivery signature

Prove delivery occurred

Product not as described

Product specifications, photos, customer communication

Show product matched description

Transaction not authorized

IP logs, device fingerprints, 3DS authentication data

Prove customer authorized purchase

Subscription cancellation

Recurring transaction agreement, cancellation policy, usage logs

Show service was provided or properly disclosed

Duplicate charge

Order details, refund records, transaction timestamps

Clarify distinct transactions

Key outcomes:

  • Evidence attached to dispute record

  • Evidence IDs returned for tracking

  • Status updated to reflect submission

  • Bank reviews evidence during adjudication

Request Fields

Field
Type
Required
Description

merchant_dispute_id

string

Yes

Your unique dispute reference

connector_transaction_id

string

No

Original transaction ID

dispute_id

string

Yes

Connector's dispute identifier

service_date

int64

No

Unix timestamp when service was provided

shipping_date

int64

No

Unix timestamp when product was shipped

evidence_documents

EvidenceDocument[]

No

Array of evidence documents

EvidenceDocument Fields

Field
Type
Required
Description

evidence_type

EvidenceType

Yes

Type of evidence. Values: GOODS_SERVICES_RECEIVED, GOODS_SERVICES_NOT_RECEIVED, GOODS_SERVICES_NOT_AS_DESCRIBED, PROOF_OF_DELIVERY, RECEIPT, REFUND_POLICY, SERVICE_DOCUMENTATION, SHIPPING_DOCUMENTATION, INVOICE_SHOWING_DISTINCT_TRANSACTIONS, RECURRING_TRANSACTION_AGREEMENT, UNCATEGORIZED_FILE

file_content

bytes

No

Binary content of the evidence file

file_mime_type

string

No

MIME type (e.g., "application/pdf", "image/png")

provider_file_id

string

No

External file storage identifier

Response Fields

Field
Type
Description

dispute_id

string

Connector's dispute identifier

submitted_evidence_ids

string[]

IDs of successfully submitted evidence items

dispute_status

DisputeStatus

Current status: OPENED, EXPIRED, ACCEPTED, CHALLENGED, WON, LOST

connector_status_code

string

Connector-specific status code

error

ErrorInfo

Error details if submission failed

status_code

uint32

HTTP-style status code

response_headers

map<string,string>

Connector-specific response headers

merchant_dispute_id

string

Your dispute reference (echoed back)

raw_connector_request

SecretString

Raw API request sent to connector (debugging)

Example

Request (grpcurl)

Response

Next Steps

  • Defend - Submit formal defense with reason code

  • Get - Check dispute status after evidence submission

  • Accept - Concede dispute if evidence is insufficient

Last updated

Was this helpful?