Delivery Proof and Compelling Evidence: Building the Representment File

Compelling evidence is the record set that answers the cardholder's claim; delivery proof is its core. Keep tracking with a signature for parcels, access and download logs for digital goods, attendance records and deliverables for services, and the consent and cancellation trail for subscriptions. Capture every record when the event happens, keyed to the order. Submit it inside the acquirer's window, in the order the dispute portal lays out.

Compelling evidence is the set of records a merchant submits in representment to show that the cardholder authorized the transaction and received what was bought. Delivery proof is its core, and its form follows the fulfilment: a carrier record with a signature for physical goods, access and download logs for digital goods, attendance records and delivered work for services, and the consent trail for recurring billing. The file must exist before the dispute, export in minutes and reach the acquirer's dispute portal in the order it expects, inside a window measured in days.

What compelling evidence means in a representment

A chargeback arrives from the issuer with a reason code that names the cardholder's claim: not authorized, not received, not as described, or a recurring charge that continued after cancellation. Representment, also called second presentment, is the merchant's answer, sent through the acquirer to the issuer, where an analyst reads it against that code. Evidence that does not address the claim is not weighed. A delivery signature answers "not received"; it does not answer "not as described". A signed contract answers neither, and when the claim is that the card was stolen, the question becomes who signed it.

The card networks use the term compelling evidence for the records that can overturn a claim, and their rules for card-not-present fraud disputes name the data elements that carry weight: a device or IP address, an account login, a delivery address, and earlier undisputed transactions from the same cardholder that share those elements. The list changes with each rule release, so the acquirer's dispute guide is the reference. The friendly fraud versus true fraud guide covers which claims are worth contesting at all. Three principles hold across every reason code; the table gives the core delivery record per fulfilment type.

• Match the claim. One reason code, one theory of the case, the contradicting records first.
• Tie the order to a person. Name, billing address, email, device and delivery address on the order should point to the same cardholder.
• Show what was disclosed. Price, terms, refund policy and any renewal, as the buyer saw them at checkout, with a timestamp.

Physical goods: tracking, signature and the address on the order

For a parcel the core record is the carrier's tracking history showing a delivered status at the address the buyer gave at checkout. The delivery address must match the order, and ideally the billing address the issuer verified; a parcel delivered elsewhere supports the cardholder's claim. A signature or a proof-of-delivery photo names who received it, which matters on higher tickets. The shipment date must also sit inside the window promised at checkout; a late shipment turns a "not received" dispute into one about your published terms. Keep the packing slip and the order confirmation with the tracking record, so parcel, item and payment form one file. For "not as described" claims, keep the product page as it appeared on the sale date, its images and specification, and the buyer's messages about the item. Archive each version of a listing with dates: a dispute months later is answered with the page the buyer saw.

Digital goods and services: access logs, attendance and delivered work

A download has no parcel, so the proof is the log: the timestamp at which the file was fetched or the content opened, the account that fetched it, and the IP address and device, matched against the purchase. Licence activation, login history and the delivery email's open and click records add weight. The merchant account guide for digital downloads lists that stack; the rule here is that the log must be written at the moment of delivery, because it cannot be rebuilt afterwards.

Services are the fulfilment type merchants document least well, because delivery is a person's time; coaching, consulting and agency work are answered with attendance and deliverables. Attendance means a booking confirmation, a calendar acceptance, the meeting platform's join and leave record, and session notes sent afterwards. Deliverables means the files, reports or access handed over, each with its sending record and the client's acknowledgement. Behind both sits the signed scope: what was sold, for how much, over what period, and what happens on cancellation. A client who attended four of six sessions and disputes the full amount is answered with four attendance records and the scope that priced the programme as a whole.

Recurring billing: the consent record and the cancellation trail

A recurring charge is disputed on two claims: the cardholder did not agree to it, or cancelled and was billed anyway. Consent proof comes first. Keep the checkout page as it was on the day of the first charge, with price, billing frequency, trial length and the date of the first full charge shown before the payment button; the checkbox or click that accepted the terms, with its timestamp and the version of the terms; and the confirmation email that restated them. For a converting trial, keep the reminder sent before the first full charge. Then the cancellation trail: every request logged with date and channel, every cancellation with the date billing stopped. The absence of a request in a searchable log is evidence, provided the cancellation path is visible on the site and in the account. Usage after a renewal shows the service was consumed after the disputed charge. Acquirers underwrite subscription billing on these records; the free trial and continuity billing guide covers what they require before the first charge.

How to store the file: capture at the sale, keep it exportable

Every record above is created at the moment of an event: checkout, shipment, download, session, renewal. None can be produced later from memory, and a reconstructed document is weaker than a system log. Storage is a design decision made before the first sale, not a task after the first dispute.

1. Key everything to the order. Order number, gateway transaction identifier, descriptor and last four digits of the card, so a dispute notice matches its file in one search.
2. Write logs where events happen. Checkout, shipping, delivery, licensing, meeting and support systems each keep a timestamped, exportable record that a listing or price change does not overwrite.
3. Archive the pages the buyer saw. Product pages, checkout, terms and refund policy, versioned by date.
4. Keep it for the whole exposure. Issuers can raise a dispute months after a sale, and later still on a recurring series; keep the file as long as the last charge can be disputed. How long the personal data inside it may be retained depends on privacy law in your markets, and a professional decides that policy.
5. Restrict and back up. Evidence is personal data. Limit who can read it, keep a backup, and test that an order's full file exports as one document in minutes.

Producing it fast, in the order the dispute portal expects

The acquirer's dispute portal notifies you of each chargeback with a response deadline counted in days from the notice. Missing it forfeits the case: the claim stands and the debit is final. Portals ask for evidence in a specific order because the acquirer forwards it through the network in categorised fields, and the issuer's analyst works through a checklist for the reason code. Respect the format and size limits, label each attachment, and never refund a transaction that already carries a chargeback: the dispute continues and the sale can be lost twice. The chargebacks for high-risk merchants guide on this blog lists the generic package; the portal-ordered file reads as follows.

1. A one-page summary: reason code, transaction, claim, and the facts that contradict it, in plain sentences.
2. The transaction record: order, amount, date, descriptor, and the authorization results (address verification, card security code, 3-D Secure where used).
3. The delivery proof for the fulfilment type, from the table above.
4. The disclosure: checkout and terms as shown, with the acceptance timestamp, and the refund or cancellation policy.
5. The cardholder communication: the support thread and any refund or replacement offered before the dispute.
6. The history: earlier undisputed transactions from the same account, device or address, where network rules allow.

Where the IBO package sits in a dispute

IBOCore does not sell chargeback management and files no representment on your behalf. The package supplies the structure a dispute lands on: a US LLC or C-Corp incorporated in the director's home state with its EIN, a business bank account at Bluebanc or Relay in the company's name, and a director, the IBO (Independent Business Operator), qualified in-house with a credit score of 650 or more and available for verification calls and acquirer queries. A dispute spike brings a risk review and the acquirer may call that director; the portal, the evidence and the responses stay with you. The IBO package costs $999 setup, then $2,999 per month from 30 days after delivery, whatever the vertical or the billing model. Ongoing billing starts 30 days after delivery. The optional document template pack ($499 one-time) includes refund policy and terms of service templates; what goes into them is your decision and, where the law is involved, a professional's.

Questions merchants ask

Is a tracking number enough for a "goods not received" dispute?

A tracking number alone is a reference; what the issuer weighs is the tracking history showing a delivered status at the address on the order, on a date inside the window you promised. Add the order confirmation with that address, the address verification result and, on higher tickets, the signature or delivery photo. If the parcel went elsewhere, or the carrier shows "delivered" with no location, the record supports the buyer, and a refund before the dispute posts is usually cheaper.

What do I do when I have no delivery proof for a disputed order?

Accept the chargeback rather than send a weak file, and fix the gap. A response that does not address the claim changes nothing, and the acquirer may charge a fee for the representment itself. Then find which system failed to write the record: shipment without tracking, download without a log, session without an attendance record, checkout without a consent timestamp. Change it before the next sale. The chargebacks for high-risk merchants guide on this blog covers the upstream fixes.

How long should I keep evidence after a sale?

At least as long as the last charge in the series can be disputed: months after delivery for a one-off sale, months after the final renewal for a subscription. Retention for dispute purposes is a business decision; retention of the personal data inside the file follows the privacy policy a professional sets for your markets. Store it so that it can be deleted per order once the exposure has passed, and test the export before you need it.

Compliance touchpoints that survive audit

Clean setups disclose beneficial ownership, file BOI, use genuine IDs, and keep the IBO informed of website and descriptor changes. Processors re-scan for prohibited products, undisclosed aggregation, and transaction laundering. Violations land on MATCH and kill future MID applications.

• AML / CDD: customer due diligence on the merchant entity.
• PEP screening: politically exposed persons get enhanced review.
• OFAC / SDN: sanctions lists checked on owners and signers.
• Website compliance: refund policy, terms, pricing visible before checkout.

Compliance shortcuts that trigger MATCH

Fake guarantors, borrowed SSNs, cloaked websites, and third-party processing through your MID are the fastest paths to MATCH listings. Recovery requires legal work and years of delay. Disclose, document, and keep the IBO in the loop.

FAQ: quick answers

How fast can I get an IBO package on IBOCore?

Available inventory ships the same day after payment. You receive Articles, EIN letter, registered agent details, bank onboarding pack and signer contact through your merchant dashboard. Processor onboarding typically follows over the next one to two weeks.

Where can I look up payment-processing jargon?

Use the Resources glossary on IBOCore (/resources) for 580+ definitions: MID, chargeback ratio, MATCH, rolling reserve, MCC, RDR, KYB and high-risk vertical vocabulary.