Reference · built on requestOperator by FibricFinance & billing

Chargeback Evidence

Order, shipment, and support records assembled into a response to each card dispute, with the submission proposed for approval.

Request accessPricing ↗

About

A card dispute arrives with a reason code and a deadline. The records that answer it sit in four systems: the processor that holds the dispute, the store that took the order, the carrier that delivered it, and the help desk that talked to the customer. This operator reads all four when a dispute opens and builds the response from what it finds.

For each dispute it proposes one evidence bundle: the fields the processor accepts, the files behind them, and a note on what is missing. Where the records do not support a challenge, it proposes accepting the dispute instead. You approve the submission. It is sent once, and the receipt records what was sent and when.

This is a reference listing. It documents what Fibric would read from Chargeback Evidence and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • New disputes and inquiries from Stripe (charge.dispute.created), with reason, status, and evidence_details.due_by
  • Adyen NOTIFICATION_OF_CHARGEBACK and REQUEST_FOR_INFORMATION webhooks, and the defense reasons Adyen lists for each dispute
  • Square disputes with their due_at deadline, and PayPal disputes from the Customer Disputes API
  • The disputed order in Shopify, Magento, or BigCommerce: line items, billing and shipping address, and the customer's order history
  • Shipments for the order in ShipStation, with carrierCode, serviceCode, shipDate, and trackingNumber, and the carrier's delivery scan
  • Support conversations with the customer in Kustomer, Zendesk, or Gorgias around the order date and after delivery
  • Evidence already submitted on the dispute, which it never overwrites

Proposed actions

  • Target capability: propose a Stripe evidence bundle: shipping_tracking_number, shipping_carrier, shipping_date, customer_communication, receipt, and uncategorized_text, with each file attached
  • Target capability: propose an Adyen defense with a defenseReasonCode and the documents that reason requires, uploaded before defendDispute
  • Target capability: propose Square evidence as TRACKING_NUMBER, PROOF_OF_DELIVERY_DOCUMENTATION, RECEIPT, and CUSTOMER_COMMUNICATION items, then one SubmitEvidence
  • Target capability: propose accepting the dispute where the order was refunded, never shipped, or has no delivery scan
  • Target capability: propose a note on the order and the support conversation recording the dispute, its deadline, and the outcome

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Answer a product-not-received dispute from the tracking record

    A Stripe dispute with reason product_not_received pulls the ShipStation shipment, the FedEx delivery scan, and the Shopify order into one bundle. You approve; the evidence is submitted once.

    With Stripe, ShipStation, FedEx, Shopify

  • Defend an Adyen chargeback with the documents Adyen asks for

    Adyen lists the defense reasons and required document types for each chargeback. The operator fills them from Magento and UPS records and proposes the defense for a finance lead to approve.

    With Adyen, Magento, UPS

  • Accept what cannot be won

    Where the Gorgias thread shows a refund was promised, or no shipment exists, it proposes accepting the Square dispute instead of challenging it.

    With Square, Gorgias

  • Keep the support record straight

    Each dispute and its outcome is noted on the Kustomer conversation and the BigCommerce order, so an agent sees it before offering a second refund.

    With Kustomer, BigCommerce

Requirements

  • A payment processor connector that exposes disputes and evidence submission: Stripe, Adyen, Square, or PayPal
  • A commerce connector for the order: Shopify, Magento, BigCommerce, or WooCommerce
  • A shipping connector with tracking numbers and delivery events: ShipStation, UPS, FedEx, or AfterShip
  • A help desk connector for customer conversations: Kustomer, Zendesk, or Gorgias
  • A rule for when to accept rather than challenge, agreed before the first dispute
Authentication
It has no processor login of its own. Disputes are read and answered through the payment, commerce, shipping, and help desk connectors you attach, with the scopes you grant each.

Limits

  • Stripe forwards a response to the issuer once. After approval nothing can be added, so the bundle is complete or it is not proposed.
  • Stripe caps text evidence at a combined 150,000 characters; Adyen caps a PDF at 2 MB. Larger bundles are trimmed and the trim is shown.
  • It reads the carrier's delivery scan. Where no scan exists, it says so rather than asserting delivery.
  • The issuer decides the outcome. The operator records won or lost from the processor; it does not predict it.

Access and pricing

Reference listing. Fibric builds the operator under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.

Request Chargeback Evidence ↗

Questions and answers

What do I approve before a response goes to the processor?
One submission per dispute. You see the reason code, the deadline, each evidence field with its source record, and the files attached. You can edit text, drop a file, or switch the proposal to accept. Nothing reaches the processor until you approve.
What record is left after submission?
A receipt per dispute: the fields and files sent, who approved, when, and the processor's outcome once it arrives. The same is noted on the order and the support conversation.
Does it ever submit or accept a dispute on its own?
No. Every submission and every acceptance waits for approval. Once approved it is sent once. If the processor reports the response already submitted, it stops and shows you rather than trying again.
Ask about Chargeback Evidence

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This operator is developed, published, and supported by Fibric. Third-party names and logos identify the systems an integration connects to; they are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy