Services Businesses Need a Different Kind of Fulfilment Record

There is no tracking number on a haircut. The records that win services chargebacks are operational, not logistical, and most merchants do not capture them.

A services business defending a chargeback has none of the artifacts the dispute process was designed around. There is no tracking number on a haircut. The shipping label that wins a 13.1 case for a goods merchant does not exist for the contractor finishing an installation, the consultant billing for a delivered hour, or the studio that ran the photoshoot. The issuer's compelling-evidence framework still applies; the records it asks for have to come from somewhere else.

The artifacts that win services disputes are operational rather than logistical: signed work orders confirming scope and price; dated photographs of completed work, taken on the merchant's phone and timestamped automatically; calendar invites accepted from the cardholder's email address, which prove the cardholder agreed to a specific date and time; communication trails (email, SMS, in-app) from before the service date confirming the customer expected the service to happen. Most services merchants capture none of these, because the order-management software they use was built for shipping goods and has no native concept of an engagement record.

Pick a place to store these artifacts (a shared drive, a CRM custom field, a project board), train the team to file them against the customer record at the time of the engagement, and decide which artifacts are mandatory before invoicing. The work is small, and the win-rate impact on a typical services portfolio is the difference between losing most chargebacks and winning most of them.