Digital Goods Disputes Turn on Access Logs, Not on Delivery

The issuer's question is not whether the digital goods were delivered. It is whether the cardholder used them after paying.

A merchant selling digital goods faces a different evidence problem from one selling physical goods, and most do not realise it until chargebacks start losing. When the deliverable is a download, a subscription login, or a license key, there is no carrier to confirm receipt and no signed manifest to point at. The issuer's question therefore shifts. They are not asking whether the goods reached an address; they are asking whether the cardholder used the goods after paying for them.

Most digital-goods merchants answer the wrong question. They supply the purchase confirmation email, the order timestamp, and a copy of the receipt, all of which the issuer has already seen, since the issuer's own systems generated the authorisation record. The supplied evidence proves the transaction occurred. The issuer is asking whether the cardholder consumed what they bought.

The records that actually win digital-goods cases are the post-purchase signal: the time-stamped first login after the transaction, the IP address and device fingerprint at first use, the file download log with timestamp and originating IP, the licence key activation event with the machine ID it ran on. Visa's compelling-evidence framework for digital goods explicitly requires two of these alongside the purchase record. Most digital merchants capture none of them. Configuring a usage-event pipeline that writes against the order at first access takes a day of engineering work and changes the win rate on digital-goods chargebacks materially.