Note: This is something I think should exist and I’m writing about it to flesh out what the problems might be and why no one’s built it. If you’

April 2024: Receipts API as a Service - Kunle.app

submited by

Style Pass

2024-05-05 18:00:05

Note: This is something I think should exist and I’m writing about it to flesh out what the problems might be and why no one’s built it. If you’re either a) working on it or b) are deeply knowledgeable about it and know something I’m wrong about, please hit reply or leave a comment.

A problem whose time has come is an easy way to programmatically retrieve itemized receipt data, that doesn’t require you to be a closed loop network [1]. Here’s why.

Across a bunch of industries and workflows, a lot of human bandwidth is spent discerning the purpose or nature of a transaction, and then accurately categorizing that transaction. In a lot of cases this is accompanied by a lot of dead-weight loss. Some examples:

Consumers often see a purchase on a credit or debit card, don’t recognize it, and file a dispute. With itemized receipts in their banking app, they’re literally less likely to file it. The actual cost of a dispute is immense. It includes

Fees a bank pays to process a dispute to their processor can be $25 - $50 per dispute interaction regardless of the size of the transaction (and a dispute can have an infinite number of interactions, but from what I have seen, 3 interactions per dispute is a reasonable average)